Privacy policy
Last updated: 1 October 2026
This policy explains what data One API for Agents ("we", "us") collects, how we use, store, share and delete it, and the choices you have. One API for Agents is operated by SALEEH K. Questions and requests: privacy@oneapiforagents.com.
Summary
- We access Google data only when a workspace member, an API key or an AI agent the workspace approved makes a call. There is no background syncing and no website monitoring.
- Google Search Console and Google Analytics access is read-only. Google Sheets and Google Docs access is read and write: we can read, create and edit spreadsheets and documents, but only the ones a caller names by ID or URL or creates, and only when the caller has read-write access.
- We do not sell Google user data, use it for advertising, or use or transfer it to develop, improve or train generalized or non-personalized AI or machine-learning models. We do not run AI models on your data ourselves.
- OAuth tokens are encrypted. Tokens, keys and auth headers are removed from everything we log.
- Each call is logged with a copy of its request and response, including the Google data returned (for example spreadsheet cells or document text), so the workspace can audit what its agents did. These copies are deleted after 30 days.
- You can disconnect an account at any time, and ask us to delete your data. We complete deletion requests within 30 days.
Who this policy covers
- Workspace users: people who sign in to the dashboard at https://app.oneapiforagents.com and belong to a workspace, such as an agency team or a solo developer.
- Connecting users: people who connect their own Google or Microsoft account, either in the dashboard or through a connect link a workspace sent them. A connecting user does not need an account with us.
What we collect
Account and workspace data
- When you sign in with Google: your name, email address and profile picture, from the
openid,emailandprofilescopes. When you sign in with an emailed code or link: your email address. - Workspace data you enter: workspace name, member roles, client names, connect links, API key names and agent approvals. API keys are stored only as a hash.
Google user data
When a Google account is connected, Google gives us OAuth tokens that let us call Google APIs for that account. A Google scope sets the most an app could do; the table below also says what One API for Agents actually does with each one. We request a product's scope only when someone chooses to connect that product, and Google shows each scope on its consent screen.
| Scope | Data | What we do with it |
|---|---|---|
openid, https://www.googleapis.com/auth/userinfo.email (email) |
The Google account's ID and email address. | Sign you in to the dashboard, and show which Google account a connection belongs to so a workspace can tell connections apart. Requested at sign-in and in every connect flow. |
https://www.googleapis.com/auth/userinfo.profile (profile) |
Your name and profile picture. | Show who is signed in to the dashboard. Requested only at dashboard sign-in, not when connecting a product. |
https://www.googleapis.com/auth/webmasters.readonly |
Search Console properties, search performance (queries, pages, clicks, impressions, CTR, position), sitemaps and URL inspection results. | Read only. List properties and sitemaps, run search analytics queries and inspect URLs when a caller asks. We never change Search Console settings or data. |
https://www.googleapis.com/auth/analytics.readonly |
Analytics account and property lists, property metadata, and report data (including realtime reports). | Read only. List accounts and properties and run reports when a caller asks. We never change Analytics settings or data. |
https://www.googleapis.com/auth/spreadsheets |
Spreadsheet metadata (title, tabs) and cell contents. | Read and write. Read ranges and tabs; append rows; update and clear cell ranges; create spreadsheets; manage tabs and apply structural changes such as adding, renaming or deleting tabs, formatting and sorting. Google lets this scope reach every spreadsheet the account can open, but we only touch a spreadsheet a caller names by ID or URL, or one it created. We cannot list or search your Google Drive. |
https://www.googleapis.com/auth/documents |
Document metadata (title, tabs, revision) and contents. | Read and write. Read documents (returned as text or markdown); create documents; append, insert and replace text; and apply other Google Docs edit requests, such as deleting a range of text or formatting it. As with Sheets, we only touch a document a caller names by ID or URL, or one it created, and we cannot list or search your Google Drive. |
Write actions in Sheets and Docs run only for a caller with read-write access: an API key created as read-write, or an AI agent that a workspace member approved with read-write access. Read-only keys and agents are refused. Search Console and Analytics have no write actions at all.
Some workspaces connect Google products with a service account instead of OAuth. In that case the owner of the property, spreadsheet or document grants the service account access in Google's own settings, and can remove it there at any time.
Other providers
- Bing Webmaster Tools: a Bing API key you paste, or a Microsoft sign-in with read-only access. We read site, query, page and crawl data from Bing.
- Workspace databases: an agent with read-write access can create databases in its workspace and save rows into them, including results of calls such as Google data. These databases belong to the workspace.
Call logs
For every API or MCP call we record:
- A summary: the time, workspace, client, connection, provider, endpoint or tool, who made the call (member, API key or agent), status, latency, cost and whether it was served from cache.
- A copy of the request and the response. This includes the Google content that was returned or written: for example Search Console rows, Analytics report rows, spreadsheet cell values and document text. Before storing, we remove tokens, API keys, authorization headers and every credential of the connection used. We do not remove content.
Workspace members can view their workspace's call logs, limited to the clients they can see.
Cached responses
When a caller sets max_age on a read call, we keep that response in a cache so a repeated identical call can be answered without calling Google again. Cached responses are stored per workspace and per connection, can include Google content such as spreadsheet cells or document text, and are deleted automatically after at most 7 days. Calls that write are never cached, and calls without max_age are not cached.
Technical data
Our hosting provider, Cloudflare, processes IP addresses and request metadata to serve the service and protect it from abuse. The marketing site does not use advertising or analytics cookies. The dashboard uses a session cookie to keep you signed in.
How we use Google user data
We use Google user data only to provide the features the workspace requested:
- to read or write Google data when a workspace member, an API key or an approved AI agent makes a call, and return the result to that caller;
- to show which Google account is connected and whether the connection still works;
- to keep the call log described above, so the workspace can audit what its agents did;
- to cache a read response, when the caller asks for it, for at most 7 days;
- to keep the service secure, for example by investigating abuse.
We do not access Google user data at any other time. There is no background syncing and no monitoring of websites.
How Google data reaches AI tools
A workspace can connect AI tools such as Claude, ChatGPT, Codex or Cursor through our MCP server or REST API. This is how it works:
- Who authorizes it. A workspace member approves each AI agent through an OAuth consent screen, choosing the workspace, read-only or read-write access, and which clients the agent can see. API keys are created by workspace members with the same choices. Members can disconnect an agent or revoke a key at any time.
- What the agent receives. Only the data it asks for in a call, from connections in its workspace and clients, such as Search Console query rows, an Analytics report, spreadsheet cells or document text.
- Why. So the agent can do the task the workspace member gave it, such as writing an SEO report or updating a spreadsheet.
- What happens next. The AI tool runs on its provider's systems, and data returned to it is handled under the agreement between the workspace and that provider. We have no arrangement with any AI provider to share data with it for its own purposes. If your AI tool lets you opt out of model training, we recommend doing so.
We do not send Google user data to any AI or machine-learning service on our own initiative, and we do not use or transfer it to develop, improve or train generalized or non-personalized AI or machine-learning models.
Google API Services User Data Policy
One API for Agents' 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:
- We use Google user data only to provide and improve user-facing features that are prominent in our product, as described above.
- We transfer Google user data to others only as needed to provide those features (see Sharing), for security purposes, to comply with applicable law, or as part of a merger, acquisition or sale of assets, and in that case only after obtaining your explicit prior consent.
- We do not use or transfer Google user data for serving advertisements, including retargeting, personalized or interest-based advertising.
- We do not sell Google user data, and do not use it to determine credit-worthiness or for lending purposes.
- We do not use or transfer Google user data to develop, improve or train generalized or non-personalized AI or machine-learning models.
- We do not allow humans to read Google user data unless you give us affirmative permission for a specific item (for example, a support request), it is necessary for security purposes such as investigating abuse, or it is required to comply with law.
Sharing
- The workspace you connected to. When you connect an account, its data becomes available to that workspace's members, API keys and AI agents, within the client limits the workspace sets. If you connected through a connect link, that means the organization that sent you the link.
- AI tools approved by the workspace, as described in "How Google data reaches AI tools".
- Service providers that process data on our behalf, under contract: Cloudflare (hosting, databases, storage, caching and email delivery). They may not use the data for their own purposes.
- Legal reasons: when required by law, or to protect the rights and safety of our users and the public.
- Business transfers: in a merger, acquisition or sale of assets, Google user data is transferred only with your explicit prior consent.
We do not sell personal data.
Security
- OAuth tokens and service-account keys for connections are encrypted with AES-GCM before they are stored. The encryption key is held in Cloudflare Workers Secrets and never leaves it. Google sign-in tokens are also stored encrypted.
- Credentials are decrypted in memory only for the length of one call, and are never returned by our API or written to logs.
- Stored request and response copies have tokens, keys and auth headers removed.
- API keys are stored hashed and shown once. Every query is scoped to the workspace and to the clients the caller may see.
- All traffic uses TLS.
No system is perfectly secure. If we learn of a breach that affects your data, we will notify you as required by law.
Retention
| Data | Kept for |
|---|---|
| OAuth tokens and keys for a connection | Until the connection is disconnected, then deleted. |
| Call log copies of requests and responses, including Google content | 30 days, then deleted automatically. |
| Call log summaries (no request or response content) | 3 months, then deleted automatically. |
| Cached responses | At most 7 days, then deleted automatically. |
| Workspace databases | Until the workspace deletes them, or the workspace is deleted. |
| Connection records (account email, provider, granted scopes, status), account and workspace data | While the account or workspace exists. Deleted within 30 days of a deletion request, except where law requires us to keep records. |
| Sign-in sessions | Up to 30 days. |
Your choices and deletion
- Disconnect an account. In the dashboard, disconnect the connection. We delete its stored OAuth token right away. When the last product using a Google account is disconnected, we also ask Google to revoke our access. If the same Google account is still connected in another workspace, that grant stays in place for the other workspace; this workspace's copy of the token is still deleted.
- What disconnecting does not delete. Disconnecting deletes credentials, not content already stored. Call log copies expire after 30 days and cached responses after at most 7 days (they can no longer be served once the connection is disconnected). Rows an agent saved into a workspace database stay until the workspace deletes them. To delete any of these sooner, email us.
- Revoke from Google. Anyone who connected a Google account can remove our access at any time at myaccount.google.com/permissions. This removes access for every workspace that used it. Affected connections stop working and are shown as expired.
- Delete your data. Email privacy@oneapiforagents.com to delete your account, a workspace, or the data stored about a Google account you connected, including call logs, cached responses, workspace databases and connection records. You don't need an account with us to ask. We may ask you to confirm you control the account, and we complete deletion within 30 days and confirm when it's done.
- Depending on where you live, you may have rights to access, correct, export or delete your personal data, or to object to its processing. Email us to use them. You may also complain to your data protection authority.
Children
One API for Agents is not directed to children under 16, and we do not knowingly collect their data.
International transfers
We use Cloudflare's global network, so data may be processed in countries other than yours. Where required, we rely on appropriate safeguards such as standard contractual clauses.
Changes
We will post changes here and update the date above. For material changes we will notify workspace owners by email before they take effect. We will not use Google user data in a new way without asking for consent where the Google API Services User Data Policy requires it.
Contact
SALEEH K · privacy@oneapiforagents.com