How We Keep Your Data Secure
Last updated: June 2026 · All data hosted in the United States · AI services by Anthropic, PBC
We can't see your data. Ever. Your submissions, uploaded documents, and Clayton interaction history are protected by Row-Level Security rules at the data layer — not just by policy. Platform administrators have access to aggregate usage metrics (review counts, scores, activity levels) for operational support, but the content of your work is inaccessible to anyone outside your explicit sharing. Here's exactly how we enforce that.
Encryption in Transit & at Rest
All data transmitted between your browser and Clayton's servers is encrypted using TLS 1.2+. Data stored in the database — including your submissions, feedback, and documents — is encrypted at rest using AES-256, the same standard used by financial institutions and government agencies.
Row-Level Security & Access Control
Every record in the database is protected by Row-Level Security (RLS) rules enforced at the data layer — not just the application layer. Submissions and uploaded documents are readable only by the submitter and the leader whose Clayton was used. Platform admins (Sagely Advisory staff) can access aggregate usage metrics — review counts, scores, activity levels — for operational support, but have no access to the content of submissions, documents, or Clayton interaction history.
Account-Level Isolation
All data is scoped to your user account at the application layer. Records are protected by Row-Level Security rules that restrict access to the account holder and explicitly shared team members. Your data cannot be accessed by other users on the platform.
Secure File Storage
Files you upload — drafts, context documents, work samples — are stored in private cloud storage and are never publicly accessible. Access requires a server-generated signed URL with a short expiry window. Raw storage paths are never exposed in API responses or the frontend.
Backend Security
All AI processing and sensitive operations run in isolated backend functions — never in your browser. API keys (OpenAI, Stripe) are stored as server-side environment secrets and are never included in any response payload or exposed to frontend code. Backend functions verify identity before performing any operation.
Authentication & Session Management
Every API call is bound to your authenticated session token, which is verified server-side on every request. Sessions are time-limited and invalidated on logout. We do not use persistent session cookies that survive browser restarts.
Have a specific security question?