Privacy Policy

Effective date: October 3, 2026

1. Introduction

FGAC.ai (“FGAC”, “we”, “us”) is a permissions layer between the AI agents you choose and your Google account. You connect your Google account to FGAC once, create agent profiles with the rules you want, and point your agents at FGAC instead of at Google. Every call an agent makes passes through FGAC’s MCP server or REST proxy, where FGAC checks it against your rules before anything reaches Google, and relays only what the rules allow back to the agent.

This policy explains what information FGAC collects, how we use, share and protect it, how long we keep it, and the choices you have. It covers the website at fgac.ai, the FGAC dashboard, the FGAC MCP server and REST proxy, and the emails FGAC sends. It does not cover the AI agents, assistants or other services you connect to FGAC (see Section 5) or Google’s own services, each of which has its own privacy policy.

2. Google API Services User Data Policy

FGAC.ai’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 plain terms, for information FGAC receives from Google APIs, we:

Use it only to provide and improve the user-facing features described in this policy: relaying it to the agents you connect, enforcing the rules you set, and showing you what you have configured.
Do not use it for advertising, and never sell it.
Do not transfer it to anyone except the agent you connected, the service providers in Section 6 that process it on our behalf, as required by law, or as needed to investigate abuse and protect the security of the service.
Do not let any person read it, except when you ask us to (for example, to investigate a support request you raise), when it is necessary for security purposes such as investigating abuse, when the law requires it, or when it has been aggregated and de-identified for internal operations.
Do not use it to develop, improve or train generalized artificial-intelligence or machine-learning models. FGAC itself runs no AI models over your data. The only AI involved is the agent you choose to connect (Section 5).

3. Information we collect

3.1 Account information

When you sign in with Google, our authentication provider, Clerk, receives your Google basic profile: your name, email address and profile picture. FGAC’s own database stores your email address and the identifiers that tie your FGAC account to Clerk. Clerk stores the profile and the Google OAuth tokens (access and refresh tokens) that FGAC uses to call Google on your behalf. FGAC’s database never stores your Google tokens.

3.2 Google user data, permission by permission

FGAC asks Google for the permissions below. The first three are requested when you sign in. The full Google Drive permission is requested only if you opt in, and only from accounts enrolled in the Drive folder-permissions beta.

Permission	What it lets FGAC reach	How FGAC uses it	What FGAC keeps
PermissionBasic profile `openid`, `email`, `profile`	What it lets FGAC reachYour name, email address and profile picture.	How FGAC uses itTo create and identify your FGAC account, show it to you, and contact you about the service.	What FGAC keepsYour email address and account identifiers, for as long as you have an account. Clerk holds the name and picture.
PermissionGmail `gmail.modify`	What it lets FGAC reachReading, searching, labelling, archiving and trashing the messages, drafts and attachments in your mailbox, and sending email from it. FGAC never permanently deletes mail: delete and batch-delete requests are refused whatever your rules say, and trashing is reversible.	How FGAC uses itOnly when an agent you connected makes a call. FGAC fetches what the agent asked for with your Google token, applies your rules in memory (for example, hide messages matching a pattern, or allow sending only to recipients you approved) and returns the allowed result to that agent. The dashboard also reads your label names, live, to populate the rule editor.	What FGAC keepsNothing from your mail: no message bodies, subjects, senders, recipients or attachments. FGAC keeps the rules you create (which may name a label or a recipient address) and the request metadata in Section 3.4.
PermissionGoogle Drive, per file `drive.file`	What it lets FGAC reachOnly the files you pick in the Google Picker and the files your agent creates or copies through FGAC: Google Sheets, Docs, Slides and other Drive files. FGAC can read, edit, comment on and copy those files and create new ones. It cannot see the rest of your Drive.	How FGAC uses itTo relay reads and edits to your agent under the per-file setting you chose (Read, Read & write, or Blocked), and to show the file’s name on the dashboard and on approval pages.	What FGAC keepsThe file’s id and title and the setting you chose. Never its contents.
PermissionGoogle Drive, full (opt-in beta) `drive`	What it lets FGAC reachAll of your Google Drive files, including shared drives and files shared with you (Google describes this permission as “See, edit, create, and delete all of your Google Drive files”). FGAC asks for it only when you click Enable full Drive access on an agent profile, a control shown only to beta accounts. Agents still cannot permanently delete anything through FGAC.	How FGAC uses itTo list your folders and files so the dashboard can show your Drive as a tree and let you search it; to read a file’s metadata (id, name, type, parent folders, shared drive, whether you own it) so FGAC can work out which folder setting applies when your agent reaches a file; to filter the file listings your agent requests down to what your settings allow; and to relay allowed reads and edits to your agent.	What FGAC keepsThe ids and names of the folders and files you set a permission on. File metadata is cached in server memory for up to 10 minutes while FGAC resolves folder settings, then discarded. File contents are never stored.

3.3 Configuration you create

