Your digital life plan is only as good as the security protecting it. Here is exactly how Constellation keeps your information safe.
Security Principles
We collect only what's necessary. Your sensitive data is encrypted before it leaves your device. We cannot read your vault contents — even our own engineers see only ciphertext.
All sensitive items are encrypted at rest using AES-256-GCM with unique per-item data keys. Master keys use envelope encryption — a compromise of one item cannot expose any other.
All API routes require authentication via Clerk, an enterprise-grade identity provider. Service accounts follow the principle of least privilege. Database-level row-level security (RLS) ensures users can only query their own data.
Every significant action is recorded with timestamps in an immutable audit log. You can export your complete audit trail as CSV or PDF at any time. Nothing happens silently.
Technical Specifications
Constellation uses industry-standard cryptographic primitives. Each vault item is encrypted with a unique data key, which is itself wrapped with a master key using envelope encryption — meaning a compromise of one item does not expose any other.
Our Commitment
Constellation is a subscription product. Your data is not our product. We do not sell, analyze for marketing purposes, or share your personal information with third parties.
We do not show ads or sell your attention.
Your data is never analyzed for marketing.
We never sell your personal information.
Security FAQ
Only you. Document vault contents are encrypted with AES-256-GCM using keys derived from your account. Even Constellation's own engineers cannot read your vault data — we only ever store ciphertext. Each vault item has its own unique encryption key, so compromising one item does not expose any other.
No. Email discovery reads metadata only — sender domains, subject-line patterns that indicate account relationships, and timestamps. We never read message bodies, download attachments, or store email content. For Apple Mail connections, app-specific passwords are used ephemerally and never stored in our database.
No. Access is controlled by your Activation. You define when and how access is granted, including a configurable grace period (typically 7–14 days) where you can override or cancel any request. Your executor must submit a formal access request, and you are notified by email at every step.
You can export your complete data at any time from your Account settings (CSV and PDF formats). On cancellation, your data is retained for 30 days before permanent deletion per our data retention policy. Document vault contents are cryptographically destroyed — encrypted data without its key is unrecoverable.
Constellation delegates all authentication to Clerk, an enterprise-grade identity provider trusted by thousands of companies. We never store or handle your password directly. Clerk supports multi-factor authentication (TOTP), social login providers, and secure session management. Sessions are validated on every API request via signed JWTs.
Yes. Row-level security (RLS) policies are enforced at the database layer in Supabase. Even if application-level code had a bug, the database itself prevents any user from querying another user's data. API routes additionally verify your authenticated user ID before any data operation.
Every response includes X-Content-Type-Options (nosniff), X-Frame-Options (DENY to prevent clickjacking), strict Referrer-Policy, Content-Security-Policy, Permissions-Policy (camera, microphone, and geolocation disabled), and Cache-Control (no-store) on all authenticated pages. A unique X-Request-Id is attached to every request for audit correlation.
Start protecting your digital life with the confidence that your data is safe.
