EventLane — Privacy Policy
The short version: EventLane runs inside your own Google account. It reads only the spreadsheet you use it in, writes events only to the calendar you pick, and sends nothing to BiLingoPlus servers. The one outside service it talks to is Paddle, our payment provider, and only to check a Pro subscription. No ads, no selling of data, no AI processing of your data.
This policy is about the EventLane add-on for Google Sheets™. The web pages describing it, on bilingoplus.com, are measured with Google Analytics like the rest of the site: see the website privacy policy. Nothing from the add-on, your spreadsheets or your calendars is sent to Google Analytics.
Where EventLane runs
EventLane is a Google Apps Script add-on. Its code runs on Google’s servers under your Google account, the same way a script you wrote yourself would. Your rows go from your spreadsheet to Google Calendar™ through Google’s own services. BiLingoPlus runs no server that your spreadsheet data passes through, and we never receive a copy of it.
What it reads
- Only the spreadsheet you use it in. EventLane uses Google’s “current spreadsheet only” permission (
spreadsheets.currentonly). It cannot open, list or read your other spreadsheets or any other Drive file. From that spreadsheet it reads the sheet tab, header row and columns you choose in its panel. - The list of your calendars, to show them in the calendar picker (
calendar.calendarlist.readonly). - Its own events. To keep the calendar in step with the sheet, it lists the events it created from this spreadsheet tab. It finds them by a private tag it puts on each one, and it does not read your other events.
- Your Google account email address (
userinfo.email), to match a Pro subscription to your account and to show you which account the panel is using.
What it writes
- Events, only in the calendar you pick (
calendar.events). Each event EventLane creates carries a private tag naming the spreadsheet and tab it came from, so EventLane only ever changes or deletes its own events. Events you created yourself are never touched. - Two columns in your sheet: “EventLane status” (the result of the last sync for each row, with a link to its event) and “EventLane ID” (the event each row belongs to).
- Guests. If you map a Guests column, the addresses in it are added to the events. Google Calendar sends them invitations only if you turn on email invitations in the panel.
What it stores
- The setup, inside the spreadsheet. The tab, header row, calendar, column choices, options, the time of the last sync and its counts, and which account runs automatic sync are saved as developer metadata of that spreadsheet, visible only to EventLane. It stays with the spreadsheet: everyone who uses EventLane in it sees the same setup, and it is deleted when the spreadsheet is.
- Small per-user settings, in your own Google account (Apps Script user properties): whether Pro is active and when that was last checked; the email used to verify Pro (your Google account email, or the checkout email you typed); counters for when to ask for a review; the list of spreadsheets where you turned on hourly sync; and the date and number of today’s Pro activation attempts.
- A Pro seat record. So that one subscription cannot be activated on many Google accounts, EventLane keeps a pairing of the checkout email with the Google account that activated it. It holds only SHA-256 hashes of the two addresses, never the addresses themselves.
- Automatic sync (Pro) uses Google Apps Script triggers in your account (
script.scriptapp): on edit, on Google Forms™ submit and hourly. They run EventLane for that spreadsheet when you are not in it.
EventLane keeps no copy of your rows or your events anywhere outside the spreadsheet and the calendar themselves.
Third parties
The only call EventLane makes outside Google is to Paddle, our payment provider and Merchant of Record, to check whether the email used for Pro has an active EventLane subscription. It sends that email address, and nothing from your spreadsheets or calendars. The check runs when you press Activate Pro and then about every three days while Pro is active. Checkout itself happens on Paddle’s pages; EventLane never sees your card details. Paddle’s privacy policy applies to the checkout.
We do not sell, rent or share your data, we show no ads, and we do not use your data for AI, machine learning or any other processing beyond the sync you asked for.
Permissions
spreadsheets.currentonly: see and edit only the spreadsheet you use EventLane in.calendar.events: create, update and delete the events EventLane makes.calendar.calendarlist.readonly: list your calendars in the picker.script.container.ui: show the EventLane panel.script.external_request: talk to Google Calendar and check a Pro licence with Paddle.script.scriptapp: run automatic sync when you are away (Pro).userinfo.email: match your Pro licence to your account.
Google API Services User Data Policy
EventLane’s use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements. Its use of data from Google Workspace APIs also follows the Google Workspace API User Data and Developer Policy.
- Google user data is used only to provide the sync you set up in the panel.
- It is not transferred to anyone, except to Paddle as described above, and not used for advertising.
- It is not used to create, train or improve any AI or machine-learning model.
- No one at BiLingoPlus reads your spreadsheets or calendars.
Technical logs
Google Apps Script keeps technical logs for us in Google Cloud Logging, so that we can see when EventLane breaks. A sync writes one line with numbers only: how many rows it read and how many events it created, updated, left unchanged or deleted, and how long it took. Errors are logged with their error message. These lines do not contain the content of your rows or events, and we use them only to fix problems.
Security
All requests EventLane makes, to Google and to Paddle, use HTTPS. Your settings are stored in Google’s own per-user storage, protected by your Google account’s security. Payment data is handled by Paddle and never reaches EventLane or BiLingoPlus.
Deleting your data
- Erase my data, at the bottom of the EventLane panel, deletes the settings EventLane keeps for your account (including the Pro status and checkout email) and switches off your automatic sync. Today’s count of activation attempts stays until the next day, so activation cannot be retried without limit. Events in your calendar stay.
- Remove events created from this sheet, under Undo and data, deletes every event this sheet created in the chosen calendar.
- The setup saved in a spreadsheet is part of that spreadsheet and is deleted with it.
- Uninstall EventLane in Google Sheets (Extensions → Add-ons → Manage add-ons) and remove its access at myaccount.google.com/connections to cut it off from your account.
- To remove the Pro seat record, or for anything else, write to info@bilingoplus.com.
Changes
If EventLane changes how it handles data, this policy will be updated before that version is published, and the date above will change.
Contact
EventLane is operated by, and the data controller is, BiLingoPlus LLC, a Wyoming limited liability company, 30 N Gould St Ste R, Sheridan, WY 82801, USA · info@bilingoplus.com
Google Sheets™, Google Calendar™, Google Forms™ and Google Workspace™ are trademarks of Google LLC. EventLane is an independent product and is not endorsed by or affiliated with Google.