Trust & transparency

Plain answers about your data.

OMGlens does not collect or store your scan content in our backend. Extracted information stays in our mobile app, in your app (SDK), or in destinations you configure—such as Google Sheets or your own HTTPS API. This page explains what that means in practice—no vague promises, no compliance badges we have not earned.

Transparency at a glance

OMGlens is built around data sovereignty: we are not a cloud guest warehouse. The table below is the model we ship toward.

Where	What lives there	OMGlens backend guest DB?
OMGlens mobile app	Saved scans, photos, exports on your device	No guest archive
Your app (SDK)	Structured fields in your product	No guest archive
Google Sheets (you connect)	Rows in your Google account	Not stored by us
Your HTTPS API (you configure)	JSON payloads on your servers	Not stored by us
OMGlens backend (licensing)	Account, plan, scan counts. With Data Encryption, a sealed envelope — not a readable name or document number.	No readable guest archive

What we do not do

Build a searchable library of your ID photos or extracted guest profiles on our servers.
Sell, rent, or broker scan content to third parties for ads or unrelated AI training.
Offer a “guest list in the cloud” product feature for your end-customer PII.

What our backend is for

Licensing — validate plans, features, and device limits.
Metering — count successful scans for billing and quotas.
Support signals — non-content metadata such as timing, document type, success or error codes, and a correlation reference—not names and addresses in an ops CRM.
Data Encryption — an optional add-on stores a sealed envelope for that scan. Opening it takes the phone’s key. See the split.

Extraction — honest & transparent

Document intelligence has to run somewhere in the chain so your app or SDK can show structured fields. That work is tied to your license and your session, and results are returned to your environment (mobile app, your product, Sheet, or your API).

We do not treat that pipeline as permission to hoard what you scan. There is no OMGlens backend database meant to hold your guest roster alongside the extraction product. If you need a deeper technical or contractual description (for example DPAs or security questionnaires), contact sales@omglens.com.

Integrations (Sheets & your API)

Google Sheets — The app asks for spreadsheet permission and writes rows to your Google account via Google’s APIs. OMGlens does not mirror that sheet into our backend.
Your HTTPS endpoint — The app POSTs JSON to a URL you provide. Payloads are structured fields (not a bundled image archive from our servers). You operate retention on your side.
Exports — ZIP/CSV/JSON/XML are created on the device; you choose where files go next.

Data sovereignty (core product)

Scan content and extracted guest fields are not stored in an OMGlens backend guest database.
Records live in the OMGlens mobile app on your hardware, in your SDK-integrated app, or in systems you connect.
We do not sell, broker, or build marketing profiles from what you scan.

Licensing & metering

Encrypted connections protect license checks and plan metering—not a guest data warehouse.
Short-lived credentials limit exposure if a device is lost.
Operational logs support billing and support—without storing a cloud copy of full extraction payloads for CRM use.

On-device hygiene

Images are optimized on the phone before network use—less data, faster results.
Hidden photo metadata is stripped in the SDK path where applicable.
Exports and shares remain your responsibility to protect.

AI transparency

Extractions are automated and probabilistic—review before high-stakes decisions.
Confidence scores help you route edge cases to a supervisor.
Model and prompt improvements target accuracy—not silent changes to your compliance posture.

What we are not

Not a regulated KYC, AML, or background check service.
Not a substitute for legal review of ID handling in your jurisdiction.
Not claiming SOC 2, HIPAA, or similar until formally completed and published.

Your responsibilities

Obtain consent and lawful basis for scanning IDs.
Secure devices, Sheet sharing, and webhook endpoints.
Ask us for enterprise security or privacy documentation when you need it.

Trust architecture

Intelligence without a readable guest list

AI processing serves your scan—OCR-compatible output stays where you point it.

Core promise
No guest archive

We do not build a backend database of who you scanned—metering uses non-content signals.
Transparent processing

Intelligence runs to serve your app or SDK; extracted content stays where you configure.
Honest metering

Licensing validates plans and scans—not a pretext to hoard identity images.
Data Encryption
Ciphertext, not a guest list

When the add-on is on we can store a sealed envelope. We still cannot read the name or document number without the phone.

Audit signal

What reviewers wanted to hear

Legal cared about custody, not buzzwords. OMGlens let us point to device + our Sheet—not a vendor vault.

Jamie O. Compliance counsel · Event & venue group SIG-01

Representative voices from teams piloting AI identity capture—names and roles are illustrative.

Mobile app

See custody on your own phone

Download the app for trial—scans stay on-device until you export or sync to systems you control.

App Store & Google Play listings are on the way. Tap below and we’ll send your trial build link (TestFlight or Android APK).

Trial on App Store Trial on Google Play

Questions about this model?

Email hello@omglens.com