CPS-03

No Forced Accounts

Basic and offline play must not require unnecessary registration, email, profile creation, or social login.

Does not pass

Prohibited patterns

Account wall before basic play, unnecessary email requirement, intentionally unusable guest mode, marketing consent tied to registration, or obstructed deletion.

Can pass

Permitted patterns

Local/guest play, optional cloud-save account, or an account limited to multiplayer, moderation, parental controls, cross-device sync, or purchase restoration.

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.