Security
Short and plain, for the person your buyer forwards this to: how the add-on is built, what it can reach, and what happens when something goes wrong.
Architecture
Your browser’s sidebar reads your spreadsheet and analyses it there. The licence server sees only licence keys and opaque install ids — it cannot see your files because nothing sends them. There is no database of customer spreadsheets to breach, because there is no database of customer spreadsheets.
Scopes and why
spreadsheets.currentonly— the one spreadsheet the add-on is opened in. Not your other files, not your Drive.script.container.ui— the menu and sidebar. No UI, no add-on.
It never asks for drive or drive.readonly — full Drive
access would contradict the product — and it never will.
What it doesn’t do
- No telemetry, no analytics, no tracking in the sidebar.
- No content in error reports — errors carry codes, so server logs can’t leak a cell.
- No full identity, card, bank or health numbers rendered or written anywhere — masked samples only.
- No silent changes: the original file is never touched unless you choose Redact in place, and the default fix is a share-safe copy.
Updates and issues
Updates ship through the Workspace Marketplace like any other add-on; there is nothing to install and no separate updater with its own privileges. To report a security issue, email support@appgarden.co.uk with “security” in the subject — it goes to the top of the queue, and you will hear back within one working day.
Google, Google Sheets™ and Google Workspace™ are trademarks of Google LLC. Personal Data and Sharing Check is not affiliated with or endorsed by Google.