Security | Ambiguous

Security at Ambiguous.

How Ambiguous protects your workspace today, what we don't have yet, and how to report issues.

TLS 1.3 + AES-256

How we protect your data

Three architectural decisions that make data breaches structurally difficult, not just operationally unlikely.

Workspace isolation

Every workspace is scoped at the ORM level. Cross-tenant data access is structurally impossible. Not just policy-prohibited; architecturally prevented.

Complete audit trail

Every action by every user and every AI coworker is logged with actor, timestamp, resource, and outcome. Immutable, queryable, exportable.

Encryption everywhere

TLS 1.3 in transit, AES-256 at rest. JWTs expire in 15 minutes, refresh tokens rotate on every use. No plaintext secrets, no downgrades.

What we do today

Production security posture as of May 2026.

What we don't have yet

Honest about our current scope. These are real gaps we intend to close.

Responsible disclosure

Found a vulnerability? We want to hear about it.

Email: security@ambiguous.ai

Direct email. No contact forms, no ticket queues. You reach the security team.

Encrypted communication: For sensitive disclosures, request our PGP public key via the email above. We will reply with the key and fingerprint for verification.

Disclosure window: 90 days from report to public disclosure. We aim to acknowledge within 48 hours and provide a fix timeline within 7 days.

Trust artifacts

Real-time status and external references.

Status page: real-time uptime monitoring

Frequently asked questions