Cellfetch privacy policy
Last updated October 20, 2026. Cellfetch: API & JSON Importer for Sheets is a Google Sheets add-on made by Great Work LLC.
This page explains what Google user data Cellfetch accesses, how it uses that data, how the data is protected, how long it is kept and how to delete it. It adds to the Great Work add-ons privacy policy, which covers billing.
Google user data Cellfetch accesses
- The spreadsheet you open it in (permission
spreadsheets.currentonly): Cellfetch writes the API results you ask for into that spreadsheet and reads the cells you reference in a request (for example a cell holding a search term). It cannot open your other files, your Drive or your Gmail. - Your email address (
userinfo.email): to look up your free trial or subscription. - Connecting to external services (
script.external_request): to call the web APIs you set up, and our licensing service. - Running on a schedule (
script.scriptapp): to create and remove the refresh trigger you turn on for a saved request. - Showing the sidebar (
script.container.ui).
How Cellfetch uses Google user data
Only to provide the import you set up: to read the cells your request refers to, to call the API you chose, and to write its response into the sheet and range you picked, when you click Run or on the refresh schedule you turned on. Your email address is used only to identify your trial or subscription. Cellfetch does not use Google user data for any other purpose: not for advertising, not for selling, not for profiling, and not to develop, improve or train AI or machine-learning models.
Where data goes and what's stored
- API data goes straight from the API to your spreadsheet through Google's servers (Apps Script UrlFetch). It never passes through Great Work's servers. Formula results may be kept in Google's per-document cache for up to the time you set (10 minutes by default).
- Your API keys and tokens ("connections") are stored only in your Google account's private add-on storage (Apps Script user properties), which other users of the spreadsheet can't read. They are never written into the spreadsheet and never sent to Great Work. Each connection is sent, over HTTPS only, to the hosts you list for it and nowhere else. OAuth access tokens are cached in the same private storage and renewed automatically.
- Saved requests, run status and the run log are stored in the spreadsheet's own add-on storage (Apps Script document properties), visible to its editors through the add-on. They contain URLs, parameter names and messages, never keys. Error messages are scrubbed of keys before they are saved.
- What reaches Great Work's servers: your Google account email, the add-on name and a count of trial uses, and if you subscribe, your Stripe customer and subscription status. No spreadsheet contents, API data or keys.
How we protect your data
- Your spreadsheet data stays inside Google. Cellfetch runs in Google Apps Script on Google's servers, under your own account. Spreadsheet contents, saved requests and stored connections live in your Google account, where Google encrypts them in transit and at rest. We keep no copy.
- Encryption in transit. Keys and tokens are only ever sent over HTTPS: Cellfetch refuses to attach a connection to a plain http:// address, and warns you that a keyless http:// request is unencrypted. Calls to our licensing service always use HTTPS. That service accepts only TLS 1.2 or 1.3 with HSTS, and each request from the add-on is signed (HMAC-SHA256) so it can't be forged or altered on the way.
- Secrets are isolated per user. Connection keys sit in per-user storage that other editors of the same spreadsheet can't read, are sent only to the hosts approved for that connection, and are removed from any error text before it is logged.
- Access controls on our server. The licensing record (email, trial count, subscription status) is held on a server that only Great Work's administrator can sign in to, with SSH keys from a single allowed network address and no passwords. A firewall blocks everything except web traffic, the service runs under its own unprivileged account whose data only it can read, and the server has file-integrity monitoring, audit logging and intrusion alerts.
- Payments. Card details are entered on Stripe's own pages and never reach us.
- People. No person at Great Work reads your spreadsheet or API data. The only exceptions are when you ask us for support and give permission, when it's needed to investigate abuse or a security issue, or when the law requires it.
- Incidents. If we learn of a security breach affecting your data, we'll tell affected users and Google promptly, as the law and Google's policies require.
Sharing
We don't sell, rent or share Google user data. The only data that leaves Google is what you send to the APIs you connect (the request you set up, with its key) and the licensing data above. Stripe processes payments; our email provider sends billing emails you ask for.
Limited Use
Cellfetch's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Retention and deletion
- Delete a connection in the Connections tab and its key and cached tokens are deleted at once. Delete a saved request to remove it and its refresh trigger.
- Remove the add-on (Extensions > Add-ons > Manage add-ons) and revoke its access at myaccount.google.com/permissions to stop all access. Data Cellfetch wrote into your sheet is ordinary sheet data; delete it as you like.
- The licensing record is kept while you use Cellfetch. Email hello@greatwork.company from that account and we delete it within 30 days, apart from billing records the law requires us to keep. Web server logs (IP address, time, request path, never request contents) are kept for 14 days. Server backups roll over within four weeks.
Contact
Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA. hello@greatwork.company