Privacy Policy

Product: ICS EU ENS HS6 Prep (Google Sheets) · Controller: ENSage Labs · Effective date: 2025-09-22

1) What this policy covers

This policy explains what Google user data the add-on accesses, why, how it is used, how it is protected, how long it is retained, and your choices.

2) Google user data we access

OAuth scopes requested

https://www.googleapis.com/auth/spreadsheets.currentonly – read/write only the spreadsheet where the add-on is installed (create templates, validations, logs, exports).
https://www.googleapis.com/auth/script.container.ui – display/run HtmlService sidebar and dialogs within Google Sheets.

Data categories (current spreadsheet only)

Sheet names, headers, and cell values you provide; data validation/formatting; add-on outputs (e.g., ICS2_Master, ICS2_House, ICS2_ValidationLog, ICS2_Score).

We do not access: other Drive files, Gmail, Contacts, Calendar, or external accounts.

3) How we use the data

Create ENS-ready templates and apply validation rules in the same file.
Run in-sheet checks and write results (log/score) to the same file.
Generate CSV for download in your browser when you click Export.

No transmission to developer servers. We don’t sell or use data for advertising or profiling.

4) Data protection for sensitive data

ENS data can include names, addresses, identifiers, and logistics details. We apply the following technical and organizational measures to protect such data:

Encryption in transit & at rest: Files in Google Drive/Sheets are encrypted in transit and at rest by Google by default; organizations may enable Client-side Encryption (CSE) for additional confidentiality. Learn more · Default encryption · About CSE.
Least-privilege access: We use the narrow currentonly scope and @OnlyCurrentDoc so the add-on can only access the active spreadsheet; no access to other files. Scopes guidance.
Data minimization: Processing occurs only on user-provided fields required for ENS preparation; we do not collect analytics or telemetry on spreadsheet contents.
No backend storage: We do not persist spreadsheet contents on developer or third-party servers; outputs remain in your file.
Logging hygiene: Errors and operational messages exclude spreadsheet contents; if users send support logs/screenshots, they must redact sensitive values.
Access controls: The add-on runs under the installing user’s Google account; sharing and permissions are controlled by the file owner’s Drive sharing settings.
Secure transport: OAuth and add-on UI communications use Google’s HTTPS/TLS infrastructure.
Incident response: If we become aware of a security incident affecting data we process, we will investigate, mitigate, and notify affected administrators/users without undue delay, consistent with applicable law and our contracts.

5) Retention & deletion

We do not store Google user data on developer systems.
All outputs remain in your spreadsheet; you control retention by editing or deleting the ICS2_* sheets or the entire file.
Uninstalling the add-on or revoking access stops further processing.

6) Sharing & sub-processors

No sale or sharing of Google user data with third parties.
No sub-processors handle spreadsheet contents for this add-on.
We may disclose information only if required by law.

7) Your choices

Uninstall via Extensions → Add-ons → Manage add-ons.
Revoke OAuth access at myaccount.google.com/permissions.
Control file access via Google Drive sharing and, if needed, enable Workspace Client-side Encryption.

8) Compliance statements

Our use of Google user data complies with the Google API Services User Data Policy (including Limited Use) and applicable Workspace Marketplace policies. This policy and in-product notices disclose how we access, use, store, and share Google user data.

9) Children

The add-on is not directed to children under 13 and does not knowingly collect their personal data.

10) Contact

Email: support@ensworks.com