Addons Privacy Policy

Last update: January 6, 2026

1. Overview

This Privacy Policy applies to all add-ons provided by AddonForge.

The first main section (2. General Privacy Information) describes our general principles for handling user data, followed by add-on specific information (3. Add-on Specific Data Access & Use).

1.1 Privacy Contact

For any privacy-related questions or data requests, please contact us via our privacy & data contact form.

1.2 Legal Terms

Legal domicile: Vienna (Austria)
Applicable law: Austrian law

2. General Privacy Information

This section explains how we handle data across all add-ons.

2.1 General Data Protection Principles

Across all add-ons, we apply the following principles:

We access Google user data only to provide the core functionality of each add-on.
We do not use Google user data for advertising, profiling, or analytics.
We do not sell or share Google user data with third parties for marketing purposes.
Data transmission is protected by HTTPS encryption.
Access is restricted to the developer only; no team or external access.
Administrative accounts are separated from daily-use accounts and secured with hardware-based two-factor authentication.
Technical logs contain no personal data or content, only anonymous events (e.g. “add-on opened”).

Those principles will be adjusted over time to maintain compliance with evolving legal requirements and best practices.

2.2 General Data Storage Principles

Most user data is stored within the Google ecosystem (Google Drive files, add-on properties, etc.).
Whenever specific add-on features need external storage we use our own Google Cloud Platform databases.

2.3 General Data Sharing Principles

Data sharing outside the Google ecosystem is only done for specific features.
Those selected third-party services are described in detail in the add-on specific sections.

2.4 General Data Deletion Principles

We apply different deletion rules depending on where data is processed or stored.
Details are described in the add-on specific sections, including data stored in Google services, our own infrastructure, and third-party providers.

2.5 Support Identifier & Technical Logs

We use a technical support identifier across our add-ons to handle support and data deletion requests.

The support identifier contains no personal data.
It is generated automatically and displayed inside the add-on.
The same identifier may appear in anonymous technical logs.

This identifier is not linked to any individual user by default.
A connection between a user and a support identifier is created only if the user voluntarily provides it in a support or data deletion request. In this case, the identifier is used exclusively to locate and delete related data in our systems and with involved service providers.

2.6 Google API Services User Data Policy

Our add-ons’ use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements.

We use Google user data only to provide the core functionality of our add-ons and do not use such data for advertising, profiling, or resale.

3. Add-on Specific Data Access & Use

The following sections describe how each individual add-on accesses and uses Google user data.

3.1 Accessibility Owl

Data accessed and purpose:

userinfo.email, userinfo.profile – Used only for account identification within the add-on and licensing.
spreadsheets.currentonly – Perform accessibility checks in the current document.
script.container.ui – Display the add-on sidebar.
script.scriptapp – Automatically open the sidebar when activated.

3.2 Add Sheets

Data accessed and purpose:

userinfo.email, userinfo.profile – Used only for account identification within the add-on and licensing.
script.container.ui – Display the add-on sidebar within Google Spreadsheets.
drive.readonly – Display and select Google Drive folders.
spreadsheets – Copy selected sheets into destination spreadsheets.
script.external_request – Verify PRO license status.

3.3 Add Slides

Data accessed and purpose:

userinfo.email, userinfo.profile – Used only for account identification within the add-on and licensing.
script.container.ui – Display the add-on sidebar within Google Slides.
drive.readonly – Display and select Google Drive folders.
presentations – Copy selected slides into destination presentations.
script.external_request – Verify PRO license status.

3.4 BLAZ

Data accessed and purpose:

userinfo.email, userinfo.profile – Used only for account identification within the add-on and licensing.
presentations.currentonly – Access the current presentation for conversion.
spreadsheets.currentonly – Access the current spreadsheet for conversion.
drive.file – Store converted files.
script.container.ui – Display the add-on sidebar.
script.scriptapp – Automatically open the sidebar when activated.
script.external_request – Call external conversion APIs and verify PRO license status.

3.5 Bulk Invoices

Data accessed and purpose:

