Jev for Sheets ("the add-on") is an open-source Google Sheets add-on. This policy explains what data the add-on accesses, where that data goes, and what it does not do. The add-on's source code is public at github.com/Cab14bacc/jev-sheets, so every statement below can be checked.
Summary
- The add-on reads only the cells you pass to a
JEV_formula, plus the spreadsheet it's opened in when you use its menu. - It sends that cell text only to TypeSafe's API (
api.typesafe.ai), using your own API key, to get the answer. - The developer has no server, receives none of your data, and runs no analytics or tracking.
- We do not transfer or disclose your information to third parties for purposes other than the ones described in this policy, and we never sell it.
- We use encryption to protect your information, and security procedures are in place to protect the confidentiality of your data.
Data the add-on accesses and why
| Data | Why | Where it goes |
|---|---|---|
Values of cells used as arguments to JEV_IF, JEV_PROB, JEV_CHOICE or JEV_SCORE, and the question and options you write in the formula |
To get the answer the formula asks for | Sent over HTTPS to TypeSafe's API (https://api.typesafe.ai/). Nowhere else. |
| Your TypeSafe API key | To authenticate requests to TypeSafe on your behalf | Stored in Google Apps Script user properties (visible only to you), or in document properties if you choose to share it with everyone using the add-on in that spreadsheet. It is sent only to TypeSafe, as the request's authorization header. |
| The answers returned by TypeSafe | To avoid paying again when the sheet recalculates | Cached in Google Apps Script's cache service for up to 6 hours, then deleted automatically. |
| The current spreadsheet (when you choose Insert example sheet) | To add a new tab with example data and formulas | Stays in your spreadsheet. |
The add-on does not read other spreadsheets, your Google Drive, your email or your contacts, and does not access your name or email address.
Google permissions requested
spreadsheets.currentonly: view and manage only the spreadsheet in which the add-on is used (to insert the example sheet and show notifications).script.container.ui: display the settings sidebar and menu inside Google Sheets.script.external_request: connect to TypeSafe's API. The add-on's manifest only allows requests tohttps://api.typesafe.ai/.
Who we share, transfer or disclose data to
We do not transfer or disclose your information to third parties for purposes other than the ones provided in this policy. We do not sell, rent or trade Google user data, and we share it with no one other than the single service listed below, which is required to produce the answers you ask for.
Data obtained through Google APIs (the cell values you pass to a JEV_ formula) is shared with exactly one third party, and only to produce the answer your formula asks for:
| Recipient | What is shared | Purpose |
|---|---|---|
| TypeSafe AI (typesafe.ai), the provider of the Jev model | The text of the cells referenced in a JEV_ formula, plus the question and options written in that formula, and your TypeSafe API key as the authorization header |
To compute the classification or score that the formula returns. Processed under TypeSafe's privacy policy and data processing agreement; TypeSafe states it does not train its models on customer requests. |
We share, transfer or disclose Google user data to no one else. Specifically:
- The developer of this add-on receives none of your data. The add-on has no server, no database, no logging service and no analytics or tracking.
- Your data is never sold, rented, or shared with advertisers, data brokers or partners.
- It is never used to train, fine-tune or improve any AI or machine-learning model, including TypeSafe's.
- There is no transfer to any other processor, affiliate or sub-processor. The add-on contacts only
https://api.typesafe.ai/, which its Apps Script manifest enforces throughurlFetchWhitelist. - Data stays inside Google's infrastructure except for the request to TypeSafe: the add-on's code runs in Google Apps Script, and both the API key and the short-lived answer cache are held by Google's Properties and Cache services.
- We would disclose data only if required by law, and as we hold none, there is nothing to disclose.
- You control the sharing: data goes to TypeSafe only when you write a
JEV_formula or press a button in the add-on. Delete the formula and nothing further is sent.
How your data is protected
Security procedures are in place to protect the confidentiality of your data, and we use encryption to protect your information. All data is transmitted over encrypted HTTPS/TLS connections, and anything stored is encrypted at rest on Google's infrastructure. The add-on handles data that may be confidential or personal, depending on what is in your cells, so the following measures apply:
- Encryption in transit: every request to TypeSafe uses HTTPS (TLS). Plain HTTP is not used, and the manifest allows only the
https://api.typesafe.ai/endpoint. - Encryption at rest: anything stored, namely your API key and cached answers, is stored by Google Apps Script's Properties and Cache services, which are encrypted at rest on Google's infrastructure. The developer operates no storage of any kind.
- Data minimization: only the cells referenced in a formula are sent. The add-on doesn't read the rest of the sheet, other spreadsheets, Drive, Gmail, or your name or email address. It requests the narrowest scopes that make the features work, including
spreadsheets.currentonlyrather than full Sheets access. - Short retention: answers are cached for at most 6 hours and then deleted automatically by Google. Cell contents are not retained by the add-on at all.
- Access control: the code runs inside your own Google account. Your API key is kept in your personal Apps Script user properties, which other users can't read, and the sidebar only ever displays its last 4 characters. A key can be removed at any time from the sidebar, and revoked in TypeSafe's console. The optional per-spreadsheet key is clearly labelled as shared with that spreadsheet's users.
- No credentials held by the developer: you bring your own TypeSafe key, so the developer never holds credentials for your accounts or services.
- Auditability: the add-on's entire source code is public (MIT) at github.com/Cab14bacc/jev-sheets, so every claim on this page can be independently verified.
- Your responsibility: because cell text is sent to TypeSafe, only use the formulas on data you're permitted to share with them. For especially sensitive material, check TypeSafe's terms first, or don't include it in the cells you pass.
- Reporting a problem: report a suspected vulnerability or data incident by opening a GitHub issue. Issues are addressed as quickly as possible, and affected users are informed through this page and the repository.
Third party: TypeSafe AI
Answers are produced by TypeSafe AI's Jev model. Cell text you send is processed by TypeSafe under their terms and privacy policy; TypeSafe states that it does not train its models on customer requests. You create and control your TypeSafe account and API key, and TypeSafe bills you directly for usage. Don't pass cells containing data you aren't permitted to share with TypeSafe.
Limited Use
Jev for Sheets' use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Data from Google Sheets is used only to provide the add-on's user-facing features described above. It is not sold, not used for advertising, not used to train AI models, and not transferred to anyone except TypeSafe, as needed to answer your formulas.
Retention and deletion
- Cached answers expire automatically after at most 6 hours.
- Remove your API key at any time in Extensions → Jev for Sheets → Settings & API key. Uninstalling the add-on also stops all access.
- For data TypeSafe holds, see TypeSafe's privacy policy or contact them.
Children
The add-on is not directed at children under 13 and does not knowingly collect data from them.
Changes
If this policy changes, the new version will be posted on this page with a new "Last updated" date. The history of changes is visible in the project's GitHub repository.
Contact
Questions about privacy: open an issue on GitHub.