Last updated: 18 October 2026
This policy describes how the Google Sheets add-on MartensLink Events (“Events”) accesses, uses, stores and shares data, including data from your Google account. Events is made by MartensLink AB (corporate identity number 559580-3437), Roslagstullsbacken 13C, 114 21 Stockholm, Sweden. Our general Privacy Policy covers our website, support and purchases.
Questions: privacy@martenslink.com
1. The short version
- Events runs inside your own Google account. Your forms, answers, participants, schedules and payment records are stored in your Google Sheets and Google Forms. MartensLink has no server that receives them, and we cannot see them.
- Events sends data to one outside service, and only if you turn it on: your own Stripe account, to create payment links.
- Events checks whether your account has Pro with MartensLink’s licence service. Google confirms which Google account you use, and the licence service keeps only an encrypted key derived from the account’s ID. No email address and nothing about your events or participants is stored there.
- We do not sell data, use it for advertising, or use it to train AI models.
2. Who is responsible for which data
You, the organiser, decide which participants’ data your event collects and why. You are the controller of that data under data protection law. Google, and Stripe if you use payments, process it on your behalf under your own agreements with them.
MartensLink provides the software. Because Events runs in your account and sends nothing to us, MartensLink is not a processor of your participants’ data. We are the controller only of the limited data described in sections 6 and 7: the licence check, technical diagnostics, and what you send to our support.
If you registered for an event that uses Events, the organiser is responsible for your data. Contact the organiser with questions about your data.
3. Google user data that Events accesses
When you install Events, Google asks you to allow the permissions below. Events uses each one only for the purpose described.
| Permission | What Events does with it |
|---|---|
See, edit, create and delete only the spreadsheet you use Events in (spreadsheets.currentonly) | Reads registrations from the spreadsheet you use Events in. Writes the lists, schedules and payment overviews you create. Keeps its own records in hidden tabs. Reads who can edit the spreadsheet, to recognise your own test sign-ups. Events cannot open or create any other spreadsheet. |
See, edit, create and delete your Google Forms (forms) | Creates and updates the registration forms you build, reads their answers, opens and closes registration, and creates a cancellation form if you turn cancellation on. |
Send email as you (script.send_mail) | Sends the emails you set up or ask for, such as confirmations, payment links, reminders and schedules, from your Google account to your participants and to you. |
Connect to an external service (script.external_request) | Connects to Stripe’s API (api.stripe.com) when you use payments, and to MartensLink’s licence service (martenslink-licens.martenslink.workers.dev) to check whether your account has Pro. Events can connect to no other address. |
Run when you are not present (script.scriptapp) | Lets Events handle new registrations and check payments automatically, for example once an hour and at the times you set for opening or closing registration, in the spreadsheet you use it in. |
Show content inside Google applications (script.container.ui) | Shows the Events panel and dialogs in Google Sheets. |
Confirm your identity (openid) | Lets Google confirm to MartensLink’s licence service which Google account you use, so that Pro follows your account to all your spreadsheets. The signed statement from Google is sent only to the licence service (section 6.2). |
See your email address (userinfo.email) | Sets your address as the reply-to address on emails to participants, sends test emails and summaries to you, keeps track of who runs the event, and recognises your own test sign-ups. |
Examples of the data this includes: the questions and answers in your forms (for example participants’ names, email addresses and the sessions they chose), the contents of the spreadsheet you use Events in, and your own email address.
4. How Events uses that data
Events uses Google user data only to provide the features that you see and use in the add-on: building forms, managing registrations and places, calculating and requesting payments, making schedules, and sending emails. It does not use the data for any other purpose.
Events does not use Google user data for advertising, does not sell it, does not use it to judge creditworthiness, and does not use it to create databases for any other purpose. Events does not use Google Workspace APIs or Google user data to develop, improve or train generalised or non-personalised AI or machine learning models.
MartensLink Events’ use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
5. Where the data is stored
Everything Events stores is stored in your Google account:
- In your spreadsheet: the response tabs, the lists and schedules you create, and hidden tabs where Events records which answers it has handled, which emails it has sent and which payments it has received. Do not delete those tabs. Without them, Events may send emails twice.
- In your Google Forms: your forms and their answers.
- In the spreadsheet’s settings (document properties): the event’s settings, such as payment settings, limits, texts and the schedule’s configuration, and the email address of whoever runs the event. It is shown to others who can edit the spreadsheet, so they know who makes the changes.
- In your account’s settings for Events (user properties): your own preferences, your saved templates and question blocks, your Stripe key if you use payments, and the licence service’s latest answer on whether your account has Pro. They are visible only to your Google account.
MartensLink has no copy of this data. It stays until you delete it (see section 9).
6. What leaves your Google account
6.1 Stripe (only if you turn on payment)
Payment uses your own Stripe account and a restricted API key that you create and paste into Events. When Events creates a payment link or checks payments, it sends to Stripe, from your account:
- the payer’s email address, to fill in the payment page and match payments;
- the receipt lines: by default the participant’s name and what they are paying for (for example a session or an option), or only a total if you choose “total only”;
- amounts, currency and VAT information, including your event’s venue address if you use Stripe Tax for admission;
- references that let Events match payments: a payment reference, a one-way coded (hashed) identifier for the payer, and an identifier for your spreadsheet.
Stripe processes this as your provider under your agreement with Stripe. Payments go directly to your Stripe account. MartensLink does not receive the data or the money. Events shows what is sent to Stripe in the payment settings.
6.2 MartensLink’s licence service
Events asks MartensLink’s licence service whether your account has Pro. The licence service runs on Cloudflare. Events sends a signed identity statement from Google (an ID token) that proves which Google account you use, and receives the licence status, for example “active until 31 March”. The statement contains your account’s ID and your email address. The licence service uses only the ID and keeps it only as an encrypted key. Your email address, your name and data about your events or participants are not stored and not passed on.
If you have Pro, Events asks at most a couple of times a day; otherwise at most once a day, so that a purchase on our website shows up by itself. For accounts with Pro, the licence service keeps the key, the licence status, Paddle’s references for the purchase and whether a purchase has been refunded (the guarantee on a first purchase applies once per customer). If your account has never had Pro, the key is kept only in counters that protect the service from overload, and those are deleted within about a day.
The purchase is made with Paddle, the Merchant of Record, which holds your purchase details. Paddle receives the licence service’s key for your account together with the purchase, so that the purchase is linked to the right account, and tells the licence service when a purchase is made, renewed, refunded or ended. Events itself never connects to Paddle (see our general Privacy Policy).
6.3 Technical diagnostics to MartensLink
When something goes wrong, Events writes a short technical message to MartensLink’s Google Cloud project, so that we can find and fix errors. Before a message leaves your account, Events removes email addresses, links, file identifiers, Stripe identifiers and quoted text such as names and titles. The message describes what happened (for example “3 sent, 1 failed”), not who it happened to. Google adds technical information such as the time and the function that ran. We keep these messages for up to 30 days.
A complete version of each error message is kept in a hidden _Log tab in your own spreadsheet, where only you can see it.
6.4 Emails to participants
Emails that Events sends are sent by Gmail from your Google account, and they are stored in your Sent folder. MartensLink does not receive them.
6.5 Nothing else
Events loads no tracking, advertising or analytics code. The QR code for your form is created inside the panel. The form link is never sent to an outside QR service.
7. When people at MartensLink can see your data
People at MartensLink cannot see your data through Events. We only see it if you give it to us, for example in a support case where you send a screenshot or share a file with us. We then use it only to solve your case, as described in our Terms of Service, section 12. We may also handle data where the law requires it, or where it is necessary for security, for example to investigate abuse.
8. Security
- Events runs in Google’s infrastructure, in your account, and connects only to Stripe and MartensLink’s licence service over encrypted connections (HTTPS).
- Events only accepts restricted Stripe keys, which limit what the key can do. It never accepts your full secret key.
- Your Stripe key is stored in your own account’s settings for Events. It is never shown again in full, and it is never written to logs.
- Diagnostics leave your account only after personal data has been removed (section 6.3).
- MartensLink protects its own accounts with two-step verification, and only the people who need access have it.
9. Deleting your data
Because your data is in your Google account, you control it:
- Remove the Stripe key: in Events, under Payment → Stripe, remove the key. You can also delete or roll the key in your Stripe dashboard at any time.
- Remove an event’s data: delete the spreadsheet and its forms in Google Drive.
- Remove saved templates and question blocks: delete them in Events under ⚙ → Save as template or block.
- Stop Events completely: uninstall it under Extensions → Add-ons → Manage add-ons, and remove its access at myaccount.google.com/permissions. Events then stops running in all your spreadsheets.
- Licence data and diagnostics held by MartensLink: email privacy@martenslink.com. Diagnostics are deleted automatically after 30 days.
Your participants’ data in Stripe is controlled by you in your Stripe account.
10. Participants’ rights
Participants should contact the organiser to see, correct or delete their data. As organiser, you can find and change a person’s answers in the response tab and the People list, take someone out of the event, and delete people you added by hand. Answers are deleted in Google Forms and in the spreadsheet.
11. Children
Events is meant for adults who organise events. Organisers may use Events for events with children, for example camps. The organiser is then responsible for any consent the law requires from a parent or guardian, and for collecting only what is needed.
12. Changes
If we change how Events uses Google user data, we will update this policy and tell you in the add-on before the change takes effect. The date at the top shows when it was last updated.
13. Contact
MartensLink AB, Roslagstullsbacken 13C, 114 21 Stockholm, Sweden
privacy@martenslink.com · support@martenslink.com
You can also complain to the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, imy.se) or to the supervisory authority where you live.