Skip to content

Google API data disclosure

Effective 21 November 2026

Inroad requests four Google scopes in total: openid, email, profile and https://www.googleapis.com/auth/gmail.send. It requests no other Google scope, and it never asks for permission to read, search, label, modify or delete mail.

This page is the scope-level disclosure for the Google OAuth verification review. The general policy — what we collect, why, and your rights — is the Privacy Policy.

1. Scopes requested

ScopeSensitivityWhy it is neededWhat we do with the data
openidNon-sensitiveSign-in with Google needs a stable subject identifier so a returning user maps to the same Inroad account.We store the Google subject identifier against your Inroad account. It is used only to authenticate you.
emailNon-sensitiveAn account needs an address for identity and support; the address is also the From address when we send on your behalf.We store your address, show it to you, and use it as the sender of approved messages.
profileNon-sensitiveThe interface greets you by name and shows your avatar.We store your name and picture URL and display them in the app.
https://www.googleapis.com/auth/gmail.sendSensitiveInroad sends outreach email from the user's own Gmail so it comes from their real address and lands in their sent mail.We send only messages the user has explicitly approved, one message at a time, and store the resulting message/thread IDs.

The Gmail permission is requested separately from sign-in (incremental authorization), and only when the user chooses to connect Gmail inside the product. A user who signs in but never connects Gmail never grants any Gmail access.

2. Why gmail.send and nothing broader

The product's only Gmail operation is sending a plain-text message the user has reviewed. That is exactly what gmail.send allows. Any broader scope would grant access we do not use:

  • gmail.readonly and gmail.metadata would let us read the mailbox — we have no feature that reads mail, so we do not ask.
  • gmail.compose would additionally let us create and manage drafts inside Gmail; Inroad keeps its drafts in its own database, so this is unnecessary.
  • gmail.modify, mail.google.com and the settings scopes would allow changing the mailbox — nothing in the product does that.

Replies are handled without reading Gmail: the user pastes a reply into the app if they want help answering it. That is a deliberate design choice so that the smallest possible scope is enough.

3. How Google user data flows through Inroad

  • Sign-in. Google redirects back with an ID token. We validate its audience, issuer, expiry and verified-email claim, then create a session cookie.
  • Connect Gmail. Google returns an authorization code; we exchange it for a refresh token and confirm that gmail.send was actually granted. If it was not, we store nothing.
  • Send. On an explicit user action we exchange the refresh token for a short-lived access token and POST one MIME message to gmail/v1/users/me/messages/send. The message is plain text, with no attachments, no tracking pixels and no link rewriting.
  • Record. We store the subject, body, recipient, timestamps and the returned Gmail message and thread IDs so the thread and follow-ups keep working.
  • Disconnect or delete. We call Google's revocation endpoint, then delete the stored token.

4. What we never do with Google user data

  • We never use Google user data to train AI models — not our own, and not our providers'.
  • We do not read, scan, index or store the contents of your inbox, sent mail, drafts, labels, contacts or calendar.
  • We do not sell Google user data, transfer it to data brokers, or use it for advertising, retargeting or profiling.
  • We do not let Inroad staff read your messages. Support sees only what you choose to paste or attach.
  • We do not use Google user data to determine creditworthiness, or for any purpose unrelated to sending the emails you approved.
  • We do not transfer Google user data to a third party except the processors listed below, and only to operate the feature you asked for.

5. Storage and security

Account records are stored in a managed PostgreSQL database (Neon). The Gmail refresh token is encrypted with AES-256-GCM using envelope encryption — a per-row data key wrapped by a master key that lives only in the server environment, never in the database. Access tokens are held in memory for the duration of a send. All traffic uses TLS, and the API is reached through the web app's same-origin proxy rather than being exposed to the browser.

The session cookie is HttpOnly, Secure and SameSite=Lax; state-changing requests require a CSRF token; administrative endpoints are restricted to an allow-list of accounts and expose usage and cost metrics, not message contents.

6. Retention and deletion

  • The Gmail refresh token is kept only while Gmail is connected. Disconnecting deletes it and revokes it at Google.
  • Messages we sent on your behalf are kept so your pipeline and thread view work, until you delete them or your account.
  • Profile → Delete account revokes the Google token, deletes uploaded files and exports, and removes your records from the database.
  • You can revoke Inroad's access independently at myaccount.google.com/permissions; sending then stops immediately.
  • A hash of an address that asked not to be contacted is retained so we do not contact it again. It contains no readable personal data.

7. Processors that may handle this data

ProcessorPurposeGoogle user data involved
Amazon Web Services (EC2)Runs the API and background workerProcesses requests, including send calls
NeonManaged PostgreSQLAccount record, encrypted refresh token, sent-message records
UpstashManaged RedisJob identifiers only
SupabasePrivate object storageUploaded documents and data exports — never Google tokens
VercelFrontend hosting and same-origin API proxyWeb requests and the session cookie
Groq / NVIDIALanguage-model inferencePrompt text for research and drafting — never tokens, never mailbox contents
TavilyWeb searchCompany and founder search queries

None of these processors receive Google user data for their own purposes, and none may use it to train models.

8. Limited Use statement

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

In particular, Google user data is used only to provide or improve the user-facing features described on this page, is not transferred to third parties except as necessary to provide those features (or as required by law), and is not used for advertising or to train general-purpose AI models.

9. Contact

Questions about this disclosure or a request relating to Google user data: hello@inroadapp.live. We respond within 30 days. The full Privacy Policy covers the rest of the data we process.