Privacy policy for Form Alerts
Exactly which Google user data the add-on accesses, how it is used, shared, protected, kept and deleted.
This page supplements the general privacy policy with the details specific to Form Alerts. Last updated 12 November 2026.
Permissions
| Permission (OAuth scope) | What it allows | Why the add-on needs it |
|---|---|---|
forms.currentonly |
Read and edit the form the add-on is open in | Read the questions (to offer placeholders and conditions) and new responses (to send notifications). It cannot see any other file. |
script.send_mail |
Send email from your account | Send the notification and confirmation emails you configure. It does not read your mailbox. |
script.scriptapp |
Manage the add-on’s own triggers | Create the “on form submit” trigger that runs your rules, and remove it when you delete the last rule. |
script.external_request |
Connect to external services | Post messages to the Slack, Discord, Google Chat and Telegram webhooks you configure, and check a Pro licence key with our payment provider. Requests can only go to those hosts. |
script.container.ui |
Show a sidebar in Google Forms | Display the add-on’s interface. |
userinfo.email |
See your email address | Identify your account for the licence and pre-fill the first rule. |
Google user data we access
- The questions and title of the form the add-on is open in.
- Each new response to that form, at the moment it is submitted.
- Your Google account email address.
Nothing else: no other forms, files, mailbox contents, contacts or calendar.
How we use it
Only to provide the features you set up: fill placeholders, check a rule’s condition, and send the emails and chat messages your rules describe. Your email address pre-fills the first rule and identifies a Pro licence. We do not use Google user data for advertising, profiling, selling, lending decisions, or to develop, improve or train AI or machine-learning models.
Who we share it with
Only with the destinations you choose, and only the content you configure:
- Email recipients in your rules, sent from your own Gmail account.
- Chat services whose webhook you add to a rule (Slack, Discord, Google Chat or Telegram). They receive the message text you configured, which may include answers from the response.
- Dodo Payments, our merchant of record, only if you buy Pro: your licence key and email address. No form data is sent to it.
We do not transfer Google user data to anyone else, including advertisers, data brokers or AI services. We run no server of our own and never receive your forms or responses.
How it is protected
The add-on runs inside your Google account on Google Apps Script. Your rules, Activity log and licence key are kept in Google’s add-on storage (inside the form or your account), protected by your Google account’s sign-in and Google’s security. Every outside request uses HTTPS, and the add-on’s manifest only allows requests to the hosts listed above. We, the developer, have no access to your forms, responses, rules or logs.
Retention and deletion
- Responses: processed when submitted and not stored by the add-on.
- Activity log: the last 30 runs (time, rule name, status and a short message, not the full response) are kept inside the form until you click Clear activity or a newer run replaces them.
- Rules: kept inside the form until you delete them.
- Licence: kept in your account’s add-on storage and by Dodo Payments while your licence exists. Email support and we delete your licence record.
- Everything: uninstall the add-on, or remove it at myaccount.google.com/connections, to revoke all access immediately.
Limited Use
Form Alerts’ use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Workspace APIs adheres to the Google User Data Policy, including the Limited Use requirements.