Your agent profiles and proxy keys (a label, the key itself, an optional expiry, and the profile’s Drive default); your access rules (a name, a type, a pattern that may contain email addresses or Gmail label ids, and the id and title of a target file or folder); delegations you grant or receive (which FGAC user may reach whose mailbox); the agent connections you approve (the connecting client’s id and name, such as “claude-desktop”, and any nickname you give it); and the approvals you grant through approval links.

3.4 Usage and technical data

Request metadata.For every call an agent makes through FGAC we record which tool or endpoint was called, when, how long it took, whether it was allowed, denied or failed and why, the mailbox address the call used (and any mailbox address the agent asked for that the key could not use), the ids and types of files involved, the agent’s client name and user-agent, and any error code or message Google returned. We never record message bodies, subjects, attachments or file contents.
Ledgers in our database.Approval requests (the action, the recipient address or file involved, the file’s title when the agent supplied one, and when the request was created, opened and approved); mailbox addresses an agent named that its key could not use; Google grants that stopped working (the mailbox, the reason and when); which notice emails we sent; and notices that bounced (the address and the bounce code).
Website analytics.We use PostHog to record page views, clicks, feature usage and errors on fgac.ai, together with your browser and device type, IP address and the approximate location derived from it. Once you are signed in these events are tied to your FGAC account (Clerk id, email address and name). Error reports contain the error’s type, message and stack trace, never your Google data. PostHog also evaluates feature flags (such as the Drive beta) using your Clerk id and email address.
Session replay.PostHog records how you interact with fgac.ai pages: mouse movement, clicks, scrolling, the page structure and browser console messages. Text you type into form fields is masked in your browser before anything is sent. What the dashboard shows you (rule names, file titles, mailbox addresses, label names) can appear in a replay; your Gmail and Drive contents cannot, because FGAC’s website never displays them. Replays are kept for 30 days.
Server logs. Our hosting provider, Vercel, keeps request metadata and error messages for a short rolling window for operations and debugging.

3.5 Cookies and similar technologies

Clerk sign-in cookies (__session, __client_uat and related) keep you signed in. They are strictly necessary.
fgac_last_account and fgac_prev_account (7 days) remember which FGAC account was last signed in on this browser, as a Clerk id only, so that a second account you create can be offered a one-click delegation to the first.
fgac_approval_wall (30 minutes) remembers which approval link you were sent to before signing in, so FGAC can send you back to it afterwards.
fgac_clerk_bounce (5 minutes) detects sign-in redirect loops.
PostHog (ph_… cookie and local storage) holds the analytics identifier and session described in Section 3.4.
The Google Picker is Google’s own component, loaded in your browser when you choose files; Google’s cookies and privacy policy apply to it.

FGAC uses no advertising cookies and no third-party advertising technology.

3.6 Information you give us directly

If you use the contact-sales form on the pricing page, we receive the email address, company, team size and needs you enter; FGAC emails you a confirmation with a copy to our sales inbox and records the lead in PostHog. If you email us, we keep the correspondence to answer you.

4. How we use information

To provide the service: authenticate you, relay the calls your agents make to Google, enforce your rules, and show you your profiles, rules, approvals and connections.
To keep you informed: transactional emails about an approval you have not acted on or a Google connection that stopped working, sent from FGAC’s own mailbox and never through your Google account, and answers to your support requests.
To keep the service secure: refuse agents presenting revoked keys, detect abuse and automated scanning, verify webhooks, and investigate incidents.
To understand and improve the product: analytics and error tracking in Section 3.4, feature flags for betas such as Drive folder permissions.
To comply with law and enforce our Terms of Service.

5. AI agents and MCP clients you connect

FGAC exists to hand your Google data to the agent you chose, within the rules you set. Agents connect in two ways: through an OAuth connection, where an MCP-compatible client (for example Claude.ai, Claude Code, the Claude desktop app, ChatGPT, Cursor, Grok, or any other MCP client) signs in to FGAC and is attached to your Default Profile so it can start immediately; or through a proxy key you create on an agent profile and paste into the agent’s configuration.

On every call, FGAC fetches the data from Google with your Google grant, applies the rules of the profile the agent is attached to, and returns the allowed result to that agent. From that point the data is in the agent’s hands: it may appear in your conversation, be stored in the agent’s history, or be processed by the agent’s provider. What the provider does with it is governed by that provider’s terms and privacy policy, not by this one, and FGAC has no control over it.

You decide which agents to connect. In the dashboard you can move a connection to a profile with narrower rules, block it, revoke a proxy key, or remove a connection; the agent is refused from that moment. FGAC does not run AI models over your data and is not itself an agent.

You can also delegate your mailbox to another FGAC user from the Accounts page. That user’s agents then reach your Gmail under the rules they configure; your Google token stays with your account and is never given to them, their calls are recorded under both accounts, and you can revoke the delegation at any time, after which access stops immediately.

6. Sharing and service providers

We do not sell personal information and do not share it for advertising. We share information only as follows.

