Privacy Policy
Last updated: November 5, 2026
This Privacy Policy explains how Sheetrocket accesses, uses, stores, shares, and deletes information when you sign in, connect data sources, and create REST APIs, embeddable widgets, and websites.
Information We Collect
- Account details, such as your email address, display name, and profile picture
- Information from data sources you authorize, including Google Sheets
- Source settings, published content, editing requests, and orders when you use those features
- Usage and security information, such as API request methods, paths, timestamps, and aggregate performance measurements
Google User Data We Access
Google sign-in accesses your Google account identifier, email address, name, and profile picture. We store these details to identify and display your Sheetrocket account. Connecting Google Sheets is a separate authorization, which stores the connected Google account details and the permissions Google actually grants. You may connect more than one Google account.
New Google Sheets connections request openid, email, profile, and access to specific Drive files you select or create with Sheetrocket (the drive.file permission). Google Picker lets you authorize existing spreadsheets. This permission does not grant access to every spreadsheet in your account. Older connections may retain broader permissions until their grants are retired. You can also connect a spreadsheet by sharing it with Sheetrocket's service account instead of using Google OAuth.
For authorized spreadsheets, we access file names and identifiers, modification times, owner information, edit permissions, spreadsheet titles, worksheet names and identifiers, column headers, rows, and cell values. Record editing also reads formulas and worksheet structure. We process Google OAuth access and refresh tokens to authenticate these requests; they are credentials, not content intended for publication.
How We Use Google User Data
We use your account details to sign you in and help you choose the correct connected account. We use authorized spreadsheet data to preview sources, create REST APIs, display widgets, and power websites. When you request it, we create spreadsheets, generate sample data, add columns or product identifiers, and read, add, update, or delete spreadsheet records. Access continues in the background while your sources remain connected so published features can work without you being signed in to Google each time.
If you enable cart, checkout, or ordering features for a spreadsheet-backed catalogue, selected product details, prices, identifiers, and variants can be stored in carts and orders and used in checkout and order notifications. These are part of the features you configure, rather than a separate use of your Google account for advertising.
Sharing and Transfers
Our hosting, database, and caching infrastructure process account information, credentials, and spreadsheet data as needed to operate Sheetrocket. Google processes API requests and the Picker selection flow. If you enable order notifications, our email delivery service, Resend, processes recipient addresses and order messages, which can include spreadsheet-derived product details. When you configure a payment gateway, the selected provider processes the checkout details required for that payment; for example, product names and prices may be sent to Stripe or PayPal. If you purchase a Sheetrocket subscription, Paddle processes billing information such as your account email.
Connecting Google does not by itself publish your Google credentials or account profile. Spreadsheet data you intentionally expose through a REST API, widget, or website is delivered to its consumers or viewers according to the access settings and fields configured for that feature. Do not publish spreadsheet content you intend to keep private. Recipients can retain their own copies, and disconnecting Google does not retrieve copies already received.
Marketing pages use Simple Analytics and Microsoft Clarity for usage analytics and session insights. These scripts are excluded from the application shell used for sign-in, Google connections, spreadsheet previews, and builders. Google account data, OAuth credentials, and spreadsheet contents are not sent to these services by the Google integration. This does not prevent website owners or visitors from using their own tools on data you intentionally publish.
Storage and Security
We store account and connected-account details, granted permissions, source identifiers, worksheet selections, and configuration in our database. Newly saved Google refresh tokens are encrypted at rest using AES-256-GCM and server-managed encryption keys. Legacy plaintext connection tokens are upgraded to encrypted storage when accessed through account management. Access tokens are processed in memory for Google requests. A short-lived access token is sent to your browser for Google Picker; refresh tokens are not returned to the browser.
Authenticated account controls check ownership, and server-side spreadsheet operations use the connection authorized for the source owner. Cached source data is separated by connection. Published access follows the relevant API, widget, or website permissions. Google API and Picker requests use HTTPS. Production website HTTPS, database and cache transport protections, and backup security depend on the hosting configuration; contact us for information about the safeguards applying to your deployment.
Retention of Google Data
- Sign-in profile details remain with your Sheetrocket account until changed or the account is deleted. Disconnecting a Sheets account does not remove the separate Google sign-in profile.
- Connected Google account details, granted permissions, and refresh tokens remain until that connection or your account is deleted. Tokens can become invalid earlier if Google revokes or expires them.
- The shared spreadsheet row cache expires after 60 seconds in server memory and, when configured, Redis. Dashboard previews can use a previous snapshot for up to ten minutes when refreshing fails. Expiry cleanup removes these memory snapshots even without another request; process scheduling can delay cleanup.
- Source configuration, copied or manually saved website/widget content, submitted edit requests, creation receipts, product identity records, carts, and orders can retain spreadsheet data or derived values beyond the cache lifetime. Editing and creation receipts have no scheduled age-based deletion and can survive deletion of a widget. Account-linked records are removed when the account is deleted.
- Some technical product-identity records and template-provisioning references are not automatically removed by account deletion. Contact us about remaining records and deletion requests. We do not promise that deleting a connection or account removes every derived record automatically.
- Infrastructure logs and backups may retain deleted information after removal from the live application. Their retention and expiry depend on provider settings; there is no single backup-deletion period enforced by the application. We cannot remove copies independently retained by people with whom you shared data.
Disconnecting Google and Deleting Your Account
To disconnect a Google Sheets account, open the source connection dialog, choose Manage accounts, and select Disconnect for that account. This deletes its locally stored connection details and credentials and attempts to revoke Google's token. Live reads and edits for dependent APIs, widgets, and websites stop. Source references, saved content, and editing or order records are not automatically deleted by disconnecting. Previously cached data expires as described above.
You can also remove Sheetrocket access in your Google account connections. Google revocation can affect other connections using the same Google account and app. If revocation fails because Google is unavailable or a credential cannot be read, local deletion still completes and you can revoke access directly with Google.
To delete your Sheetrocket account, open Settings, enter your account email, and confirm Delete my account. This removes the account and its account-linked Google connections, sources, APIs, widgets, websites, orders, and editing or creation receipts from the live database and attempts Google token revocation. Retained records, logs, backups, and recipients' copies follow the limits described above. Neither disconnecting Google nor deleting your Sheetrocket account deletes your spreadsheets from Google Drive. For a service-account connection, remove sharing with that service account in Google Sheets to withdraw its access.
Google API Services User Data Policy
Sheetrocket's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Read the Google API Services User Data Policy. Google user data is used for the features you request, not sold to data brokers or used for advertising, retargeting, or credit decisions. Transfers are limited to providing those features with your consent, security needs, or applicable legal obligations. Any human access must be limited to the circumstances permitted by that policy, such as your affirmative agreement to view specific data or a necessary security investigation.
AI and Machine Learning
The Google integration does not send Google Workspace user data to an AI service or use that data to train generalized AI or machine-learning models. Generating sample spreadsheets uses predefined sample data, not an AI inference service. Publishing spreadsheet data does not give Sheetrocket permission to use it for model training.
Your Rights and Contact
You can request deletion of your information or ask about retained data, infrastructure providers, and privacy practices by emailing allen@sheetrocket.com. Include the email for your Sheetrocket account and identify the data or connected source concerned. Do not send us Google passwords or OAuth tokens.
This policy may be updated from time to time. Changes to how we use Google data require updated disclosures and any consent required by Google's policies before that new use begins.