ShotToSheet

Privacy

Your image itself is never written to disk and never stored — it is processed in memory and discarded immediately after the extracted table is returned to you. ShotToSheet does not use your image to train its own models.

ShotToSheet does use a database for a few narrow, non-image purposes: enforcing the free monthly limit per device, keeping subscription status in sync for Pro/Premium accounts, and — for 24 hours only — caching the extracted table if you re-upload the exact same image, so a retry or an accidental re-upload doesn't cost a second extraction. That cache stores the table data that came back, not the image itself, and expires automatically after a day. None of this is linked to the visual content of anything you upload beyond what was already extracted from it.

If your table contains sensitive data

Financial statements, medical records, or anything with account numbers or personal information still travel to a third-party AI vision API for the few seconds it takes to read the table structure. That provider processes the image to return a result and is not instructed by ShotToSheet to retain it — but its own retention and training policy is set by that provider, not by us, so we can only speak for what ShotToSheet itself does with your data. If that's a concern, redact the sensitive cells before uploading, or wait for ShotToSheet's upcoming local, zero-upload extraction mode.

Signing in with Google

ShotToSheet offers two separate, optional Google sign-ins. Each requests only the narrow permission it needs — connecting one does not grant the other.

Sign in with Google (for Pro/Premium): before starting a paid checkout, you may be asked to sign in with Google. This only reads your Google account's email address (the userinfo.email scope) — nothing else. That email is used to tie your Stripe subscription to your Google identity, so if you sign in with the same Google account on another device, your paid quota can be recovered there instead of asking you to buy it again. The email is stored as a signed cookie in your own browser for up to 90 days — not in a server-side database — and is otherwise only known to Stripe, which already has it from checkout.

Connect Google Sheets (for exporting): if you choose to export a table directly to Google Sheets, a separate consent screen asks for permission to create and write to new spreadsheets in your Google account (the spreadsheets scope). This grant is deliberately narrow — it can only create brand-new spreadsheets and cannot read, list, or modify any file you already have in Google Drive. The resulting access credential is encrypted (AES-256-GCM) and stored as a cookie in your own browser, not in a database, and is used only to talk to Google's Sheets API on your behalf.

You can disconnect either at any time from ShotToSheet (this deletes the cookie and revokes the credential with Google) or directly from your Google Account permissions page.

Payments

Billing is handled entirely by Stripe. ShotToSheet never sees or stores your card details.