DefuseCrew is operated by Atanas Petrov, based in Bulgaria, who is the controller responsible for the processing described here.

You do not need an account or analytics consent to play. Bomb generation and game rules run on your device. We do not ask for a player name or email address. Requests needed to deliver the website include your IP address and browser information; the website host may process these for delivery and security independently of optional analytics.

Only if you accept, we load Google Analytics through Firebase to understand visits, game difficulty and module mix, solved modules, strikes, round duration and outcomes, replays, and manual usage. This helps us improve onboarding and game balance.

Google receives event data, page paths, browser/device information, cookie identifiers and network information including your IP address when your browser connects to its services. Analytics can derive approximate location. This is not anonymous data simply because we do not ask for your name. Our event code excludes query strings, fragments, referrers and game seed codes. Advertising personalization and Google Signals are disabled in the integration.

The legal basis for optional analytics and analytics cookies is your consent (Article 6(1)(a) GDPR). Rejecting analytics does not restrict the game. We do not load the analytics SDK or send analytics events before acceptance, and do not replay earlier activity after acceptance.

We save your accept/reject choice in your browser's local storage under defusecrew-analytics-consent-v1 so we can respect it on later visits. This preference remains until you change it or clear the site's storage. It is stored on your device, not sent as a gameplay event.

After acceptance, Google Analytics may set _ga and _ga_* cookies to distinguish browsers and sessions. Google's default cookie lifetime is up to two years and may be refreshed by later activity; browser restrictions can shorten it. Cookie lifetime is separate from event retention on Google's servers.

To withdraw, open Analytics settings at the bottom of any page and choose Reject analytics. This stops future collection by this integration and removes accessible Google Analytics cookies for this site. Withdrawal does not affect the lawfulness of earlier processing or automatically erase information already sent. You can also clear site storage in your browser, which removes the saved choice.

Google processes analytics data to provide the service. For users in the European Economic Area, Google Ireland Limited is the relevant Google service entity. Google and its service providers may process information outside Bulgaria and the EEA, including in the United States. Google's applicable terms describe transfer safeguards, including standard contractual clauses where applicable.

Our Google Analytics event-data retention setting is two months. Reset user data on new activity is enabled, so later activity can renew the retention period for the user identifier. Google's retention setting does not apply to standard aggregated reports, which may remain available longer. Deletion is subject to Google's processing schedules.

If you email us, we use your address and message to answer your request, based on our legitimate interest in responding to enquiries or our legal obligation to handle data-protection requests. We retain correspondence only as needed to handle the request and any applicable legal obligations.

Subject to applicable law, you can request access, correction, erasure, restriction or portability of your personal data, and object to processing based on legitimate interests. You can withdraw analytics consent at any time. Email the contact above to exercise these rights. Because we do not create player accounts, identifying a particular analytics record may require additional information; we will explain what is reasonably needed.

You can complain to Bulgaria's Commission for Personal Data Protection or the supervisory authority where you live, work, or believe an infringement occurred.

We will update this notice if our processing changes and revise the date above. A change requiring fresh analytics consent will be presented before that processing begins.