Skip to content
IDVERF
Security & compliance

Verification without exposure.

IDVerf is built so that a verification answers one question — does this match? — and nothing more. Here's how we handle data, who can use which checks, and what we ask of you.

No personal data out

Responses, webhooks and the logs you can see in the portal carry signals only. A signal tells you whether the data you sent agrees with authoritative identity data sources — never what those sources hold.

No signal ever contains a stored name, address, phone number, email address or date. This is enforced by automated response-schema tests that run on every release.

The result: IDVerf can't be used as a people-search tool, and a leaked API key can't be used to pull anyone's details.

What a response contains

"identity": {
  "name": "MATCH",
  "dob": "PARTIAL",
  "address": "MATCH",
  "deceased": false,
  "data_fullness": 0.81
}

Enums, booleans and numbers. MATCH, PARTIAL, NO_MATCH, NOT_FOUND, NOT_CHECKED, ERROR.

Purpose & consent on every call

Every verification must state why it is being run and when the end user agreed to it. Both are required fields and are stored with the audit record.

  • Account opening account_opening
  • Account recovery account_recovery
  • Age verification age_verification
  • Fraud prevention fraud_prevention
  • Transaction authorization transaction_authorization

Each account is approved for specific purposes during onboarding. A purpose outside that list is rejected with 403 purpose_not_permitted.

Not a consumer report

IDVerf is not a consumer reporting agency, and its results are not consumer reports under the Fair Credit Reporting Act (FCRA). IDVerf results may not be used, in whole or in part, to determine a person's eligibility for:

  • Credit
  • Employment
  • Housing
  • Insurance

…or for any other purpose covered by the FCRA. The API's purpose field has no such values, and our Terms of Service prohibit these uses.

Vetted access & GLBA

Checks that compare inputs against identity records run under the Gramm-Leach-Bliley Act (GLBA) exceptions for fraud prevention and identity verification, and only for accounts whose business and use case we have reviewed. Every account is granted checks individually, through entitlements.

Entitlement tiers

open

Any verified account

Phone type and status, email validity, postal address validation, IP and device location, all document forensics, and the phone code in Full verification.

vetted

Business use case reviewed at onboarding

Adds identity record matching: name, address and date of birth, deceased indicator, data fullness, residence, phone and email ownership, address type and homeowner match.

credentialed

Enhanced review plus a GLBA permissible purpose

Reserved for future high-sensitivity checks.

Requesting a check you aren't entitled to returns NOT_CHECKED (and isn't billed). Saving a policy that requires one returns 403 entitlement_required. Apply for a higher tier from the portal.

Data retention

We keep the inputs you send only as long as needed, and the results long enough to support your audits and disputes.

Raw inputs

90 days

Encrypted at rest, then purged. Configurable per account all the way down to 0 days.

Results & audit metadata

5 years

Decision, score, signals, purpose and consent record — no raw inputs.

On demand

Instant

DELETE /v1/results/{id}/inputs purges a verification's inputs immediately.

Biometrics

Full verification captures a selfie and photos of an ID on our hosted page. Before anything is captured, the person reads our biometric consent notice and agrees; that agreement is recorded with the session. Photos are encrypted in transit and at rest, and kept only for your image retention setting — 0 to 7 days, default 3 — so your team can review a result in the portal, then deleted automatically. Face measurements are used for the comparison and not stored. Images are not included in API results or webhooks. Read the Biometric Privacy Notice.

Platform security

Keys hashed at rest

Secret API keys are shown once at creation and stored only as hashes. Live (sk_live_) and sandbox (sk_test_) keys are separate.

IP allow-listing

Optionally restrict each API key to your servers' IP addresses. Requests from anywhere else get 403 ip_not_allowed.

TLS 1.2+ only

The API is HTTPS-only with TLS 1.2 or newer. Plain HTTP is never accepted.

Signed webhooks

Every delivery carries an HMAC-SHA256 signature with a timestamp, so you can reject forged or replayed events.

Two-factor authentication

Protect portal accounts with authenticator-app 2FA and review active sessions from your settings.

Encryption at rest

Stored verification inputs are encrypted at the application level, on top of encrypted storage.

Rate limiting

Per-key limits protect your account and our sources from runaway or abusive traffic.

Audit trail

Every verification keeps who ran it, with which key, under which policy version, purpose and consent.

Least privilege

Internal access to production systems is limited to staff who need it, and is logged.

SOC 2

We are working toward a SOC 2 Type I report and are building our controls with that framework in mind. IDVerf is not SOC 2 certified today. If you need security documentation for a vendor review, contact us through the support center.

Your part

  • Get clear consent from the end user and record its time and version.
  • Send a truthful purpose with every request.
  • Keep secret keys on your servers — never in browsers or mobile apps.
  • Verify webhook signatures and reject stale timestamps.
  • Use results only for the permitted purposes in our Terms and Acceptable Use Policy.

Questions about security or compliance?

Our team is happy to help with vendor questionnaires and integration reviews. To report a security issue, please contact us through the support center.