Privacy
Last updated September 2026.
This is a private tool used by two people. It is not a company, there are no other users, and nothing here is sold, shared, or used to train anything.
The short version
- Your notes are locked before they are saved. The key that unlocks them is kept somewhere separate, so a copy of the stored data on its own is unreadable.
- Your messages are never read. Not WhatsApp, not Instagram, not email. This app has no way to see any of them.
- Nothing is sent for you. It writes a draft and hands it to you. You press send yourself, in your own app.
- The part that writes drafts never learns anyone's name. Every real name is swapped for a placeholder before it is asked to write, and swapped back afterwards.
- Only two people can get in, and only with an approved Google account.
What it keeps
- People you add or import: names, and whichever of email, phone, handle, company and city you feel like filling in.
- What you wrote about a meeting, and the follow-up message written from it.
- Meetings that have already finished: the title, the time, and who was invited. That is how it knows to ask you about them.
What it never touches
No message content of any kind. Your WhatsApp threads, Instagram DMs and email stay exactly where they are, seen by nobody but you. When you send a follow-up, the app opens your own messaging app with the words already typed, and you decide whether to send it.
Your calendar
It can see when meetings end, and it can add follow-up reminders you asked for. It cannot read your email, and never asks to. That is used for nothing except reminding you to follow up.
You can switch that off whenever you want, and it stops immediately: myaccount.google.com/permissions.
Getting rid of it
Ask, and everything belonging to you is deleted. No forms, no waiting period.
The technical detail, for anyone who wants it
Notes, drafts and message bodies are encrypted with AES-256-GCM at the application layer before they reach Postgres. The key lives in the server environment, never in the database.
Follow-up drafts are generated by a hosted language model. Two masking passes run before any text leaves the server: known contacts by lookup, and unrecognised proper nouns by shape. A test in the suite stands up a fake API and greps the outgoing request body, so a leaked name fails the build.
Google scopes requested: calendar.events,
calendar.calendarlist.readonly, and basic profile. No Gmail
scopes exist anywhere in the codebase. Google user data is not transferred
to third parties except as needed to provide the features described here,
and is not used to develop, improve or train generalised AI or machine
learning models.
Sign-in is restricted to a fixed allowlist of email addresses, checked before a session is created.
Questions: brrosenthal@gmail.com