Google integration

Otto AI

Otto AI is the personal assistant that runs on an Otto — a small computer you buy once and keep in your home. Connect your Google Account and it works your Gmail, Google Calendar, and Google Drive on your behalf, in plain language, on hardware you own.

Gmail

Read, draft, send, triage

Ask what came in, get a thread summarized, dictate a reply, file or label what you're done with.

Calendar

Check, book, move, cancel

Ask what's on today, find a free slot, put a meeting on the right calendar, reschedule the one that slipped.

Drive

Find, read, write, organize

Pull up a document by name, summarize it, draft a new one, file it where it belongs, share it with someone.

How it works

You choose the permissions.

You connect your Google Account from the Otto app on your phone or desktop, on Google's own consent screen. Nothing is connected by default, and Otto AI reaches nobody's account but yours.

The direct Google integration calls Google's APIs from your Otto. Reading and changing information follows your approval settings, standing permissions and automation permissions. Depending on those settings, an action such as sending a message, moving an event or sharing a file may pause for approval in the app or proceed under permission you have already granted.

Permissions

What we ask for, and why.

gmail.modify

Read, compose, send, and organize mail in your mailbox.

Otto reads existing threads, drafts and sends replies, and changes message labels, read status, archive and trash state. Read-only and send-only permissions cannot organize existing messages; label-management permission alone cannot apply labels to messages. We do not request mail.google.com, which permits immediate permanent deletion.

calendar.events

Read, create, update, move, and cancel events.

Booking and rescheduling require event changes, including on shared calendars you can edit. Read-only or owned-calendar-only access would prevent those requests.

calendar.calendarlist

List your calendars and add or remove subscriptions.

Otto finds the right calendar for your request and can subscribe or unsubscribe when you ask. Read-only calendar-list access cannot change subscriptions.

calendar.calendars

Read and change calendar properties, and create or delete secondary calendars.

Otto reads calendar time zones and manages secondary calendars at your request. Read-only access cannot make those changes; app-created-only access excludes calendars you already use.

calendar.acls.readonly

Inspect calendar sharing permissions.

Otto can answer who has access to a calendar. It requests read-only sharing access because changing calendar sharing permissions is not a supported operation.

calendar.events.freebusy

Check availability on calendars you can access.

Finding meeting times requires the availability endpoint, including for shared calendars. Event permission alone does not authorize availability queries.

drive

See, edit, create, and organize your Drive files.

Otto finds and works with existing files you name without requiring you to select each one first. The narrower drive.file permission covers app-created or individually selected files; it cannot support discovery and changes across your unselected existing files. Read-only access cannot update, move, or share them.

openid · userinfo.email · userinfo.profile

Identify your Google Account and read its email address and display name.

Your email selects the account Otto acts on. Your Google display name labels account choices in chat, helping you distinguish connected accounts. The name does not replace the email used to select an account.

Your data

How your data is used.

The tokens that let Otto AI act on your Google Account are held encrypted on your own device. They are not stored on our servers, and the assistant is never shown them — it asks the device to make a call, and the device makes it.

Your mail, events and files are retrieved to carry out your requested tasks. Retrieved information and action results can remain in local conversation history and agent memory and can be used for later tasks.

The selected AI provider receives the content needed to perform those tasks, which can include Google information. When you use Otto's AI gateway, our backend processes that request and response on the way to and from the provider. When you use your own provider key, those model requests go directly from your Otto to the provider. The provider's retention and handling depend on its terms and applicable account settings.

We do not sell Google user data, we do not use it for advertising, and we do not use it to train models — ours or anyone else's.

You can disconnect the account at any time from the Otto app. The stored tokens are deleted when your Otto processes the request; an offline device must reconnect first. Disconnecting does not erase existing conversation history or agent memory. You can also revoke access from your Google Account permissions page.

Limited use

Google API Services.

Otto AI's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Publisher

The Tokenry, Inc.

Otto AI is built and operated by The Tokenry, Inc., which makes the Otto device and the Otto apps. Read the privacy policy, the terms of service, or get in touch. Questions about this integration go to support@myotto.ai.