BLOCK THROW
Play
Privacy and Cookie Policy
What personal data is processed when you play Block Throw, why, who it is shared with, and your rights.
Last updated: 1 November 2026
1. Who is responsible
The controller under the EU General Data Protection Regulation ("GDPR") and Turkey's Personal Data Protection Law No. 6698 ("KVKK") is Nihat Yasin Satar, who develops Block Throw under the name Laterfix. Contact: [email protected].
2. What data we process
When you play as a guest
- An anonymous user ID that Firebase creates for you, and the random guest name you are given.
- Settings kept in your browser: language, sound on/off, the install reminder, your cookie choice.
When you sign in with Google
- Your email address, name and account ID from your Google account (through Firebase Authentication).
- The username you choose, your best score, wins, rating and leaderboard position. Your username and scores are visible to other players on the leaderboard.
- The move records and results of your online matches (to check results are genuine), and the replays you choose to share.
For everyone
- Security data: to stop cheating, bots and abuse, Firebase App Check and Google reCAPTCHA Enterprise process browser and device information and your IP address.
- Server logs: Cloudflare and Firebase, which serve the site, keep technical logs such as IP address, browser type and request time for security and operation.
- Advertising data: Google AdSense processes data such as your IP address, browser and device information and the page you visit to show ads. It uses cookies only with your consent (see section 6).
The game does not access your location, contacts, camera or microphone. We do not take payment details.
3. Purposes and legal bases
| Purpose | Legal basis |
|---|---|
| Providing the game: your account, online matches, the leaderboard, replays | Performance of a contract (GDPR Art. 6(1)(b); KVKK Art. 5(2)(c)) |
| Preventing cheating, bots and abuse, keeping the site secure, fixing technical problems | Legitimate interests (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f)) |
| Advertising cookies and personalized ads | Consent (GDPR Art. 6(1)(a); KVKK Art. 5(1)). You can withdraw it at any time. |
| Legal obligations and legal claims | Legal obligation; establishing or defending legal claims |
4. Who we share data with
We do not sell your data. We use these service providers to run the game:
- Google LLC / Google Ireland Ltd.: Firebase (authentication, databases, server functions; mostly on servers in Europe), reCAPTCHA Enterprise and AdSense.
- Cloudflare, Inc.: hosting and protecting the site.
These providers may have servers outside your country, including in the EU and the US, so your data may be transferred internationally. Transfers rely on the safeguards required by GDPR Chapter V and KVKK Article 9, such as the providers' standard contractual clauses.
We may share data with public authorities where the law requires it.
5. How long we keep it
- Account, username, score and rating data: while your account exists. Deleted within 30 days of your request.
- Online match data: kept live during the match; the records needed to check results and the leaderboard are kept with your account.
- Shared replays: as long as the share link works.
- Your cookie choice: 12 months, then we ask again.
- Server and security logs: for the short periods set by the providers.
6. Cookies and similar technologies
A cookie is a small file a website stores in your browser. Block Throw also uses your browser's local storage (localStorage, IndexedDB). We group them like this:
| Group | What for | Examples | Consent |
|---|---|---|---|
| Necessary | Language and sound settings, staying signed in, remembering your cookie choice, cheat and bot protection | flutter.*, bs_consent (localStorage), Firebase sign-in data (IndexedDB), _GRECAPTCHA | Not needed; cannot be turned off |
| Advertising | Counting ad views, not showing the same ad over and over, preventing fake clicks | Google ad cookies (e.g. __gads, __gpi, IDE) | Your consent |
| Personalization | Choosing ads based on your interests | Google ad cookies | Your consent |
We ask on your first visit. If you do not agree, no advertising cookies are used; ads are shown without cookies and are not personalized. Rejecting is as easy as accepting and does not limit the game in any way. Visitors from the European Economic Area, the UK and Switzerland are asked through Google's certified consent message.
You can change your choice at any time: in the game under Settings > Cookie settings, or with the Cookie settings link at the bottom of this page. You can also delete or block cookies in your browser; deleting the necessary data resets your settings and signs you out.
7. About Google ads
- Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites.
- Google's use of advertising cookies enables it and its partners to serve ads to you based on your visit to this site and/or other sites on the Internet.
- You can opt out of personalized advertising in Google's My Ad Center. You can opt out of some third-party vendors' cookies at www.aboutads.info.
- How Google uses data: How Google uses information from sites or apps that use our services.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
8. Your rights
You can ask us to access, correct or delete your personal data, to restrict or object to processing, and for a copy of your data in a portable format. Where processing relies on consent, you can withdraw it at any time without affecting earlier processing. You can also complain to your local data protection authority (in Turkey, the Personal Data Protection Board).
Write to [email protected] from the email address of your account, with your username, so we can verify it is you. We answer within 30 days, free of charge. To delete your account and data, just write to the same address.
9. Children
Block Throw is not directed at children under 13, and we do not knowingly collect their personal data. If you learn that a child under 13 has created an account, write to us and we will delete it.
10. Security
Connections are encrypted with HTTPS. Only authenticated requests can reach the databases, and only as far as the security rules allow; scores are checked on the server.
11. Changes
We may update this policy from time to time. For important changes we update the date and, where needed, ask for your consent again.
12. Contact us
Developer: Nihat Yasin Satar (Laterfix)
Website: laterfix.com
Email: [email protected]