Skip to content

Security & data handling ​

Otto never handles your password ​

Otto never asks for or stores a mailbox password. Every connection is a standards-based OAuth exchange with Microsoft or Google — Otto receives only a token, scoped to the permissions you approved on the provider's own screen.

You can revoke that token at any time, from inside Otto or at the provider. See Revoking access at the source.

How tokens are stored ​

In per-user mode, each mailbox's access token is encrypted at rest with authenticated encryption (AES-256-GCM) before it ever reaches the database. The stored row is unreadable ciphertext without Otto's separately held encryption key.

Disconnecting a mailbox deletes that row outright.

Permissions requested ​

Provider and modePermissions
Microsoft, per-userMail.Read · Mail.ReadWrite · Mail.Send · User.Read · offline_access
Google, per-usergmail.readonly · gmail.send
Microsoft, organizationMail.Read · Mail.ReadWrite · Mail.Send · User.Read.All · MailboxSettings.Read — application-level, granted tenant-wide at admin consent
Google, organizationShown live on your Integrations page — copy from there

In organization mode, the two non-mail Microsoft permissions exist to make attaching mailboxes safe and readable: User.Read.All lets Otto confirm an address you attach maps to a real user in your tenant, and MailboxSettings.Read reads display name and locale for the mailbox list. Neither grants access to mail by itself.

Mail.ReadWrite (added October 2026) is used for two things only. The first: when an email you send through Otto carries more than 3 MB of attachments — a submittal packet, say — Microsoft only lets those files be attached to a draft. Otto creates that email as a draft in your mailbox, attaches the files, and sends it within seconds; if anything fails before it is sent, Otto deletes the draft. In one rare case a draft can stay behind: Microsoft reports an error while creating it but created it anyway — Otto never got its id, so it cannot delete it, and it is never sent. Otto never repeats a send Microsoft may already have accepted.

The second is Mail filing, and only for a mailbox whose person has turned it on (it is off by default, and a workspace must have it switched on as well). Otto then moves read mail out of that mailbox's Inbox into the mailbox's own folders, by rules the person sets (read mail only, unless the person's rule says otherwise), and creates a folder when the person asks for one. Filing never deletes email, never takes mail from any folder but the Inbox, and every move can be undone. To suggest rules, Otto looks once at the mail already in the mailbox's folders and keeps only a count of messages per folder for each sender address and sender domain; those counts are deleted when filing is turned off.

Otto does not use Mail.ReadWrite to change, move or delete any other email. If your Microsoft 365 admin hasn't approved it yet, Mail filing cannot be turned on; and if it isn't approved, or your organization caps message size below the email, Otto keeps sending: files over 3 MB go as a download link in the email instead, and a product image that no longer fits is left out of that email. To approve it, a workspace owner clicks Approve updated permissions on Workspace Manager → Settings → Integrations → Microsoft 365 (per-user mailboxes: the person disconnects and connects the mailbox again).

None of these include contacts, calendar, files, or anything outside mail.

Verify the scopes yourself

You don't have to take this page's word for it. Microsoft and Google both list the exact permissions being requested on their own consent screens, before you approve — and the Google Workspace scopes are rendered live on your own Integrations page.

Mailbox visibility inside Otto ​

Each connected mailbox has its own member list, separate from workspace membership. Being a member of the workspace — even an owner or admin — does not automatically grant visibility into every connected inbox.

  • Organization mode: admins manage each inbox's list from the Connected inboxes table on the provider's page under Integrations.
  • Per-user mode: a mailbox is visible to the person who connected it.

Questions this guide doesn’t answer — contact Otto support. · Privacy policy