Your notes, and who can read them

Minutes collects the Gemini notes Google attaches to the meetings in your calendar, and the facts of your own calendar: titles, times, who was invited, how you answered. This page says who can see what. It is the promise the code keeps, checked by tests, last changed on 15 October 2026.

  1. Only the people who were in the meeting can read its notes.

    The invitation as it was when the notes were written decides, and only those invitees who connected their own calendar. Somebody added to the meeting afterwards cannot read them here. Nobody else at Zattoo, and not the tool's administrators: they see that you connected and whether the sync works, never a note. A note you may not read does not exist for you; the page answers "not found". A one-to-one is the smallest case of the same rule: its notes exist for its two people and nobody else, and Ask reads them only when one of the two asks.
  2. Everything about your meetings is encrypted before it is stored.

    Notes, transcripts, who was invited, your calendar facts, your conversations, your marks and tags are sealed with a key that only the running app holds, so a person with access to the storage sees ciphertext. Everything stored is encrypted.
  3. Nothing leaves unless you ask.

    Ask sends the matching parts of notes you may read to an AI model through Vercel's AI Gateway to write the answer, and to nothing else. Ask runs under a zero-retention policy: the question, the parts of notes sent with it and the answer are deleted by the gateway the moment the request completes, and every request goes only to a provider with a verified agreement to keep nothing and train on nothing. No model is trained on your notes, no log holds their content, and the Google Docs in Drive are never touched. No analytics or tracking runs in your browser either: no Google Analytics, no Vercel Analytics, no third-party script of any kind. The only cookies are your sign-in session and two display preferences, and your browser alone remembers which notices you dismissed.

Who can see what

DataYouOther inviteesOther people at ZattooAdministratorsSomeone with access to the storageThe AI model
A note's content, and its transcriptyesonly those who were on the invitation when the notes were written, and connected their own calendarnonono, encryptedonly when you ask about it
Who was invited to a meeting, and when it was heldyesonly those who were on the invitation when the notes were written, and connected their own calendarnonono, encryptedonly when you ask about it
Your calendar: titles, times, rooms, who was there, how you answeredyesnononono, encryptedno
Your Ask conversationsyesnononono, encryptedyour question, when you ask it
Your to-do marks and series tagsyesnononono, encryptedno
That you connected, when the sync last ran, and its errorsyesnonoyesyesno
That you are online right nowyeseveryone signed ineveryone signed inyesyesno

“Other invitees” are the people on the meeting's invitation; “someone with access to the storage” means the hosting dashboard, where encrypted data reads as ciphertext.

Your controls

  • Exclude any meeting from your import in Settings; its note stays with the other invitees who imported it, and leaves your lists.
  • Hide a note of a meeting you organised; nobody on the invitation can open it, including you, until you show it again.
  • Delete any Ask conversation; they are saved under your name alone.
  • Disconnect your calendar at any time; your Google token and your calendar facts are deleted that moment. Notes stay with the people who were invited, as they belong to them too.

How long things are kept

  • Notes, transcripts and calendar facts stay as long as the tool runs; nothing expires on its own. A meeting you exclude leaves your lists, a note the organiser hides is closed to everyone, and disconnecting deletes your token and your calendar facts the same moment.
  • When you leave Zattoo, or revoke the tool's access in your Google account, the import stops at once; after 30 days without access, your connection, calendar facts, conversations, marks and tags are deleted. Notes stay with the other invitees who imported them, as they belong to them too.

Good to know

  • The engineers who deploy the app's code could, in principle, make it reveal a note, as with any software. Two things keep that honest: every change is reviewed before it is merged, and the source code is open to everyone at Zattoo, so anyone can read exactly how notes are stored, sealed and served, and see every change ever made to it, by whom and when.
  • The AI model behind Ask, deepseek/deepseek-v4.1-flash today, sees what Ask sends it when you ask; nothing is sent when you do not, and nothing is kept: Ask runs under a zero-retention policy. DeepSeek published the model's weights openly; it runs on the servers of Fireworks AI, a US company, and DeepSeek itself is not in the path and sees nothing. The request goes through Vercel's AI Gateway, which deletes the question and the answer the moment the request completes and keeps only counts, and every request is routed only to a provider with a verified agreement to keep nothing and train on nothing, or fails rather than go anywhere else (checked 15 October 2026).
  • Google Drive holds the Gemini Docs themselves under Google's own sharing rules; Minutes reads them and never changes who can open them.
  • Administrators of Google Workspace can read those Docs in Drive under Google's rules, with Google's audit log; Minutes neither widens nor narrows that, and a note's access here is never broader than its Doc's in Drive.
  • Server logs hold addresses, counts and timings, so a failure can be found; never a note, a question or an answer.

Questions go to Pavel Verkhovskyi, who runs the tool. Every promise above is in the code, which every member of Zattoo's GitHub organisation can read: the access rule, the encryption, this text and the tests that pin it to the code. The version stamp in the footer names the commit that is running; the repository holds its history.