Trust center
Trust & Security at AtmanID
AtmanID is built so security and compliance fall out of good engineering — not bolted on for procurement. This page is the public source of truth for our certifications, subprocessors, and operational commitments.
Certifications & Attestations
SOC 2 — Not Yet Audited
AtmanID does not yet hold a SOC 2 report or any other third-party attestation, and no audit firm is engaged today. We track our own readiness control by control: by our assessment, 43 of 43 SOC 2 controls are in place.
Evaluating AtmanID now? We'll answer your security questionnaire and walk through the architecture under NDA.Request a security review →
Continuous Compliance Monitoring
The product maps your evidence to 6 frameworks with 84 controls in its Compliance Hub: SOC 2, SOX, ISO 27001, HIPAA, NIST 800-53, PCI-DSS. This is a feature for your programme, not a certification of AtmanID. The hash-chained audit trail makes tampering detectable.
How We Address the Trust Services Categories
Security
Session-based authentication, role-based authorization, and phishing-resistant MFA (WebAuthn/FIDO2 Passkey). Database-layer tenant isolation, edge boundary protection. Continuous monitoring with risk-scored anomaly detection and segregation-of-duties enforcement.
Availability
Auto-scaling application layer + serverless database. 99.9% monthly uptime is our target; no formal SLA is committed yet. Daily backup snapshots; 7-day point-in-time recovery.
Confidentiality
Tenant isolation enforced at the database layer by three independent controls (row-level security, application-level tenant scoping, and connection-level context) — cross-tenant data access is structurally prevented. TLS 1.2+ for all data in transit. AES-256 encryption at rest.
Processing Integrity
Schema-validated input on every state-changing endpoint. Append-only audit log with cryptographic hash chain. Workflow state machines + connector reconciliation + rollback compensation.
The Privacy category is not covered here yet, and we have not designated a DPO. For your own GDPR programme, the product provides personal-data export and erasure and retention settings, and we sign a DPA.
Subprocessors
Third parties that process customer data on AtmanID's behalf. We notify customers of any new subprocessor 30 days before they begin processing data, per your DPA.
| Vendor | Service | Data Shared | Region | Attestations | Tier |
|---|---|---|---|---|---|
| Vercel Inc. | Application hosting + edge runtime + serverless functions | All HTTP requests + transient processing | Global edge, primary US-East / EU-West | SOC 2 Type 2 · ISO 27001 · HIPAA | critical |
| Vercel Blob (Vercel Inc.) | Object storage for tenant logos + uploaded files | Tenant logos; uploaded org assets | US-East | (covered by Vercel SOC 2) | critical |
| Neon Inc. | Serverless Postgres database with role-based privilege separation | All persistent customer data (identity records, audit trail, credential metadata) | AWS US-East-2 + S3 point-in-time recovery | SOC 2 Type 2 · GDPR · HIPAA-eligible | critical |
| GitHub, Inc. (Microsoft) | Source code hosting + GitHub Actions CI/CD | Source code (private); ephemeral env vars during build only | US (primary), EU mirror | SOC 2 Type 2 · ISO 27001 · FedRAMP | critical |
| Cloudflare, Inc. (R2 Object Storage) | Immutable copy of the audit-chain signatures (object lock, 7-year retention) | Tenant id, sequence number, hashes and signatures only — no audit record content, no personal data | Automatic (EU-only on request) | SOC 2 Type 2 · ISO 27001 · ISO 27018 | critical |
| Amazon Web Services, Inc. (AWS KMS) | Key management: the key that wraps the per-record keys of most stored secrets | Wrapped data keys and a label of purpose, tenant id and, for MFA secrets, user id. No secret values or records: encryption runs inside AtmanID | AWS US-East-2 | SOC 2 Type 2 · ISO 27001 | critical |
| Anthropic, PBC | Claude AI inference for Iris and other AI features | Iris: the user's name, email, role and department, the page they are on, their question and earlier turns of the conversation, and the identity and access records the answer reads (people, accounts, entitlements, audit events), truncated to fit, not redacted. Public docs chat: the visitor's question and our documentation | US-West | SOC 2 Type 2 · ISO 27001 | high |
| Voyage AI | Text embeddings: Iris question routing and docs search, and the public docs chat | The text of the user's question as typed (it can name people), with no user, tenant or account ids attached; our public documentation | US | Review pending | high |
| Upstash, Inc. | Redis counters for rate limits, the login throttle and Iris usage budgets | Counter keys that expire on their own (minutes up to 30 days): IP addresses and request paths, login account names (usually emails), tenant, user, agent and Slack user ids, Iris users' emails. No records or request content | AWS US-East-1 | Review pending | high |
| Resend, Inc. | Transactional email delivery (approval CTAs, password resets, alerts) | Recipient email + subject + body of transactional emails | US (primary) + EU | SOC 2 Type 2 · GDPR-compliant | high |
| Functional Software, Inc. (Sentry) | Error tracking + performance monitoring (10% sample, PII scrubbed) | Error stack traces (PII scrubbed) + breadcrumbs + performance traces | US-East | SOC 2 Type 2 · ISO 27001 · GDPR | high |
| Vercel Analytics (Vercel Inc.) | Web analytics (page views, Core Web Vitals) | Anonymized user agent + page URL + performance timings (no user identifiers) | (same as Vercel) | (covered by Vercel SOC 2) | low |
Customer-controlled integrations (not subprocessors): Customer-configured Workato/Tray/SCIM endpoints · Customer-configured Slack/Teams notification webhooks · Customer-configured Jira/ServiceNow ITSM integrations · Customer-configured Snowflake/BigQuery/Databricks (analytics/BI export). These flows are configured by tenant admins; the destination relationship is the customer's, not AtmanID's.
Changes to this list
Every addition, removal and change, newest first. A new subprocessor is announced here at least 30 days before it begins processing data. Follow changes with thechange feed (Atom)— an Atom feed for your feed reader; customers are also notified directly by email under their DPA.
- 2026-11-04Changed· Anthropic, PBC
Corrected what we send. This entry said Anthropic receives no personal data and that we use a zero-retention tier. Both were wrong. Each Iris request carries the user's name, email, role and department, the page they are on, their question and the conversation so far, and the identity and access records the answer reads, truncated to fit but not redacted. We have not confirmed a zero-retention arrangement, so that claim is removed.
- 2026-11-04Listed· Voyage AI
Added to this page. Voyage AI already turned questions into embeddings for Iris and the public docs chat, but this list omitted it. It receives the question text as typed, with no user, tenant or account ids attached.
- 2026-11-04Listed· Upstash, Inc.
Added to this page. Upstash already held our rate-limit and login-throttle counters, but this list omitted it. Its keys hold IP addresses, login account names, and tenant, user and agent ids, and they expire on their own.
- 2026-11-04Listed· Amazon Web Services, Inc. (AWS KMS)
Added to this page. AWS KMS already held the key that protects most stored secrets, but this list omitted it. It sees wrapped keys and a tenant id (and a user id for MFA secrets), never the secrets themselves.
- 2026-10-16Listed· Cloudflare, Inc. (R2 Object Storage)
Added to this page. Cloudflare R2 already held the immutable copy of our audit-chain signatures and was in our internal inventory, but this public list omitted it. It holds tenant ids, hashes and signatures only — no audit record content and no personal data.
Security Commitments
Audit Trail Signing
Every audit record is SHA-256 hash-chained to the one before it. Every five minutes the head of each tenant's chain is signed twice over the same bytes — with Ed25519 and with ML-DSA-65 (FIPS 204), a post-quantum algorithm — and both signatures are kept in the database and in a separate immutable store, so the audit trail stays verifiable even against a future quantum computer.
| Key | Algorithm | SHA-256 fingerprint (SPKI) |
|---|---|---|
| v1 | Ed25519 | 5d8ff25105f2d2966deb2dafc6be8e27c5076a06a10bd1576485a78173b28306 |
| pq-v1 | ML-DSA-65 (FIPS 204, post-quantum) | 27080ac6f0ed07ad39af642e89b429c334a4ab3f4bdf3e6f6a5d6c66f5ed9d0e |
An auditor can verify any signature offline with the public key and standard tooling.Request the public keys and a verification walkthrough →
What Customers Are Responsible For
Our controls cover what AtmanID operates. These complementary controls are the customer's responsibility for them to be effective:
- Maintaining the security of your AtmanID admin credentials (no password sharing).
- Promptly removing AtmanID admin access when an admin leaves your organization.
- Configuring per-role MFA policies appropriate for your threat model.
- Reviewing and approving access requests in a timely manner per your policies.
- Performing certifications on a cadence that meets your compliance obligations.
- Notifying AtmanID immediately upon discovery of any suspected account compromise.
- Configuring connector credentials with least-privilege scopes appropriate to your environment.
- Maintaining accurate manager + role assignments in your HR system if HR sync is enabled.
- Reviewing this Trust Page for subprocessor changes within the 30-day notification window.
Running a security review?
We don't have a SOC 2 report yet. We will answer your questionnaire, walk through the architecture and threat model, and show you the controls running — under NDA.
Request a Security Review →