Privacy Policy

Last updated: July 6, 2026

GPTSheet is built around a simple promise: your data and API keys don't touch our servers. This page explains exactly what we store, where, and why.

What we collect

• Email address. When you purchase a license, Stripe collects your email at checkout. We store it alongside your license key so we can deliver the key and bind it to your Google account.
• License key + bound Google account email. When you activate your license inside the add-on, we record which Google account it was bound to so the key cannot be re-used by someone else.
• Server logs. Our license-verification endpoint logs request IPs and timestamps for at most 30 days, used only to debug failures and detect abuse.

What we do not collect

• The contents of your spreadsheets.
• Your prompts to OpenAI, Anthropic, or Google Gemini.
• The output of any LLM call you make.
• Your LLM provider API keys. These are stored locally in your browser (sidebar tools) or in Google's per-user properties storage (cell formulas). They never transit our servers.
• Analytics, tracking pixels, or cookies on the marketing site beyond what Vercel sets automatically for hosting.

Where your data lives

• Your license key + bound email: Supabase (Postgres), in the EU/US region you visit closest.
• Your provider API keys: Your browser's localStorage (for the sidebar) and Google's PropertiesService (for cell formulas). Neither is visible to us.
• Payment info: Stripe. We never see your card number.
• License delivery emails: Sent via Amazon SES.

Google user data

GPTSheet requests a small set of Google OAuth scopes so the add-on can work inside your spreadsheet. Here is exactly what each grants and how the data is handled:

• Spreadsheet access (current document only) — used to read the cells you point a formula or the agent at, and to write results back. Spreadsheet contents never leave your Google account except for the calls you configure to your own LLM provider or data sources.
• Google Analytics, Search Console, YouTube Analytics (read-only) — used only when you connect one of these sources and run a report. The report data is written directly into your spreadsheet. We never receive, store, or process it on any server we control.
• Drive (per-file) — used only to save images generated by =AI_IMAGE as files the add-on itself creates. GPTSheet cannot see any other file in your Drive.
• Sidebar display, external requests, and triggers — Apps Script runtime scopes that let the add-on show its sidebar, call the APIs you configure, and refresh your scheduled imports. They grant no access to your personal data.

Your Google OAuth tokens are issued to and held by Google's own Apps Script runtime. They are never transmitted to, stored by, or retrievable by us — even we cannot access them.

How we protect your data

• Encryption in transit. Every connection — to our license server, to Google APIs, and to your LLM provider — uses HTTPS/TLS 1.2 or higher. No data is ever sent in plaintext.
• Encryption at rest. The one thing we do store (your license key and bound email) lives in Supabase-managed Postgres, encrypted at rest with AES-256.
• Access controls. The license database accepts connections only from our verification functions using service-role credentials; row-level security blocks all other access. No human reads it except to resolve a support request you initiate.
• Sensitive data isolation. Your Google user data (spreadsheet contents, analytics reports) is processed entirely inside Google's Apps Script runtime and your browser. It has no path to our infrastructure — protection is architectural, not just policy.
• Credential storage. Your LLM and connector credentials live only in your browser's localStorage and Google's per-user PropertiesService — both scoped to you and unreadable by us.
• Minimal retention. License-server request logs are kept for at most 30 days, then deleted automatically.
• Incident response. If a breach ever affects the limited data we hold, we will notify affected users by email without undue delay.

Data retention and deletion

• Google user data: retained by us for zero seconds — it never reaches our systems, so there is nothing for us to delete.
• License record (key + bound email): kept for as long as your lifetime license is active. Email support@gptsheet.com to have it deleted at any time (this permanently deactivates the license).
• Revoking GPTSheet's access: you can revoke the add-on's Google permissions at any time at myaccount.google.com/permissions, or uninstall it from the Extensions menu. Credentials stored in your browser can be cleared from the add-on's API Keys page or by clearing site data.

Limited Use disclosure

GPTSheet'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: data obtained through Google APIs is used only to provide the spreadsheet features you invoke, is never used for advertising, is never sold, and is never transferred to third parties except at your explicit direction (e.g., the LLM provider you configure), for security purposes, or to comply with law.

Third parties we use

• Stripe — payment processing.
• Supabase — license storage and verification.
• Amazon Web Services (SES) — license-delivery email.
• Vercel — hosting for the marketing site and docs.
• Google — Apps Script runtime, OAuth, Workspace Marketplace listing.

We don't sell or share your data with any other party.

What GPTSheet sends to LLM providers

When you run a formula or use the sidebar, your prompt (and any cell values you reference) goes directly from your browser or from Google's Apps Script runtime to the LLM provider whose API key you configured. We have no visibility into that traffic. Refer to the privacy policies of:

• OpenAI
• Anthropic
• Google (Gemini)

Your rights

You can request deletion of your license record at any time by emailing support@gptsheet.com. Note that deleting your record means your license will stop working; this is permanent.

Children

GPTSheet is not intended for use by anyone under 13.

Changes

If we materially change what we collect, we'll update this page and bump the "Last updated" date.

Contact

Questions: leepun@gmail.com.