This is a courtesy translation. The German version is authoritative.
Privacy policy
1. Controller
Christian Reißig, Pleißenbachstr. 87, 09212 Limbach-Oberfrohna, Germany, is responsible for processing your data. Send privacy questions and requests about your rights to info@gamerdesk.app.
2. What data we process and why
Account: the email address of your login account and, if you sign in with email and password, your password. If you sign in with Google or Apple, we receive your email address and your name from there.
Profile: username, profile picture, platforms, favourite games, short description, whether you can host LANs, your location (city, region, country and the associated coordinates), how far you travel for a LAN, how many players you can host, your gaming account names, and your language and theme setting.
LAN content: name, description, cover image, date, location, the city of the LAN with its coordinates, seat plan, schedule, shopping list, tasks, game suggestions and votes, and internal notes about the LAN.
Collaboration: invitations, roles, seat assignments, notifications and chat messages within a LAN.
Technical data: record timestamps and server logs that arise while operating the application.
We process this data to run your account, to plan LAN parties together and to operate the platform securely.
Place search: When you search for a place in your profile or while creating a LAN, our server sends the search text you typed to Geoapify. No IP address and no account data of yours is transmitted; only the chosen place with its coordinates is stored. Game search: When searching for games, our server sends the search term to IGDB (Twitch). Here too, no IP address and no account data of yours is transmitted.
3. Sign-in and emails
You can sign in with email address and password, with Google or with Apple.
When an account is created, the platform sends a confirmation code by email; resetting the password also runs through an email. These emails are sent by the sign-in service of the Base44 platform.
Invitations and notifications about a LAN appear in the app and are not sent by email.
4. Legal bases
Processing for your account, your profile and the joint planning of your LANs is based on Article 6(1)(b) GDPR (performance of the user agreement).
Security measures and server logs are based on Article 6(1)(f) GDPR; our legitimate interest is a secure and stable operation.
Where you have given consent, Article 6(1)(a) GDPR applies. You can withdraw consent at any time with future effect.
5. Hosting and processors
GAMERDESK runs on the Base44 platform (Wix) and uses its database, file storage and sign-in service. Base44 processes the data as a processor.
According to Base44's publicly documented information, its servers are currently located in the United States and app data is stored there. Data processing agreements cover transfers to the United States; depending on the case, standard contractual clauses, adequacy decisions or the Data Privacy Framework apply. Base44 provides a directory of subprocessors in its Security Trust Center.
The domain gamerdesk.app is managed through the platform's domain service.
Profile pictures and cover images are stored in the platform's media storage and served via publicly reachable addresses.
6. Who can see which data
Your profile is publicly visible, also without signing in: username, profile picture, platforms, favourite games, short description, your location (city, region, country), your LAN profile and your public LANs. The coordinates of your location are not shown to anyone. Only signed-in players can see your gaming accounts. On your profile, only you can see your private LANs.
The email address of your account is never shown publicly.
Public LANs are visible to everyone, also without signing in. Private LANs appear in the overview with name, cover image, date, LAN style, participant count, host and the game with the most votes. Description and location are available to members only, meaning owner, organizers and participants; anyone who is invited but has not joined yet sees the description and the address of the LAN in the invitation as well, but not the city, the participant list, the chat or the internal notes.
Only members of a LAN can see its chat and internal notes. Owners and organizers additionally manage roles, tasks and seats.
7. Storage period and deletion
You can delete your player profile in the profile settings. This removes your username, profile picture and all profile details. Your chat messages stay in the LAN and afterwards appear without a name as “Deleted player”.
Your login account with the email address is not deleted automatically by this. Please request deletion of your account by email to info@gamerdesk.app.
When a LAN is deleted, GAMERDESK removes the associated content: participations, invitations, seat plan, shopping list, schedule, tasks, games, votes, reactions, internal notes and chat messages.
We store data for as long as it is needed for the purposes described or as long as legal obligations require.
8. Cookies and local storage
GAMERDESK sets no cookies for advertising or analytics and uses no analytics or tracking services. The analytics feature of the SDK is switched off in the app.
For sign-in, the platform keeps an access token in your browser's local storage.
In addition we store in your browser your language, your theme setting (light or dark) and, per LAN, the time of the last chat message you read, so that unread messages can be counted.
You can delete these entries at any time through your browser's settings.
9. Your rights
You have the right to access, rectification, erasure, restriction of processing, data portability and objection. You can withdraw a given consent at any time with future effect. Contact info@gamerdesk.app for this.
You may also complain to the competent supervisory authority: Sächsische Datenschutz- und Transparenzbeauftragte (Saxon Data Protection and Transparency Commissioner).
10. Changes to this policy
This privacy policy may be adjusted when the application or the legal requirements change. The version published here applies in each case.