Security & Trust
Kept asks families to trust us with irreplaceable things. That trust has to be earned with specifics, not reassurance.
Named threat: voice-cloning
A library of identified, family-linked voice recordings is, by another name, a voice-cloning asset. We know this. It is the most serious category of risk this product carries, and it shapes every decision below: who can access audio, how it is stored, and what we do and do not send off-site. We do not have a complete answer to this risk — no one does — but we think naming it plainly is the minimum a product like this owes its users.
Audio and video files are stored in Backblaze B2 object storage and are never served from an open public path. Inside the app, every file link is signed, is only given to someone signed in to the family it belongs to, and stops working within 24 hours. When you deliberately share something — a public link, a book QR code, an event gallery, or a future message — its links last longer, so the person you shared it with can open it without an account.
All data in transit uses TLS 1.2 or higher. Every audio, video and photo file kept in storage is encrypted by Kept with AES-256-GCM, using a key we hold, before it is uploaded — Backblaze stores it as ciphertext it cannot read. The one exception is a file your family chooses to keep only in its own Google Drive: copies stored there are protected by Google, not encrypted by Kept. The PostgreSQL database is a different case: it is encrypted at rest on Render's infrastructure using Render's keys, not ours, so database security at that layer is tied to theirs. We do not offer customer-managed keys — you cannot hold a key we don't have. For a family archive we think that is the right trade: a key only you hold is a key that loses every recording your family has when it is lost.
Memories are private to the family that created them by default. Someone has to deliberately share a memory for it to be seen outside that family — with a linked family through cross-family sharing, or through a public link or book QR code. Family admins can see their family's memories, except those of a member whose access has been restricted. A restricted member can't browse the family at all; they can only download their own memories or start a family of their own. There is no admin backdoor that grants access to a family's content without an account in that family. And no admin — including a family's owner — can delete a memory someone else recorded; only the person who made it can. Memories a member marked “Only me” stay private to that member — admins can’t see them either.
Passwords are hashed with bcrypt (cost factor 12) and never stored in plaintext. Sessions use signed, HTTP-only cookies. Changing your password lets you sign out every other device at the same time, and resetting a forgotten password does so automatically. Failed login attempts are rate-limited. As alternatives to a password, you can sign in with an emailed link, a code sent by text, or a personal sign-in link a family admin can set up for an older relative.
All connections to mykeptapp.com and api.mykeptapp.com use HTTPS. We set HSTS headers to prevent downgrade attacks. Cookies are marked Secure and SameSite=Lax. API responses include standard security headers (X-Content-Type-Options, X-Frame-Options, Referrer-Policy).
The backend runs on Render.com (US region). The database runs on Render's managed PostgreSQL. Media files live on Backblaze B2. Transcription runs on our own server using an open-source speech model, and the audio never leaves it — that is the default on every plan, including the free one. The only way a recording reaches an outside AI service is if someone deliberately chooses the paid 'best quality' transcription, and the 'no off-site processing' setting blocks even that. Optional AI features you switch on yourself can send a transcript's text — or, for two of them, a photo — to an outside AI service; each is off until you choose it, and the same setting blocks them all. We do not sell data or share it with advertisers.
We test Kept's security on an ongoing basis: automated dependency scanning runs continuously to catch known vulnerabilities, and we've run several hands-on internal security reviews, most recently a full re-audit in October 2026 covering access-control scoping, rate limiting, session management, signed media, and input validation. Confirmed findings were fixed and deployed. We do not yet have an independent third-party penetration test on record — closing that gap is on our roadmap.
If you find a vulnerability, please email hello@mykeptapp.com with the subject line 'Security'. We will respond within 48 hours, fix confirmed issues promptly, and credit you if you'd like. We ask that you give us time to fix the issue before disclosing it publicly.
This page reflects our practices as of October 2026.
Updated: October 24, 2026
Kept only uses cookies needed to sign you in. No tracking. Privacy
Questions? Email us at help@mykeptapp.com
mykeptapp.com