Privacy Policy
Effective November 5, 2026
This policy explains how Calendrow (the Google Sheets add-on and the website calendrow.com) handles personal data. Calendrow is provided by Brad Alan McBee, an individual (sole proprietor) located in Iowa, United States ("we", "us"). We are the controller of the personal data described here. Contact: support@calendrow.com.
The short version
- Calendrow runs inside Google Sheets under your own Google account. Your spreadsheet and calendar contents are processed there and are not sent to Calendrow servers.
- We don't sell data, use it for advertising, or use it to train AI models.
- The website uses no cookies and no tracking.
Google user data Calendrow accesses
When you install Calendrow, Google asks you to allow these permissions. Calendrow uses each one only to provide the feature you are using:
| Permission | What Calendrow does with it |
|---|---|
View and manage spreadsheets that this application has been installed in (spreadsheets.currentonly) | Reads the rows and headers of the sheet you open Calendrow in, and writes the sync status and hidden link columns back to that sheet. It cannot open your other files. |
Make secondary Google calendars, and see, create, change and delete events on them (calendar.app.created) | Creates the calendar you ask for, and creates, updates, restores or moves the events that correspond to your rows. It cannot see or change your other calendars. |
Display and run third-party web content in prompts and sidebars inside Google applications (script.container.ui) | Shows the Calendrow sidebar. |
Calendrow's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not allow humans to read your Google user data, except with your explicit permission for a support request, where required for security or legal reasons, or when the data has been aggregated and anonymized for internal operations.
Where Calendrow stores information
- In your spreadsheet: the Sync status, Sync message and Last synced columns, plus three hidden columns (event ID, calendar ID and a fingerprint of the row) that link rows to events.
- In your spreadsheet's add-on settings (Google document properties): your column choices, chosen calendar and time zone.
- In your Google account's add-on settings (Google user properties): the list of calendars Calendrow created for you, your monthly event count for the free plan, and a random identifier that marks which person set up a sheet.
- In your Google Calendar: the calendars and events you create. Each event carries a small hidden tag linking it to its spreadsheet.
All of the above lives in your Google account, and you can delete it at any time (see "Deleting your data").
Diagnostic logs
To find and fix problems, Calendrow records technical events in Google Cloud Logging under our developer account. These contain counts and error codes, for example "batch of 100 rows: 98 created, 2 skipped". They do not contain your event titles, dates or locations. If an error occurs, the log may include the short error message shown to you, which can name a column header. Logs are kept for 30 days.
Paid plans
When paid plans are available, payments will be processed by Paddle.com, our reseller and Merchant of Record. Paddle collects your name, email, billing address and payment details under its own privacy policy (paddle.com/legal/privacy), and shares with us the information needed to provide your plan: name, email, country, plan and subscription status. To check your plan, Calendrow will send a one-way scrambled (hashed) form of your Google account email and your email domain to our licensing service. It never sends spreadsheet or calendar contents.
Website
calendrow.com uses no cookies, analytics or advertising trackers. It is hosted by Cloudflare, which processes visitors' IP addresses and request details to deliver and protect the site.
Support emails
If you email us, we keep your message and email address to answer you and to improve Calendrow. We delete support conversations two years after they end, or sooner if you ask.
Why we process data (legal bases)
- To provide Calendrow when you use it (performance of a contract).
- Diagnostic logs and security (our legitimate interest in a reliable, secure service).
- Billing records (legal obligation, and contract).
Who receives data
- Google: Calendrow runs on Google Apps Script, and your data stays in Google's services under your account.
- Paddle.com: Merchant of Record for paid plans.
- Cloudflare: website hosting, email forwarding and, for paid plans, the licensing service.
- Professional advisers, and authorities where the law requires it.
Some of these providers process data in the United States and other countries. Where required, they rely on safeguards such as standard contractual clauses.
Retention
Data in your Google account stays until you delete it. Diagnostic logs: 30 days. Support emails: up to two years after the conversation ends. Billing records: as long as tax law requires (Paddle keeps transaction records as Merchant of Record).
Your rights
Depending on where you live, you may have the right to access, correct, delete, restrict or object to our processing of your personal data, to data portability, to withdraw consent, and to complain to your data protection authority. Email support@calendrow.com and we will respond within one month.
Deleting your data
- Remove the add-on: Extensions → Add-ons → Manage add-ons → Calendrow → Remove.
- Revoke access at myaccount.google.com/permissions.
- Delete Calendrow calendars in Google Calendar and the sync columns in your sheet.
- Ask us to delete support emails or licensing records: support@calendrow.com.
Security
Calendrow requests the narrowest Google permissions that make it work, never asks for your password, and keeps your content inside your Google account. Access to our developer and payment accounts is protected with two-factor authentication.
Children
Calendrow is not directed to children under 13 and we do not knowingly collect their data.
Changes
We will post any changes here and update the effective date. If a change materially affects how we use Google user data, we will tell users in the add-on before it applies.