AvaganceLegal
Connected Google and Microsoft Accounts
Last updated: 16 November 2026
Advisers and firms can connect a Google account (Gmail and Google Calendar) or a Microsoft account (Outlook and Microsoft 365) to Avagance. This page explains what access Avagance asks for, what it does with the data, who can see it, and how to remove the access. It forms part of our Platform Privacy Policy.
For the email and calendar data in a connected account, Avagance acts as the processor for the adviser's firm, under our Data Processing Agreement.
1. What Avagance asks for, and why
Each person connects their own account by signing in to Google or Microsoft and approving access. A firm can also connect one shared mailbox that the platform sends the firm's emails from. Avagance asks only for the access below.
| Account | Access | Why Avagance needs it |
|---|---|---|
| Gmail | Read, search, organise (labels, read status, archive), draft and send email (gmail.modify) |
So Ava can check the inbox, find client and provider emails, file them to the right client, prepare replies, and send email from the adviser's own address |
| Google Calendar | View and edit events (calendar.events) |
So client meetings booked in Avagance appear in the adviser's calendar, and changes in either stay in step |
| Google account | Email address (openid, email) |
So Avagance knows which account is connected and which address email goes from |
| Outlook and Microsoft 365 | Read, organise, draft and send email (Mail.ReadWrite, Mail.Send) |
The same as for Gmail |
| Outlook calendar | View and edit events (Calendars.ReadWrite) |
The same as for Google Calendar |
| Microsoft account | Sign in and read the basic profile (User.Read), and stay connected (offline_access) |
So Avagance knows which account is connected, and keeps working without asking the person to sign in again each time |
Avagance never permanently deletes email.
2. How we use the data
- Only for features the person sees in Avagance. Checking the inbox, filing emails to clients, preparing replies, sending email and keeping meetings in the calendar.
- Never for advertising. We do not sell the data, use it for advertising, or pass it to anyone to build a profile of the person or their clients.
- Never to train AI models. Email and calendar data from a connected account is not used to develop, train or improve any artificial intelligence or machine-learning model, ours or anyone else's. It is also left out of the feedback that improves Ava within a firm.
- AI processing. When Ava reads an email or prepares a reply, the content is sent to our language-model provider (Opper, or OpenAI where the feature uses it), only to produce that result. Our contracts with them forbid them from using it to train their models. They are listed on our Sub-processors page.
3. Who can see it
- The person who connected the account. When they file an email to a client, colleagues at their firm who can open that client's record can read it there.
- Not Avagance staff. Our people do not read the email or calendar data in a connected account, with three exceptions:
- the person asks us to look at a specific message, for example in a support request;
- we need to investigate a security incident or abuse;
- the law requires it.
- Our sub-processors, only as far as a feature needs it. The current list is on our Sub-processors page.
4. How we store and protect it
- Access tokens. The access tokens Google and Microsoft issue are encrypted at rest and never sent to anyone's browser.
- What we keep. Only what a feature needs: for example, an email filed to a client's record, a reply Ava prepared, or a meeting that was booked.
- Where. It is stored in Google Cloud's London region, encrypted in transit and at rest, with the measures in section 13 of our Platform Privacy Policy.
5. Removing access
- In Avagance. Disconnect the account in Avagance at any time. We stop reading it and delete the access tokens we hold. For a Google account, we also ask Google to withdraw the access it granted.
- At Google. Remove Avagance at myaccount.google.com/permissions.
- At Microsoft. For a personal Microsoft account, remove Avagance at account.live.com/consent/Manage. For a work account, your organisation's Microsoft 365 administrator can remove it.
- What stays. Emails already filed to a client's record stay in the firm's account until the firm deletes them or the subscription ends, when they are deleted or returned as set out in the DPA.
6. Google API Services User Data Policy
Avagance'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. The use of information received from Google Workspace APIs will adhere to the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.
We apply the same rules to data from Microsoft accounts.
7. Contact
Questions about this page, or a request to delete data: policy@avagance.com.