FaceGUID
About

Who runs this, and how to reach us.

FaceGUID gives a human face one permanent identifier, and builds four things on top of it: linked accounts, an encrypted vault, sealed documents, and an API that lets other applications check they are dealing with a real person.

Operator details to be completed before launch. The lines marked [ ] below are the only placeholders on this site. They need the registered legal name, the registered address and the governing jurisdiction of whoever operates FaceGUID. Everything else on this page is a factual description of the running system.
Operator
Legal entity[ registered company name ]
Registered address[ registered address ]
Company number[ company number, if applicable ]
Jurisdiction[ jurisdiction ]
Servicefaceguid.com
General enquirieshello@faceguid.com
Privacy and data rightsprivacy@faceguid.com
Security reportssecurity@faceguid.com
Legallegal@faceguid.com
What FaceGUID will never do

Worth stating explicitly, because a service that asks for a camera and for your accounts should be easy to tell apart from one that is imitating it:

  • We will never ask for a password to another service. Not your email password, not your bank, not your wallet. FaceGUID has no password of its own either.
  • We will never ask for a seed phrase or a private key. The vault can store one if you choose to put it there, encrypted in your browser — but nobody from FaceGUID will ever ask you to type one, and any message that does is not from us.
  • We will never ask for card or payment details on this site.
  • We will never email you a link asking you to re-verify your face. Face checks start from a page you navigated to yourself.
  • We only ever operate on faceguid.com. Check the address bar. Anything on another domain claiming to be FaceGUID is not.
How it is built

The entire service is one Cloudflare Worker: the site, the API and the identity provider. Data lives in Cloudflare D1 and R2. Nothing is fetched from a third-party CDN at runtime — even the face-recognition models are served from this origin, which is why the Content-Security-Policy can forbid outside scripts entirely.

The cryptography is documented in full, including its failure modes, on the security page. If you want to check a claim on this site rather than believe it, that page is written to make that possible.

Reporting something

Security vulnerabilities: security@faceguid.com, details in security.txt. Good-faith research is welcome and will not be met with legal threats.

Abuse of the service, or an application misusing FaceGUID: security@faceguid.com. Data-protection questions: privacy@faceguid.com.