You are trusting us with the most sensitive data of your life. Here is exactly how we protect it.
Every document, message, and piece of sensitive data you store in your vault is encrypted using AES-256-GCM before it is written to our database. This is the same standard used by the US National Security Agency for top-secret information and by every major bank in the world.
Encryption happens before your data is stored. When you retrieve it, it is decrypted for display and then discarded from memory. At no point does unencrypted data rest on our servers in a retrievable form.
When you store a password or account credential in your digital asset vault, it is encrypted on your device before being transmitted to our servers. We receive only ciphertext — we never see the plaintext password.
This is called a zero-knowledge architecture: even Memoari staff with full database access cannot read your stored passwords. If you forget a stored password, we cannot recover it — because we never had it. This is by design.
Our database uses Supabase Row Level Security (RLS). Every query is filtered at the database level by your authenticated user ID. Even if an attacker bypassed our application layer, they could only retrieve rows belonging to their own authenticated session.
RLS policies are written in SQL and enforced by the database engine, not our application code. This provides a defence-in-depth guarantee that is independent of our API logic.
When a beneficiary receives access to your vault, we issue a one-time cryptographic access token. These tokens are time-limited, single-use, and generated using a cryptographically secure random number generator.
Tokens cannot be guessed by brute force — they are 256 bits of entropy. Once used, a token is immediately invalidated. Links cannot be shared or reused. Every access is logged with a timestamp and the requestor's identity.
All communication between your browser and Memoari's servers uses TLS 1.2 or higher. We enforce HTTPS on all endpoints, redirect HTTP to HTTPS, and use HTTP Strict Transport Security (HSTS) headers.
We achieve an A+ rating on SSL Labs. Our TLS configuration disables known-vulnerable cipher suites and supports only modern, forward-secret key exchange.
You can revoke any beneficiary's access at any time, change your unlock contacts, modify death-trigger conditions, and lock your entire vault instantly from any device.
Memoari staff have no administrative override for vault contents. We cannot open your vault on your behalf, read your documents, or override your contact designations. Your vault is yours.
Data at rest
AES-256-GCM encryption
Data in transit
TLS 1.2+ (HTTPS)
Authentication
Bcrypt password hashing
Database
Row Level Security
Vault passwords
Zero-knowledge credentials
Beneficiary access
Cryptographic access tokens
Transport
HSTS headers
Application
CSRF protection
Brute force protection
Rate limiting on auth endpoints
Multi-tenancy
Supabase RLS policies
Monitoring
Audit logging
Data governance
UK GDPR compliance
Any acquisition agreement would require the acquirer to maintain all existing security standards and privacy commitments. All users would be notified and given the option to export and delete their data before any data transfer occurs.
We have not experienced a security breach affecting user data. If a breach were ever to occur, we would notify all affected users within 72 hours as required by UK GDPR, and we would provide clear guidance on steps to take.
No. Our application is designed so that vault contents are encrypted before storage and can only be decrypted by an authenticated user session. Our staff can see metadata (account status, plan type, timestamps) but not vault contents.
Data is stored in EU/UK Supabase regions, with replication for redundancy. We do not transfer personal data to countries outside the UK or EU without appropriate safeguards.
We conduct internal security reviews on a quarterly basis and plan an independent third-party penetration test before our public launch. Audit results summaries will be published in this section.
🔍
If you discover a security vulnerability in Memoari, please report it responsibly. We take all reports seriously and aim to respond within 48 hours.
security@memoari.org
Please do not publicly disclose vulnerabilities until we have had a chance to investigate and remediate.