Legal
Trust Center
In this section
How Authdog protects your data, what encryption it lets you add to your own product, where certification stands, and who to contact.
Last updated: November 12, 2026
Authdog encrypts what it stores for you. It also gives every environment its own key management service (KMS), so you can add end-to-end and application-level encryption to your product without running key infrastructure yourself.
End-to-end encryption enablement
Encrypt data where it is created, and keep it encrypted until an authorized service opens it.
- A public key per environment. Generate an RSA-OAEP-4096 key pair in the console. The public key is returned as PEM when the pair is created, ready to ship to a browser, a mobile app, or another service.
- Encrypted before it leaves the sender. The sender encrypts with that public key (
kmsEncrypt). The payload stays ciphertext in transit and in every queue, log, and database it passes through. - Opened only by an authorized call. Decryption happens server-side through
kmsDecrypt. The private key is wrapped at rest and never leaves Authdog.
One limit, stated plainly: the private key is held by Authdog on your behalf, not by your end users. This protects a payload from everything between the sender and your decrypt call. It is not a zero-knowledge design.
Application-level encryption
Encrypt individual fields and secrets in your application, on top of disk and transport encryption.
- AES-256-GCM keys. Generate keys per environment and choose the default. The raw key is shown once, at creation, for your offline backup. The platform keeps a wrapped copy for server-side use.
- Authenticated encryption. AES-256-GCM detects tampering as well as hiding content. There is no built-in fallback key: an encrypted write is refused when the required key is missing.
- Fast enough for request paths. AES-256-GCM encrypt and decrypt measure well under a millisecond in our published figures. Use RSA keys for hand-off and AES keys for data read on every request.
- Rotation you control. The KMS records each key's rotation state. Rotate first, let re-wrapping finish, then disable the old key.
Keys, secrets, and their access logs are scoped to one environment. A key created in development cannot decrypt production data. See Vault for the full behavior, including what encryption does not cover.
Security posture
Every Authdog environment runs with:
- Its own signing keys and user store. A credential leaked from one environment cannot validate in another. Clients verify tokens with the environment public key (
pk_...) and never see the private key. - Edge validation. Sessions are checked close to the user, against that public key, before a request reaches a central session store.
- Secrets encrypted at rest. Vault entries use AES-256-GCM, and every read of a secret is written to its access log.
- An audit trail. Sign-ins, role changes, and provisioning updates are recorded as events you can read and forward. See Audit logs.
- Signed webhooks. Outbound events carry
X-Authdog-Signature: t=...,v1=..., so receivers can reject forged calls.
Attack protection, session security, and key rotation are covered in Security and Security Guidelines.
Certifications
| Program | Status |
|---|---|
| SOC 2 Type 2 | In progress with Oneleet. Not yet certified. |
| ISO 27001 | In progress. Not yet certified. |
| Penetration testing | Independent testing is planned as part of the certification track. Reports will be shared with customers under NDA when available. |
We do not claim a certification before its report is issued. When a status here changes, the date at the top of this page changes with it.
Vulnerability disclosure
Report security vulnerabilities through the responsible disclosure page. Include the affected endpoints, steps to reproduce, and your contact details. We acknowledge each report, validate it, and agree disclosure timing with you. Safe-harbor rules for testing are on that page.
Data handling
| Topic | What applies |
|---|---|
| Roles | For Customer Data, you are the controller and Authdog is the processor. Authdog LLC, established in the United States, is the controller for website and operations data. See the Data Protection Notice. |
| Location | Processing takes place in the United States and other countries where our infrastructure runs, including a global edge network. See Subprocessors for vendors and transfer safeguards. |
| Residency | Customers with data residency requirements can run a dedicated tenant deployment, including EU placement. Contact support to scope one. |
| DPA | A Data Processing Agreement is available on request. Email [email protected] or open a Security & compliance ticket with your organization name and the environments to cover. |
Availability
- Current uptime and incident history are on status.authdog.com.
- The Enterprise plan includes a 99.99% uptime SLA.
Contact
| For | Go to |
|---|---|
| Security reports | Responsible disclosure |
| Privacy and DPA requests | [email protected] |
| Account or console issues | Contact support |