We treat your documents the way we'd want our own accountant to treat ours. This page describes the safeguards we have in place today and what we're improving next.
Data in transit & at rest
- All client and server-to-server traffic uses TLS 1.2 or higher.
- Documents and previews live in a private storage bucket. There are no public URLs — every download is a short-lived signed link.
- Storage and database encryption at rest uses AES-256.
Access control
- Row-Level Security is enforced on every user-data table — a user can only read or write their own mailboxes, documents and extractions.
- Roles are stored in a dedicated table and checked with a security-definer function to prevent privilege escalation.
- Service-role credentials are stored in secrets, never exposed to the browser, and used only inside trusted server functions.
AI processing
- Extraction requests go to our AI provider over TLS. The provider processes the request and does not retain or train on customer inputs.
- We downscale images and de-duplicate by content hash before calling the provider — minimizing data sent and stored.
Deletion
Deleting a document removes the storage object, preview and extraction. Deleting a mailbox cascades to all documents inside it. Account deletion removes all your data within 24 hours; backups are purged within 30 days.
Operational practices
- All changes ship via reviewed deployments.
- Production secrets are scoped and rotatable on demand.
- Server-side errors are aggregated for monitoring without capturing document contents.
Responsible disclosure
If you believe you've found a vulnerability, email aislan@longevitylabs.tech. We acknowledge within 2 business days and will not pursue legal action against good-faith research that follows this policy.
On our roadmap
- SOC 2 Type I report.
- Self-serve DPA download and sub-processor change notifications.
- Optional region-pinned storage (BR / EU / US).