Google Data Access
What Google access is used for.
Clients can connect a Google Account so their AI employee can help with requested work across Drive, Calendar and Meet, Forms, Sheets, Docs, Slides, and Gmail.
Why Nonstop asks for Google access
Nonstop AI Solutions uses Google access to perform work a client requests from their AI employee. Google permissions can cover a broader set of actions than one individual request. Nonstop's policy is to use those permissions only for the client-requested actions described below.
Connected capabilities
Depending on the client's approved workflow, the connector can provide these capabilities:
- Google Account Identity — confirm which Google Account is connected.
- Drive Upload and File Creation — save requested deliverables to Google Drive.
- Drive Search, Read, and Copy — find, review, download, or copy requested Drive files.
- Calendar and Google Meet — review calendar events and, when approved, create calendar events with Google Meet links.
- Forms — create or read requested forms and review requested form responses.
- Sheets — create, read, update, and format requested spreadsheets.
- Docs — create requested documents with requested content and read requested documents.
- Slides — create and read requested presentations.
- Gmail Search and Read — find requested messages and review message metadata and snippets.
- Gmail Send — send a requested message only through an explicit approval workflow.
- Legacy YouTube Read Access — accounts that authorized YouTube before July 31, 2026 may retain read-only channel access until that permission is revoked. New standard Workspace connections do not request YouTube access.
How Google data is used
Google user data is used only to provide client-requested services, such as identifying the connected account, finding or creating requested files, saving outputs, reviewing or scheduling requested events, working with requested forms, spreadsheets, documents, presentations, or messages, and returning useful links, content, or status to the client.
How access is protected
- Google OAuth tokens are kept in the protected connector backend rather than given directly to client AI runtimes.
- Client runtimes use a protected client-specific credential to obtain a fresh, short-lived helper token when a workflow needs a Google action.
- Client runtimes do not receive stored Google refresh tokens.
- Nonstop's operating policy requires explicit approval before sending Gmail, creating a real calendar event or invitation, or changing a live client file.
What Nonstop does not do
- We do not sell Google user data.
- We do not use Google user data for advertising.
- We do not ask clients for raw Google passwords.
- We do not send Gmail messages without an explicit request and approval.
- The current client helper does not provide actions for deleting or publicly sharing Drive files.
Revoking access
You can revoke Nonstop AI Solutions access at any time from your Google Account permissions page: https://myaccount.google.com/permissions.
Contact
Questions about Google data access can be sent to nonstopaisolutions.contact@gmail.com.