Collecting gameplay telemetry to balance our game: what privacy traps should we know about?
retained text
We're a small indie studio based in Germany making a roguelite hex tile-builder. The most difficult challenge for us is balancing the game. We have a huge spreadsheet of numbers and values, and systems interact with each other, so changing one value will affect other ones. We want to collect gameplay telemetry from playtests and later the public release, purely to balance the game: which items get bought, what each one scores, where runs fail, how long seasons take, etc. We want to collect a random install ID (a GUID generated on first launch, not tied to Steam, hardware, or anything else), session and run ID, and gameplay events: start/end, season scores, purchases, placements, contract outcomes We don't want to collect anything that you can be identified by, like Steam ID, name, email, hardware/OS info or anything outside the game. Before we build the upload side, we'd like to get the privacy part right. Questions for anyone who's been through it: 1. Is a persistent random install ID still personal data under GDPR, even with nothing else attached? Would you drop it and use per-session IDs instead? 2. The EU "cookie rule" also covers IDs stored on the player's device. Did you ask for opt-in consent for telemetry, or rely on an opt-out in settings? 3. Technically, the server will see IP addresses on upload, is it still counts as a personal data? 4. Self-hosted vs. GameAnalytics, Unity Analytics, and the like: did a third-party service make compliance easier or harder? 5. Steam and consoles: did you hit any requirements (privacy policy, disclosure, certification)? 6. Anything country-specific that surprised you? I'll summarize the answers in an edit for anyone else doing this.
document fetched 2026-09-26 00:26 · canonical https://reddit.com/r/gamedev/comments/1wprfox/collecting_gameplay_telemetry_to_balance_our_game