Your choices.
Your little corner.

Popping Candy is developed and published by Benjamin Colin Roy, the controller of the data described here. Contact hello@poppingcandy.app for support or privacy requests. This policy covers the game and poppingcandy.app.

Progress stays on your device

The game stores levels, scores, settings, hints, consent choices and a limited diagnostic log locally. There is no Popping Candy account or cloud save. These records support gameplay and troubleshooting. Settings lets you export a playtest report or reset local progress. Reports are not automatically emailed to us.

Optional gameplay analytics

Only if you allow gameplay analytics, we send selected events to PostHog's EU-hosted service: launches, tutorial steps, puzzle attempts and outcomes, scores, chain lengths, hints, timings, settings changes, limited error codes and ad delivery/revenue callbacks. Events include app/content versions, platform, major operating-system version, device category, a random installation identifier and session identifiers.

We use this information to understand difficulty, replay, retention, reliability and advertising performance. We do not send names, email addresses, precise location, free-text feedback, advertising identifiers or screen recordings to PostHog. Automatic interaction capture and session replay are not used. Network providers necessarily process an IP address when receiving a connection; we disable location enrichment for these gameplay events.

Analytics rely on your consent. You can play without them and change your choice in Settings → Usage analytics. Turning them off stops new collection and removes queued events and the local analytics identifier. It does not automatically erase events already received. A later opt-in creates a new identifier.

Advertising and consent

Releases with advertising use Google AdMob to show occasional ads between rounds and optional rewarded hints. We request non-personalised ads and do not request Apple's cross-app tracking permission or access the IDFA. Google's publisher first-party identifier is disabled in the production configuration.

Google's SDK may process IP-derived approximate location, device or app identifiers, ad views and interactions, diagnostic information and performance data to deliver and measure ads, prevent abuse and maintain the service. Non-personalised ads still involve data processing. Google's consent service presents the choices required for your region before ads can be requested. You can refuse optional consent; available advertising may then be limited.

Open Settings → Ad privacy choices when available to review or withdraw advertising consent. These choices are separate from gameplay analytics. See Google's privacy policy and how Google uses information from apps for its processing and retention practices. TestFlight builds may use demonstration ads that generate no revenue.

Game Center

If you choose to share your best score and open Game Center, we send your best score under the current game rules to Apple. Apple associates it with your Game Center profile for rankings. We do not send that profile to PostHog. Game Center is governed by Apple's privacy policy and your Apple settings.

Support and this website

If you email us, we receive your email address, message and any attachments you choose to send. Cloudflare Email Routing forwards incoming support mail to our support inbox hosted by Google. We use it to answer your request and troubleshoot the game, based on our legitimate interest in providing support.

This website is hosted on GitHub Pages, with Cloudflare providing domain and related infrastructure. These providers may process connection data such as IP addresses and technical logs to serve and protect the website. We add no advertising cookies, analytics scripts or tracking pixels to these pages.

Storage, sharing and deletion

Local game data remains until you reset it or remove the app. Queued gameplay events are capped at 1,000 and expire after seven days. PostHog stores delivered events according to the project's retention settings and service plan. Support correspondence is retained while needed to resolve enquiries and maintain relevant support records. Service providers may retain technical records for their own security or legal obligations.

We use the providers named above to operate the game, measure optional gameplay analytics, deliver advertising and respond to support. Providers may process data internationally; their published privacy terms describe applicable transfer safeguards. We do not sell gameplay analytics or use it to build cross-app advertising profiles.

You may ask for access, correction or deletion of personal data we hold, withdraw consent, or raise a concern using the contact address above. Because gameplay analytics use random identifiers, we may need your help identifying relevant records; we will not ask for your Apple password. You may also complain to your local data-protection authority, including the UK Information Commissioner's Office.

Audience and changes

Popping Candy is intended for a general teen and adult audience, not specifically for children. If you believe a child has supplied personal information to us, contact us so we can investigate. We update this policy when the game's data practices change and show the revision date above.