userinfo.email, userinfo.profile – Used only for account identification within the add-on and licensing.
spreadsheets – Create invoice data from templates.
drive – Store generated invoice PDFs.
script.container.ui – Display the add-on sidebar in Google Spreadsheets.
script.external_request – Convert spreadsheets into PDFs.
script.send_mail – Send invoices to recipients.

3.6 CAPY: Form Choice Eliminator & Choice Limiter

Google user data our add-on accesses:
a) User information
The user’s email address is used solely for account identification within the add-on and for licensing purposes.
If the user activates notifications (e.g. when limits are reached), notifications are sent to this email address.

b) Google Forms
Form responses are used exclusively to apply limits, which is the core functionality of this add-on.

c) Google Spreadsheets
Users may link the response sheet to the add-on to define advanced limiting rules (for example, if a calculated value in a specific cell exceeds a defined threshold).

How this data is used:
All Google user data is accessed strictly to provide the core functionality of the add-on: applying limits to form responses and sending notifications.

Data storage:
We do not store user content on external servers.
All content remains under the user’s control within their own Google account.

Data sharing:
No data other than described below is shared with third parties.

a) ThriveCart and Stripe
We share limited user information only with our payment and licensing providers for subscription management and legal accounting purposes.

b) MailerSend
Only the user’s email address and the notification message are sent to MailerSend for the delivery of system notifications.

Data deletion:
All user data remains under the user’s ownership and control within their Google account.
Users may delete related data at any time by removing created files or uninstalling the add-on.

3.7 Choice Eliminator X: Enhanced Choice Limit

Google user data our add-on accesses:
a) User information
The user’s email address is used solely for account identification within the add-on and for licensing purposes.
If the user activates notifications (e.g. when limits are reached), notifications are sent to this email address.

b) Google Forms
The questions and choices of the current form are read so that a limit can be applied to a single choice.
Form responses are used exclusively to count how often a choice has been picked, which is the core functionality of this add-on.

How this data is used:
All Google user data is accessed strictly to provide the core functionality of the add-on: applying limits to individual choices and sending notifications.

Data storage:
The standard mode stores everything within your own Google account.
The enhanced mode additionally keeps the count of each choice in a database of ours on Google Cloud Platform, which is what the page limiter.addonforge.com serves — that is how the count stays correct when many people answer at the same moment. Stored are the id of your form, the id of the question, the text of each choice and its limit. No participant identities and no answers are stored there.

Data sharing:
No data other than described below is shared with third parties.

a) ThriveCart and Stripe
We share limited user information only with our payment and licensing providers for subscription management and legal accounting purposes.

b) MailerSend
Only the user’s email address and the notification message are sent to MailerSend for the delivery of system notifications.

Data deletion:
All content within your Google account remains under your ownership and control; you may delete it at any time by removing created files or uninstalling the add-on.
The counts of the enhanced mode are removed together with the limits when you reset or delete them in the add-on. For anything still held on our side, please contact us via our privacy & data contact form and provide the support code displayed within the add-on.

3.8 CLOSY: Response Limit & Form Limiter

Google user data our add-on accesses:
a) User information
The user’s email address is used solely for account identification within the add-on and for licensing purposes.
If the user activates notifications (e.g. when the form has been closed), notifications are sent to this email address.

b) Google Forms
Form metadata is read, and the form is closed once the rule you defined is met — that is the core functionality of this add-on.

c) Google Drive
The rule is read from a spreadsheet you select yourself through the Google file picker. The add-on can only access files you explicitly pick or that it created; it reads the cell you pointed it at and nothing else.

How this data is used:
All Google user data is accessed strictly to provide the core functionality of the add-on: closing the form when your rule is met, and sending notifications.

Data storage:
We do not store user content on external servers.
All content remains under the user’s control within their own Google account.

Data sharing:
No data other than described below is shared with third parties.

a) ThriveCart and Stripe
We share limited user information only with our payment and licensing providers for subscription management and legal accounting purposes.

