ChessPin privacy policy
Effective date and last update: 19 October 2026. Version 0.3.
1. Who is responsible for your data
The controller is “iChess” JANUSZ LISOWSKI, al. Zwycięstwa 96/98/B.1, unit 126, 81-451 Gdynia, Poland. Contact for ChessPin and privacy requests: app@chesspin.link.
This policy covers the ChessPin mobile app and chesspin.link. The service is intended for people aged 16 and over.
2. Information we process
- Browsing without a player account: Firebase creates an anonymous technical session to allow access to the map and public content. It does not create a player profile. Technical installation and session identifiers may still be processed.
- Accounts: email address, display name, Firebase user ID, sign-in provider, confirmation of the minimum age, and account timestamps. Google and Apple passwords are not shared with ChessPin. Firebase handles email/password authentication.
- Profiles: information you choose to provide, such as city, description, languages, playing preferences, and public chess ratings or profile IDs from Chess.com, Lichess, and FIDE. Profile information intended for players is visible to signed-in users.
- Location: with your device permission, approximate or precise location helps show nearby places and games. You can choose a city instead. We do not request background location. Coordinates of a place or game you create are shared as part of that content. Google Maps also processes information needed to deliver maps.
- Photos: images you choose to add, author ID, and date. Photos are resized on the device and EXIF metadata is removed before upload. Place photos may be visible to other players and guests.
- Games and tournaments: places, schedules, playing preferences, participant identifiers, invitation codes, pairings, match results, rankings, feedback, and reports. A private block list is visible only to the account that created it. Public browsing does not provide access to private player profiles or private communications.
- Technical information: push tokens, installation identifiers, app and operating system versions, crash reports, IP addresses, server logs, and per-account usage counters that protect service limits. Release versions use Firebase Crashlytics; debug and emulator versions do not send crash reports through that integration.
- Support requests: your email, topic, message, and optional device/app version. Do not send passwords, sign-in codes, or sensitive material. Website requests are delivered to our support mailbox.
3. Why we use information
Account, profile, game, tournament, and requested map functions are processed to provide the service you request (GDPR Article 6(1)(b)). Security, abuse prevention, necessary technical diagnostics, and answering general enquiries are based on our legitimate interests in operating a safe and working service (Article 6(1)(f)). Legal obligations are handled under Article 6(1)(c). Where separate consent is legally required, processing is based on Article 6(1)(a).
Device permissions let you control access to location, camera, photos, and notifications. They are separate from the legal basis for processing a game or photo you choose to submit. You can change permissions in device settings; related features may then be unavailable.
Providing profile extras, photos, precise location, and push permission is optional. An email and technical account identifier are necessary for account features. We do not make automated decisions that produce legal or similarly significant effects on you.
4. Service providers and other recipients
We use Google Firebase/Google Cloud for authentication, database, functions, push, and crash diagnostics; Google Maps for maps; Google and Apple for sign-in; and public Chess.com, Lichess, and FIDE services for ratings you select. Public place discovery uses OpenStreetMap/Overpass and Geoapify. We send an area or country query to place providers, rather than an account identifier or your exact device position. Public data and photos can be seen by guests; account information is shown only where the app makes it available to other players.
The website and email are hosted by WEBD.pl (Globtel Internet Szymon Hersztek). The host processes connection logs, necessary form sessions, and email delivery. Information may be shared with authorities when legally required. We do not sell personal data.
Some providers process data outside the European Economic Area. Where applicable, transfers rely on adequacy decisions or standard contractual clauses and related safeguards. Contact us for information about the safeguards relevant to your data. Google's privacy information and Firebase processing terms describe the provider's arrangements.
5. Advertising and website cookies
The current app does not contain Google AdMob or another third-party advertising SDK. Google advertising and occasional own banners are planned. Before activating them, we will update this policy and store declarations and implement any required consent choices. This website has no advertising, analytics trackers, or marketing cookies.
The contact form uses a temporary, necessary session cookie to prevent forged submissions and show delivery status. It expires when the browser session ends. Anti-spam counters use a hash of the connection IP address, are valid for one hour, and contain no message text. Expired counters are removed on the next form submission. Hosting connection logs are separate from those counters.
6. Retention
Account data is held while the account is active. Photos, push tokens, block lists, and the player profile are removed by account deletion. Public place entries and game/tournament history may remain to preserve useful public information and the integrity of results; this is not a reason to retain unnecessary personal details. Reports and security records are kept while needed to resolve the issue, prevent abuse, meet legal duties, or address claims. Support correspondence is kept while necessary to handle the request and related follow-up or legal duties. Provider logs, crash reports, and technical backups follow the applicable service retention cycle.
Contact us about a specific record. We review personal details remaining in tournament history, reports, and other records separately when handling a deletion request; the in-app deletion flow does not automatically remove every historical tournament entry.
7. Delete your account or data
In the app, use Profile → Delete account and confirm your identity. We delete the sign-in account, profile and its ratings, push tokens, private block list, and your photos. You are removed from games; your open games are cancelled. Public places and some history, feedback, or security records may remain as described above.
You can also use the account deletion page without reinstalling the app or email app@chesspin.link. Use the address linked to your account. We verify identity before deleting anything; a form submission alone does not delete an account. We respond without undue delay, normally within one month, and explain any lawful extension or necessary retention.
You can also request deletion of specific data without closing your account. Use the support form or email app@chesspin.link from the address linked to your account, identifying the photo, record or data you want removed. We verify your identity and explain any necessary retention under section 6.
8. Your rights
Under applicable data protection law, you may request access, correction, deletion, restriction, or portability of your data, object to processing based on legitimate interests, and withdraw consent without affecting earlier lawful processing. Email app@chesspin.link. You may complain to your local data protection authority, including the Polish President of the Personal Data Protection Office (UODO).
9. Security, safety, and changes
We use access controls, authentication, encrypted connections, and provider security mechanisms. No system is entirely risk-free. Report privacy or safety concerns through support or app@chesspin.link. ChessPin is not directed at children; please report accounts of people under 16.
Updates will be published at this address with a new date. Material changes may also be announced in the app. This policy describes the current app; future features may require different disclosures and choices.