Privacy Policy

Last changed 9 November 2026.

This page says what this site keeps about you, who else sees it, what leaves the server, and how to remove any of it yourself. The short version: it keeps what a band calendar needs and nothing else, there is no tracking and no advertising here, nothing about you is sold or rented to anybody, and the Delete account button on the Settings page takes all of it out at once.

Ivan Arsic (arsa3d.dev@gmail.com) runs this site. They are who to write to for a copy of what is held about you, and for anything about your data that Settings does not let you change.

What is kept about you

Your Google identity: The account ID Google uses to name you, your email address, your display name, and the link to your profile picture. Google hands these over when you sign in, and the site keeps them so it knows who you are next time. Of these, only the email address is ever shown on a page, and only on your own Settings page.
Your username: The name your band sees. It is on the member list of every band you are in, next to every tick you make on an event page, and in the notifications about events booked or deleted in your bands. No page here says who booked which event: a booking sits on the calendar with no name beside it, and the notification announcing it is the only place a booking is ever said out loud as somebody's.
How the site looks to you: Your colour scheme and your two typefaces. Choosing them changes your pages and nobody else's.
The time you agreed to these pages: One timestamp, kept so the site knows you have been asked and roughly which version you were asked about. Nothing else about that moment is stored, and no copy of these pages is kept against your name.
The time your account was made: One timestamp, from your first sign-in. Those two are the only stamps an account carries here: there is no record of when you last visited, when you last changed something, or what you looked at. A band calendar has no use for that, and keeping it would be the kind of thing this page exists to rule out. Events do keep the time they were last written, because a date that moves silently is worse than one that does not.
Each browser you switched notifications on for: Three strings per browser: the address a notice is posted to, and two keys used to encrypt it on the way. They are what make your phone reachable. They are never shown to anybody on any page, not to you and not to your bandmates, and pressing Turn off in that browser deletes them. Deleting your account deletes them in every browser at once, which is the only way to take them out of a browser you no longer have.
What you book, and how you answer it: An event's title, its kind, its day, its time, its note, who booked it, and who ticked that they are coming. This is the part the site is for, and it belongs to the band rather than to you alone: an admin of the band can delete what you booked, and if you leave the band your ticks in it go with you while the booking stays. Deleting your account is the other way round - it takes what you booked out of every band, along with every tick you left anywhere.

Who sees it

Your band sees your username on its member list, every event in its calendar with the title, kind, day, time and note on each one, and which of its members have ticked that they are coming. What it does not see is who booked which event: no page here says so, and a booking is not attributed to a person except in the notification announcing it.
Somebody who is not in the band sees none of it. Every page behind the sign-in looks up whether you belong to that band first, and a band you are not in simply does not exist for you.
Your email address, your display name, and your profile picture are shown to you and to no one else. Your band sees the username you chose, not the name on your Google account.

What leaves the server

Signing in. The sign-in page loads Google's sign-in button, your browser takes a token from it, and this server asks Google whether that token is real. That is the whole trip, and it is what makes a password here unnecessary.
Notifications. If you press Enable in Settings, a notice about an event - its name, the band, the day and time it is on, who booked it - is carried to your browser through a push service run by Google, Apple, Firefox, or whoever your browser uses. That service sees the text of the notice and the address it is going to. It does not see the rest of your account, and nothing is sent anywhere until you press Enable.
Typefaces. If you pick a body or heading face in Settings, your own browser downloads that face from Google Fonts. Until somebody picks one, no visitor's browser is asked to fetch anything from anywhere but this server.

The one cookie

This site sets exactly one cookie: the signed session that keeps you signed in and holds the token that protects its forms from a page that is not this site. It cannot be read by any script running on a page, it is sent only to this server, and it ends when you close the browser. Everything listed above lives in this server's own database rather than in your browser.

What is not done here

No analytics, no statistics built from what you do, no advertising, and nothing sold or shared for money.
No tracking of where you came from, what you read elsewhere, or what you did on this site beyond what a page has to know to draw it.
No code from a third party on a page except the Google sign-in button on the sign-in page and the typefaces a person chooses.

Where it is kept

Everything is kept in one database file on the machine running this copy of the site. That machine is a virtual server rented from Webdock.io ApS, standing in their data centre in Denmark: they hold the computer the file lives on, and they run the network its address is reached through. This site sends nothing about you to them. The sign-in cookie is signed by that machine, so a tampered one is refused instead of believed. The site keeps no log of what you did: no page-view table, no record of who looked at which event. A server may keep a plain record of the requests it handled, which is part of running a server and not something this site adds to you.

If you want something done

Deletion. The Delete account button at the bottom of Settings deletes your account and everything on it in that moment, with nobody to ask and nothing to wait for: the Google identity, your username, your colours and typefaces, the two timestamps, what you booked in every band, every tick you left anywhere, and every browser you registered for notifications. There is no undo. A band you were only added to carries on without you, and a band you created carries on whenever somebody else is in it and passes to whoever joined it first. The Terms of Use say what the button does, and Settings prints the counts next to it before you press it.
Taking back your agreement. The tick you gave at sign-in covers the Terms of Use and this page together. That same Delete account button is how you withdraw it: this site works only as a band calendar for people who want to be in one, so there is nothing an account can be for once the agreement is gone, and taking the agreement back means taking the account back with it.
A copy. Ask, and you get what is held about you in the terms above, in a form you can read.
A correction. Your username, your colours, and your typefaces are yours to change in Settings, and anything you booked is yours to delete from its own page. Anything else - an email address that is wrong, a name you do not want kept - ask whoever runs the site.
Somebody else to write to. If you would rather complain to an official body than to the people running this site, write to the data protection authority for the country you live in.