Service providers (sub-processors) that process data on our behalf under their own data-processing terms:

Provider	Role	What it receives
ProviderGoogle	RoleGmail, Drive, Sheets, Docs and Slides APIs; sign-in; the Google Picker.	What it receivesThe calls FGAC makes with your grant, and the files you pick.
ProviderClerk	RoleAuthentication, storage of your Google OAuth tokens, and the OAuth server that MCP clients connect through.	What it receivesYour profile, Google tokens, sessions, and the registrations of the clients you connect.
ProviderNeon	RolePostgreSQL database hosting.	What it receivesThe account, configuration and ledger data in Sections 3.1, 3.3 and 3.4.
ProviderVercel	RoleApplication hosting, edge network and runtime logs.	What it receivesAll traffic to fgac.ai, including agent calls in transit, and the server logs in Section 3.4.
ProviderPostHog	RoleProduct analytics, error tracking, session replay and feature flags.	What it receivesThe analytics, error and replay data in Section 3.4.

Others, at your direction or as required:

the AI agents and MCP clients you connect (Section 5), including those of anyone you delegate your mailbox to;
a partner application, if you connected FGAC through that partner’s own “connect” flow: FGAC may send it notifications containing only Gmail message ids, never content, so the partner can fetch the message through FGAC under your rules;
law enforcement or other parties when required by law, or to protect the rights, safety and security of FGAC, its users or the public;
a successor, if FGAC is involved in a merger, acquisition or sale of assets, in which case this policy continues to apply and you will be notified.

Our service providers host data in the United States. If you use FGAC from elsewhere, your information is transferred to and processed there.

7. Security

Encryption. All traffic to fgac.ai, to Google and to our providers travels over HTTPS (TLS). Our database, authentication and analytics providers encrypt stored data at rest.
Token custody. Your Google tokens are held by Clerk and used server-side. They are never written to FGAC’s database, and they are never given to an agent; agents hold only an FGAC proxy key or an FGAC OAuth token that FGAC can revoke. The one place a token leaves our servers is your own browser, to open the Google Picker.
Least privilege by default. Google Drive access is per file unless you opt in to the full Drive permission; sending email is denied until you approve a recipient; a new proxy key reaches only the mailboxes you attach to it; permanent deletion is refused everywhere.
Nothing stored that need not be. Gmail and Drive contents are processed in memory and discarded when the call completes.
Access controls. Every dashboard action requires your Clerk session; approval links are signed and only work for the signed-in owner; incoming webhooks are signature-verified; access to production systems is limited to the people who operate FGAC.
No system is perfectly secure. If we learn of a breach affecting your data, we will notify you as the law requires.

8. Retention, deletion and revoking access

Data	How long FGAC keeps it
DataGmail and Google Drive contents	How long FGAC keeps itNot stored. Held in memory only while a call is in flight.
DataDrive file metadata (full-Drive beta)	How long FGAC keeps itUp to 10 minutes in server memory, then discarded.
DataGoogle OAuth tokens	How long FGAC keeps itHeld by Clerk until you revoke FGAC’s access in your Google Account, remove the Google connection from your FGAC account settings, or delete your FGAC account.
DataAccount, profiles, keys, rules, delegations, connections	How long FGAC keeps itWhile your account exists and until you delete them. Deleted rules are removed immediately. Revoked keys and delegations are kept as revoked records so that an agent presenting an old key is refused.
DataApproval, connection-failure, refusal and bounce ledgers	How long FGAC keeps itWhile your account exists; they are what keep FGAC’s transactional emails to one per event.
DataAnalytics events (PostHog)	How long FGAC keeps itUp to seven years, under PostHog’s standard retention.
DataSession replays (PostHog)	How long FGAC keeps it30 days.
DataServer logs (Vercel) and database restore history (Neon)	How long FGAC keeps itA short rolling window of days.

Revoking access

Revoke Google access at any time from your Google Account at myaccount.google.com/permissions. FGAC’s token stops working immediately and every agent call on that mailbox is refused until you reconnect.
Control your agents in the dashboard: narrow a profile’s rules, block or remove a connection, revoke a key, revoke a delegation, or withdraw the full Drive permission by reconnecting with the per-file permission only.

Deleting your account

When you delete your FGAC account, Clerk notifies FGAC and FGAC immediately revokes all of your proxy keys, revokes every delegation you granted or received, and removes the access those delegations provided; your Google tokens are deleted with the Clerk account. Our database keeps an inert record of the account (your email address and identifiers) together with its revoked keys, rules and ledgers, so that a later sign-up with the same address starts fresh and cannot inherit the old access, and for security audit. To have that record erased as well, email support@fgac.ai from the address on the account; we will erase or anonymise it within 30 days of verifying the request unless the law requires us to keep it.

9. Contact

Questions about this policy and requests about your data (access, correction, export or deletion) go to support@fgac.ai. We verify requests against the address on your account. FGAC.ai operates from the United States.

← Back to Home