Zero BS AI Sandbox

Connect your accounts to an AI assistant you control

The Sandbox is part of Zero BS AI. It runs command-line tools inside an isolated environment so that an AI assistant (Claude, via the Model Context Protocol) can act on the accounts you connect — on your behalf, only when you ask it to in conversation. Nothing runs on a schedule and nothing is shared with anyone else. Below is every integration the Sandbox supports today, and exactly what each one accesses and why. As we add more command-line tools, each new integration will appear here with the same breakdown before you can connect it.

Integrations

Currently available:

Google Workspace

gog

Connect a Google account and the assistant can read and act on that account’s Google Workspace data — Gmail, Calendar, Drive, Docs, Sheets, Slides, Contacts, Chat, Classroom, Tasks, Forms, Meet, Apps Script — and read your Analytics, Search Console and YouTube reporting. We request write access (not just read) because the assistant composes, edits, sends and organises on your behalf — it doesn’t only look.

What it accesses, and why

You choose which account to connect, and the provider shows you the full list of permissions before you authorise it.

Sign-in identity

openid, email, profile

Identifies which Google account is connected and shows its email address in the app.

Gmail

gmail.modify, gmail.settings.basic, gmail.settings.sharing

Read, search, label, draft, send and organise mail, and read/update settings such as filters, signatures and forwarding — when you ask the assistant to triage your inbox, reply, or set something up. Read-only scopes are insufficient because the assistant composes and sends on your behalf.

Calendar

calendar

View your calendars and create, edit, move and delete events when you ask the assistant to schedule or reschedule something.

Drive, Docs, Sheets, Slides

drive, drive.activity.readonly, documents, spreadsheets, presentations

List, open, create, edit, move and share files in your Drive, and read recent file activity, when you ask the assistant to draft a document, build a spreadsheet, prepare slides, or find and update existing files. A per-file scope cannot work because the assistant operates across files you name in conversation.

Contacts & directory

contacts, contacts.other.readonly, directory.readonly

Look up and update contacts (and, in Workspace organisations, the shared directory) so the assistant can address emails and meeting invites to the right people.

Google Chat

chat.spaces, chat.messages, chat.memberships

Read and post messages, and manage spaces and memberships, when you ask the assistant to follow up in Chat.

Classroom

classroom.courses, classroom.rosters, classroom.coursework.me, classroom.coursework.students, classroom.announcements, classroom.topics

Read and manage courses, rosters, coursework, announcements and topics for educators who ask the assistant to help run a class.

Tasks & Forms

tasks, forms.body, forms.responses.readonly

Create and update task lists, build and edit Forms, and read form responses when you ask the assistant to set up a checklist or a survey.

Google Meet

meetings.space.created, meetings.space.readonly

Create meeting spaces and read details of meetings the assistant created, for scheduling and follow-up.

Apps Script

script.projects, script.deployments

Create and deploy Apps Script projects when you ask the assistant to automate something inside your Workspace.

Analytics, Search Console, YouTube (read-only)

analytics.readonly, webmasters, youtube.readonly

Read reporting data so the assistant can answer questions about your sites and channels. These are read-only — nothing is changed.

Connecting

Sign in to the app and use the Google integration on your account page. Google shows you the full list of permissions before you authorise it. You can connect more than one Google account and pick which one is active.

Disconnecting

Remove the account from the same page at any time — we delete the stored tokens. You can also revoke access directly from your Google account at myaccount.google.com/permissions.

How your data is handled

This applies to every integration. OAuth tokens for connected accounts are stored encrypted at rest. Your data is fetched on demand to carry out the action you asked for, processed in short-lived, isolated sandbox containers, and is not used for advertising, profiling, or sold to anyone. Full detail is in our Privacy Policy and Terms of Service.