Doorstub privacy policy
Last updated November 20, 2026. Doorstub: QR Event Tickets & Check-In is a Google Sheets add-on made by Great Work LLC.
This page explains what Google user data Doorstub 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 Doorstub accesses
- The spreadsheet you open it in (permission
spreadsheets.currentonly): Doorstub reads the guest list in that spreadsheet (names, email addresses and any columns you use in the ticket email) and writes its own columns (ticket code, ticket status, check-ins), a check-in log and an attendance sheet. It cannot open your other spreadsheets, your Drive or your Gmail. - Sending email as you (
script.send_mail): to send the ticket emails you start, each with its QR code, to the guests in your sheet, and at most one note a day to you when new registrations are waiting for tickets. This permission can only send. It cannot read, search or delete any email. - Running when you are not present (
script.scriptapp): only if you turn on automatic tickets or phone scanning, to create Doorstub's own triggers on that spreadsheet: one that issues a ticket when a linked form adds a registration, and an hourly one that sends emails held back by Google's daily email limit and copies phone check-ins into the sheet. - Your email address (
userinfo.email): to know which account a free trial, subscription or ticket pack belongs to, and to sign requests to Great Work's ticket service. - Connecting to an external service (
script.external_request): used only to reach Great Work's services at addons.greatwork.company: the licensing service, which checks your trial or subscription, and the Doorstub ticket service, which keeps your ticket pack balance and, if you turn on phone scanning, the encrypted door list. - Showing the sidebar and dialogs (
script.container.ui).
How Doorstub uses Google user data
Only to provide event tickets and check-in: to give each guest a ticket code and QR code, email their ticket, check them in at the door, and keep your sheet's check-in columns up to date. Guest names and email addresses are used only for those tickets and emails. Your email address is used only to identify your trial, subscription or ticket packs and to sign requests to our service. Doorstub does not use Google user data for any other purpose: not for advertising, not for selling, not for profiling, and not to develop, improve or train AI or machine-learning models.
Where data goes and what's stored
- Most of the work happens inside Google. Doorstub runs in Google Apps Script on Google's servers, under your own account. QR codes are made inside Apps Script. Ticket emails are sent from your account through Google's mail service; their contents never pass through Great Work.
- In your spreadsheet: the guest list, Doorstub's columns, the check-in log and the attendance sheet.
- In the spreadsheet's add-on storage (Apps Script document properties): your event settings and email wording, the secret key used to make ticket codes, and, while phone scanning is on, the scanner key.
- In your Google account's private add-on storage (Apps Script user properties and cache): small counters (such as when the last daily note was sent) and a cached copy of your license status.
- Phone scanning (optional, off by default). When you turn it on, Doorstub builds the list the door phones need: event name, date and venue, session names, and for each ticket its code, the guest's name (or, if the row has no name, the part of the email address before the @), which sessions it opens, whether it is cancelled and whether it is already checked in. No email addresses or other columns are included. Doorstub encrypts this list inside Google Apps Script with a random 256-bit key before it leaves Google. The key exists only in your spreadsheet's add-on storage and in the scanner link after the # sign, which browsers never send to a server. We can't read the list.
- What the Doorstub ticket service stores (addons.greatwork.company/forms-event-tickets): for phone scanning, the encrypted list, the event ID, your Google account email (so only you can update or delete it), a hash of a key derived from the scanner link, and each check-in (ticket code, session number, time and the label the staff member typed, such as "Maria at door 1"). For ticket packs, your balance and a record of purchases (Stripe Checkout session IDs, pack, ticket count) and spends (counts only), against your Google account email.
- The scanner page keeps the encrypted list and any scans waiting to sync in the phone's browser storage.
- What reaches Great Work's licensing service: your Google account email, the add-on name and a count of tickets issued during the trial, and if you subscribe, your Stripe customer and subscription status.
How we protect your data
- Your guest data stays in your Google account. The guest list, emails and check-in columns live in your Google account, where Google encrypts them in transit and at rest. Our service never receives email addresses or your other columns.
- End-to-end encrypted door list. The phone scanning list is encrypted and authenticated (HMAC-SHA256 based, encrypt-then-MAC) before it leaves Google, and only phones holding your scanner link can decrypt it. Making a new scanner link stops all old links at once.
- Least access. Doorstub asks only for the spreadsheet it is opened in, never your Drive or other files, and only for permission to send email, never to read it.
- Signed requests. Each request from the add-on to our services is signed (HMAC-SHA256) and can't be replayed, and only the Google account that created an event can update, read check-ins from or delete it.
- Encryption in transit. Calls to our services always use HTTPS, with only TLS 1.2 or 1.3 and HSTS.
- No logs or tracking. Web server access logging is turned off for the ticket service and the scanner page. The scanner page loads no third-party scripts, sets no cookies and sends no referrer.
- Access controls on our server. The ticket service and licensing records are held on a server in the United States (DigitalOcean, New York) 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, each 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 guest data. 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. Ticket emails go to the guests in your sheet, sent from your own account, at your direction. The encrypted door list reaches only the phones you give the scanner link to. Stripe processes payments; our email provider sends billing emails you ask for.
Limited Use
Doorstub'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
- Phone scanning data (the encrypted list and its check-ins) is deleted from our service when you turn phone scanning off in the Door tab, or automatically after 90 days with no activity. Signatures used to block replayed requests are deleted after 15 minutes.
- Ticket pack records (balance, purchases and spends) are kept while you use Doorstub, because packs never expire.
- Your sheet, its columns and the add-on's settings stay in your spreadsheet until you delete them. Uninstall Doorstub (Extensions > Add-ons > Manage add-ons) and revoke its access at myaccount.google.com/permissions to stop all access.
- Email hello@greatwork.company from your account and we delete your ticket pack and licensing records within 30 days, apart from billing records the law requires us to keep. Web server logs for our licensing service (IP address, time, request path, never request contents) are kept for 14 days. Server backups roll over within four weeks.
Contact
Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA. hello@greatwork.company