法律

隐私政策

Exactly what we collect, who we share it with, and how to turn any of it off.

Effective October 25, 2026·v4.1

01Overview

This policy covers the Google Apps Script Copilot Chrome extension, the gscopilot.com / home.gscopilot.com website, and our backend services. We do not sell your data. We use the contents of your Apps Script code and your AI chat messages only to provide the service to you: generating the responses you ask for, keeping your chat history, chat summaries and project memory, and diagnosing problems through our logs. We never use them for advertising. GS Copilot's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

02Account information we collect

When you create an account we collect your name, email address, and authentication identifiers. Accounts are stored and authenticated through PocketBase, our backend user-management system, hosted on infrastructure we control. If you sign in with Google, we receive your Google account's name, email, and profile picture from Google's OAuth flow — we do not receive your Google password.

03Billing information

Payments and subscriptions are processed by LemonSqueezy, our merchant of record. When you subscribe or make a purchase, LemonSqueezy collects your payment details (card number, billing address) directly — we never see or store your full card number. We receive your subscription status, plan tier, and order history from LemonSqueezy so we can grant access to paid 功能s. See LemonSqueezy's privacy policy at lemonsqueezy.com/privacy.

04Your prompts and code — how they're handled

This depends on which mode you use. On the default Cloud/免费 plan, when you send a prompt or select code for the AI to work on, that content is sent from your browser to our own backend (a Cloudflare Worker at ai.gscopilot.com), which forwards it to the underlying AI model provider to generate a response, then returns the result to you. On the Lifetime + BYOK plan, when you connect your own API key, your prompt and code are relayed from our Worker to the AI provider you configured, using your key. In both modes, your saved chats keep your prompts, any code included in the conversation, the AI's responses and tool results, so you can return to them. We also keep a short summary of each chat and project memory notes (facts about a project that carry over between chats), which can contain information from your conversations. Older parts of a long conversation may be condensed by an AI service and cached for up to one hour. Chat summaries, project memory and condensing use our own AI providers, including on the BYOK plan. We do not use your prompts or code to train any model.

05Which AI providers may process your content

Depending on your plan and model selection, your prompts/code may be processed by one or more of: OpenAI, Anthropic, Google (Gemini), OpenRouter, Fireworks AI, DeepSeek, Mistral (Codestral), Together AI, or DeepInfra — or, for BYOK users, any OpenAI-compatible provider you configure, including local runtimes like Ollama or LM Studio that never leave your machine. For AI-powered search 功能s, we may also send limited query data to search providers such as Jina AI. Each provider processes this data under its own terms.

06Product analytics — PostHog

We use PostHog, a third-party analytics provider, to understand how the extension is used and to fix bugs — for example, which 功能s you open, onboarding progress, and plan/usage status. This data is sent from your browser through PostHog's reverse proxy at t.gscopilot.com. We do not send the contents of your prompts, your code, your files, or your billing details to PostHog — the authentication, billing, and chat/prompt areas of the product are explicitly excluded from analytics capture.

07Session replay

Our codebase includes a session-replay capability (built on PostHog) that can record a visual, masked reconstruction of on-screen activity, intended to help us diagnose UI bugs that are hard to reproduce from a bug report alone. This capability is currently disabled — it is not active in any released version of the extension. If we ever enable it in the future, it will only ever apply to Google Apps Script Copilot's own extension windows (never the Google Apps Script editor page itself), will mask all text and form input before anything is recorded, will fully exclude sensitive areas such as billing, authentication, and chat/prompt content, and we will update this policy and the extension's in-product settings before it goes live.

08Error tracking — GlitchTip

We use GlitchTip, a Sentry-compatible error tracker that we host ourselves at glitchtip.bytelogist.com, to capture crash reports and error diagnostics from the extension, the website and our backend — for example stack traces, the extension version and the error message — so we can fix bugs. We turn off the SDK's default collection of personal data and send only a sample (about 10%) of extension errors. Error messages and diagnostic details can still include parts of what was being processed when the error happened, such as fragments of a prompt, code, an AI response or an error returned by Google or another connected service. We do not intentionally send your account credentials to it. Error reports are not deleted on a fixed schedule; email support@gscopilot.com to request deletion.

09Editor account detection

If you connect Google services (Sheets, Docs, Gmail, Drive, Calendar, etc.) through Google Apps Script Copilot's MCP integrations, the extension detects which Google account is currently signed in on the script.google.com tab you have open, by reading the account indicator already shown in Google's own editor UI — we do not read your document content or any other page data to do this. That detected email address is sent to our backend as a request header so we can warn you, via an in-product banner, if the Google account open in your editor doesn't match the account your MCP connections are using. This detection only runs on script.google.com and is used solely for this account-mismatch check.

10Inline code suggestions

As you type in the Apps Script editor, Google Apps Script Copilot's inline-suggestion 功能 sends the surrounding code context to our backend to generate ghost-text completions and predicted next edits. This is core to the product's function — the code you're actively editing is used to generate the suggestion and is not saved to your chat history or project memory, but our operational logs can contain the prompt and the generated completion (see "Tool and diagnostic logs").

