Privacy Policy

The short version

SheetPilot writes rows from your browser directly to your own Google Sheet using Google's official API — the saved data never passes through our servers and is never stored by us. Our servers see page content only when you explicitly run an AI action (extract, list capture, cleanup) on that page, and only to produce the result. We never read pages in the background.

Google account access

To write into your spreadsheet, the extension asks Google for the spreadsheets permission via Chrome's built-in sign-in. The resulting access token stays inside the extension on your device; it is sent only to Google's own API endpoints and never to our servers. We cannot see, list or open your spreadsheets. You can revoke this access anytime at myaccount.google.com/permissions. SheetPilot's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Data we collect

• Account data. When you create an account: email address, name, and — if you sign in with Google or GitHub — the basic profile those providers share.
• AI requests. When you run an AI action, the relevant text of that page (your selection, extracted text, and a compact outline of page elements), plus the page URL, title and your target column names, are sent to our server and forwarded to our AI provider (OpenRouter) to produce the rows. We do not use this data for training and do not retain the page content after the request completes.
• Recipes. When AI learns a page layout, the resulting rule (site hostname, column names, CSS selectors) is stored in your account so it can sync across devices. Recipes contain the pattern only — never the data extracted with them.
• Billing. Payments are processed by Paddle, our merchant of record. We never see your card details; we store your subscription status and Paddle customer/subscription identifiers.

What we never collect

• The rows you save — they go from your browser straight to your Google Sheet.
• Your Google access token, or any ability to open your spreadsheets ourselves.
• Your browsing history — the extension reads a page only when you ask it to.
• Anything from idle usage — no background telemetry.

Extension permissions and why they are needed

These are exactly the permissions declared in the extension's manifest — no more, no fewer. If a permission is ever added or removed, this list changes with it.

• identity — obtains the Google sign-in token used to write rows into your own spreadsheet. The token never leaves your device except to Google's API.
• storage — remembers your saving targets (which spreadsheet and columns), interface language, panel settings, local save history and cached recipes. Nothing in storage is sent to a server except recipes you sync to your account.
• unlimitedStorage — lets the local save history and recipe cache grow without hitting the browser's default quota. This storage is on your device only.
• sidePanel — SheetPilot has no popup; its whole interface is a Chrome side panel opened beside the page.
• contextMenus — adds right-click items so you can save a selection to a target sheet without opening the panel.
• tabs — reads the active tab's title and URL so the panel can show which page it is about to act on, and addresses the extraction request to that exact tab. Your other tabs are not enumerated and no browsing history is collected or transmitted.
• activeTab + scripting — after you invoke SheetPilot on a tab (right-click, shortcut or toolbar), injects the reader into that one tab if it was opened before the extension was installed.
• clipboardWrite — copies extracted rows when you click a copy action.
• Host access to sheets.googleapis.com — writes rows and creates spreadsheets in your Google account, directly from your browser.
• Host access to sheet.xeviora.com — the extension calls our API for AI actions, recipe sync and your account status, reusing your normal site session cookie.
• Content script on all sites — SheetPilot exists to capture data from whichever page you are currently viewing, and that page can be on any website, so the script must be declared broadly. It has no user interface, does nothing on page load, and reads the page only when you invoke SheetPilot on that tab.

Data retention and deletion

Recipes persist until you delete them from the dashboard or the extension. Local save history can be cleared inside the extension anytime. You can delete your entire account yourself from Settings → Danger zone: type the confirmation code shown there and your account, every recipe and your credit history are removed immediately and permanently. No email request and no waiting period. Rows already written to your Google Sheet are yours and are unaffected.

Third parties

We rely on: Vercel (hosting), Neon (database), OpenRouter (AI processing), Paddle (payments), and Resend (transactional email). Each receives only the minimum data needed for its function. Writes to your spreadsheet go directly to Google.

Cookies

We use a single first-party session cookie for authentication, scoped to sheet.xeviora.com only. No advertising or cross-site tracking cookies.

Contact

SheetPilot is a product of Xeviora. Questions about this policy: support@xeviora.com.