Privacy Policy

Last updated: March 15, 2026

We built this app to help organizations verify identities safely—without compromising your privacy. Below we’ve explained, in plain language, how we handle personal information and what happens to it during a verification session.

1. Overview

Our goal is to confirm who you are, without storing more than we absolutely need.
Most processing happens right on your device, and any data that leaves your browser is either encrypted, redacted, or tied to a specific verification request you’ve agreed to.

2. What We Collect

We only collect the data needed for the verification you’ve been invited to complete.
Before anything starts, we’ll show you exactly what information the requesting organization is asking for.

You may be asked to provide:

• Photos of your ID (front and back)
• A short “liveness” selfie
• Data from your ID barcode (such as name, date of birth, or address)

We don’t collect any unrelated information—no contacts, no messages, no hidden tracking.

3. What Happens on Your Device

• Face recognition and matching happen directly in your browser using your device’s camera.
• No raw images leave your device for face matching — though limited image data may be sent to our servers for OCR and image cleanup (see Section 4).
• Face embeddings (digital face patterns) are used briefly for comparison, then erased immediately—they’re never stored or shared.

4. What We Send to Our Servers

Your browser may make limited API calls to services we run for two purposes:

1. OCR (Optical Character Recognition): Reads text from your ID images so we can extract name, DOB, and other PII fields you were asked to share.
2. Image Cleanup: Enhances clarity or lighting on ID or selfie photos, so face detection and OCR work better.

Those APIs process images temporarily and don’t permanently store them. Logs automatically remove or redact sensitive details.

5. What Gets Shared with the Requesting Company

Only the fields that the requesting company explicitly requested are sent to them.
They receive the results (like “license appears real” or “face matches”) and specific data items (like “name” or “license number”)—nothing more.

All transmissions use secure, encrypted connections (HTTPS).
This service supports end‑to‑end encryption (E2EE) between your browser and the requesting company’s system. When the requesting company provides their own RSA public key, even we cannot read or decrypt the data.

6. What We Store (and What We Don’t)

Data	Stored?	Details
Raw ID or selfie images	❌ No	Processed and discarded immediately. Exceptions: cropped license face photo (paid tier, optional) and manual review images (only with explicit user consent) are stored as PII with full encryption and retention policies.
Face embeddings	❌ No	Used in memory only, then deleted
Verification result summary	✅ Yes	Non-sensitive confirmation data (e.g., “verification passed,” timestamps)
API logs	✅ Yes, redacted	Internal diagnostics only—personal fields are masked or omitted
Requested PII (e.g. name, DOB)	✅ Temporarily	Kept only long enough to send securely to the client and then encrypted or deleted

7. Consent and Control

You’ll always see a consent screen before submitting anything.
Participating is optional—if you stop or exit, no personal data is sent or stored.

If a company asks for data you’re uncomfortable sharing, you can decline.

8. Security Measures

• Strong encryption during all transfers (HTTPS + TLS)
• Role-based access control and data isolation
• Logs with sensitive fields automatically redacted
• Full end‑to‑end encryption for verified data delivery (available now)
• Regular security reviews for OCR and face-processing systems

9. Retention and Deletion

We keep your verification data only as long as necessary to complete the request and deliver results to the requesting company.
Once delivered, data is either securely deleted or encrypted so that only the authorized client can decrypt it.

10. Contact