Privacy Policy
Last updated 6 August 2026
FaceData is operated by Digital Experience Corporation ("we", "us", "our").
This policy explains what personal data FaceData collects, why, who else receives it, and what you can do about it. Digital Experience Corporation is the data controller. It covers the FaceData website and application.
FaceData involves biometric data — face images used to confirm that two faces belong to the same person. That is a sensitive category of personal data, and the sections below set out exactly how it is handled.
1. What we collect
Account data
Your name, email address, a cryptographic hash of your password (never the password itself), and — if you enable two-factor authentication — an encrypted authenticator secret and encrypted recovery codes. We also record timestamps such as when you confirmed your email address and when an account was deactivated.
Identity and biometric data
When you verify your identity, you are handed off to our verification provider's hosted flow and submit your identity document, a selfie, and a liveness capture directly to them. We do not receive or store your identity documents or the selfie you gave them. What we store is the outcome of that check — whether verification passed, failed, or is still pending.
Separately, you upload a profile photo to FaceData. This photo is biometric data, not a decorative avatar: face comparison works by matching a live face capture against it. We also store the pass/fail outcome and timestamp of each comparison attempt, but not the live captures themselves.
Profile and usage data
Your public display name, profile address, whether your profile is listed publicly, any social or website links you add to your profile, the bio you write about yourself (reviewed by us before it appears on your profile page), the verification codes you generate or enter and their outcomes, and your credit balance and transaction history. If you save a card for faster checkout, we store its brand and last four digits and a reuse reference issued by the billing provider — never the card number itself.
Technical data
Your IP address and browser user-agent, kept for security and abuse prevention, plus the cookies described below. These are not only in our server logs: we record the address and browser your last successful face comparison came from, and those of every verification code you enter. That lets us skip asking you to re-verify moments after you already did, and leaves a record of when we made that decision. Error diagnostics and aggregate analytics may also be collected in our production environment — see the providers table.
2. Why we process it
- To provide the service — running verifications, managing your account and credits. Necessary for performance of our contract with you.
- Biometric processing — carried out on the basis of your explicit consent, given when you verify your identity and use verification. You may withdraw it (see "Your rights"), which ends your ability to be verified.
- Security, fraud and abuse prevention — rate limiting, logging, investigating misuse. Our legitimate interest in keeping the service safe.
- Legal and dispute-resolution records — retaining evidence of verifications and transactions. Legal obligation and legitimate interest.
3. Who else receives your data
We use the third-party providers below. The status column reflects what is actually in use today, so you can tell a live provider from one we have selected for a feature still being built.
| Provider | Purpose | Data involved | Status |
|---|---|---|---|
| VerifyMy (VERIFYMY LIMITED) | Identity verification | Identity document, selfie, liveness capture, and your account identifier | In use |
| VerifyMy | Face comparison at code entry (our "liveness check") | A live face capture, compared by them against the identity they already hold for you | In use |
| Segpay, Epoch | Payment processing | Billing details and payment-instrument data, held by the biller. We keep only a saved card's brand, last four digits and a biller-issued reuse reference | In use |
| Bugsnag | Error tracking | Error diagnostics, which may include IP address and account identifier | Planned; production and staging only |
| Fathom Analytics | Aggregate, cookie-less analytics | Page views and aggregate custom events. No cookies and no personal identifiers | Planned; production only |
| Mailgun | Transactional email | Your email address and message contents | In use |
| Hosting provider | Running the application and its database | All data described in this policy, at rest | Planned; provider not yet selected |
We do not sell your personal data, and we do not share it for advertising. We may disclose data where legally required, or to protect our rights or the safety of our users.
4. Cookies and local storage
We use only what the site needs to function. We do not use advertising or tracking cookies, and our analytics provider (once enabled) is cookie-less by design.
| Name | Type | Purpose | Essential |
|---|---|---|---|
| facedata_session | Cookie (expires with your session) | Keeps you signed in | Yes |
| XSRF-TOKEN | Cookie (expires with your session) | Protects form submissions against cross-site request forgery | Yes |
| remember_web_* | Cookie (persistent) | Keeps you signed in between visits — only set if you choose "remember me" | Set only at your choice |
| coupon_code | Cookie (7 days) | Remembers a coupon code you arrived with, so it still applies when you register or buy | Functional |
| referral_code | Cookie (7 days) | Remembers the campaign link you arrived through, so the free credits it offers are applied when you register | Functional |
| invite_attribution | Cookie (30 days) | Remembers whose invite link or invitation email you arrived through, so the signup can be credited to them | Functional |
| facedata.cookie-notice-dismissed | Browser local storage | Remembers that you dismissed our cookie notice | Yes |
| facedata.referral-welcome-dismissed.* | Browser local storage | Remembers that you dismissed the welcome message a campaign link showed you (one entry per campaign) | Yes |
5. Retention and deletion
Deactivating your account changes nothing about your data — it stays as it is, and you can reactivate whenever you like.
Deleting your account is not an immediate erasure, and we want to be plain about that. Your account is closed, you can no longer sign in, and your email address is replaced with a non-deliverable placeholder so the original address is free to use again. But the underlying records — your profile, verification codes, comparison attempts and credit transactions — are retained for support, dispute-resolution and audit purposes. We do not currently operate an automatic purge schedule, so we do not promise a fixed retention period.
If you want your data actually erased rather than closed, contact us and we will handle it manually, balancing your request against records we are required to keep.
6. Your rights
Depending on where you live, you may have the right to access the data we hold about you, correct it, have it deleted, receive a copy in a portable form, object to or restrict certain processing, and withdraw consent for biometric processing. You also have the right not to be discriminated against for exercising these rights.
There is no self-service export or erasure tool — these requests are handled manually. Contact us and we will verify your identity before acting on a request. Withdrawing biometric consent ends your ability to be verified through FaceData, since verification cannot work without it. If you are in the EU or UK you may also complain to your local data protection authority.
7. Security
Passwords are stored as hashes, two-factor secrets and recovery codes are encrypted at rest, and traffic is encrypted in transit. Administrative access is restricted by role and requires two-factor authentication. No system is perfectly secure, and we cannot guarantee absolute security.
8. International transfers
Our providers may process data in countries other than your own. Where required, transfers rely on appropriate safeguards such as standard contractual clauses.
9. Children
FaceData is strictly for adults aged 18 and over. We do not knowingly collect data from anyone under 18. If you believe a minor has an account, contact us and we will remove it.
10. Changes to this policy
We will update this policy as the service changes — in particular as the providers listed above move from planned to live. The "last updated" date reflects the current version.
11. Contact
For privacy questions or to exercise any of the rights above, contact Digital Experience Corporation through the contact details published on our site. Our Terms of Service govern your use of FaceData.