Invited beta
Beta privacy notice.
Last updated 28 October 2026. This notice covers the free, invited beta. A full privacy policy and terms come before paid launch.
The short version
We can't read your context at rest, in backups, or without a connector you have authorized. Your context is decrypted only in memory, only while a connector you approved is making a request, and every access appears in your audit log. Your data is stored in the EU. Requests from your AI tools are handled on our provider's global network and may be processed outside the EU, close to where those tools run.
Your "context" is your memory pages and your profile. They are encrypted with user-held keys: a key that only you hold, unlocked with your passkey or your recovery key. We store them locked. If you lose every passkey and your recovery key, your context cannot be recovered, by you or by us.
Personal use only during the beta
MultiPass is for your own personal context. Do not store your employer's, clients', or customers' information in it, or other people's personal data beyond what you would normally keep about the people in your life. Work contexts will be a separate product with their own rules.
Who is responsible
MultiPass is an offering of Phantazein S.L., registered in Spain, which is the data controller for the information described here. Contact us about privacy or anything else at access@multipass.host.
What we store, and why
| What | Why | Readable by us? |
|---|---|---|
| Waitlist entry: email address, signup date, your browser's user agent, and the country your request came from | To invite you and to understand where interest comes from | Yes |
| Account: email address, your handle (the name in your context URL), and a sign-in cookie that lasts 7 days | To sign you in and serve your context URL | Yes |
| Your context: memory pages (paths, titles, content, tags) and your profile | The service itself | No. Stored encrypted with your key; decrypted only in memory while a connector you approved is making a request, or in your own browser when you open your memory in the control panel |
| Keys: locked (wrapped) copies of your context key, one per passkey, one for your recovery key, and one per connected AI; for each passkey, its identifier, public key, and label | So you, and the AIs you approved, can unlock your context | No. Each copy opens only with a secret we never store |
| Connections and audit log: which AI clients you approved, the permissions you granted, and every access: when, which client, what kind of action, and counts (for example "2 pages"); and which profile fields changed and when (field names, never their values) | So you can see and revoke every access, and to keep the service secure | Yes, but it never contains your content, paths, or search terms. Access tokens are stored only as hashes |
| Security counters: request counts per network address, keyed by a hash of the address, never the address itself | To limit abuse of sign-in and connection endpoints | Counts only |
When each page was last changed, and whether it is marked sensitive, are stored in the clear, so that AI clients without permission for sensitive pages never receive them. Its path, title, and content are encrypted like every other page.
Sign-in links are single-use, expire after 15 minutes, and are stored only as hashes. We use this information only to run MultiPass for you. We do not sell it, use it for advertising, or use your context to train AI models.
Legal basis
We process your account and context to provide the service you asked for (GDPR Article 6(1)(b)), and the audit log and security counters to keep it secure (Article 6(1)(f), our legitimate interest in protecting your data and the service). What you choose to put in your memory is up to you; it is encrypted like everything else, and we cannot read it at rest.
Where it is stored, and who helps us
- Cloudflare hosts the site and the databases. The databases are created in Cloudflare's EU jurisdiction, so your data is stored in the EU. Requests are handled at the Cloudflare data center closest to whoever makes them, which for AI tools is often outside the EU; that is where an authorized request is decrypted in memory. We are building our own EU server for these requests before the beta opens widely.
- Mailjet sends the waitlist confirmation and your sign-in links, so it receives your email address.
- Plausible counts visits to our public pages (the home page, the comparison page, and the waitlist page) without cookies and without personal data. It is never loaded in the control panel, your memory, key setup, or the sign-in and consent screens.
The AI clients you connect (for example Claude or ChatGPT) receive what they ask for under the permissions you grant. Their own privacy terms apply to what they do with it.
How long we keep it
Until you delete your account. You can do that yourself in the control panel. Your account is deleted at once. Copies in our backups expire within 30 days, and if we ever restore a backup, your deletion is applied again before anything is used. Deleting the account also deletes every locked copy of your key, so nothing we hold can open your context again. If we close the beta, we will tell you first and give you time to take your data with you.
Your rights
You can see, correct, and delete your context yourself in the control panel, see every access in your audit log, and revoke any connected AI at any time. A self-service export of your context is in development; until it ships, you can read everything in the control panel, and we will help by email. You also have the right to ask us for access to, correction or deletion of, or a copy of your information, to object to or restrict how we use it, and to complain to the Spanish data protection authority, the Agencia Española de Protección de Datos.
Changes
If this notice changes in a way that matters, we will email you before the change applies.