Skip to content

Data residency + disaster recovery

This page states where data lives and what recovery AtmanID can and cannot offer today. Provider and region detail is available under NDA through the Trust page.

Where data lives

  • Customer data — the application database, including identities, access, and the audit log — is stored in a single cloud region in the United States.
  • Uploaded files such as tenant logos are stored in the United States and may be cached at the hosting provider’s edge locations worldwide.
  • Application servers run on the hosting provider’s network; requests that need data are served from the database’s region.
  • Sub-processors — the AI provider used by Iris, the embedding provider, email delivery, and error monitoring — process data in the United States. The current list is available on request.

There is no EU, APAC or government-cloud residency option today. Customers with data-localisation requirements cannot use AtmanID without accepting US residency.

Backup and recovery

  • Point-in-time recovery. The database provider keeps continuous backups that allow the database to be restored to any moment within its retention window. This is the main defence against logical errors — for example, a misconfigured bulk change — because a copy from before the error can be restored alongside the live database and the affected data recovered without disturbing other tenants.
  • Where backups live. Backups are held by the same database provider, in the same region as the live database, under the same provider-managed encryption.

If the region fails

AtmanID does not run a standby in a second region. If the database’s region became unavailable, the platform would be unavailable until service was restored there or the database was rebuilt elsewhere. The documentation site, which has no database dependency, would keep serving.

Roadmap

  • A backup copy held outside the database provider, in separate storage, with immutable retention. This is the next step, and closes the gap that a provider-level failure or compromise could affect both the live database and its backups.
  • EU residency, when a customer contracts for it.
  • Regional failover, when a customer contracts for a failover commitment.

What this design does not provide

  • An off-provider backup. Today all backups sit with the database provider (see Roadmap).
  • Regional failover or a published recovery-time commitment for a region-level outage.
  • Data residency outside the United States.
  • Snapshot-consistent exports. Customers can export their data through the API, but exports read the live database, so a long export can include changes made while it ran.
  • Proof of deletion. Erasure requests delete personal data and redact it from the audit log; AtmanID does not provide cryptographic proof of deletion.

Adjacent reading

© AtmanID · Privacy