CPS-02

No Tracking

The game must not profile, follow, fingerprint, or collect people beyond what is necessary for requested operation, security, or tightly limited diagnostics.

Does not pass

Prohibited patterns

Advertising identifiers, cross-app attribution, device fingerprinting, session replay, behavioral profiles, data brokerage, unrelated location/contact collection, or indefinite event-level telemetry.

Can pass

Permitted patterns

On-device logs shared by the player, minimized crash/security diagnostics, short-lived aggregate operational counts, and explicit opt-in research with withdrawal.

How the audit treats this rule

Evidence, behavior, and edge cases.

Evidence

Provide the relevant configuration, catalog, service inventory, screenshots or recordings, test account/build, and a clear description of remotely controlled behavior.

Test

The reviewer checks actual behavior across applicable account states, regions, purchase paths, notifications, remote flags, and relevant service traffic.

Pass condition

The prohibited behavior is absent, permitted behavior fits the stated caveat, and the evidence is sufficient for the frozen product scope.