11Tool and diagnostic logs

When the AI agent uses tools — for example, to read a file or run a lint check — we record which tool ran, whether it succeeded, timing, a few selected arguments (such as a file name or search query, up to 200 characters each) and any error message (up to 500 characters). Successful tool results are not stored in these records. Separately, our backend's operational logs on Cloudflare can contain error details returned by Google or other connected services, AI responses, and parts of prompts or code (for example, from inline code suggestions). These operational logs may record requests to our backend. They stay in Cloudflare Workers Logs only, which keeps them for up to 7 days. We use these logs only to run and fix the service. Tool records have no fixed deletion period and are not removed when you delete a chat; email support@gscopilot.com to request deletion.

12Cloud infrastructure

Google Apps Script Copilot's backend runs on Cloudflare Workers, with Cloudflare D1 (database), Cloudflare KV (caching), and Cloudflare Vectorize (semantic search) used to operate the service. Cloudflare processes this data solely as our infrastructure provider.

13MCP / tool connectors — Composio

When you connect third-party tools or other Google services (Sheets, Docs, Gmail, Drive, Calendar, etc.) through Google Apps Script Copilot's MCP integrations, Composio, a third-party MCP infrastructure provider, brokers the OAuth connections and tool calls for those services. The Google Apps Script connection uses GS Copilot's own Google OAuth client directly from our backend (Cloudflare Worker). Composio never receives Apps Script data or Apps Script tokens.

14Google user data we access

When you authorize Google Apps Script Copilot (GS Copilot, shown on Google's consent screen as "Apps Script Copilot") with your Google account, we access only the Google user data needed to provide the 功能s you use: your Apps Script projects (script content and project metadata), deployments, script processes (executions and their logs), and project metrics. We use this data only to give you user-facing 功能s inside GS Copilot, such as reading your code and project files, creating versions and deployments when you ask, and showing execution logs and metrics. We process this data to fulfil your request. Results returned by Google (for example script code, the manifest, and deployment, execution or metrics details) become part of your conversation, so they are saved with your chat history and may be reflected in chat summaries and project memory. Older parts of a long conversation may be cached for up to one hour, and our operational logs can contain error details returned by Google, AI responses and parts of prompts or code (see "Tool and diagnostic logs"), and error reports can contain similar fragments (see "Error tracking — GlitchTip"). See "Data retention" for how long this is kept and how to delete it. We do not sell this data. We share it only with the infrastructure and AI model providers listed in sections 05 and 12, and only to generate the response you asked for. We never use it for advertising. We do not use your Google user data, including your Apps Script project data, deployments, processes and metrics, or your prompts and code, to develop, improve or train any AI or machine-learning model, whether ours or a third party's. GS Copilot's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. For the Apps Script connection, Google refresh and access tokens are encrypted using AES-GCM before being stored in our own account database, used only to keep the connection working by calling Google APIs for your requests and refreshing access, and when you click Disconnect we ask Google to revoke the token and delete the stored token record.

15Cookies & local storage

We use local storage (in your browser and in the extension) to remember your theme, your last-active tab, and your authentication session. We do not use third-party advertising cookies and we do not share data with ad networks.

16BYOK & your keys

On the Lifetime + BYOK plan, your third-party API key is stored encrypted in your browser's local storage. We never receive it, log it, or forward it anywhere except the AI provider you connected it to, for the sole purpose of fulfilling your request.

17Data retention

Account and billing records are kept while your account is active. Saved chats (including their messages, tool results and chat summary) and project memory are kept until they are deleted; we do not currently delete them automatically after a set period. Condensed conversation content is cached for up to one hour and then expires. Tool records are kept without a fixed deletion period, and operational logs on Cloudflare are kept for up to 7 days. Deleting a chat in the extension removes it from your chat history and deletes its summary. Individual message records, project memory and diagnostic records are stored separately and may not be erased when you delete a chat; to make sure all related records are erased, or to have your account or any other retained data deleted, email support@gscopilot.com.

18How to opt out

Product analytics can be disabled for your account at any time by emailing support@gscopilot.com. Session replay is currently disabled entirely across the product, as described above. If we introduce in-product analytics controls, we'll update this section to point to them directly.

19Your rights

You can update your profile details and delete individual chats in the extension. To request an export or deletion of your account data, project memory or other retained records, email support@gscopilot.com. EU and California residents have additional rights under GDPR/CCPA — email support@gscopilot.com to exercise them. You can remove Google access by clicking Disconnect on the Apps Script card in GS Copilot (MCP Servers), or by revoking GS Copilot's access at https://myaccount.google.com/permissions.

20Children's privacy

Google Apps Script Copilot is not directed at children under 13, and we do not knowingly collect data from anyone under 13.

21Changes to this policy

If we change how we handle data in a material way, we'll notify registered users by email at least 14 days before the change takes effect, and update the "Effective" date above.

22联系 us about privacy

Questions or concerns? 邮件支持@gscopilot.com — a real human reads each one.