Who is responsible. This site is run by whoever set it up (they have not stated who they are: ask them where you got the link); you reach them at the address they gave you. They are the controller of your data in the sense of the GDPR. There is no data protection officer, as the site is run by one person or a small group.

What we process, why, and on what basis. To find a time for a meeting we process what you give us for it: the times you mark, your name (unless you are anonymous), your e-mail address if you give one ("Invite me at": kept with each meeting and with your profile, see the terms), the title and length of a meeting, your time zone, and, if you connect one, what your calendars say about when you are busy. We use it for nothing but running this site: finding the time, showing the others who can when, inviting them, and keeping the site working. The legal basis is that you ask us to do this (Art. 6(1)(b) GDPR: it is needed for what you use the site for). Where somebody else enters data about you (a host names you for a meeting, or gives your address so that you are invited), the basis is their and our legitimate interest in arranging that meeting with you (Art. 6(1)(f)); you learn of it with the invitation, and you can leave the meeting or have everything removed (see "Your rights"). Keeping the server safe (limits on what one address may ask, a log of errors without names) is our legitimate interest as well (Art. 6(1)(f)). Your browser's storage of what you put into forms is used only with your consent, which the choice at the top of this notice gives or withholds (Art. 6(1)(a)); the random identity it must keep is needed for the site to work at all. We do not use your data for advertising, we do not profile you, and no decision with legal effect on you is made automatically: the best time is a proposal to the host, who decides. You are under no obligation to give us any data; what you do not give is simply not used (without a name you are "Anonymous", without calendars we go by what you mark).

Where your data is. Our server runs on a machine of whoever runs this site, and what it stores is kept in a database there. What is in each stored item (names, titles, addresses, the times you mark, what gives access to a calendar) is in addition encrypted by our server itself before it is stored, with a key that is kept apart from the database. Your identity and everything kept for it (your profile, the calendars you connected, your open meetings) expire two years after you last used the site; a scheduled meeting expires one day after its last day (see "How long"). Readable in the database itself are only the keys under which the items are found and when they expire: random ids of users and meetings, the kind of each item (e.g. "availability", "meeting"), and the day a meeting or a day of it starts, by which the items are sorted. Not when you can or what is in your calendar: that is inside the items. What was read from your calendars a moment ago is kept on the server itself for some minutes, to not read them again at once, and is gone at the latest after a day. Nothing is passed on to anybody else, except as described here (e.g. an invitation your calendar sends).



Who else gets your data. The company that runs the machine and the database (see "Where your data is") is our processor: it stores the encrypted data for us and may not use it. If you connect Google Calendar, data goes to Google at your request (your Google account is where the calendar is), under Google's own privacy terms; Google is in the USA, and such transfers rest on the EU-US Data Privacy Framework and Google's standard contractual clauses. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. A CalDAV server or a calendar address you connect is one you chose; what we exchange with it is described below. Other participants of a meeting see your name and when you can, as described here and in the terms. Nobody else gets anything, and nothing is sold or passed on for advertising.

Calendars outside N meet K. What we write into a calendar (yours, or the one of a host that invites you), and the invitations and cancellations such a calendar sends, become part of that calendar and of the calendars and mailboxes of everybody who received them, at Google, a CalDAV server or elsewhere. They may keep names and addresses after a meeting, or your profile, is deleted here. That is out of our hands: we can not remove anything there.

