How Mavio uses Google user data.

Mavio can connect to Google Calendar, Gmail, Google Docs, Google Drive, and Google Chat. Each connection is optional, each is granted separately at the moment you turn that feature on, and none is a condition of using Mavio. You can use Mavio without connecting a Google account at all.

This page lists every Google permission Mavio can request, the exact OAuth scope behind it, what Mavio does with it, and what that permission does not allow Mavio to do. It supplements the Google user data section of our Privacy Policy.

Mavio is operated by Syntrigen Tech Private Limited. Recording, transcription, and summarisation happen on your own device and in our own infrastructure; connecting a Google service adds a destination for the results, and in the case of Calendar, a source of meeting titles and times.

Google Calendar — https://www.googleapis.com/auth/calendar.events.readonly. Mavio reads events from the calendars you select so it can list your upcoming meetings, start a recording already named after the right meeting, and assemble a brief from previous meetings with the same attendees. This scope is read-only. Mavio cannot create, modify, or delete an event, and the application rejects any such request internally rather than sending it to Google.

Gmail — https://www.googleapis.com/auth/gmail.compose. Mavio composes a follow-up email from a meeting and places it in your own Gmail drafts, and sends that message when you choose to send it. This scope grants no read access of any kind: Mavio cannot read, search, download, or delete the existing contents of your mailbox, and cannot see messages it did not write.

Google Docs — https://www.googleapis.com/auth/documents. Mavio creates a new Google Doc containing a meeting's transcript, summary, or action items, or appends that content to a document you explicitly nominate as the destination.

Google Drive — https://www.googleapis.com/auth/drive.file. Mavio lists the destination folder you choose, and uploads charts or images that it embeds into a document it has just created, deleting those temporary files once the embed is complete. This is the per-file Drive scope: it restricts Mavio to files it created or that you specifically opened with Mavio, and does not permit access to the rest of your Drive.

Google Chat — https://www.googleapis.com/auth/chat.spaces.readonly and https://www.googleapis.com/auth/chat.messages.create. Mavio lists the spaces available to you so you can choose where summaries should go, and posts meeting summaries into the spaces you choose. Mavio does not read the messages in those spaces; the read permission covers the list of spaces, not their contents.

Sign-in — openid, email, profile, and https://www.googleapis.com/auth/userinfo.email. Where you sign in with Google or connect Google Chat, Mavio receives your name, email address, and profile picture in order to identify your account and to show which Google account a connection belongs to.

Mavio's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. That policy is published at https://developers.google.com/terms/api-services-user-data-policy.

Providing user-facing features: we use Google user data only to provide and improve the features described on this page, each of which is visible in the Mavio interface at the point where the data is used.

Transfers: we do not transfer Google user data to third parties except as necessary to provide or improve those features, to comply with applicable law, or as part of a merger or acquisition after obtaining your explicit consent.

Advertising: we do not use Google user data for advertising, ad targeting, ad measurement, or any related purpose, and we do not sell it.

Human access: we do not allow humans to read Google user data except with your explicit consent for specific items, where necessary for security purposes such as investigating abuse, to comply with applicable law, or where the data has been aggregated and anonymised for internal operations.

The use of raw or derived user data received from Google Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements. This includes the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy.

Mavio uses AI models, including models operated by third-party AI service providers, to power the features described on this page — for example, using the title and attendees of a Google Calendar event to name a recording or prepare a meeting brief. Google user data is sent to those models only to provide the feature you are using at that moment.

We do not use, transfer, or sell Google user data — whether raw, aggregated, anonymised, or derived — to create, train, fine-tune, or improve foundational or generalised machine-learning or artificial-intelligence models, whether our own or a third party's. We use AI service providers only under terms that do not permit them to use this data to train or improve their models.

Mavio cannot read your Gmail inbox, your sent mail, or any message it did not itself compose.

Mavio cannot create, edit, move, or delete Google Calendar events, and cannot see calendars you have not selected.

Mavio cannot browse, open, or download files in your Google Drive that it did not create.

Mavio cannot read the contents of your Google Chat spaces or direct messages.

Mavio cannot access Google services you have not connected. Connecting Calendar does not grant Gmail, and disconnecting one does not affect the others.

OAuth tokens are encrypted at rest and are used only to make the API calls described above on your behalf. They are never exposed to other users or to the browser.

Data retrieved from Google — for example the title and time of an upcoming meeting — is stored against your account and is subject to the retention rules in our Privacy Policy, and to your plan's retention settings.

All data is encrypted in transit using TLS and at rest using AES-256. Access by our personnel is restricted, logged, and governed by the human-access commitment above.

In Mavio, open Settings → Integrations and disconnect the Google service you no longer want connected. Mavio revokes the token with Google and deletes the stored credentials for that connection.

You can also review and revoke Mavio's access directly in your Google Account at https://myaccount.google.com/permissions. Revoking there takes effect immediately and Mavio stops being able to call the relevant APIs.

Deleting your Mavio account removes the stored credentials for every connected service. See the data retention section of our Privacy Policy for the full timeline.