CPS-08

No Hostile Notifications

Notifications must be useful, truthful, requested, easy to stop, and free of guilt or manufactured urgency.

Does not pass

Prohibited patterns

"Your character misses you," team guilt, false emergency, streak-loss threats, repeated purchase pressure, default-on marketing, or repeated permission nagging.

Can pass

Permitted patterns

Requested reminders, factual multiplayer turns, transaction/security notices, download completion, and off-by-default event categories.

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.