Skip to content

Transparency

Google API scope disclosure

This page exists for two audiences: the customer deciding whether to connect a Google account, and the Google reviewer assessing our OAuth application. It states every Google scope NoOops can request, in which part of the product it is requested, exactly what it does, and why a narrower scope would not work. Only the Gmail group is needed to use NoOops; Directory and Drive are optional and are requested only when an administrator turns that feature on.

No write access to your directory No permanent-delete capability No Google data used for AI training

Gmail — the shared inbox

Requested when a user connects a mailbox to NoOops. Granted per mailbox, by the person who owns it or by a Workspace administrator for a delegated identity.

https://www.googleapis.com/auth/gmail.modifyRestricted

NoOops is a shared inbox. It must read the messages of the mailbox the user connects so a team can work them as a queue, and it must write back the state the user changes inside NoOops — marking read, applying or removing labels, and archiving — so the user's own Gmail stays in step with what they just did in NoOops.

What it is used for

  • Read messages, threads, attachments and headers for the connected mailbox so they appear in the shared or private inbox.
  • Mirror read/unread state back to Gmail when a teammate opens or resolves a thread.
  • Apply and remove NoOops labels (Closed, Snoozed, Waiting) so the mailbox owner can see the same state in Gmail.
  • Archive a thread in Gmail when it is resolved in NoOops, if the user enables that.
  • Run users.watch so new mail arrives in the queue without polling delay.

What it is never used for

  • ✕Permanently deleting mail — NoOops never requests or performs permanent deletion.
  • ✕Reading mailboxes the user has not explicitly connected.
  • ✕Training AI models or building advertising profiles.

Why a narrower scope will not do

gmail.readonly cannot write back read state, labels or archive, which is the core of a shared inbox, and gmail.labels alone cannot read message content. gmail.metadata is insufficient because agents must read the body of a claim or appeal to answer it.

https://www.googleapis.com/auth/gmail.sendSensitive

Replies must leave from the organization's own address, through the organization's own Google account, so SPF, DKIM and DMARC continue to pass and the recipient sees the address they already know.

What it is used for

  • Send a reply, reply-all or forward composed by a user inside NoOops, from the connected address.
  • Send a one-off setup verification message when a user asks NoOops to test a newly connected mailbox.

What it is never used for

  • ✕Sending marketing or bulk mail.
  • ✕Sending anything automatically — Sorna AI can draft, but a person presses send.

Why a narrower scope will not do

There is no narrower Gmail scope that permits sending. The alternative would be relaying mail through our own servers, which we deliberately refuse to do because it would break the customer's SPF/DKIM alignment and would place their mail — including PHI — on our infrastructure.

https://www.googleapis.com/auth/gmail.settings.basicRestricted

When an organization routes a Google Group (for example billing@ or appeals@) into a NoOops queue, NoOops creates one Gmail filter that files that group's mail under its own label. Without the filter, mail that arrives while NoOops is not actively syncing cannot be attributed to the right queue.

What it is used for

  • Create or update a single Gmail filter per mapped group so its mail is labelled at delivery time.
  • Read the mailbox's existing Send-As identities so only identities the user has already verified with Google are offered as a From address.

What it is never used for

  • ✕Creating or changing forwarding addresses, vacation responders, IMAP/POP settings or delegation.
  • ✕Adding a Send-As identity — NoOops only reads the ones Google has already verified.
  • ✕Changing any setting the user did not configure inside NoOops.

Why a narrower scope will not do

Gmail has no read-only or filter-only settings scope; settings.basic is the narrowest scope that can read Send-As identities and write a label filter. We deliberately do not request gmail.settings.sharing on this connection, so delegation and forwarding remain out of reach.

https://www.googleapis.com/auth/gmail.settings.sharingRestricted

Requested only on the optional Workspace domain-wide delegation path, where an administrator authorizes NoOops once for the whole domain instead of each user connecting individually. It is needed to read the delegated Send-As identities that let an agent answer as a shared address.

What it is used for

  • Read Send-As and delegation identities for a delegated mailbox so an agent can reply as the shared address the organization already uses.

What it is never used for

  • ✕Granting mailbox delegation to anyone, or altering existing delegation.
  • ✕Any use at all on the standard per-user OAuth connection — this scope is not requested there.

Why a narrower scope will not do

settings.basic cannot read domain-level Send-As/delegation identities, which is the only thing this path needs. Organizations that do not want this scope can use the per-user connection instead, which never requests it.

Google Workspace Directory — optional

Requested only from Settings, and only by an organization owner or Workspace administrator who chooses to map their existing Workspace people and groups into NoOops instead of typing them in by hand. Every scope here is read-only.

https://www.googleapis.com/auth/admin.directory.user.readonlyRestricted

So an administrator can pick teammates from their real Workspace directory when creating NoOops users, and so an agent's NoOops identity stays matched to their Workspace account.

What it is used for

  • List domain users (name, work email, suspension state) to offer as NoOops accounts.
  • Keep a mapped NoOops user matched to the correct Workspace identity.

What it is never used for

  • ✕Creating, editing, suspending or deleting any Workspace user.
  • ✕Reading personal profile fields the directory does not expose to administrators.

Why a narrower scope will not do

There is no non-Directory API that lists a domain's users. The write scope (admin.directory.user) is deliberately not requested, so NoOops cannot change your directory.

