What you can expect, and what we ask.

FaceGUID issues a globally unique identifier bound to a human face, and provides four things built on it: an identity you can link accounts to, an encrypted vault, sealed document storage, and an API that lets other applications verify you are a live human or sign you in. The security model describes precisely how each works.

• One face gets one GUID. Attempting to obtain several by evading the matching — masks, synthetic faces, another person's face — is a breach of these terms.
• Enrol only your own face. Enrolling someone else's, with or without their knowledge, is prohibited and may be unlawful where you are.
• You are responsible for what is done through your identity while you can present the face that opens it.

The keys that open your vault and your sealed documents are derived from your face and exist nowhere else — not in our database, not in a backup, not in an escrow. This is the point of the design and it is also its sharpest edge.

• If you cannot present the face that enrolled — injury, illness, death, or a change beyond what the matching tolerates — the contents cannot be recovered by anyone, including us. We cannot make an exception because we hold nothing that would allow one.
• If you set the optional passphrase and forget it, the same applies.
• Keep independent copies of anything you cannot afford to lose. Do not make FaceGUID the only place a document or a secret exists.

A seal is evidence that a specific file, unchanged, was signed by a specific face at a specific moment. It is not a notarisation, a witnessing, a legal signature, or a statement that the contents are true or that the signer had any right to sign. Whether a seal carries legal weight in your jurisdiction is a question for a lawyer, not for us.

Do not use FaceGUID to:

• Store or seal material that is unlawful to possess.
• Impersonate another person, or present someone else's face to any check.
• Attack the service — automated enrolment, credential stuffing, attempts to extract other users' data, or to circumvent rate limits or the liveness checks.
• Present proofs of human obtained by deceiving a person into performing a check for you.
• Resell, sublicense or misrepresent the service as your own without written agreement.

Good-faith security research is welcome and explicitly not a breach of these terms — see security.txt for how to report.

• Keep your client secret on your server. A secret in a browser bundle or a mobile app is a secret you have published.
• Verify proofs and tokens server-side. A check performed in the browser is performed by code your attacker controls.
• Do not present FaceGUID as more than it is. A proof of human is strong evidence, not certainty, and the security page states the limits plainly.
• Quotas apply per organisation per calendar month. We may suspend a client that is abusing the service, and will tell you why.
• Your users' biometric data is never yours to receive. You get an identifier.

The service is provided as it stands, without a service-level guarantee unless you have a written agreement that says otherwise. We may change or discontinue features. If we ever discontinue the service, we will give notice with enough time to export your documents and vault, because the alternative is destroying things you cannot get back.

Seal certificates are designed to outlive us: verification needs only the certificate, the file and a public key, and no call to this service.

To the fullest extent the law allows, the operator is not liable for indirect or consequential loss, for lost profits, or for data you lose because you could not present your face or forgot your passphrase — the one risk these terms warn about twice. Nothing here limits liability for death or personal injury caused by negligence, for fraud, or for anything else that cannot lawfully be limited.

You can delete your identity at any time from the Accounts page; that ends this agreement and erases what we hold. We may suspend or terminate an account that breaches these terms, and where we do, we will say which term and give you a chance to respond unless the breach makes that unsafe.

These terms are governed by the laws of [ jurisdiction ], and the courts of [ jurisdiction ] have exclusive jurisdiction — see About, where the operator's details are recorded.

Questions about these terms: legal@faceguid.com.