Data deletion:
All user data remains under the user’s ownership and control within their Google account.
Users may delete related data at any time by removing created files or uninstalling the add-on.

3.9 Coda and Sheets

Data accessed and purpose:

userinfo.email, userinfo.profile – Used only for account identification within the add-on and licensing.
spreadsheets.currentonly – Change data in the current document.
script.container.ui – Display the add-on sidebar in Google Spreadsheets.
script.external_request – Sync data via the Coda API.

3.10 FORM PAL: Time Limit

Google user data our add-on accesses:
a) User information
The user’s email address is used solely for account identification within the add-on and for licensing purposes.
If the user activates notifications, notifications are sent to this email address.

b) Google Forms
Form metadata is read so that the form can be delivered with a countdown and closed when the time is up — that is the core functionality of this add-on.

c) Google Spreadsheets
The add-on creates a spreadsheet named "Form Access Log: [your form]" in your own Google Drive and records in it who opened the timed form and when.
Our service account is given edit access to that one sheet so the countdown page can write those rows. The sheet remains your file — you can open, export or delete it at any time.

How this data is used:
All Google user data is accessed strictly to provide the core functionality of the add-on: delivering your form with a countdown, recording access to it, and sending notifications.

Data storage:
The add-on stores the following data outside your Google account.

a) Google Cloud Platform (GCP)
Your timer settings and the id of the access log sheet are stored in a database of ours on GCP. This is what allows timer.addonforge.com to deliver your form together with its countdown.
Deletion: Please contact us via our privacy & data contact form and provide the support code displayed within the add-on.

Data sharing:
No data other than described below is shared with third parties.

a) ThriveCart and Stripe
We share limited user information only with our payment and licensing providers for subscription management and legal accounting purposes.

Data deletion:
The access log is a file in your own Google Drive — you can delete it there at any time.
All other content within your Google account remains under your ownership and control and can be removed by deleting the created files or uninstalling the add-on.

3.11 Gantt Chart & Project Management by GANTTophant

Data accessed and purpose:

userinfo.email, userinfo.profile – Used only for account identification within the add-on and licensing.
spreadsheets – Edit spreadsheets to create and manage interactive Gantt charts.
script.container.ui – Display the add-on sidebar in Google Spreadsheets.
script.scriptapp – Automatically open the sidebar when the add-on is activated.
script.external_request – Verify PRO license status.

3.12 Gantt Chart by GANTTophant Reloaded

Data accessed and purpose:

userinfo.email, userinfo.profile – Used only for account identification within the add-on and licensing.
spreadsheets – Store and manage Gantt chart data.
gmail.addons.execute – Enable the add-on in Gmail.
calendar.addons.execute – Enable the add-on in Google Calendar.

3.13 Invoice Generator

Data accessed and purpose:

userinfo.email, userinfo.profile – Used only for account identification within the add-on and licensing.
documents – Create copies of invoice templates.
drive.file – Store generated invoice PDFs.
gmail.send – Send invoices to recipients.
spreadsheets – Store invoice metadata (e.g. invoice numbers).
script.container.ui – Display the add-on sidebar in Google Docs.
script.scriptapp – Create time-based triggers.
script.external_request – Verify PRO license status.

3.14 LIMIT IT: Form Response Limiter

3.15 MARIO: Notion Sync & Negative Marking

Data accessed and purpose:

userinfo.email, userinfo.profile – Used only for account identification within the add-on and licensing.
forms.currentonly – Read form responses.
spreadsheets.currentonly – Insert and update grading data.
script.container.ui – Display the add-on sidebar.
script.scriptapp – Create time-based triggers for syncing and grading.
script.external_request – Sync data with the Notion API and verify PRO license status.
script.send_mail – Send notifications for new responses.

3.16 SCRABY scrape Yahoo Finance, Amazon, Crypto, Stock

Data accessed and purpose:

userinfo.email, userinfo.profile – Used only for account identification within the add-on and licensing.
spreadsheets.currentonly – Insert data using custom formulas.
script.container.ui – Display the add-on sidebar in Google Spreadsheets.
script.scriptapp – Automatically open the sidebar when activated.
script.external_request – Call external APIs to scrape websites, fetch holidays, and sync data with Coda.

