Privacy Policy

Agentic Research is a research toolkit that connects AI coding agents you run (Claude Code and OpenAI Codex) to your Google account through connector programs that run on your own computer or computing-cluster account. This policy explains what Google data those connectors access, how it is used, where it is stored, and who receives it.

Google Data We Access

With your consent, the local Gmail and Google Workspace connectors request the permissions below. Gmail is authorized separately from Workspace. The Workspace permissions listed are the defaults; a narrower configured grant limits the actions available to the connector. Scope names below use the prefix https://www.googleapis.com/auth/.

• Gmail, read-only (gmail.readonly): message content, headers, threads, labels, and attachments. The connector cannot send, modify, or delete email.
• Google Drive (drive): file names, metadata, and contents, with the ability to create, edit, move, share, and delete files.
• Google Docs, Sheets, and Slides (documents, spreadsheets, presentations): reading and editing those files.
• Google Calendar (calendar): reading calendars, their settings, and events, and creating, updating, or deleting calendars and events.
• Your Google account email address, to show which account is connected.

How We Use It

Google data is used to carry out requests you give your AI agent, such as finding an email, summarizing a document, or updating a spreadsheet. The local MCP connectors read or change Google data when the agent calls their tools. A connector may also contact Google during authorization, account-status checks, and token refresh. The optional Gmail checker runs independently of an agent session. It periodically searches for matching messages and records message IDs and a latest summary, which can include From, Subject, and Date headers. It does not send email or invoke an AI agent when new mail arrives.

Google data is not sold, not used for advertising, and not used by Agentic Research to develop, improve, or train generalized artificial-intelligence or machine-learning models.

Storage and Security

OAuth client credentials, sign-in tokens, and connector settings are stored on the computer or cluster account where you run Agentic Research. The default location is .research/mcp/gmail/ and .research/mcp/google-drive/ inside the installation; registered projects can use a configured shared state location. On supported Unix systems, managed credential files use owner-only file permissions. These are local credential files, not a developer-hosted token store. The local connectors communicate with Google's APIs over encrypted HTTPS connections. There is no developer-operated Agentic Research backend receiving these tokens or Google data in normal operation.

Sharing

Content returned to your agent may be transmitted to the AI provider configured in that client, such as Anthropic for Claude Code or OpenAI for Codex, to perform your requested task. That provider processes it under the terms, privacy policy, and account settings applicable to your service. If you ask the agent to share a file or place content in a shared document or calendar, the selected recipients may also receive it through Google. Agentic Research does not otherwise send your Google data to the developer or to advertising or data-broker services.

Limited Use

Agentic Research'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.

Retention and Deletion

Credentials, tokens, and the Gmail checker's state remain in your configured local storage until you delete them. The checker overwrites its ID snapshot and latest summary after successful checks rather than keeping a mailbox database. Check output can also be captured in terminal, service-manager, or batch-job logs. Content you ask an agent to retrieve or download may remain in local files or agent conversation history.

1. Stop any running Gmail checker and agent sessions using the connectors.
2. Revoke the relevant OAuth app grants from your Google Account connections page. If you authorized multiple Google accounts or OAuth apps, revoke each relevant grant.
3. Delete the saved credentials, tokens, and checker state from the configured mcp/gmail/ and mcp/google-drive/ directories. Their default parent is .research/; check your installation if shared state is configured.
4. Remove any downloaded files, exported data, logs, and agent history you no longer need. Copies retained by your AI provider follow that provider's retention and deletion controls. Revoking access does not delete files or events in Google.

This Website and Other Integrations

These public information pages do not request Google sign-in and contain no analytics scripts, tracking cookies, or contact forms. GitHub Pages hosts the website and may process technical request information under the GitHub Privacy Statement. This policy covers the local Gmail and Google Workspace connectors described above. Other optional integrations and separately configured hosted services have their own data flows and provider policies.

Changes and Contact

Changes to this policy are published on this page with a new effective date. Questions or requests: changzeng@umass.edu.