What Data Do Games Collect About Players?

Start with the specific game and operator

There is no single collection rule shared by all games. A local board, a console store and a large multiplayer service can have very different data flows. Start with the privacy notice linked by the game you use, then check which operator and services it covers. A statement about one publisher should not be copied onto another publisher’s games. The examples here were checked on October 16, 2026 and illustrate categories to look for; they are not a complete audit of those services.

Gameplay records are more than a final score

EA’s policy describes collecting in-game profile information, gameplay and statistics in online games. It also explains that some information can be visible to other players, including outside the immediate game, and describes recordings and controller inputs in certain competitive contexts. The details and conditions matter. A record used to run a match, an optional public profile and a replay distributed to others involve different questions about visibility. Look for what is collected, why it is used and who can see it.

Communications and security have their own rules

Riot’s April 28, 2026 notice describes account and service information alongside player behavior, communications and anti-cheat purposes. It states that automated tools can scan certain content and monitor activity to detect policy violations and security risks. Do not translate that into a claim that every publisher records every conversation. Read the named service’s notice, relevant support documentation and available settings. A feature that sends voice, reports or diagnostic information deserves its own explanation rather than being hidden inside the vague word analytics.

A recorded action and an inferred trait differ

A session duration is a record of an event. A claim about why someone played, or what their behaviour says about their personality, is an interpretation. CNIL’s 2016 discussion of GAMR considered potential implications of behavioral profiling, including imagined future uses; it did not establish that every such use was already happening. When a service describes a profile or recommendation, ask what inputs support it and what decisions it affects. Do not assume that a useful statistic is an accurate account of a person.

Read a notice with a short set of questions

Identify the operator, the categories of information, the stated purposes, the recipients and the retention explanation. Then look for privacy controls and the contact route that applies to your region. Consider where a public username appears and whether you want the same name across unrelated services. These are reading prompts, not a statement of your legal rights or a substitute for the full policy. Avoid sharing account credentials with a third-party tool merely because it promises better statistics or an entertaining personality result.

Apply the same questions to browser games

A game without a login can still use hosting logs or browser storage. A saved preference on a device is different from a public leaderboard, and both should be described accurately. Read this website’s current Privacy page for its actual implementation rather than applying a commercial publisher’s policy to it. The former GAMR research consent is a separate historical record. Playing a current ProjectGAMR game does not enrol you in that study, recreate a participant profile or establish an institutional connection with its researchers.

Revisit a notice when a game introduces a new social or account feature, because the feature may change the relevant questions. Keep a dated link to the policy you read so you can distinguish its wording from your own interpretation.