Security

Private by design

LINEAGE is built around one principle: your memories belong to you. The architecture enforces this at every layer — authentication, storage, access control, and delivery. Your entries and recordings are visible only to you, never to other users, and that isolation is enforced by the database itself.

For what this means in plain words — ownership, export, and what happens if we ever go away — read our promise.

Encryption in transit

All traffic between your device and LINEAGE is encrypted via TLS 1.2+. This covers your voice recordings, vault entries, and all data sent to or from the platform. HTTP connections redirect to HTTPS automatically. HSTS is enforced with a one-year max-age.

Encryption at rest

All data is encrypted at rest using AES-256. This applies to vault entries, audio recordings, transcripts, and account information. Storage encryption is managed at the infrastructure level and applies automatically to everything in your vault.

Future delivery encryption

Sealed messages — entries you schedule for future delivery to family members — are encrypted in your browser with AES-256-GCM before they are stored. Each message uses a unique key, which LINEAGE protects separately so it can release the complete private link at the scheduled time. This is not zero-knowledge encryption: LINEAGE operates the delivery-key service. A delivered link releases its encrypted payload only once, when the recipient explicitly opens it.

Access control

Access policies are defined and enforced at the database level — not the application level. This means your entries cannot be accessed by any other user regardless of how the API is called. You see only your own data, enforced by the database itself.

Voice and audio data

When you record a reflection, your audio is stored in private cloud storage accessible only to your account. It is processed for transcription and then remains in your vault. Audio is never shared beyond what is required to produce your entry. You can delete any recording at any time.

AI processing

Your transcripts are processed by AI to be shaped into vault entries. Your content is not retained beyond the processing request and is not used to train any model, internal or external. LINEAGE will never use your memories to improve an AI system.

Authentication

Sign-in uses email and password through Supabase Auth. Passwords are stored only as salted bcrypt hashes, not as readable text. Web sessions use secure cookies; native-app sessions use the operating system keychain or keystore and short-lived access tokens with automatic refresh.

Vulnerability disclosure

If you discover a security vulnerability in LINEAGE, please report it to info@lineageproject.dev. We will acknowledge your report within 48 hours and work to resolve confirmed issues promptly.