https://www.googleapis.com/auth/admin.directory.group.readonlyRestricted

Mail sent to a Google Group such as billing@ must be routed to the NoOops queue that owns it. To offer that mapping, NoOops has to list the groups that exist.

What it is used for

  • List domain groups and their addresses so each can be mapped to an inbox.

What it is never used for

  • ✕Creating, renaming or deleting a group.

Why a narrower scope will not do

Group addresses are only enumerable through the Directory API; the read-only variant is the narrowest form.

https://www.googleapis.com/auth/admin.directory.group.member.readonlyRestricted

Mail to a group arrives in every member's mailbox. NoOops reads membership so the same message is attributed to one group conversation instead of being duplicated per member.

What it is used for

  • Read group membership to deduplicate group mail and attribute it to the right queue.

What it is never used for

  • ✕Adding or removing members of any group.

Why a narrower scope will not do

Without membership, group mail cannot be deduplicated and a single email appears once per member. The write scope is not requested.

https://www.googleapis.com/auth/apps.groups.settingsSensitive

A group can only be worked as a queue if its posting and delivery settings actually allow the mapped mailbox to receive and reply. NoOops reads those settings to tell the administrator, before they map it, whether the group will work.

What it is used for

  • Read a group's posting, delivery and access settings to validate a mapping and warn about a configuration that would silently drop replies.

What it is never used for

  • ✕Changing group settings without an explicit administrator action in NoOops.
  • ✕Any access to message content — this scope carries none.

Why a narrower scope will not do

The Groups Settings API has no read-only scope. Without it the product can only fail at runtime instead of warning the administrator during setup.

Google Drive — optional, customer-owned evidence storage

Requested only when an organization turns on the SPOOON desktop agent and chooses to keep its own workforce screenshots and call recordings in its own Drive rather than on our infrastructure. NoOops writes into folders it creates and can see nothing else in the Drive.

https://www.googleapis.com/auth/drive.fileSensitive

The customer, not NoOops, should hold its own monitoring evidence. drive.file lets NoOops create a SPOOON folder in the customer's Drive and read back only the files it put there, so the organization owns and can audit its own retention.

What it is used for

  • Create the SPOOON Screenshots, SPOOON Keystroke Logs and call-recording folders.
  • Upload screenshots and call recordings captured by the customer's own agents.
  • Read back or stream only those files when an authorized supervisor opens them in NoOops.

What it is never used for

  • ✕Reading, listing or touching any file NoOops did not create.
  • ✕Sharing files outside the organization.

Why a narrower scope will not do

drive.file is already the narrowest Drive scope; it is per-file and gives no visibility of the rest of the Drive. We deliberately do not request drive or drive.readonly.

https://www.googleapis.com/auth/userinfo.emailNon-sensitive

To show the administrator which Google account the Drive storage is connected to, and to prevent the wrong account being connected by mistake.

What it is used for

  • Display the connected account's email address on the integration screen.

What it is never used for

  • ✕Contacting the user, marketing, or profile enrichment.

Why a narrower scope will not do

This is the minimum identity scope; without it the connection is anonymous and unverifiable by the administrator.

openidNon-sensitive

Standard OpenID Connect sign-in used to complete the authorization handshake and identify which account granted it.

What it is used for

  • Identify the authorizing account at the moment of consent.

What it is never used for

  • ✕Replacing NoOops sign-in, or any ongoing profile access.

Why a narrower scope will not do

Required by OAuth 2.0 / OIDC itself.

How the data is handled

  • Limited Use. NoOops's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
  • No AI training. Google user data is never used to train generalised models. Sorna AI sends only the conversation a user is working on, with detectable identifiers redacted first, and the provider is contractually barred from training on it.
  • Token handling. Refresh and access tokens are encrypted at rest and are never returned by our API. Disconnecting revokes access immediately.
  • Minimum scope. We do not request the full mail scope, Calendar, Contacts, the full Drive scope, or any Directory write access. We do not request permanent deletion. Directory and Drive scopes are requested only if an administrator enables those optional features.
  • Access control. Only members of the inbox a mailbox is routed to can read its mail, enforced server-side on every request. Private inboxes are isolated from shared queues.
  • Auditability. Connecting, reauthorizing, disconnecting and sending are all written to an append-only audit ledger with actor, IP and device.

Revoke access and delete your data

You can withdraw our access to your Google account at any time, and you do not need to contact us to do it.

  • In NoOops. Settings → Integrations → the connected account → Disconnect. We call Google's revocation endpoint immediately and delete the stored refresh and access tokens. Gmail push notifications for that mailbox stop at the same moment.
  • From Google. Remove NoOops at myaccount.google.com/permissions. Our access ends immediately; we detect the revoked grant and mark the connection as disconnected.
  • Delete the synchronised copy. Disconnecting stops all further access. To also erase the messages, attachments and metadata already synchronised into your workspace, an organization owner can delete the mailbox and its inbox in Settings, or email privacy@nooops.ai from the account's domain. We complete verified deletion requests within thirty days.
  • Drive files stay yours. Screenshots and recordings written with drive.file live in your own Drive; deleting the SPOOON folders in Drive removes them permanently and we cannot recover them.
  • Whole account. Email privacy@nooops.ai to delete the entire organization. Legally required audit records are the only exception and are listed in the privacy policy.