Privacy

Candy Rush sends data on three separate routes. They have genuinely different characters, so they are described separately rather than collapsed into one paragraph.

Last updated 13 September 2026

The short version

Nothing Candy Rush sends can be used to recognise you across sessions unless you chose to submit a score.

  • Performance telemetry carries no persistent identifier of any kind — no account id, no device fingerprint, nothing stored on disk.
  • Leaderboard submissions do carry your Steam ID and display name, because a ranked score has to be attributable. You choose when to submit.
  • Diagnostic logs are sent from every build, with your Steam ID, the account name in file paths, and your computer name removed first. They carry nothing that links one session to another.

Performance telemetry

The game measures how well it runs and sends a small summary at the end of each run. This is what the public performance page is built from.

  • What is sent: frame-time statistics, memory use, load times, what your display can present, and for each finished run its arc, outcome, depth and duration.
  • What identifies the session: a random number generated when the game starts and thrown away when it closes. It is not derived from your machine, your account, or anything saved to disk.
  • What is never sent: your Steam ID, your name, your IP address as stored data, any hardware fingerprint, and the seed of any run you played.
  • Retention: raw sessions are deleted from the collection bucket after five days; only the aggregate totals survive, and no aggregate is published from fewer than five sessions.

Because there is no persistent identifier, two sessions from the same player cannot be linked — not by us, and not by anyone reading the stored data. That is why there is no opt-out toggle and no deletion request process: there is no record attached to you to switch off or delete. Hashing an identifier would NOT have achieved this, which is why none is sent at all.

Leaderboard submissions

Submitting a run to the weekly leaderboard is a service you ask for, and it is the one route that identifies you.

  • What is sent: your Steam ID, your Steam display name, your score and the recorded inputs of the run so it can be replayed and verified.
  • Why: a ranked score has to be attributable to somebody, and a verified score has to be reproducible.
  • Where it appears: published on the public leaderboard alongside your Steam display name.
  • Control: the game asks before submitting, and the setting can be turned off. Nothing is submitted from a run you did not choose to submit.

This route is unchanged by the performance dashboard. The two systems share no data and no storage.

Diagnostic logs

Every build can upload its log file to help diagnose a crash or a performance problem. The game removes the identifying strings listed below before the file leaves your machine, and nothing in an upload links one session to another — which is why there is no opt-out toggle and no deletion request process, for the same reason as performance telemetry above.

  • What is sent: the log file. That includes the system-information banner the game writes at startup (graphics card, device model, operating system, screen size, memory), the performance measurements taken during the session, and whatever the game printed before it stopped. Our servers also record the country the upload came from.
  • What is removed first: your Steam ID, the account name where it appears inside file paths, and your computer’s name. This is a best-effort clean-up of a file that contains whatever the game happened to log, so it is not a guarantee that no identifying text ever survives — it is a guarantee that we look for those three and take them out.
  • What identifies the upload: a random number generated when the game starts and thrown away when it closes. Nothing is stored on your device, and nothing is derived from your account or your hardware, so two uploads cannot be linked back to the same machine.
  • Retention: logs are deleted after 30 days. The storage is private, has no public address, and only the developer can read it.

This website

The site is static and fetches published JSON files directly from a CDN.

  • No advertising, no third-party analytics, and no tracking cookies.
  • The performance page and the leaderboard fetch public data files; nothing you do on them is recorded.

Questions

Email admin@irsik.software with any question about what is collected or why.