Entity.ID is built on best-in-class infrastructure to keep your identity, your entities and your records safe at every layer. That means encryption in transit and at rest, sign-in without passwords, wallet keys held in secure hardware and partners whose security is independently audited.
SOC 2 Type 2
Held by our hosting and sign-in providers.
ISO 27001
Held by our hosting, database and identity check providers.
PCI DSS Level 1
Held by Stripe, which handles card payments.
AES-256
Encryption of everything our database and file storage hold.
Your data is encrypted on its way to us and wherever it is stored.
In transit
Every connection to Entity.ID uses HTTPS, and browsers are told to refuse anything else.
At rest
Our database and file storage encrypt everything they hold with AES-256.
Payments
Card details go straight to Stripe. They never reach our servers.
Sign in without a password. You never set one with us, so there is none to forget, reuse or have stolen.
Email codes
Sign in with a one-time code sent to your email.
Passkeys
Add a passkey and sign in with your fingerprint, your face or a security key.
Accounts you already have
Use your Google, GitHub or X account.
Your own wallet
Connect an Ethereum or Solana wallet you already hold. Its key stays with you.
Keys in secure hardware
Wallets we create for you are run by Privy. The key is only ever used inside secure hardware, and Entity.ID never sees it.
Two-step approval
Add an authenticator app or a passkey, and that wallet asks for it before it signs, sends or exports anything.
Agents sign in too
An AI agent connects through your account and has to present its token on every call.
A registry is open by design. The documents that prove who you are stay out of it.
Public by design
An entity record shows its name, its members and their roles, its constitution and its standing. Do not put on a record anything you do not want public.
Verified, not exposed
A record shows that a member has passed an identity check. It never shows the documents behind it.
Passport proofs
Verify with a proof made on your own phone. We receive the proof and the few details it confirms, not a copy of your passport.
Your data, your call
Ask for a copy of what we hold about you, or for your account to be closed, at hello@entity.id.
| Provider | What it does for us | Independent audits |
|---|---|---|
| Vercel | Hosting and file storage | SOC 2 Type 2, ISO 27001 |
| MongoDB Atlas | Database | SOC 2, ISO 27001 |
| DigitalOcean | Servers behind the record gateway | SOC 2 Type 2 |
| Privy | Sign-in and wallets | SOC 2 Type 2 |
| Sumsub, Didit, Socure | Identity checks | ISO 27001 |
| Stripe | Card payments | PCI DSS Level 1, SOC 2 Type 2 |
| Intercom | Support chat | SOC 2 Type 2, ISO 27001 |
| Resend | Email | SOC 2 Type 2 |
Email and site analytics | SOC 2, ISO 27001 | |
| PostHog | Product analytics and error reports | SOC 2 Type 2 |
How the service is watched and kept honest.
Monitored around the clock
Automated monitors check our sites and services, and incidents are posted on our public status page.
Failures are reported
Server errors and failed payments, emails or identity checks are reported to us automatically.
Trusted messages only
Messages from our payment and identity providers are accepted only when they prove where they came from.
Decisions on record
Every identity review made by our staff is recorded with the person who made it and the time.
Short answers. Longer ones at security@entity.id.
Is the infrastructure audited
Yes. Hosting, database, sign-in, identity checks and payments run on providers audited to SOC 2 Type 2, ISO 27001 or PCI DSS Level 1. They are listed above.
Can you fill in a security questionnaire
Yes. Write to security@entity.id and a person replies.
Can a record be deleted
No. Public records are permanent, and corrections are added on top so the history stays visible. A registry that forgets is not a registry.
Do you sell my data
No. Usage data helps us keep the service working and find faults. We do not sell it.
If you find a security problem, tell us before you tell anyone else.
Write to security@entity.id with what you found, how to reproduce it and what you think the impact is. We acknowledge within three business days and keep you informed until it is fixed.
Please do not access, change or delete data that is not yours, and do not run tests that degrade the service for others. We do not run a bug bounty programme. We credit reporters who want to be credited once the fix is live.
In scope: entity.id, app.entity.id, directory.entity.id, our record gateway, our agent server and our contracts. Out of scope: denial of service, spam, social engineering of our staff, physical attacks and faults in our providers' own systems.
security@entity.id reaches the people who can fix it.