Privacy Policy
SZACHOWALIGA.PL · VERSION 1.8 · 22 OCTOBER 2026
This is an informational translation of the Privacy Policy. The Polish version is legally binding: Polityka prywatności (Polish).
This policy explains what personal data we process in connection with the SGH Business Chess League (Szachowa Liga Biznesu SGH) and the szachowaliga.pl website, including the Player Zone: where we obtain it, why and on what legal basis, to whom we disclose it, how long we keep it and what rights you have.
1. Data controller
The controller of personal data is the Polish Chess Foundation (Fundacja Polskie Szachy), with its registered office in Warsaw, ul. Świeradowska 47, 02-662 Warszawa, KRS 0001063106, NIP 5273079799 (‘Controller’, ‘we’). We have not appointed a data protection officer. In all matters concerning personal data, write to liga@szachowaliga.pl or by post to our registered office address.
2. What data we have and where we obtain it
We process data that:
- you provide yourself — in the registration forms (first name, surname, email address, optionally a telephone number, invoicing details; when registering a team, also the company name and tax identification number (NIP) and the team name; information that you have played in the League before, with the name of your former team), when buying a ticket for an open event on the Stripe payment page (first name and surname, email address, billing address, optionally the company name and NIP, the participant’s first name and surname and, for a parent-and-child ticket, optionally the child’s first name; point 3.25), in the Player Zone (profile: first name and surname, nickname, description, company, Polish chess category and title, FIDE and Polish Chess Federation ID (CR PZSzach) numbers, links to your profiles on LinkedIn, lichess and chess.com and to a website, Player Card; consent and notification settings; messages to other players and contacts; your lichess.org username when you join SLB SGH Online; your Discord username, if you enter it in your profile), in the post-event survey (rating, comments, name of a recommended company), on our Discord server (Discord username and account ID, nickname, avatar, messages and other posts, questions to the Magnus bot), in the League’s WhatsApp groups (telephone number, profile name, messages), in an access request for the Player Zone and in correspondence with us;
- are provided to us by a team captain or by the person registering a team — a player’s first name, surname, email address and optionally telephone number, as well as those of a person added to the team’s SLB SGH Online player list (point 8);
- arise during competitions and events — line-ups, pairings, game results, standings and rankings, SLB SGH Online classifications, as well as photographs and videos;
- come from the League’s archive for 2023–2026, from the public FIDE rating list and from lichess.org: results of tournaments we organise there and requests to join our club (point 8);
- are collected automatically when you use the website — IP address, browser information, sign-in session data, and on the public pages of the website also data about visits from which statistics are produced (point 3.26).
3. Purposes and legal bases of processing
- Registration and participation in the League — accepting your registration, payment, line-ups, organisation of Match Days, organisational announcements by email, by SMS and in the Player Zone (e.g. a Match Day reminder, a change of room; point 3.21): Article 6(1)(b) GDPR (contract) in respect of a person who registers in their own name; Article 6(1)(f) GDPR (our legitimate interest — organising the competition) in respect of team players and persons acting on behalf of a company, e.g. a captain.
- Settlements and invoices, including the submission of structured invoices to KSeF: Article 6(1)(c) GDPR (tax and accounting obligations).
- Publication of results — publicly, without signing in: first name and surname as given in the registration, team (usually with the company name), FIDE title entered in the profile, starting rating, pairings, game results, standings, player records and all-time rankings: Article 6(1)(f) GDPR — openness of results is the essence of sporting competition. You may object (point 7). A child is registered for a family tournament by their parent or guardian; we publish a child’s results in the same way as adults’ results, with first name and surname, which the parent or guardian acknowledges when registering.
- Archive of results for 2023–2026 and all-time rankings: Article 6(1)(f) GDPR (a reliable history of the competition). You may object (point 7). If we uphold your objection, we will replace your first name and surname in the public results with an anonymous designation; the game results themselves will remain, because they are also the results of your opponents.
- Player Zone account — signing in with a one-time link, profile, Captain’s Panel, 1:1 messages, contacts, results history: Article 6(1)(b) GDPR (contract for the provision of services by electronic means, Regulations, § 11). 1:1 messages can be seen only by their participants; we look at their content only after abuse has been reported. Your email address and telephone number are not visible to other players or to arbiters — they are visible to the Organiser’s team and to your team captain (for contact on team matters).
- Player directory — visibility of your profile to other signed-in participants: Article 6(1)(a) GDPR (consent). Consent is switched off by default, and you can withdraw it with one click in the Player Zone (Settings). The directory is not available without signing in or in search engines.
- Linking your account to your results history from previous seasons — at your request when registering or on the basis of team registration sheets: Article 6(1)(f) GDPR. The decision is taken by a human after checking evidence other than the first name and surname alone (e.g. the same team, CR or FIDE number, email address).
- Player Card (a generator using artificial intelligence) — only at your request: Article 6(1)(b) GDPR (Player Zone service). We send the uploaded photograph to OpenRouter, Inc. (USA), which passes it on to the provider of the image-generating model (currently Google). We do not store the source photograph. We automatically save each generated card in your history in the Player Zone; the file is available at an address known to people who have a link to it or who view your profile. We will delete an individual card at your request. The card is an image generated by artificial intelligence. Upload only your own photograph.
- Handling correspondence (emails to League and Foundation addresses): Article 6(1)(f) GDPR (replying to messages). We store messages in our database, and the team receives a notification in the Slack messaging service with the sender, subject and an excerpt of the content. To prepare a draft reply we may use an Anthropic language model: we send the sender’s address (with information on whether it is in our database), the subject and the content of the message directly to Anthropic (point 4) and, when that route does not work, via OpenRouter, Inc. (USA). The draft is always read and sent by a human. Messages sent automatically, and messages whose subject or content indicates a code, sign-in or password, are not passed to the model — for these, Slack receives the header only. If you do not want your message to reach Slack and the language model, write to us by post.
- Access request for the Player Zone: Article 6(1)(f) GDPR (checking whether you take part in the League and replying to your request). The request goes to the organiser’s panel, and the team receives a notification in Slack.
- SMS messages — organisational messages to season participants: on the bases set out in point 1; marketing messages (recruitment, offers) only with consent: Article 6(1)(a) GDPR and Article 398 of the Electronic Communications Law (Prawo komunikacji elektronicznej).
- Newsletter (email): Article 6(1)(a) GDPR and Article 398 of the Electronic Communications Law (consent). You can withdraw your consent to the newsletter and to marketing SMS messages in the Player Zone (Settings) or by writing to liga@szachowaliga.pl.
- Image — photo and video coverage of League events in the website gallery and on the Organiser’s social media: Article 6(1)(f) GDPR (documenting and promoting the League). We disseminate the image of a person who is merely a detail of a larger whole, e.g. of the room during a round, on the basis of Article 81(2)(2) of the Act on Copyright and Related Rights; photographs in which a given person is the main subject are published with that person’s consent (Article 81(1) of that Act), given in the registration form or in the Player Zone (Settings). Consent may be withdrawn at any time. Anyone who does not wish to be photographed may tell the photographer or us — we do not publish such shots, and we remove published ones on request. We publish the image of a child (a person under 18) — in the gallery and on the League website and on the Organiser’s social media — only with the consent of their parent or legal guardian, including where the photograph comes from a family event or the child is merely a detail of a larger whole. The parent or guardian gives consent in a statement (in writing or by email) when registering the child for the event or at the event itself, and may withdraw it at any time by writing to liga@szachowaliga.pl — we will then remove the child’s photographs from publication. Without such consent, photographs in which a child can be seen remain only in the League’s non-public archive.
- Website security and abuse prevention — attempt limits, form protection (Cloudflare Turnstile), a log of messages sent, sign-in sessions: Article 6(1)(f) GDPR.
- Database backups: Article 6(1)(f) and Article 32 GDPR.
- Arbiters’ search tool based on the FIDE list (point 8): Article 6(1)(f) GDPR — efficient entry of players into tournaments; data from the list is not published.
- SLB SGH Online: a club on lichess.org (League tournaments played online, Annex 2 to the Regulations). We save your lichess.org username with your Player Zone account, give you a verification code and check your request to join the club. We check in the League database whether you are entitled to club membership and admit you to the club. We calculate points, classifications and the Online Team Cup, assigning your results to your team. We send messages on lichess.org: on the day of a club tournament, one message to all club members, and when you lose your entitlement to the club, a message to you with advance notice and an invitation to the Warsaw Chess club. 30 days after that message we remove you from the SLB SGH Online club. Legal basis: Article 6(1)(b) GDPR (a service you request in the Player Zone, Regulations, § 11 and Annex 2). You provide the username yourself. We do not know your lichess.org password and we do not ask for it. A captain may add the company’s employees and associates to the team’s SLB SGH Online player list (Annex 2, point 5): the captain provides their first name, surname and email address. We process this data to send these persons an invitation, give them access to the Player Zone and the club and count their results towards the Online Team Cup, on the basis of Article 6(1)(f) GDPR (organising the competition, point 8.1).
- Publication of SLB SGH Online results — publicly, without signing in: tournament results, classifications and the Online Team Cup with the lichess.org username. Until the date on which Annex 2 to the Regulations enters into force (19 October 2026) we show usernames only. From that date we show the first name, surname and team name next to the username, as in the League results (point 3.3), including for results obtained earlier: Article 6(1)(f) GDPR (openness of the results of sporting competition). We do not show the lichess.org rating (it is public on lichess.org). You may object (point 7).
- Open tournaments in the Warsaw Chess club: downloading results from lichess.org (username, place, score, rating from the tournament), determining the winners, issuing codes for the Individual League and sending them by private message on lichess.org, showing the podium on the League website (username and, for League players with a confirmed username, as set out in point 3.18): Article 6(1)(f) GDPR (organising the tournament and awarding the announced prizes). This also applies to persons who do not play in the League (point 8.4).
- Fair play in SLB SGH Online — checking whether lichess.org has flagged or closed an account for violating its rules, analysing reported games, exclusion from classifications or being passed over for a prize: Article 6(1)(f) GDPR (fair competition).
- League announcements in the Player Zone — organisational messages that we show to signed-in participants in the Player Zone (the ‘From the League’ tab), e.g. a line-up reminder, information about a tournament or, for a captain, about the team’s payment. We store the content of the announcement, to whom we showed it and whether you have read it, so that new announcements are marked and read ones do not come back as new. You cannot see the other recipients of an announcement. Legal bases as in point 3.1.
- Post-event survey — after a Match Day or another League event, we send its participants (persons who played a game there or were recorded as present) an email with a link to a short survey: a rating from 0 to 10, comments and the name of a company worth inviting to the League. We use the survey to improve events and develop the League: Article 6(1)(f) GDPR (our legitimate interest). Responses are read only by members of the Organiser’s team, and we view ratings and comments in summaries without surnames. If, next to the recommended company, you tick ‘I can introduce them’, the team will see your first name, surname and email address in order to contact you, and in the Slack messaging service it will receive a card with your first name and surname, the company name and the event. In the company field you enter only the company name: we do not collect data about the people who work there. If you do not want to receive surveys from us, reply to the survey email or write to liga@szachowaliga.pl (objection, point 7). We do not send surveys to children registered for an event by a parent or guardian.
- The ‘Szachowa Liga Biznesu SGH’ Discord server — the League community’s meeting place: conversations about tournaments and chess, looking for a team or a player, online tournaments. You join voluntarily, through an invitation link, with an account set up on Discord on Discord’s terms (point 4). As the server owner, we can see your username, nickname, avatar and what you write in the server’s channels. We cannot see private messages between users. We assign roles (e.g. ‘Kapitan’ opens the captains’ channel) and moderate the server: we may remove a post that breaks the server rules, or remove or ban an account from the server. Our bot Magnus publishes announcements, previews and tournament results, i.e. the same data that we show on the League website (points 3.3 and 3.18). The bot does not read conversations in the channels; it responds only to commands addressed to it. If you ask it a question about the League with the /magnus command, we send the content of the question directly to Anthropic (point 4). The answer is prepared by a language model. We do not store the original content of your question or the bot’s answer in the League database; we store only the general form of a question about chess knowledge and the search statistics, described below. For questions about general chess knowledge (rules, history, champions), the answer is based on excerpts from our public knowledge base. To select these excerpts we may use the Jev model of TypeSafe AI, Inc. (USA). We do not send it your original question: the language model that prepares the answer (Anthropic) first rewrites it as a single sentence about chess knowledge only, without the first names and surnames of private individuals, mentions, channel names and contact details, and we additionally remove mentions, channel names, links, email addresses and telephone numbers from that sentence. The names of well-known chess players and other public figures you ask about may remain in that sentence. Jev receives this sentence and excerpts from the public knowledge base so that it can indicate which of them best fit the answer. We do not send it your username, nickname, ID or channel name (points 4 and 5). TypeSafe AI processes this data on our behalf, under a data processing agreement. Under the agreement, it does not use the data to train models. It stores the data on servers in the USA for as long as necessary to provide the service and as required by law; the agreement does not specify a fixed period. The content of this sentence depends on what you type in your question, so do not include personal data in your question. In the League database we store only this cleaned sentence about chess knowledge (not your original question, although for a simple question it may read the same), the keywords the bot used to search the knowledge base, and the search statistics: whether it found anything, how many excerpts, from which files of our knowledge base and whether excerpt selection worked. When the bot answers without chess knowledge (e.g. a question about the tournament calendar), we store only the fact that such a question was asked and the names of the tools used, without any text. We do not store your username or nickname, ID, server, channel, thread or the content of the bot’s answer, and we round the time of the entry to the full hour to make it harder to match the entry to the question on Discord. We do not link entries to the server history or to any other data about you. If you nevertheless type personal data in your question (your own or another person’s) and the model does not leave it out, it may remain in the stored sentence or in the keywords; the names of well-known chess players and public figures remain in them deliberately. Purpose of storage: developing and improving the chess knowledge base (we check what users ask about and what is missing from the base). Legal basis: Article 6(1)(f) GDPR (our legitimate interest — improving the quality of the bot and the knowledge base). You may object to this storage (point 7): we will then skip your subsequent questions, and the bot will continue to answer you as before. We keep entries for 12 months and then delete them automatically (point 6). From the entries we produce summaries (most frequent topics, questions without a match, numbers), which the organiser analyses, including with the help of artificial intelligence tools; only summaries in which sentences asked just once are omitted are passed to such analysis, and we delete the summaries themselves after 30 days. Because the entries contain no data about the person asking, we usually do not know who made a given entry; we give effect to rights in respect of entries when an entry can be identified on the basis of information from you (Article 11 GDPR; point 7). Legal basis for the other activities on the server: Article 6(1)(f) GDPR (our legitimate interest — running the League community and keeping order on the server). You may object (point 7) or leave the server at any time. In ‘My profile’ in the Player Zone you may voluntarily enter your Discord username. It is visible only to you and to the Organiser’s team: we do not show it to other players, including the captain, or in the player directory. Using this name, we assign you a role on the server (e.g. ‘Zawodnik SLB’ or ‘Kapitan’) and may contact you on organisational matters. Legal basis: Article 6(1)(b) GDPR (a Player Zone service that you request by entering the name; Regulations, § 11). You can remove the name at any time by clearing the field.
- The ‘Kapitanowie’ and ‘Ogłoszenia’ WhatsApp groups — in the ‘Kapitanowie’ (Captains) group we carry on day-to-day communication with team captains; in ‘Ogłoszenia’ (Announcements) only the organisers post. Both groups operate alongside the Discord server until the end of 2026. You join voluntarily, through an invitation link, with an account set up in the WhatsApp messaging service on WhatsApp’s terms (point 4). The other group members, including the organisers, can see your telephone number, profile name and what you write in the group. We do not transfer the member list to the League database. Legal basis: Article 6(1)(f) GDPR (our legitimate interest — efficient communication with League participants). You may object (point 7) or leave the group at any time.
- Tickets for open events (currently Chess Halloween on 29 October 2026, also for people from outside the League) — selling the ticket, the list of participants for entry, organising the event and settlement. You buy the ticket on the Stripe payment page (point 4): you provide your first name and surname, email address and billing address, optionally the company name and NIP (an invoice to a company), the participant’s first name and surname and, for a parent-and-child ticket, optionally the child’s first name. We do not collect a telephone number. On the basis of this data we issue in Fakturownia an invoice to an individual or to a company, which we submit to KSeF (point 3.2) and send from Fakturownia to the buyer’s email address; a free ticket (100% invitation code) has no invoice. The team receives a notification in the Slack messaging service with the ticket type, the participant’s first name and surname, the name of the code used and a link to the invoice (with the buyer’s details from the invoice: name, address and NIP), and, when the invoice has to be issued manually, also with the buyer’s name and NIP; without the email address and without the child’s first name. Legal basis: Article 6(1)(b) GDPR (contract with the buyer); in respect of a participant named by the buyer, including a child — Article 6(1)(f) GDPR (organising the event for which the buyer registered them); invoice — Article 6(1)(c) GDPR.
- Website visit statistics — we count how many people visit the pages of the website, where they come from (e.g. from the newsletter, from social media or from a search engine) and how many of them submit a registration. This tells us which pages and campaigns work. We use the Plausible Analytics tool for this (point 4). It does not use cookies and does not store anything on your device (point 10). When you open a page, your browser connects to the Plausible server and passes on: the page address, the address of the website you came from, campaign tags included in the address (e.g. utm_source), information about your browser, operating system and type of device, the time spent on the page and how far you scrolled it. We send the page address without query parameters, except for campaign tags and the source of the visit. From the address of the page you came from, we send only the name of the website, and when you move between pages of our website we do not send it at all. When you click selected buttons (buying a ticket for an event, the invitation to the Discord server) or submit a registration, Plausible receives only the name of that event, without the address of the link and without the data you entered. It uses your IP address only momentarily: it determines your country, region and city from it and, together with the browser information, calculates a hash from it with the addition of a random value changed every 24 hours, so that visits from one day are counted as one person. Plausible does not store the IP address itself or the full browser information. It deletes the random value after a day, so after that new visits can no longer be linked to earlier ones. We see only aggregate statistics and do not know who visited a page. We do not measure pages with a personal link from a message (newsletter unsubscribe, post-event survey, link for a team captain), the Player Zone, the organiser’s panels or the results screen in the hall: on these pages the Plausible script is not loaded at all. If your browser sends a Global Privacy Control or ‘Do Not Track’ signal, the script is not loaded either and we do not measure your visits. Legal basis: Article 6(1)(f) GDPR (our legitimate interest — measuring the effectiveness of the website and campaigns). You can object (point 7) or block the script from plausible.io in your browser; the website then works in the same way.
- Establishment, exercise or defence of legal claims: Article 6(1)(f) GDPR.
4. To whom we disclose data
Data is processed on our behalf by the service providers we use:
- Supabase — database and files (servers in the European Union);
- Cloudflare — website hosting and content delivery network, storage of gallery photographs and videos, form protection (Turnstile);
- Plausible Insights OÜ (Estonia) — website visit statistics without cookies (point 3.26); it stores the data on servers in the European Union (in Germany) and does not transfer it outside the European Economic Area;
- Resend — sending and receiving email;
- Google — the team’s email (Google Workspace), website fonts (Google Fonts) and the model that generates the Player Card (point 3.8);
- Slack — internal team notifications about registrations, access requests, messages, SLB SGH Online tournaments, recommendations from surveys (‘I can introduce them’) and tickets bought for events (point 3.25);
- SMSAPI — sending SMS messages;
- Anthropic (we concluded the agreement with Anthropic Ireland, Limited, a company in the Anthropic, PBC group; Anthropic stores the data in the USA) — the language model that prepares draft replies to correspondence and the Magnus bot’s answers on Discord;
- TypeSafe AI, Inc. (USA) — the Jev model, which helps select excerpts from our public chess knowledge base for the Magnus bot’s answers; it receives only the rewritten question about chess knowledge (without the first names and surnames of private individuals and without contact details) and excerpts from that base, without the username, IDs or channel name (point 3.23);
- OpenRouter and the AI model providers to which it forwards requests (currently Google and Anthropic) — the Player Card generator and a back-up route to the language model when the direct connection to Anthropic does not work;
- GitHub — website automation and encrypted database backups;
- Fakturownia — issuing pro forma invoices and invoices, including for event tickets (point 3.25);
- an accounting firm — bookkeeping.
Online payments are handled by Stripe (Stripe Payments Europe, Ltd.), which processes some of the data as a separate controller, under its own privacy policy. For event tickets (point 3.25) we can see the data from the purchase form in the Stripe dashboard. We submit structured invoices to the National e-Invoicing System (KSeF) run by the Ministry of Finance — this is a legal obligation. Participants’ data can also be seen by authorised members of the Organiser’s team, arbiters (without players’ contact details) and your team captain (point 3.5). Results, starting lists and player records are public (point 3.3), and we publish photographs in the website gallery and on our social media (Facebook, Instagram, LinkedIn), whose operators process them under their own rules.
SLB SGH Online tournaments take place on lichess.org. It is run by Lichess.org, an association under French law (association loi 1901) with its registered office at 350 Chemin du Pré Neuf, 38350 La Mure, France. Lichess.org processes its users’ data as a separate controller, under its own privacy policy (lichess.org/privacy). You set up your lichess.org account yourself. From us, lichess.org receives only what results from running the clubs and tournaments: the decision to admit you to the SLB SGH Online club or remove you from it, and the messages we send on lichess.org (about tournaments, a prize code, advance notice of the end of your club entitlement). We do not pass your first name, surname, email address or telephone number to lichess.org. Lichess.org has its registered office in France, so this disclosure takes place within the European Economic Area.
The League community server runs on Discord (point 3.23). For users from the European Economic Area, the data controller for this service is Discord Netherlands BV, with its registered office in the Netherlands, and Discord stores the data on servers in the USA (point 5). Discord processes its users’ data, including the account, messages and photographs, as a separate controller, under its own privacy policy (discord.com/privacy). You set up your Discord account yourself. From us, Discord receives what we and the Magnus bot publish on the server (announcements, previews, tournament results), the roles we assign and moderation decisions. We do not pass your email address or telephone number to Discord.
The ‘Kapitanowie’ and ‘Ogłoszenia’ groups run in the WhatsApp messaging service (point 3.24). For users from the European Economic Area, the data controller for this service is WhatsApp Ireland Limited, with its registered office in Ireland (Meta group). WhatsApp processes its users’ data, including the telephone number, profile and messages, as a separate controller, under its own privacy policy (whatsapp.com/legal/privacy-policy-eea). You set up your WhatsApp account yourself. From us, WhatsApp receives what we write in the groups and our decisions as group administrators, e.g. removing a member. We do not pass your email address or any other data from the League database to WhatsApp.
5. Transfers of data outside the European Economic Area
Some providers have their registered office in the United States (including OpenRouter, Anthropic, TypeSafe AI, Google, Slack, Resend, Cloudflare, GitHub) and may process data outside the EEA. This applies in particular to the photograph sent to the Player Card generator, the content of messages for which we prepare a draft reply, and questions asked of the Magnus bot on Discord. We base the transfer on the European Commission decision finding an adequate level of data protection under the EU–US Data Privacy Framework — in respect of providers that participate in it — or on standard contractual clauses approved by the European Commission (Article 46(2)(c) GDPR). For Anthropic and TypeSafe AI, these are the standard contractual clauses in the data processing agreements. We will provide information about the safeguards and a copy of them on request sent to liga@szachowaliga.pl. Discord (point 4) stores its users’ data on servers in the USA. Discord bases the transfer of that data from the EEA on the same European Commission decision (it participates in the EU–US Data Privacy Framework) and on standard contractual clauses. WhatsApp Ireland Limited (point 4) transfers data to the USA, to WhatsApp LLC and Meta Platforms, Inc., on the basis of the EU–US Data Privacy Framework and standard contractual clauses.
6. How long we keep data
- Invoices and settlement data — 5 years from the end of the calendar year in which the tax payment deadline expired.
- Registration and League participation data — for the duration of the Season, and then until the limitation period for claims expires.
- Sporting results and the archive (starting lists, pairings, results, standings, rankings) — without time limit, as an archive of the competition, subject to objection (point 3.4).
- Player Zone account (profile, contacts, 1:1 messages, generated Player Cards) — until the account is deleted, which we do at your request. We do not store the photograph sent to the Card generator.
- Data processed on the basis of consent — until consent is withdrawn. We keep the register of consents (who consented to what and when, or withdrew consent) without deleting entries, because we must be able to demonstrate that consent was given (Article 7(1) GDPR).
- Photographs and videos from events — in the League archive, without time limit; we will remove a shot showing your image from publication on request.
- Email correspondence (together with the draft reply) and access requests for the Player Zone — currently without an automatic deletion period; we delete them on request, unless they are needed for the establishment, exercise or defence of legal claims.
- Technical data: attempt-limit records with the IP address — 48 hours; sign-in sessions (with the IP address at the time of signing in) — 30 days after expiry or signing out; sign-in links (we store only their hashes) — 14 days after expiry; the log of messages sent (email address and IP address) — 12 months (this is our only record that we sent information about data processing, e.g. an invitation to the Player Zone). On request we delete this data earlier, together with the account. The IP address recorded with an access request — currently without an automatic deletion period; we delete it on request.
- Automatic database backups (encrypted) — 30 days.
- Data from the FIDE list — until the next monthly update; we delete the data of persons who drop off the list at the update.
- SLB SGH Online: the link between your Player Zone account and your lichess.org username, and the verification code — until the Player Zone account is deleted. After the username is unlinked (point 7), the record remains in the database marked as unlinked until we delete the account; on request we will delete it earlier. Tournament results and classifications, including the open tournament results of persons who do not play in the League — as sporting results (point 6.3): without time limit, as an archive of the competition, subject to objection. Prizes from open tournaments (winner’s username, place, code, information on sending) — until the code expires, and then until the limitation period for claims expires; a code used at registration is kept together with the registration data (point 6.2).
- League announcements in the Player Zone (content, list of recipients and read status) — 12 months from sending. An announcement disappears from your list in the Player Zone earlier, when its validity period ends or we withdraw it.
- Post-event surveys (invitation, your responses and company recommendation) — 24 months from sending the survey.
- Discord server: we can see your username, nickname, avatar and roles for as long as you are on the server. Messages, photographs and other posts remain on the server until you delete them yourself, or we delete them during moderation or at your request. Leaving the server does not in itself delete them. If we ban an account from the server, its ID remains on the server’s ban list until we lift the ban. We keep the Discord username entered in your Player Zone profile until you remove it or we delete the Player Zone account.
- WhatsApp groups: group members can see your telephone number and profile name for as long as you are in the group. After you leave the group, WhatsApp shows your number on the list of past participants for up to 60 days. Messages from the group remain on its members’ devices. We do not transfer the member list to the League database.
- Questions to the Magnus bot stored in general form (the cleaned sentence about chess knowledge, keywords and search statistics, time rounded to the hour, without the username and ID of the person asking) and counters of questions without chess knowledge — 12 months from the entry, then automatic deletion. Summaries prepared from these entries for reviewing the knowledge base — 30 days. The hash of the account ID of a person who has objected to storage — for as long as the objection applies (point 3.23).
- Tickets for open events (point 3.25): invoices — as in item 1. Purchase data (including the participant’s first name and surname and the child’s first name, if given) remains in the transaction data in our Stripe account for as long as Stripe’s rules and accounting legislation require — we do not delete it earlier. We delete the extract of the participant list prepared for entry within 30 days after the event, and ticket notifications in Slack within 12 months after the event.
- Visit statistics (point 3.26): neither Plausible nor we store the IP address. Plausible deletes the random value from which the hash is calculated after 24 hours. Plausible keeps the visit data without the IP address, from which the summaries are produced, for as long as we use the service; when we stop using it, we will delete the data together with the website’s account in Plausible.
7. Your rights
You have the right of access to your data and to a copy of it, the right to rectification, to erasure, to restriction of processing, to data portability (where we process the data on the basis of consent or a contract), the right to object to processing based on legitimate interest — including to the publication of results and the archive — and the right to withdraw consent at any time, without affecting the lawfulness of processing before its withdrawal.
You can change marketing consents, visibility in the directory and consent to the use of your image yourself in the Player Zone (Settings). Send other requests — including an objection — by email to liga@szachowaliga.pl, preferably from the address you use in the League, or by post to our registered office address. State what the request concerns (e.g. ‘objection to the publication of my surname in the results archive’). We reply within one month; we may ask you to confirm your identity. We handle messages sent to liga@ as described in point 3.9.
You can unlink your lichess.org username yourself in the Player Zone (the ‘Online tournaments’ tab, ‘Unlink username’ button); from that moment new results from that account are not assigned to you. You can leave the club on lichess.org yourself at any time or ask us to remove you from the club. The data of your lichess.org account (profile, games, rating) is managed by lichess.org as a separate controller: rights in respect of that data are exercised with lichess.org, and its privacy policy sets out the rules and contact details.
You can delete your own post or photograph on the Discord server yourself for as long as you have access to the channel. You can ask for a post or photograph to be removed, including a photograph of you added by someone else, at liga@szachowaliga.pl, also after you have left the server. You can leave the server at any time. The data of your Discord account is managed by Discord as a separate controller: rights in respect of that data are exercised with Discord, and its privacy policy sets out the rules and contact details.
The stored general sentences of questions to the Magnus bot do not contain your username or ID, so on their own they will usually not show that an entry is yours (Article 11 GDPR). If you wish to exercise the right of access, erasure or restriction in respect of such an entry, write to liga@szachowaliga.pl and give the wording of the question and the approximate time (day and hour). We will delete or show you an entry that we identify on that basis; where it cannot be identified, we cannot attribute it to you and will inform you of this. If you do not want your subsequent questions to be stored in this form (objection), write to liga@szachowaliga.pl and give your Discord username: we will switch off storage for your account, and the bot will continue to answer you. We will then keep only the hash of your account ID, needed to skip your questions, for as long as the objection applies. Entries disappear after 12 months in any case.
Visit statistics (point 3.26) do not contain data by which we could recognise you, so we are usually unable to identify your visits (Article 11 GDPR). You can switch off the measurement yourself by turning on the Global Privacy Control or ‘Do Not Track’ signal in your browser or by blocking the script from plausible.io. You can also send an objection to liga@szachowaliga.pl.
You can leave a WhatsApp group yourself at any time. On request sent to liga@szachowaliga.pl we will remove you from it. The data of your WhatsApp account is managed by WhatsApp as a separate controller: rights in respect of that data are exercised with WhatsApp, and its privacy policy sets out the rules and contact details.
You also have the right to lodge a complaint with the President of the Personal Data Protection Office (UODO) (ul. Stawki 2, 00-193 Warszawa).
8. Data we have not obtained from you
This part fulfils the information obligation under Article 14 GDPR towards persons whose data has not been obtained from them.
- Players registered by a team captain (or by the person registering the team). From the captain we have the player’s first name, surname, email address and optionally telephone number. We process them in order to organise the competition (line-up, pairings, organisational announcements, access to the Player Zone) and to publish results — on the basis of our legitimate interest (Article 6(1)(f) GDPR). The data can be seen by the Organiser’s team and the team captain (including the email address and telephone number), and by arbiters — without contact details; results are public. A player added with an email address by default receives from us a message with an invitation to the Player Zone, which states who registered them and for which team, and contains a link to this policy. If the captain switches off sending the invitation or selects the player from the company squad or from the League history, the player receives from us a short information email, without a sign-in link: who added them and to which team, where we obtained their data, for what purpose we process it and what rights they have, including that they can send an objection or a request for erasure of their data to liga@szachowaliga.pl. For a person on the team’s SLB SGH Online player list (point 3.17), the captain provides their first name, surname and email address. We process this data to enable that person to take part in SLB SGH Online (Player Zone, the club on lichess.org, classifications, the Online Team Cup, organisational announcements) and to publish tournament results — on the basis of our legitimate interest (Article 6(1)(f) GDPR). Such a person receives from us an email with a link to the Player Zone and the same information: who added them and to which team, where we obtained their data, for what purpose we process it and what rights they have. The information in this point is also permanently available on this page.
- The League archive for 2023–2026. We have transferred the results of our tournaments previously run on ChessArbiter and ChessManager to our own system: first name, surname, team, chess title and rating, CR PZSzach number and game results. We also have email addresses from team registration sheets from previous seasons and from earlier League forms. Purpose: the results archive and all-time rankings (Article 6(1)(f) GDPR), and, for email addresses, signing in to the Player Zone and linking the account to the results history. We publish only results, never email addresses; we send the newsletter only to persons who have consented to it.
- The FIDE rating list. Once a month we download the Polish part of the rating list from the public FIDE service: FIDE number, first name and surname, federation, sex, title, ratings, year of birth and activity status. It is used only by arbiters to search for players when entering them into tournaments (Article 6(1)(f) GDPR) and is not published.
- Participants in SLB SGH Online tournaments on lichess.org. From lichess.org we download the results of tournaments we organise in the SLB SGH Online and Warsaw Chess clubs: username, place, score and rating from the tournament. When someone joins the SLB SGH Online club, we read the list of join requests (username and request text) and store only the result of checking the username of the person who clicked ‘Check’. The purposes and legal bases are described in points 3.17–3.20. About persons who do not play in the League we know only what lichess.org shows publicly in the tournament results, and we do not combine this with any other data. The description of each tournament on lichess.org leads to www.szachowaliga.pl/online, and from there to the Regulations and this policy.
- Participants named when buying an event ticket. From the ticket buyer we have the participant’s first name and surname and, if given, the first name of the child they are coming with. We process them in order to prepare the list of participants and organise the event (point 3.25), on the basis of Article 6(1)(f) GDPR. How long we keep them (including in the transaction data in our Stripe account) — point 6, item 17. We do not publish the child’s first name and we do not pass it to Slack.
The categories of data, purposes, legal bases, recipients and retention periods are described in points 2–6, and your rights, including the right to object, in point 7.
9. Do you have to provide data
Providing data is voluntary, but without your first name, surname and email address we will not accept a registration or set up a Player Zone account, and without the company details we will not issue an invoice to a company. We will not sell an event ticket without the buyer’s first name and surname, the participant’s first name and surname, the email address and the billing address (needed for the invoice); you give the NIP only if you want an invoice to a company, and the child’s first name is optional. Consents to the newsletter, marketing SMS messages, the directory and the use of your image are voluntary and are not a condition of taking part in the League. Providing your lichess.org username is also voluntary, but without it you will not join the SLB SGH Online club. Joining the Discord server and the WhatsApp groups is voluntary and is not a condition of taking part in the League.
10. Cookies and browser storage
The website does not use analytical, advertising or tracking cookies. We collect visit statistics with the Plausible Analytics tool (point 3.26), which does not store anything on your device: it does not create cookies or entries in browser storage and does not assign you a persistent identifier. We use only the cookies necessary for the Player Zone to work: slb_sesja (keeps you signed in, up to 30 days, not accessible to the page’s scripts) and slb_zalogowany (tells the page that you are signed in — it changes the label in the header, up to 30 days). After a team registration is submitted, the browser briefly remembers the pro forma invoice address in tab storage (sessionStorage) in order to show it on the thank-you page, and deletes it after it has been read.
The registration forms are protected by Cloudflare Turnstile, which checks browser parameters to tell a human from a program. We load the website fonts from Google Fonts servers — your browser then connects to Google and passes on its IP address. On the pages we measure, the browser also downloads a script from the Plausible server (plausible.io) and passes on its IP address to it (point 3.26). Payments take place on Stripe pages, where Stripe’s cookies and privacy policy apply; we do not receive your card number or your bank sign-in details.
11. Automated decisions
We do not take decisions based solely on automated processing, including profiling, which would produce legal effects concerning you or similarly significantly affect you (Article 22 GDPR). Access requests for the Player Zone, the linking of accounts to results history and publications are reviewed by a human. Pairings in tournaments are calculated by a program in accordance with the FIDE rules, under the supervision of an arbiter. In SLB SGH Online, an automated system admits players to the club on the basis of the code from the Player Zone, calculates points and issues codes to the winners of open tournaments according to the rules in Annex 2 to the Regulations. At your request, any such decision, including passing over an account flagged by lichess.org, will be reviewed by a human.
12. Changes to the policy
We update the policy when providers, website functions or the law change. The current version, with its number and date, is always available at szachowaliga.pl/prywatnosc.