Security
We handle biometric data, so it is worth being precise about what we do — and honest about what we have not done yet.
What we do
Encrypted in transit
Everything moves over TLS. HSTS is enforced, so a browser that has seen the site once will not fall back to plain HTTP.
Account isolation in the database
Every table carries row-level security keyed to your account. Isolation is enforced by Postgres itself, not by application code remembering to filter.
Private storage for face images
Enrolled face crops sit in a private bucket. Each image is served through a link that expires after ten minutes — there are no permanent public URLs.
Deletion actually deletes
Removing a face removes its embedding and its stored image. Deleting your account erases the collections, the images, the usage history and the billing details.
No card data on our systems
Checkout and card storage are handled entirely by Dodo Payments, our Merchant of Record. We only ever see the brand and last four digits.
Run history, kept for seven days
What you run through the tools is stored with its result, in private per-account storage, so Recent Runs can show it back to you. It is deleted after seven days, or once fifty newer runs have pushed it out — whichever comes first. Face Store is separate: it keeps what you explicitly enrol, until you delete it.
What we don't have yet
We hold no third-party security certification — not SOC 2, not ISO 27001 — and we have not commissioned an external penetration test. We are a young company and have not been through those processes.
Retention is also not yet configurable. Everyone gets the same seven days of run history, and there is no zero-retention mode that would process an image without storing it at all. If that is a requirement for you, say so — it is on the roadmap and knowing it is needed moves it up.
If your procurement process requires any of this, we would rather you found out on this page than three weeks into a review. Tell us what you need and we will tell you honestly whether and when we can meet it.
Biometric data
Face embeddings and crops are special category data. Our Privacy Policy sets out exactly how they are stored and deleted, and the Terms set out the consent you must have before uploading someone's face. Please read both before you enrol anyone.
Who else touches your data
Four companies, and only one of them ever sees an uploaded image. The subprocessor list names each one, what it receives and where it runs.
Reporting a vulnerability
Email bugs@quantilence.com. We will acknowledge within two working days and keep you updated until it is resolved. We follow coordinated disclosure and will not pursue legal action against anyone researching in good faith who gives us reasonable time to fix an issue before publishing.