Privacy
Last updated 19 October 2026
Mutuals holds notes about the people in your life. That is sensitive, so this page says plainly what we store, who else touches it, and what is not built yet.
Who is responsible
Mutuals is operated by WeAmplify e.U., Lange Gasse 3/22, 1080 Vienna, Austria (company register number FN 609504f), owned by Kyrillus Mehanni. WeAmplify e.U. is the controller for your account data. Contact: hello@getmutuals.ai. Full company details are in the imprint.
For the notes you keep about other people, you decide what goes in and why. We store and process that content on your behalf, for you, and do not use it for our own purposes.
What we store
Your account
- From Google sign-in: your email address, whether Google has verified it, your name, your profile picture address and your Google account identifier. We ask Google for your identity only. We do not request access to your Google contacts, calendar or email.
- Your sessions: a hashed session token, the browser user agent and the IP address of the sign-in.
- Your settings, such as time zone.
Your relationship data
- The people, organizations, notes, interactions and follow-ups you add, whether typed in the app, imported from a file, sent through a chat channel or saved by an agent you connected.
- Every value keeps its history and its source, so that you can see where a fact came from. Undoing or correcting something adds to that history.
- Imported files are read in memory and are not kept as files. The rows you uploaded are stored with the import so you can review, fix and re-export them.
Chat channels, if you link one
- The phone number or Telegram identifier you link, the messages you send to the Mutuals number or bot, and our replies.
- Voice notes are transcribed and the transcript is stored. The audio itself is not kept.
- Linking a channel does not import your chat history, and Mutuals never messages your contacts.
Connected agents
- Which agent you authorized, the permissions you granted, when it expires, and hashed access credentials.
Operations
- Request logs contain the method, the path without its query string, and a request identifier.
- For each AI request we record which model was used, token counts, cost and timing. The content of the request is not recorded in that trace by default.
- If you send feedback from inside the app, your description, any screenshots you attach, the page you were on, your name and email, and technical details of your browser are filed in a private issue tracker.
This website
- If you join the waitlist: the email address or phone number you enter, the referring page and campaign tags, and your referral code.
- Visits are counted with Plausible, which does not use cookies and does not build a profile of you.
Why, and on what legal basis
- To provide the service you signed up for: performance of our contract with you (Art. 6(1)(b) GDPR).
- To keep the service secure and working, for example rate limiting, session records and logs: our legitimate interest in running a safe service (Art. 6(1)(f) GDPR).
- To answer you when you write to us or join the waitlist: your request or consent (Art. 6(1)(a) and (b) GDPR).
We do not sell personal data, we do not show advertising, and we do not use your relationship data to train models.
AI processing
Understanding a note takes a language model. When you save a note, the text of that note, your own name and the names of people you were recently in touch with are sent to a model provider so the right person can be recognized. When you send a voice note, the audio and a list of names from your workspace, used as spelling hints, are sent for transcription. Summaries send the fields and recent notes of the one record being summarized.
These requests go to Melious, which runs open-weight models in data centres inside the European Union: currently GLM 5.3 Flash, made by Z.ai, to understand notes and answer questions, and Whisper, made by OpenAI, to transcribe voice notes. The companies that made the models do not receive your data. Melious does not log the content of requests, and none of its providers train on it. Real names are included, because matching a note to a person does not work without them.
Agents you connect
If you connect an agent such as Claude Code, Codex or Meta's Muse, it can read what you permitted on the consent screen, including real names and notes, and that information reaches the agent's provider. Its own privacy policy then applies. You can disconnect an agent at any time in Settings, then Connections. That stops future requests. It cannot recall what the agent already received.
Who processes data for us
- Fly.io: application hosting, Frankfurt, Germany.
- Neon: PostgreSQL database, Frankfurt, Germany (AWS eu-central-1).
- Google: sign-in.
- Melious: AI processing as described above, inside the European Union.
- Meta (WhatsApp), Twilio and Telegram: only if you link that chat channel. Telegram bot chats are not end-to-end encrypted.
- GitHub: in-app feedback reports, in a private repository.
- Vercel, Plausible, Cloudflare Turnstile and Resend: this website, its visit counts, its spam check and waitlist emails.
Some of these providers are based in the United States, so parts of your data can be processed outside the European Economic Area. We use each of them under its standard data processing terms. If you want to know which safeguard applies to a particular provider, write to us and we will tell you.
How long we keep it
Your account and relationship data stay until you delete them or ask us to delete your account. When an account is deleted, encrypted copies in our database provider's backups expire within 30 days, and request logs age out on their own. Sessions expire after 30 days without use. Agent connections expire after 30 days unless renewed, and their access tokens after 15 minutes. Waitlist entries are kept until access is granted or you ask us to remove them.
Your rights, and deleting your account
You have the right to access, correct, export and delete your data, to restrict or object to processing, and to withdraw consent. Self-service account deletion and full export are not built into the app yet. Until they are, write to hello@getmutuals.ai from the address you signed in with and we will export or delete your account and everything in your workspace within 30 days.
You can also complain to a supervisory authority. Ours is the Austrian Data Protection Authority (Datenschutzbehörde), dsb.gv.at.
People you take notes about
Mutuals is a private notebook. The people in it are not users and are not contacted by us. If you believe someone keeps information about you in Mutuals and you want to exercise your rights, write to us and we will pass your request to the account holder where we can identify them.
Security
Data is encrypted in transit, over TLS, and at rest: our database is stored with AES-256 encryption and our servers' disks are encrypted too. Every read and write is scoped to your workspace, so one account cannot reach another's data. Session and agent tokens are stored only as hashes, and an agent's access token expires after 15 minutes. Only the people who run Mutuals can reach production systems.
To report a vulnerability, write to hello@getmutuals.ai. We acknowledge reports within three working days and will not take action against good-faith research that avoids other people's data. Our security.txt says the same.
No system is perfectly secure. If a breach affects your data, we tell you without undue delay, notify the Austrian Data Protection Authority within 72 hours where the law requires it, and notify the platform whose connector you used, such as Meta for Muse, within the time its terms set.
Age
Mutuals is for adults. You must be at least 18 to create an account.
Changes
When this page changes in a way that matters, we will update the date at the top and tell account holders by email before it takes effect.