Last updated: 18 August 2026
The short version: this add-on runs entirely inside Google Apps Script. It has no server of ours, no database and no analytics. It applies ordinary Google Docs highlighting to the text you selected in the document you have open, reads that document's highlighting to build its summary, and sends nothing anywhere. We cannot see your documents, and we do not receive, store or transmit any of your content.
Highlighter — Colour-Code & Extract ("the add-on") is published by Going Stellar SRL. Contact: gheorghe.beschea@overheat.agency.
| Permission requested | Why it is needed |
|---|---|
documents.currentonly"View and manage documents that this application has been installed in" |
Three uses, all inside the single document you have open: applying a background colour to the text you selected when you press a category (and removing it with Remove highlight); reading the document's existing highlighting to count the passages in each category; and writing the "Coded extract" section at the end of the document when you press Extract passages. This permission does not grant access to your other documents or to your Google Drive. |
That is the only permission the add-on requests. It asks for no access to your other documents, and none at all to Gmail, Drive, Calendar, your contacts, or any other Google service.
Everything you mark is standard Google Docs background colour — the same thing the built-in highlighter pen applies. It lives in your document, not in the add-on: collaborators see it whether or not they have the add-on installed, it survives if you uninstall the add-on, and you can remove it with the add-on's Remove highlight button or with Docs' own tools. The add-on holds no copy of it.
Nothing is sent to us. The add-on has no backend server of ours, no database, and no
analytics or tracking of any kind. The document is read inside Google's own Apps Script runtime to find
highlighted passages. No document content, no document titles and no usage statistics are transmitted to us
or to any third party. Error logging is switched off in the add-on's manifest
(exceptionLogging: NONE).
Two small things, both in the add-on's user properties inside your own Google account, neither of them document content:
If you buy Pro, you receive a licence key and paste it into the add-on. That key is stored in your own Google account, in the add-on's user properties, and it stays there — it is never transmitted to us, because the add-on checks it by verifying its signature rather than by asking a server. The key contains the email address or domain it was issued to, so it is personal data held inside your Google account. You can remove it at any time with Manage → Remove licence from this account.
Separately, when you write to us to buy a licence or ask for support, we receive your email address and whatever you put in the message. We use it to issue your key and to answer you, we keep it for as long as we support the product, and we do not sell, share or profile it. Write to the address above to have it deleted.
All processing happens within Google's infrastructure, under your own Google account, subject to Google's Privacy Policy. No data leaves that boundary.
We receive and hold no document data. The add-on stores only the two items described above — your palette and, if you buy Pro, your licence key — both in your own Google account, not with us. Your highlights and any extract you created are part of your document and remain under your control there. You can clear the licence key yourself from the panel; uninstalling the add-on from the Google Workspace Marketplace, or revoking its access at myaccount.google.com/permissions, immediately ends all access.
The add-on's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In practice this is trivially satisfied: no user data is transferred out of the Apps Script runtime at all.
The add-on is a document productivity tool and is not directed at children under 13.
If this policy changes we will update this page and the date above. Because the add-on collects no data, any change would concern wording rather than practice.
Questions about privacy: gheorghe.beschea@overheat.agency. We answer.