Google API Verification Support

Jarvis acts only after the user authorizes it.

Jarvis is a personal AI assistant designed to help one user or one dedicated assistant account manage communication, scheduling, and collaborative work inside Google Workspace and consumer Google accounts. The product does not rely on password harvesting, hidden scraping, or silent access. Every Google connection begins with explicit OAuth consent from the account owner.

Read privacy policy Read terms

jarvis.connect({
  account_owner: "user-controlled",
  auth_model: "Google OAuth 2.0",
  storage: "encrypted local runtime",
  services: [
    "Gmail",
    "Calendar",
    "Drive",
    "Docs",
    "Sheets",
    "Slides"
  ],
  purpose: [
    "read or send email on request",
    "manage calendars and events",
    "create and edit user documents",
    "work with spreadsheets and decks",
    "share files selected by the user"
  ]
})

What Jarvis is

Jarvis is a user-facing assistant that helps with operational work. It can draft email, read and organize inbox state, inspect availability, create events, produce documents, update spreadsheets, and build presentations when the user asks it to.

Personal assistant model

Each Jarvis instance operates for one owner or one owner-controlled assistant account. The user remains in control of the Google account, the scopes granted, and the moment access is revoked.

Explicit user intent

Jarvis uses Google APIs to perform concrete tasks requested by the user, such as reading a message, sending a reply, scheduling a meeting, creating a document, or updating a spreadsheet.

No dark patterns

The product is not built for advertising, resale of user data, credential collection, shadow syncing, or unrelated profiling. Access exists only to provide the assistant features the user explicitly enabled.

Why we use Google APIs

Google APIs are required so that Jarvis can operate on behalf of the authenticated user instead of simulating or scraping web sessions. Access is limited to features that the user has asked the assistant to handle.

API / Service	Primary use inside Jarvis	Examples
Gmail API	Read mailbox state, draft, send, reply, label, and organize email on user request.	Summarize unread mail, reply to a thread, create drafts, send messages.
Google Calendar API	Inspect availability, list calendars, create or update events, and coordinate schedules.	Check free time, create meetings, patch event details, list user calendars.
Google Drive API	Support file creation, file lookup, and sharing flows for user-selected Drive content.	Work with documents the user created with Jarvis or explicitly shared with Jarvis.
Google Docs API	Create and modify text documents used for notes, plans, reports, drafts, and collaboration.	Create a brief, update a proposal, read a document shared with the assistant.
Google Sheets API	Read, append, and update spreadsheet values for structured operational work.	Update trackers, append rows, inspect a planning sheet, clear a range.
Google Slides API	Create and modify presentations used for user work products.	Create decks, update slide content, inspect a presentation shared with the assistant.

How access works

The product flow is designed to make ownership and authorization clear. The user chooses the Google account to connect and can disconnect it later.

User starts the connection

The user opens the Jarvis connection flow and is sent to Google's consent screen. Jarvis does not ask the user for a Google password in its own forms.

User grants explicit scopes

Google shows the scopes requested by Jarvis. The user decides whether to approve them for the connected assistant account.

Jarvis stores delegated access

After approval, Jarvis stores the resulting delegated access required to perform future actions on behalf of that same user-controlled account.

User control and reviewer notes

This product is meant to satisfy a user instruction loop, not to build a background data lake. The account owner can revoke access at any time through Google account permissions or through the product connection settings.

What Jarvis does

User-authorized actions only Direct Google API integration Dedicated assistant accounts supported Revocation supported

Performs tasks requested by the user.
Works with content created by the user or shared with the connected assistant account.
Uses API access to avoid brittle web scraping flows where possible.
Supports productivity use cases such as email, calendar, writing, spreadsheets, and decks.

What Jarvis does not do

No ad targeting No resale of Google data No hidden scraping of personal accounts No unrelated model training on Google data

Does not sell user Google data to third parties.
Does not request Google passwords inside Jarvis forms.
Does not use connected Google data for advertising.
Does not access accounts that were not explicitly authorized by their owner.

Compliance note

Use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.