WMJ webmasterj.dev

Privacy policy: Ticket to Calendar

Last updated: 15 November 2026

In short: Ticket to Calendar runs inside your own Google account. It reads only the email you have open, creates the calendar event you ask for, and saves the ticket PDFs to your own Google Drive. Your data is never sent to me or to anyone else, never sold, and never used for advertising.

This policy explains what data the Ticket to Calendar add-on for Gmail ("the add-on") uses and why. The add-on is made by Jadran Bizic, Zagreb, Croatia ("I", "me"). Contact: support@webmasterj.dev.

Where the add-on runs

The add-on is a Google Apps Script program. It runs on Google's servers, under your own Google account, only while you use it in Gmail. It talks only to Google's own services (Gmail, Google Calendar, Google Drive and Google Contacts). I don't run a server for it, and it has no analytics, tracking or advertising.

What it accesses and why

Google dataWhat the add-on does with it
The email you have open (gmail.addons.current.message.readonly, gmail.addons.execute) When you open the add-on next to an email, it reads that one email (sender, subject, text and attachments) to find the event title, date, time, venue and ticket PDFs. It can't read, search or change any other email.
Calendar events (calendar.events) Creates the event you confirm, with the guests you choose, and looks for an event it created earlier from the same email so you don't create duplicates. It marks its events with the email's ID for that purpose. It doesn't read or change your other events.
Drive files the add-on creates (drive.file) Creates an Ulaznice folder in your Drive, saves the ticket PDFs from the email (or the PDFs you upload) there, attaches them to the event and shares them with the guests you add. To read the text of a ticket PDF, it briefly converts it to a Google Doc and deletes that copy straight away. It can't see any other files in your Drive.
Contacts (contacts.readonly, contacts.other.readonly) Suggests names and email addresses while you type a guest's name. Only the matching names and addresses are used, and they're not stored, except the ones you add as guests (see "Nicknames" below).
External requests (script.external_request) Needed to call the Google Calendar, Drive and Contacts services listed above. The add-on doesn't connect to anything outside Google.

What it stores

  • In your Google Calendar and Drive: the events and ticket files you create. They're yours, and they stay until you delete them.
  • Add-on settings (stored by Google, for your account only): the ID of your Ulaznice folder, your default event length, your nicknames (names you've invited with their email address, so they're quicker to pick next time), and the list of PDFs you uploaded for an email until the event is created.
  • Temporary cache (for your account only): the text read from a ticket PDF, for up to 6 hours, so reopening the same email is faster.

I can't see any of this. It isn't sent to me, and the add-on keeps no logs of your emails, events, files or contacts.

Sharing

Your data isn't sold, rented or shared with anyone. The only sharing the add-on does is what you ask for: when you add guests, it invites them to the event (if you choose to send invitations) and gives them view access to the event's ticket PDFs.

Google API Services User Data Policy

Ticket to Calendar's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The data is used only to provide the features described above, is not transferred to anyone, is not used for advertising, and isn't read by people.

Deleting your data

  • In the add-on, open Settings → Delete saved data to delete your nicknames, settings and upload list.
  • Delete events in Google Calendar and the ticket files in your Ulaznice Drive folder as usual.
  • To remove the add-on and its access, uninstall it from Gmail, or remove it at myaccount.google.com/connections.

Security

All data stays within Google's infrastructure and is transferred over encrypted connections. The add-on asks only for the narrowest permissions it needs (for example, only the open email instead of your whole mailbox, and only its own Drive files).

Children

The add-on is not directed at children under 16.

Your rights

Under the EU General Data Protection Regulation (GDPR) you have the right to access, correct and delete your personal data. Because the add-on keeps your data only in your own Google account, you can do all of this yourself as described above. If you have a question or complaint, email me. You can also contact the Croatian data protection authority (AZOP).

Changes

If this policy changes, the new version will be posted on this page with a new date. If the add-on ever needs new permissions, Google will ask you for consent again.

Contact

Jadran Bizic · support@webmasterj.dev