Your Google accounts. Your AI. Your rules.
Updated October 29, 2026
What Leash does
Leash is an integration platform and security gateway. Connect an account, choose an AI, and ask that AI to help with your email, files, calendar or contacts. For example: “Summarize my two latest emails,” “Move this document into my travel folder,” or “Create a calendar for this project.” These are current features, subject to the Google permissions and AI limits you choose.
Your AI chooses the supported action and supplies its arguments. Leash checks permissions and your protections, sends the structured request to Google, then returns the permitted result to that AI. Leash does not use a language model to plan or rewrite your task, or automatically retry an uncertain change. Some security checks use TypeSafe’s JEV decision model.
Choose one service and its access
Signing in to Leash only identifies you; it does not connect your mailbox or files. In Your data, connect only the services you need. Read only requests a narrower Google grant. Full access enables supported changes, including irreversible operations. Each connection has its own consent flow; Leash does not request all four services at sign-in.
Gmail
Read only: Find and read messages, drafts and labels.
Full access: Compose and send mail; organize labels; archive, move to Trash or restore messages; permanently delete messages when requested; manage supported mailbox settings and filters.
Read-only scopes: gmail.readonly. Full-access scopes: https://mail.google.com/ + gmail.settings.basic. Unless shown as a complete URL, Google scope names use the prefix https://www.googleapis.com/auth/.
Google Drive
Read only: Find and read existing files and folders, export supported documents, and list installed Drive apps.
Full access: Create and upload files; update content and names; manage folders and sharing; move files to Trash, restore or permanently delete them; inspect changes and revisions.
Read-only scopes: drive.readonly + drive.apps.readonly. Full-access scopes: drive + drive.apps.readonly. Unless shown as a complete URL, Google scope names use the prefix https://www.googleapis.com/auth/.
Google Calendar
Read only: Read events and availability.
Full access: Create, edit and delete events and calendars; manage calendar subscriptions and supported sharing permissions.
Read-only scopes: calendar.events.readonly. Full-access scopes: calendar. Unless shown as a complete URL, Google scope names use the prefix https://www.googleapis.com/auth/.
Google Contacts
Read only: Find and read contacts and contact groups.
Full access: Create, edit and delete contacts and contact groups; manage group membership.
Read-only scopes: contacts.readonly. Full-access scopes: contacts. Unless shown as a complete URL, Google scope names use the prefix https://www.googleapis.com/auth/.
Leash uses openid, https://www.googleapis.com/auth/userinfo.email and https://www.googleapis.com/auth/userinfo.profile separately for Google sign-in. Those identify your Leash account; they do not grant Workspace content access.
Why broader access is sometimes needed
A user may ask their AI to find and edit a file that already exists in their Drive. The drive.file permission alone cannot search and manage all those existing files. Users who only want to search and read can select Read only instead. Installed Drive app discovery requires its separate drive.apps.readonly scope.
Managing calendars and their sharing needs more than event-only permissions. Contacts changes need write access; read-only Contacts does not allow creating or editing a person. Gmail permanent deletion requires the full mail scope; basic settings and filters use a separate settings scope. Leash does not request the administrator-only gmail.settings.sharing scope.
Permissions support these existing tasks. They are not requested for hypothetical future features or to build a copy of your account. Google’s own resource and organization restrictions continue to apply.
You control each AI
Provider defaults apply to new AIs. You can limit an individual AI to read-only access, disable particular actions, pause a provider, or revoke an AI connection. Protections can ask for your approval or stop actions under your chosen settings. Activity shows what happened; supported confirmed changes may have Undo. Leash only controls actions routed through its connection.
AI privacy and Google Limited Use
Leash does not use raw Google data, summaries, classifications, activity metadata or aggregated/anonymized Google data to create, train or improve general-purpose AI models. Our use and transfer of data received from Google Workspace APIs adheres to the Google Workspace API User Data and Developer Policy, including its Limited Use requirements.
Requested results are returned to the AI service you choose to connect. That service handles received content under its own terms, privacy policy and account settings. Leash does not control those external settings.
Configured security checks may send relevant content directly to TypeSafe JEV. TypeSafe’s policy prohibits training or fine-tuning on submitted inputs. We do not claim zero data retention or a self-hosted/offline model. Leash does not route Workspace requests through a managed multi-model generation service.
See Privacy Policy for data access, temporary approvals, activity retention, encrypted Undo recovery, deletion and human-access limits, and external services for recipients.
Connect, review and disconnect
- Sign in at Your Leash using Google, Microsoft or verified email.
- Open Your data, choose a Google service, and select Read only or Full access.
- Read Leash’s data-sharing notice, continue to Google and review all requested permissions.
- Open Your AIs, choose your AI, follow its setup instructions and set any action limits.
- Ask your AI for a task. Use Activity to inspect its outcome and notifications to answer approval requests.
- Pause or disconnect a service in Your data, revoke an AI in Your AIs, or delete your Leash account. You can also revoke Leash in Google Account connections.
No Leash phone verification or payment is required to reach the Google service connection flow. Reviewers should use their own Google accounts and disposable resources for changes.