Collect less
We only want the information needed to run the service. More data creates more risk.
Privacy approach
We think world-class privacy starts with a simple idea: a memory app should not casually have access to your memories.
In practice
We want the service to hold only what it needs to operate, not broad access to the memories themselves.
The principles
We only want the information needed to run the service. More data creates more risk.
Your recordings and media should not be casually readable by the company behind the app.
Your archive should not live only on our servers. Your own storage should remain part of the plan.
Open source code and clear architecture make the privacy model easier to verify, not just believe.
What that looks like
Voice recordings and attached media are protected on your device before they reach storage. That means the hosted service is not built around browsing through family memories behind the scenes.
A lot of products talk about privacy while still keeping the power to unlock everything. We are intentionally not built that way.
Encrypted exports to your own storage are part of the product. The archive should outlast the company, the app, and the moment.
The service still needs account, billing, delivery, and storage systems to work. But we want those systems to have narrower access, not wider access.
What makes this feel modern
Modern privacy should mean more than a long policy nobody reads. It should mean products are designed to avoid unnecessary access in the first place.
For a family memory app, that standard matters even more. These are intimate recordings, not just generic user content. The bar should be higher.
What makes this world-class
The strongest privacy posture is often not "we handle your data carefully." It is "we designed the product so we do not need as much access to begin with."
If your memories only live inside one company account, that is a fragile kind of trust. Portability is part of privacy because it reduces dependence.
Parents should be able to understand the basics without learning security jargon. And for anyone who wants to look deeper, the code and contracts should be inspectable.
No product can promise zero risk. The better standard is to be clear about what the service does, what it does not do, and where your control begins.
Plain summary
We need enough information to run the service. We do not want more access than that. That is the privacy approach in one sentence.
If you want the legal details, the full privacy policy can explain the operational side. This page is the product principle behind it.