Privacy commitment
How Keepsake protects your stories
Keepsake exists so families can preserve their memories. That goal only works if you trust us with your stories. This page explains in clear language how we keep your data under your control, and it complements the legal details in our Privacy Policy.
Summary at a glance
- Projects are private by default. Only the owner decides who joins, and can share a single Story through a public link they can turn off at any time.
- From Settings, the owner can download the whole Project as one file, with readable Stories and the original photos, recordings and videos.
- We invest in secure hosting, storage, payments, and email infrastructure so your family stories stay safe. We disclose the categories of services involved below.
You stay in control
- A Project has one owner and may have family members. Only the owner can invite or remove family members.
- Family members can help with Questions, Answers, Stories, and book content, but they cannot manage membership, public sharing, payment, export, or deletion.
- Public sharing is off unless the owner explicitly shares a current Story.
- Anyone with a shared Story link or a printed QR code can open it without an account and can pass the link on. A recording behind a QR code is not limited to people holding the book.
- Cookie and tracking preferences are available at any time.
Access and export
- Each Question email includes a private link where you can answer without creating an account.
- From Settings, the owner can download the Project as one file: readable Stories, who added what, the original photos, recordings and videos, and a machine-readable index of everything included.
- If the current version of your book was ordered in print, its PDF is included in that download. Keepsake keeps no separate PDF backups or earlier downloads.
Security that matches the story you are telling
Our technical stack is built on services with strong security track records, and we add our own controls on top.
- Our hosting and network services provide encrypted connections and network-level attack protection.
- Stories and attachments are kept in restricted database and object storage. Data is encrypted in transit and at rest, and access is restricted and audited.
- Payments go through a specialist payment provider, and Keepsake does not store full card numbers.
- The emails we send, such as Questions and sign-in links, go through an email service that uses standard email security protocols.
- An error-monitoring service helps us diagnose and respond to technical issues.
- We use limited product analytics. Optional website analytics and advertising measurement activate only for the category you consent to, and you can withdraw that choice at any time. Our own product analytics record a short list of named actions, such as a Question being sent, and never the content of your Stories.
- Access to live systems is limited to the work needed to run and support Keepsake.
Transparent support practices
- Support looks at your Project only as far as needed to diagnose a problem or recover your data.
- Deleting the whole Project removes its recordings, so QR codes in printed books stop playing. Before a Project can be deleted, the owner downloads it first, and if printed QR codes would stop playing, Keepsake warns and asks for a separate confirmation. Editing or deleting a single Story does not remove recordings kept for a book that was already paid for. Printed books cannot be recalled.
- For privacy questions, contact support@makekeepsake.com.
Next steps
Review the formal language in our Privacy Policy. If you want a human conversation about how Keepsake protects your family, email support@makekeepsake.com.