Privacy Policy

Effective September 8, 2026

MyMemoryHub stores the context you choose to keep — memories, to-dos, projects, and the connections you set up — so that the AI tools you already use can pick up where you left off. This page explains what we store, why, who else touches it, and how you stay in control. It is written to be read, not skimmed past.

The short version

What we collect

Account details. Your email address, used to sign you in with a one-time link and to send account messages. There is no password to store.

Content you create. Memories, to-dos, projects, notes, rules, and voice profiles that you or an AI acting on your instruction write into your Hub. This includes anything an AI tool saves on your behalf during a session.

Secrets you place in the vault. API keys and credentials you choose to store are encrypted at rest with a key held separately from the database. They are decrypted only when you, or a tool you authorised, retrieve them, and every retrieval is logged with its stated purpose.

Connected services. If you link Google Drive, a Telegram account, or a voice recorder, we store the tokens needed to keep that link working and the content you ask us to pull in. Linking is always something you do; nothing is connected by default.

Session and usage records. Which AI tool wrote or read what, and when, so that your activity log and morning brief are accurate. We keep server logs for troubleshooting.

Forms on this site. If you join the waitlist or write to us as an investor, we keep what you typed so we can reply.

What we do with it

We use your content for one purpose: to give it back to you, and to the tools you connect, in a useful shape. That means storing it, searching it, summarising it, extracting people and places from it, and turning it into the briefs, reminders and to-do lists the product exists to produce. To do that we run your content through AI models (see the next section), but always to serve your account, never to build a model.

Who else processes your data

We run on a small number of providers, each used for one job:

Each provider receives only what its job needs and is bound by its own terms not to use your content for anything else. The AI tools you connect to your Hub (for example Claude or ChatGPT) are governed by your agreement with them; what they do with a memory once they have read it is outside our control.

Sharing with people

A project is private to you until you invite someone into it by name. Members you invite can see that project's memories and to-dos at the level you grant. Guest mode lets you hand a tool temporary, limited access without exposing the rest of your Hub. Nothing is ever shared with another user by default.

Your controls

How long we keep it

Content stays until you delete it or close your account. Server logs are kept for a short operational window and then discarded. Backups roll off on the provider's schedule, so a deleted item can persist in a backup for a limited time before it is gone everywhere.

Security

Data is encrypted in transit and at rest. Vault secrets carry a second layer of encryption with a key that is not stored alongside the data. Access to your content is scoped to your account, and to the projects you have been granted, at the database level. If we ever learn of a breach affecting your data we will tell you promptly and plainly.

Children

MyMemoryHub is for adults and is not directed at children under 16. We do not knowingly collect data from them.

Changes

When this policy changes we update the date at the top and, for anything material, tell you in the app or by email before it takes effect.

Contact

Questions, export requests, or a request to close your account: reply to any email we have sent you — your sign-in link counts — and a person will answer.