Form Bugle privacy policy
Last updated October 20, 2026. Form Bugle: Form Alerts to Chat™ and Webhooks is a Google Forms™ add-on made by Great Work LLC.
This page explains what Google user data Form Bugle accesses, how it uses that data, how the data is protected, how long it is kept and how to delete it. It adds to the Great Work add-ons privacy policy, which covers billing.
Google user data Form Bugle accesses
- The form you open it in (permission
forms.currentonly): its questions and its responses, and the respondent's email address if your form collects it. It cannot see your other forms, your Drive or your email, and it cannot send email. - Your email address (
userinfo.email): to look up your free trial or subscription. - Connecting to external services (
script.external_request): to post alerts to the chat or webhook destinations you add, and to reach our licensing service. - Running when a response arrives (
script.scriptapp): to create and remove the form-submit trigger and the retry/digest timer. - Showing the sidebar (
script.container.ui).
How Form Bugle uses Google user data
Form Bugle uses your form's data for one purpose: to send an alert about each new response to the destinations you set up. When someone submits your form, it reads that response, builds a message containing the answers you chose for each destination (all answers, or only the questions you pick, plus the respondent's email and response links if you leave those options on), and posts it to that destination. It reads the form's questions so you can choose fields and set conditions in the sidebar. Your email address is used only to identify your trial or subscription.
Form Bugle does not use Google user data for any other purpose. It does not use it for advertising, does not sell it, does not build profiles, and does not use it to develop, improve or train AI or machine-learning models.
Where responses go
Only to the destinations you add and approve in the sidebar, which must be on Form Bugle's list of supported HTTPS hosts (Slack, Discord, Microsoft Teams, Google Chat, Telegram, Zapier and similar webhook services). Once posted, a message is stored and governed by that service (for example Slack's or Discord's own privacy policy), not by us. Responses go from Google's servers directly to your chosen service; they never pass through Great Work's servers.
What's stored, and where
- Your destination settings are stored in the form's own add-on storage (Apps Script document properties).
- Webhook links, bot tokens, the delivery log, the retry queue and pending digests are stored in your own Google account's private add-on storage (Apps Script user properties), so other editors of the form can't read them.
- What reaches Great Work's servers: your Google account email, the add-on name and a count of trial uses, and if you subscribe, your Stripe customer and subscription status. Never the form, its questions or its responses.
How we protect your data
- Form data stays inside Google until it goes to your destination. Form Bugle runs in Google Apps Script on Google's servers, under your own account. Responses, settings and queued messages live in your Google account, where Google encrypts them in transit and at rest. We keep no copy.
- Encryption in transit. Alerts are posted only to https:// addresses on the supported-host list; plain http:// and unlisted hosts are refused, both by the add-on and by Google's URL allowlist in its manifest. Calls to our licensing service use HTTPS (TLS 1.2 or 1.3, with HSTS), and each request is signed (HMAC-SHA256) so it can't be forged or altered on the way.
- Secrets are isolated per user. Webhook links and bot tokens are kept in per-user storage that other editors of the form can't read, and are shown masked in the sidebar.
- Least data per destination. Each destination receives only the fields you selected for it.
- Access controls on our server. The licensing record (email, trial count, subscription status) is held on a server that only Great Work's administrator can sign in to, with SSH keys from a single allowed network address and no passwords. A firewall blocks everything except web traffic, the service runs under its own unprivileged account whose data only it can read, and the server has file-integrity monitoring, audit logging and intrusion alerts.
- Payments. Card details are entered on Stripe's own pages and never reach us.
- People. No person at Great Work reads your form responses. The only exceptions are when you ask us for support and give permission, when it's needed to investigate abuse or a security issue, or when the law requires it.
- Incidents. If we learn of a security breach affecting your data, we'll tell affected users and Google promptly, as the law and Google's policies require.
Sharing
We don't sell, rent or share Google user data. Response data goes only to the destinations you configured. Stripe processes payments; our email provider sends billing emails you ask for.
Limited Use
Form Bugle's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Retention and deletion
- Retry and digest copies of a message are deleted once delivered, after about a day of failed retries, or when you turn alerts off. The delivery log keeps only recent entries.
- Remove a destination to delete its link or token. Remove the add-on (in the form, the puzzle-piece menu > Manage add-ons) and revoke its access at myaccount.google.com/permissions to stop all access. Deleting the form deletes the settings stored with it.
- The licensing record is kept while you use Form Bugle. Email hello@greatwork.company from that account and we delete it within 30 days, apart from billing records the law requires us to keep. Web server logs (IP address, time, request path, never request contents) are kept for 14 days. Server backups roll over within four weeks.
Google Forms and Google Chat are trademarks of Google LLC.
Contact
Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA. hello@greatwork.company