Privacy
A short, plain-English summary.
The formal policy is being drafted by a privacy lawyer ahead of public launch. Until then, here is exactly how we will operate — and the commitments we will not walk back later.
What you upload is yours.
The bytes you upload — your photos and videos — are stored as you uploaded them. Bit-for-bit, byte-identical. We do not transcode the original, strip metadata from it, or replace it with a smaller copy. Derivatives (thumbnails, web sizes) are regenerated from your original whenever they are needed; the original is the source of truth.
We do not train AI on children's faces.
Auto-tagging, face recognition, and scene detection are off the table. You will never have to opt out, because we never opted in.
We do not sell your data.
We will not sell, rent, or trade your photos, your usage, or your identity to a third party for marketing, advertising, or any other purpose. If we ever introduce optional integrations, they will be opt-in and clearly labelled.
You can leave with everything, today.
A standing export of your full archive — originals plus a documented JSON schema — is part of the product, not a request you have to make. If we ever shut down or sell to a worse owner, you will not be locked in.
What we do collect.
Account email (so you can sign in), the photos and entries you choose to upload, and the operational logs required to run the service (e.g. which API endpoints were called and from which session). We do not collect device sensor data, location, contacts, or third-party tracking identifiers.
Who can see your entries.
By default, no-one but you. Entries are visible to a follower only if you have explicitly added them to a Circle and the Circle includes that entry. Followers cannot see your other Circles, your account email, or anything you have not shared with them.
Questions, requests, or concerns.
Email hello@keepsake.example — a real person will reply. You can ask us to delete your account at any time; we will confirm by email and remove your data within 30 days (objects in object storage, database rows, and backups).
This page is a placeholder.
The legally binding Privacy Policy will replace this page before public launch. The principles above will not be relaxed in that version; they may only be expanded with more specifics. If you ever notice a future version contradicting one of the commitments above, that is a bug — please write to us.
Last updated: 11 May 2026 · Back to Keepsake