Privacy policy
Protocol is a private meeting assistant used by one small team (see About). This policy explains what Google user data Protocol accesses, how it uses, stores and shares that data, and how to have it removed.
Google user data Protocol accesses
Protocol connects to a single Google account — the team's assistant account — through Google OAuth, with two scopes:
- Google Meet,
meetings.space.created: creates meeting rooms and, when creating one, chooses whether people with the link join directly or ask to be let in. Protocol does not access recordings, transcripts, chat or participant lists from Google Meet. - Google Calendar,
calendar.events: creates an event for a meeting in that account's primary calendar — the title, description, time and the email addresses of the invited people, all entered by the team member who asked for the meeting. If that team member chooses to, Google Calendar emails the invitation to those addresses. Protocol does not read, change or delete any other events.
Along with these, Protocol keeps the OAuth tokens Google issues for the account.
How Protocol uses it
Only to set up the meeting a team member asked for and confirmed: to create the room, put it in the calendar and show the meeting link. Nothing is created or sent automatically without that confirmation.
How it is stored
- OAuth tokens are stored in a configuration file on the computer or server that runs Protocol's assistant component, readable only by that system's account. They are never put in source code, shared databases or messages.
- The link and identifier of each room or event Protocol created are kept in the assistant's task log, so the app can show whether a meeting was set up.
- All requests to Google are made over HTTPS.
How it is shared
- The meeting link is sent over Telegram to the people the team member chose to invite, after the team member confirms the message; the calendar invitation, if chosen, is emailed by Google Calendar.
- When a team member sets up a meeting through Protocol's built-in assistant, the meeting link and the details they entered are passed to the language-model provider that runs the assistant (Anthropic or OpenAI), so the assistant can report what was created.
- Beyond this, Google user data is not transferred to anyone, except where the law requires it. It is not sold and not used for advertising.
- Google user data is not used to develop, improve or train artificial intelligence or machine-learning models.
Protocol's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Call recordings and transcripts
These are not Google user data, but for completeness: audio is recorded and stored on the computer of the person who recorded the call, and it is transcribed on that same computer. To build the written meeting record, transcript text may be sent to a language-model API (Anthropic or OpenAI) under the team's own API key. No Google user data is added to that text.
Retention and deletion
- OAuth tokens are kept until access is revoked. Access can be revoked at any time at myaccount.google.com/permissions; a revoked token stops working immediately.
- Task-log entries are kept while they are needed to show meeting history and are deleted on request.
- To ask for deletion of any data described here, write to the contact below.
Changes
If this policy changes, the new version is published on this page with a new effective date.