3.17 SEAL: Choice Eliminator & Send Certificates

Google user data our add-on accesses:
Our add-on uses the minimum data necessary to provide its core functionality.

a) User information
The user’s email address is used solely for account identification within the add-on and for licensing purposes.

b) Google Forms
The add-on accesses Google Forms to configure required form fields needed for certificate generation.
Form responses are used to populate certificates and to send them to the respective recipients via email.
For documentation purposes, form responses are also stored in a user-owned Google Spreadsheet.

c) Gmail
The add-on retrieves the remaining mail quota and displays it to the user.
The user’s Gmail account is used exclusively to send generated certificates to form respondents.

d) Google Slides
The add-on accesses Google Slides only to copy user-selected certificate templates and insert data provided through Google Form responses.
The final certificate is converted into an image file for delivery.
The add-on does not analyze, extract, or process any information from existing Slides content.

e) Google Drive
Users may select a custom Google Slides template via a file picker.
The add-on accesses only files that the user explicitly selects or that are created through the add-on.

f) Google Calendar
Calendar names are retrieved to allow users to choose where events should be created.
New events are created containing links to the Google Form and the corresponding response spreadsheet.

g) Managing the responses
The add-on lists the responses of your form so that you can view a single one, delete it, or copy the link that lets a participant edit their own entry. Deleting a response also frees the seat it occupied. An optional daily or weekly reset deletes the responses for you; it is off unless you switch it on.
Deleting a response removes it from your Google Form and cannot be undone by us — the deletion happens in your own document.

How this data is used:
All Google user data is accessed strictly to provide the core functionality of the add-on: generating certificates, tickets and invoices, sending emails (mail merge), and creating related calendar events.

Data storage:
All content remains under the user’s control within their own Google account.
Deletion: Users may delete related data at any time by removing created files / data. When an add-on is uninstalled, data stored within add-on properties is removed according to Google’s data lifecycle policies.

Data sharing:
No data other than described below is shared with third parties.

a) ThriveCart and Stripe
We share limited user information only with our payment and licensing providers for subscription management and legal accounting purposes.
We need to retain billing data as required by legal and accounting obligations.

Data deletion:
All user data remains under the user’s ownership and control within their Google account.
Users may delete related data at any time by removing created files / data or uninstalling the add-on. When an add-on is uninstalled, data stored within add-on properties is removed according to Google’s data lifecycle policies.

3.18 FORMeleon: Choice Limit by Spreadsheet Value

Google user data our add-on accesses:
a) User information
The user’s email address is used solely for account identification within the add-on and for licensing purposes.
If the user activates notifications (e.g. when a choice has been removed), notifications are sent to this email address.

b) Google Forms
The questions and choices of the current form are read, and a choice is removed once the rule you defined is met — that is the core functionality of this add-on.

c) Google Drive
The rule for each choice is read from a spreadsheet you select yourself through the Google file picker. The add-on can only access files you explicitly pick or that it created; it reads the cell you pointed it at and nothing else.

How this data is used:
All Google user data is accessed strictly to provide the core functionality of the add-on: removing a choice when your rule is met, and sending notifications.

Data storage:
We do not store user content on external servers.
All content remains under the user’s control within their own Google account.

Data sharing:
No data other than described below is shared with third parties.

a) ThriveCart and Stripe
We share limited user information only with our payment and licensing providers for subscription management and legal accounting purposes.

Data deletion:
All user data remains under the user’s ownership and control within their Google account.
Users may delete related data at any time by removing created files or uninstalling the add-on.

3.19 YAA: Calendar Templates

Data accessed and purpose:

userinfo.email, userinfo.profile – Used only for account identification within the add-on and licensing.
spreadsheets.currentonly – Create calendars in the current document.
script.container.ui – Display the add-on sidebar.
script.scriptapp – Automatically open the sidebar when activated.
script.external_request – Call external APIs to fetch country-specific holidays.