How Amberis connects to your accounts

Gmail

What the connection can reach, and what each piece is for:

• Your mail: headers, bodies, snippets, labels, read and starred state. This is what everything else is built on. Threads join one list ranked by what it costs you to miss, each with a line under it saying what it is asking for. The same mail feeds the morning briefing, and Ask answers questions with the specific messages attached. Your own sent mail, read per contact, is what drafts learn your voice from.
• Attachments: every file from a thread listed under it and streamed from Gmail when you open it, so you are not digging back through the thread for the version you were sent.
• Read, archive and label state, written back, so clearing a thread in Amberis clears it in Gmail and you never do the same tidying twice.
• Sending, so a reply you approve goes out from your own address, in the real thread, with the right threading, quoting and signature.
• Who you are: the email address on the Google account, so we know which mailbox we are connected to.

We ask Google for permission to read and change mail, not for full mailbox access. Google’s all-of-Gmail permission is never requested, so Amberis cannot permanently delete your mail. Nothing is sent or archived without your click either.

Calendar is separate, and optional. Turn it on and Google asks you once more, for read-only access to your calendars and the events on them. That is what puts the day’s meetings next to the threads that created them, and lets the briefing say who you are seeing today. Events are fetched live when you look at them and are not stored.

If you then use scheduling, meaning creating an event, answering an invitation, or holding time for something, Google asks a third time, for permission to write to the calendar. Both steps start with you, and mail works without either.

To switch it off, disconnect Gmail in Settings. You can also revoke the grant from Google’s side at myaccount.google.com/permissions.

Amberis’s use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Outlook

Outlook and Teams are one connection: your Microsoft account, authorised once. This section covers the mail and calendar side of it, the next one covers Teams.

What it can reach through Microsoft Graph, and what each piece is for:

• Mail in the connected mailbox: headers, bodies, folders, categories, read and flag state. Outlook threads sit in the same ranked list as everything else, with the same one-line reason under each, and feed the briefing, search by meaning and Ask. Your sent mail here teaches drafts your voice the same way Gmail’s does.
• Attachments: the files on those threads, listed under them and fetched from Outlook when you open one.
• Read and flag state, written back, so clearing a thread in Amberis clears it in Outlook.
• Sending, so an approved reply lands in the real thread, from your own address.
• Your calendar, viewing and scheduling: the day’s events sit beside the threads that created them, and when you schedule from Amberis it can create the event, answer an invitation, or hold the time. Events are fetched live when you view them and are not stored.
• Your name and email on the Microsoft account, so we know whose mailbox is connected, and permission to stay connected, so syncing carries on in the background instead of stopping the moment you close the tab.

Microsoft asks for all of that at the first connect, calendar included. Its consent system has no way to start read-only and upgrade later the way Google’s does, and answering an invitation is itself a write. So the permission is granted up front and sits unused until you schedule something. Nothing is sent, changed or put in your calendar without your click.

To switch it off, disconnect the Microsoft account in Settings. Because it is one grant, that ends Teams with it. You can also revoke it from Microsoft’s side: personal accounts at account.live.com/consent/Manage, work and school accounts at myapps.microsoft.com.

Microsoft Teams

Teams is not a separate grant. It rides the Microsoft account you connected above: one consent screen, one connection, one disconnect. What it reaches, and what for:

• Chats and channel messages your own account can already see, so a Teams thread that matters more than your inbox is not buried behind it. Amberis never sees more of a team than you do.
• Message text, so chat sits beside the mail about the same thing, turns up in the morning briefing, and can be searched by meaning and asked about with the messages behind the answer attached.
• Directory entries (display name, email), so you can see who wrote what rather than an account id.

To switch it off, disconnect the Microsoft account in Settings, which ends Outlook and Teams together. The provider-side revocation is the same one: personal accounts at account.live.com/consent/Manage, work and school accounts at myapps.microsoft.com.

Slack

Amberis connects as you, with a user token, so it sees exactly what your own Slack account sees and never more of a workspace than you do. What that covers, and what each piece is for:

• Channels, group conversations and direct messages you are already in, and the history in them, so Slack lands in the same ranked list as your mail with the same one-line reason under each thread, feeds the morning briefing, and can be searched by meaning and asked about with the messages behind the answer attached.
• Sending messages as you, only when you press send. The reply goes out from your own Slack account, in the conversation it belongs to.
• Keeping read state in step, and opening a direct message when you start one, so a conversation you have dealt with in Amberis is not still bold in Slack, and writing to someone new works from here. These are ordinary member permissions, not admin ones: Amberis cannot administer the workspace or reach conversations you are not in.
• Reactions, read and added, so a thumbs-up answer still reads as an answer in Amberis, and you can send one back without opening Slack.
• Files shared in those conversations, listed and fetched, so Slack attachments sit under their thread with the ones from mail instead of in a separate app. Files you attach to a reply go up with it.
• The workspace member directory (display name, email), so you can see who wrote what rather than an account id.
• The workspace name and its custom emoji, so messages render the way they do in Slack, in-jokes included.

Nothing is sent, no reaction is added and no file is uploaded without your click.

To switch it off, disconnect Slack in Settings. You can also remove it from the workspace’s own app management page, under Settings & administration → Manage apps in Slack.

What holds for all four

• We do not run ads and we do not profile you for advertising.
• We do not sell your data.
• AI providers process your content to power your own features: ranking, drafts, briefings, search and Ask. Their API terms do not permit using it to train their models, and we do not train models of our own on it.
• Disconnect a channel and the data already synced from it is deleted after 30 days. Its stored tokens go immediately.
• Delete your account in Settings and everything goes at once, with no grace period. Your actual mail and messages stay where they are; we are deleting our copy, not yours.

The clocks and the exact tables are set out under how long we keep data. If you want a channel purged today rather than in 30 days, or you have a question this page does not answer, write to info@amberis.ai.