Skip to content
Briqler
PrivacyTerms

Legal

Privacy
Policy

Effective: October 30, 2026
Last updated: November 5, 2026

OverviewLocal dataOptional servicesAdvertisingDaily comparisonFriends leaderboardsSharingYour choicesRetentionChildrenContact
01

Overview

This Privacy Policy explains how Briqler (“Briqler,” “we,” “us,” or “the game”) handles information when you use the Briqler Android application and this website.

Core promise: Briqler’s core puzzle is playable offline without creating an account. Optional network services are designed not to block gameplay.
02

Information stored on your device

Briqler stores game information locally so the game can work offline. This may include:

  • a randomly generated installation identifier;
  • saved games and Daily Challenge progress;
  • scores, personal bests, progression, rewards and settings; and
  • gameplay statistics used to tailor your in-game experience.

This information stays on your device and your saved games are not uploaded. There are two exceptions: the placements of a finished Daily Challenge are sent, without any identifier, to compare your score (see Daily score comparison), and if you join a friends leaderboard your nickname and scores are stored on our server (see Friends leaderboards).

03

Optional analytics and crash reporting

If you separately enable Optional analytics or Crash reports in Settings, Briqler may use Google Firebase services.

Optional analytics

Analytics may include a pseudonymous installation identifier, app version, general device information, and gameplay events such as games started and finished, scores, play time and rewards used. We use this to understand how the game is played and to improve it. Analytics does not include your name, email address, contacts or precise location.

Optional crash reports

Crash reports may include technical details about the error, the app and operating-system version, device model and time of the crash, so we can fix problems.

Google may process IP addresses and device or app information as part of delivering these services. See Google’s Privacy Policy.

This website

This website does not set its own cookies and contains no analytics, forms or third-party media. It runs on Cloudflare. Cloudflare may process request data such as IP address, browser information, timestamps and security signals to deliver and protect the site. See Cloudflare’s Privacy Policy.

04

Advertising and ad measurement

Briqler may show ads provided by Google AdMob. Before ads are requested, Google’s consent tools ask for your choices where required by law.

Ad services may process the Android advertising identifier where available, IP address, device and app information, consent choices and ad interactions, to show ads, measure their performance and prevent fraud. We receive reports about the ads shown in the game, which help us understand ad performance and improve the game. See how Google uses information in ads.

Rewarded ads are always optional. Ads are not shown while you are placing pieces, and you can always start a new game without watching one.

You can change your advertising privacy choices from Briqler Settings.

05

Daily score comparison

When you finish a Daily Challenge, Briqler sends the challenge code and your placements to our server on Google Firebase (Cloud Functions and Firestore). The server replays the run to confirm the score, then tells you what share of other players’ verified first finishes you beat.

The request contains no name, account, device identifier or advertising identifier, and the stored result contains no IP address. The server keeps only the challenge code, the verified score, the day it was received and a fingerprint of the placements (so each run counts once). Because nothing identifies you, these records cannot be linked back to you. They are deleted after 90 days. Google processes your IP address to deliver the request and may keep it in Google Cloud request logs for up to 30 days.

To award rank colors, the game asks the server once more after that Daily is over, sending only the challenge code and your verified score. The colors are stored on your device.

When you share a verified Daily result, the link includes a short reference to your stored run (the start of its fingerprint). A friend’s game uses it to ask the server whether that run really has the score in the link. The reference identifies the run, not you.

Weekly challenges work the same way, except that each time you beat your own best of the week, that run is sent and stored too, so the score in your links can be verified. Weeklies show no comparison with other players.

To keep automated submissions out, the game also sends a Firebase App Check token: Google Play Integrity confirms that the request comes from Briqler as installed from Google Play, without telling us who you are. To limit repeated requests, the server briefly keeps a scrambled fingerprint of your IP address in memory; it is never stored.

To stop sending Daily results, turn off Compare Daily scores in Settings.

06

Friends leaderboards

Friends leaderboards are optional and need no account. If you create or join one, the nickname you type is sent to our server on Google Firebase and shown to the other players on that leaderboard, with your score on each puzzle. A leaderboard’s name is shown to them too. You don’t have to use your real name.

The server stores the leaderboard’s name, your nickname, a random member identifier, a fingerprint of a random secret kept on your device, and your verified scores. It stores no account, device identifier, advertising identifier or IP address. When you finish a Daily or Weekly, the game sends the challenge code and your placements to each of your leaderboards so the server can replay the run. These requests use the same App Check and request limits described above.

Leaving a leaderboard deletes your nickname and scores from it straight away, and so does being removed by its owner. Deleting your local progress in Settings first leaves every leaderboard the game can reach. Otherwise scores are deleted 14 days after they are sent, and your nickname 90 days after you joined or last sent a score.

If someone reports a name, we keep the reported name and the leaderboard’s name for up to 90 days to review it. Blocking a player happens only on your device.

07

Sharing and external links

When you choose to share a Daily Challenge image or code, Briqler creates the content locally and opens Android’s share interface. The destination service you select processes the shared content under its own terms and privacy policy. Briqler does not automatically post it or upload your share-sheet contacts.

Challenge codes identify the puzzle, not you.

08

Your choices and controls

  • Analytics: enable or disable Optional analytics in Settings.
  • Crash reports: enable or disable Crash reports independently.
  • Daily comparison: turn off Compare Daily scores to stop sending finished Daily runs.
  • Advertising privacy: use Privacy options in Settings when available.
  • Local data: use “Delete local progress and settings” in Settings, or clear the app’s storage through Android.
  • Deletion requests: see Delete your data for every way to delete Briqler data, including asking us.
  • Sharing: do not select a destination in the Android share interface if you do not want to share.

Disabling an optional service stops future custom collection through that setting. Information already processed by a service may remain subject to its retention, legal and security obligations.

Depending on where you live, you may have rights to ask about, access, correct, delete, restrict or object to processing of personal information, or withdraw consent. Use the contact method below to make a request. Because Briqler has no account system, we may be unable to associate service data with you unless you provide enough non-sensitive information to locate it. You may also complain to your local data-protection authority.

09

Retention, security and transfers

Local game data remains on your device until you delete it, clear app storage or uninstall the game, subject to Android backup behavior. Turning off analytics also discards analytics events that have not been sent yet. Daily comparison records are deleted after 90 days. Third-party service data is retained according to configured service settings, contractual requirements and applicable law.

We use reasonable technical safeguards, data minimization and access controls, but no storage or transmission method is completely secure. Google and other ad providers may process information in countries other than yours using the transfer protections described in their policies.

10

Children’s privacy

Briqler is not directed to children below the minimum age required to consent to data processing in their country. We do not knowingly ask children to provide a name, email address or account profile in the game. If you believe a child has provided personal information through an optional service, contact us so the issue can be reviewed. Distribution to child audiences may require additional Google Play Families controls and region-specific consent measures.

11

Changes to this policy

We may update this policy when Briqler, its service providers or legal requirements change. We will update the date above and, when appropriate, provide notice in the app or store listing. Material changes apply prospectively unless the law permits otherwise.

12

Contact

For a privacy question or request, email support@briqler.com and include “Privacy” in the subject. Please do not send passwords, advertising identifiers or other sensitive information.

© 2026 Briqler.

Privacy PolicyTerms of ServiceDelete your data
EnglishEspañolPortuguêsFrançaisالعربيةहिन्दीDeutschItaliano