Your calendars (Google Calendar, CalDAV, iCal address). Connecting a calendar is optional. If you connect one, we use it in two ways only.
1. We read the start, end and title of your events on the days of a meeting you take part in, and of the coming weeks if you use the availability page or look at My availability (four weeks, unless you set another number in your profile, at most twelve), and leave these times out of the availability you marked. We read them when you save availability, set up or open a meeting, open My availability, when somebody opens your availability page, or when the best time of a meeting you take part in is computed again because somebody else marked times or scheduled (at most every ten minutes per meeting). Events that last whole days, that are marked as free or that you declined are ignored. The times and titles are stored on our server with your availability for that meeting and are removed with it. The titles are only shown to you. Other participants, and visitors of your availability page, see only when you are available or busy. With Google Calendar we also read the list of your calendars, so that you can choose which of them count.
2. Once a meeting has a confirmed time, we add it to your calendar (Google Calendar and CalDAV) if you are the one who invites to it: its host, or the one a time was booked with. It goes into the calendar you chose under "Organize from" in your profile (or for that meeting). The entry names the other participants as guests, each at the address they gave for it (in their profile under "Invite me at", or when booking), so that your calendar server invites them in your name; the others get the meeting as that invitation, and everybody invited sees the names and addresses of the others in it. If you tick "Also invite my "Invite me at" address" in your profile, the entry in your own calendar names your own address for the meeting as a guest as well, so the guests of meetings you host see it too; this is decided when the entry is first written, and stays so for that meeting. We add it to nobody else's invitation. Who is anonymous in a meeting is named as a guest only if they gave an address for that very meeting (e.g. when booking a time), as "Anonymous", and for an anonymous meeting nobody is (an invitation names its guests to each other): without an address, take the time into your calendar yourself, with the download or the feed of your meetings. Having a meeting of somebody else written into your own calendar by us is an experimental feature, off unless you switch it on in your profile ("Also enter the meetings of others into my calendar"): then such a meeting is entered into your calendar where the host's calendar does not invite you, or where you choose so for a meeting. Without it, a meeting of somebody else reaches you only by the host's invitation, the feed of your meetings, or this site. Instead of a calendar we write to, a host can invite with their own calendar on the web (Google Calendar, Outlook) or by e-mail from their own mail program: the meeting and the addresses of the others the host was given are then handed to the browser of the host, which opens that program with them; this does not go through our server. We change or remove the entry we made when the meeting changes. We do not change or remove any other events by ourselves. If you remove an entry of your calendar yourself with the x on it in the grid, we take it out of that calendar and keep it in encrypted form for a day, so that you can put it back.
If you switch on the free/busy feed in your profile, whoever has its address gets the times you are busy from all your calendars and meetings together, as "busy" without titles; your calendars are then also read when that address is fetched. If you join the availability page of a group (with its invite link, after being told this), the page shows when you are free in the coming weeks, computed from your usual week (the one of My availability, or one you mark on the page for that group only, which is kept with the page and removed when you leave it), your calendars and your meetings scheduled here: the times only, never what you have then. Who sees that is set for the page and said before you join: all its members with your name, or only its host while the others see how many members are free at a time, or nobody but such numbers. Members (on an anonymous page only its host) can schedule a meeting with you at once, which is then among your scheduled meetings. The e-mail address of your profile, if you gave one and are not anonymous, is kept with the page when you join. It is used only if you chose, with a tick when joining, to be invited to these meetings by e-mail: then whoever schedules a meeting with you gets it (the host of the page; another member only if the host lets the members invite each other), and everybody invited to the same meeting sees it, as a calendar invitation shows its guests to each other. Without the tick nobody gets it and nobody invites you: you find these meetings among your scheduled ones and add them to your calendar yourself. Nobody who is not a member gets any of it, the page is not listed anywhere, and you can leave it at any time; the others do not see your times anymore then. If you give an address to be told about bookings on your booking page, it is kept with the page (and removed when you unpublish it), used to mail you, and given to somebody who booked only as part of an invitation once their time is set. If you send invitations yourself (by e-mail, or with a calendar of yours on the web), nothing invites who books a time with you: they are then given your address (the one you gave for the meeting they book on, else your "Invite me at" address), so that they can tell you they booked. Where this server sends mail itself (about bookings), an address that somebody typed in gets the bare fact only, with a link to confirm that the address is theirs and one to never get mail from here again; names, messages and calendar entries are mailed to confirmed addresses only. Of an address we keep for that only a hash and what its holder chose. You can also keep signing in on your side: of a calendar file you downloaded we keep, as it was when you handed it over, only when its entries are (also those that repeat) and their titles, not who is invited, where they are or their descriptions, and no entry that is over; and with Google signed in in your browser we receive only when you are busy, not the events and nothing that gives access to your account. For the calendars the server reads itself, we store in encrypted form what gives access to the calendar: the access key issued by Google together with your Google address, the iCal address, or the CalDAV address, user name and password (please use an app password). They are not passed on to anybody. You can remove a calendar at any time under "Calendars"; a Google access key is then revoked at Google, and all are deleted here.

Notices and cancelled bookings. When somebody a meeting of yours was made for leaves it (who booked a time with you cancels), the site tells you with a notice that names them, the meeting and what became of it. It is kept until you dismiss it, at most 60 days. If you chose to keep a cancelled booking, marked as declined, the name and address the visitor gave for it are kept with it until it expires: one day after the booked meeting ends (for a booking that repeats weekly, after its last week). The other way round, if you cancel a booking whose host keeps it, your name and address stay with the host that way; "Download my data" shows them.

How long. Your identity and everything kept for it expire two years after you last used the site. A scheduled meeting expires one day after its last day (of a booking: one day after the booked time; of a meeting set up over some days: one day after the last of them; of one that repeats weekly: after its last week), with everything kept for it, also a booking kept as declined. A notice to a host is kept at most 60 days. What we note of an entry we wrote into a calendar (in which calendar, whom it invited, so that we can change it) is kept until 60 days after the last time of the meeting. A meeting its host deleted can be brought back for 4 hours (not once somebody who was in it deleted everything about them), an entry you removed from a calendar through us for a day (see above); then they are gone. The entries we read from your calendars are kept for minutes to a day. The server's own log (one line per request, with the first characters of random ids and no names) is kept for thirty days. A log of things that went wrong on the server, without names or ids, is kept in its memory until it is restarted.

Your rights. You can see all that the server keeps of you ("Download my data" in your profile: right of access and to data portability, Art. 15 and 20), change it (your name, address and calendars in the profile, your times in each meeting: Art. 16), and have all of it removed at once ("Delete everything about me" in your profile: Art. 17). Then nothing on our server names you anymore: the meetings you host are removed for their participants too, what you marked in other meetings is taken out, your page and its bookings are gone, your calendars are disconnected and a Google key revoked. Where a meeting of somebody else stays (a booking its host keeps as declined, a title made from your name, a notice to its host), you are named "<deleted account>" there, without an address, and nobody is told. What calendars outside N meet K received stays there (see "Calendars outside N meet K"). You can also remove single things: leave a meeting, remove a calendar, unpublish your page. For anything else (restriction of processing, Art. 18; objection, Art. 21; questions) write to the address above. You have the right to complain to a data protection supervisory authority, for example the one of the German state you live in, or the one of the state the site is run from.

Security. Everything between your browser and the server goes over https. The server encrypts what it stores with a key that is kept apart from the database, and limits what one address may ask of it. Your identity is a random secret in your browser: keep it to yourself (see the terms).

Changes. This notice is updated when the site changes; the date of the terms says when.