Privacy notice

Spiele & Einsatzplan

This app gives trade-fair teams cheat sheets for their games and a shift plan for the booth. Each team (an “instance”) is connected to a Discord server. This page explains which personal data is processed, why, and for how long.

1. Controller

Jens Rey
Sankt-Hubertus-Ring 43
40589 Düsseldorf

Privacy requests: j+datenschutz@rey.nrw

Each team maintains its instance’s content (games and shift plan) itself. For questions about the shift plan, such as the spelling of your name, your team is the quickest contact.

2. Logging in with Discord

The app has no accounts of its own. You log in through Discord, and on Discord’s page you allow us to receive:

We use this to check whether you may use the app and whether you may edit content. While you are logged in, we check your roles with Discord again about every 15 minutes. The legal basis is Art. 6(1)(b) GDPR (providing the app you want to use) and Art. 6(1)(f) GDPR (protecting the content from unauthorised access).

Retention: your login (session) is kept on the server and ends after at most 14 days or when you log out. In addition, every instance you open stores your user id, your username, display name and nickname on its server (kept current at login, by the bot's commands and by a daily check with Discord), and the time of your last login, so that the team’s admins can match you to your name in the shift plan. This entry is deleted automatically 12 months after your last login.

3. Shift plan

The shift plan is copied regularly from the team’s planning spreadsheet (a Google Sheet). It contains the names of the people on the plan, with days, shifts and positions, and the notes the team writes in parentheses after a name (for example who covers during breaks, which can be another person’s name). Unless the team has switched it off, a name is stored only as first names and the initials of the last name (“Max M.”, a few more letters where two people would otherwise look the same), also in the notes; otherwise as written in the sheet. Every copy replaces the previous one completely, so it holds exactly what the sheet holds now, and nothing is kept longer than there.

The plan is visible to everyone who may access the instance, and to the members of the Discord server in whose channels the /pep command is used. Its purpose is organising the booth; the legal basis is Art. 6(1)(f) GDPR (the team’s legitimate interest in staffing its booth and telling everyone the schedule).

You can link your Discord account to your name in the plan, so the app shows you your own shifts; the team’s admins can set this link too. Once you are linked and have logged in, your Discord name (your nickname on the server, else your display name, else your username) is shown after your name wherever the plan shows it, as a link to your Discord profile, to everyone who sees the plan (in the bot’s answers as a mention of your account, which notifies nobody). The link is deleted together with your entry from section 2; if you never logged in, 12 months after it was created.

Shift swaps: if the team turns them on, you can offer a colleague to swap one of your shifts for one of theirs. The instance then stores the two shifts, both names and user IDs, your optional note, each step (proposed, accepted, approved, rejected or reverted, by whom and when) and, if given, the admin’s reason. While a swap isn’t in effect, only the two of you and the team’s admins see it; once it is in effect, it shows in the plan for everyone, marked as a swap, until the planning spreadsheet shows it too. Purpose and legal basis are the same as for the plan. A swap is deleted 12 months after it ended.

Calendar subscription: if the team turns it on, you can make a personal link that shows your own shifts in your calendar app (with days, times, positions, the game at the position, the place and the sheet’s note for the shift, which can name another person, for example who covers during breaks; no other names). You decide whether to make one, and which calendar service you give it to: that service (for example Google, Apple or Microsoft) then fetches your shifts regularly and stores them under its own privacy policy. The instance stores only a fingerprint of the link (not the link itself), the language, when it was made and when it was last fetched. The link works for anyone who has it, so keep it to yourself; you can replace or remove it at any time under the shift plan. While it is in use we check with Discord about every 15 minutes that you still belong to the team; if you don’t, the link is deleted. It is also deleted together with your entry from section 2. Legal basis: Art. 6(1)(b) GDPR (the function you asked for).

Shift reminders: if the team turns them on, the Discord bot posts once an hour in a channel the team chooses which shifts start in the next hour: positions, names and, where your account is linked to your name, a mention of it (which notifies nobody). Everyone who can read that channel sees it, as with /pep; purpose and legal basis are the same as for the plan. Separately, you can ask under the shift plan for a direct message before each of your shifts (you choose how long before). For that the instance stores that you asked for it, your language, how long before, the ID of the direct-message channel Discord opens for it and, if Discord refuses a message (for example because you don’t accept direct messages from server members), when and why. Before each message we check with Discord that you still belong to the team; if you don’t, your request is deleted. You can stop the messages at any time under the shift plan; the request is also deleted together with your entry from section 2. Legal basis: Art. 6(1)(b) GDPR (the function you asked for). For both, the instance notes which reminder it sent (the shift and, for a direct message, your user ID), so that none is sent twice, and deletes the note 14 days after the shift. Discord delivers and stores the messages (section 7).

Notes on the games: if the team turns them on (for every member, or only for its admins), you can write short notes on a game’s card on the games page. The instance stores the note, your user ID, your name and when it was written and last changed. Everyone who may access the instance sees the note with your name. You can change or delete your note at any time; the team’s admins can delete it too. Purpose and legal basis are the same as for the plan. A note is deleted 12 months after it was last changed, and together with your entry from section 2.

Where team members live: the team can give the operator a list of its members with their names and postal codes, for a map of the team. The location is the centre of the postal code’s area, looked up at OpenStreetMap (section 7), never an address. The instance stores the name, the postal code and that location rounded to about 1 km. Each new list replaces the previous one completely, and it is deleted together with the instance. Everyone who may access the instance sees it on the “Supporter Map” page: each name with its postal code at that location. Legal basis: Art. 6(1)(f) GDPR (the team’s legitimate interest in organising itself, for example travel to the fair).

4. Discord bot

When you use the /pep, /my-pep or /game commands on the Discord server, Discord sends us, among other things, your user id, your roles on the server, the channel and the command. We use this only to check whether you may use the command and to answer it; none of it is stored. Answers to /pep are visible to everyone in the channel, answers to /my-pep and /game only to you. While you type a game’s name, Discord sends what you have typed so far, to suggest matching games; that isn’t stored either. If the note on one of your shifts names a person whose Discord account is linked to that name in the plan, or whose Discord name it is, /pep and /my-pep show a link to that account after the name (a mention, which notifies nobody), so you can message them. The bot also sends the shift reminders from section 3, if the team uses them.

5. Cookies and storage in your browser

There is no advertising, no analytics or tracking, and no third-party content: fonts, images and scripts all come from this server. The one exception is the map on the “Supporter Map” page: its map images come from OpenStreetMap, and only once you have clicked “Load map” (section 7).

6. Server and change logs

For every request the web server logs technically necessary details: IP address, time, the requested address, status code, amount of data, the referring page and the browser identifier. We need them to run the app and to detect faults and attacks (Art. 6(1)(f) GDPR). For a calendar subscription, the requested address contains your personal link. The logs are deleted after 14 days.

Change log: when admins change settings, roles, games, files or mappings, when you link your account to your name in the plan, when a shift swap is proposed, answered or decided, or when a calendar link is made, replaced or removed (never the link itself), when you turn reminder messages on or off or change how long before they come, when you write, change or delete a note on a game (never its text), when you mark a product as few left, sold out or available again, or when a list of where members live is imported (only how many), the instance records who (user ID and name) changed what and when. The team's admins can see it. The purpose is to trace changes and to fix mistakes (Art. 6(1)(f) GDPR). Entries are deleted automatically after 12 months.

7. Recipients

We don’t pass data on beyond that. Server backups are rotated regularly; deleted data disappears from them once the backup in question is overwritten.

8. Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20). Where we process data on the basis of Art. 6(1)(f) GDPR, you may object at any time on grounds relating to your particular situation (Art. 21). You may also lodge a complaint with a data protection supervisory authority (Art. 77), for example the one where you live or where the controller is based.

Entries in the shift plan are changed by the team in its planning spreadsheet; the app picks up the change at its next update.

Last updated: 2 Oct 2026

← Back to the start page