Privacy & Compliance
GameRebellion is designed with privacy as a first-class concern. The SDK includes built-in mechanisms for consent management, PII handling, and regulatory compliance.
Consent Management
Setting Consent
// After the player makes a consent choice:
GameRebellion.SetConsent(Consent.Granted); // Full data collection
GameRebellion.SetConsent(Consent.Denied); // Anonymous analytics only
GameRebellion.SetConsent(Consent.Unknown); // Default — same as Denied
Consent Flow
Player opens app
│
▼
Show consent dialog
│
┌────┴────┐
▼ ▼
Granted Denied
│ │
▼ ▼
Full data Redactor strips PII
collection Anonymous events only
The Consent Gate
The Consent Gate is the first stage of the client-side pipeline:
| Consent State | Behavior |
|---|---|
Granted | Full data collection: advertising IDs, IP, player identity |
Denied | PII stripped. Anonymous analytics still flow. |
Unknown | Treated as Denied until the player makes a choice |
The Redactor
When consent is denied, the Redactor strips PII before events leave the device:
| Field | Action |
|---|---|
idfa | Removed |
gaid | Removed |
ip | Removed |
player_id | One-way hashed |
email | Removed |
Server-Side Privacy
Additional measures on the server:
- IP Anonymization: Last octet of IPv4 (or last 80 bits of IPv6) is masked before storage
- GeoIP Resolution: Country/region resolved from IP before anonymization
- Data Retention: Configurable per environment
Regulatory Compliance
| Regulation | How GameRebellion helps |
|---|---|
| GDPR | Consent gates, PII redaction, data minimization, right to erasure support |
| CCPA | Opt-out support via consent denial, no selling of personal data |
| COPPA | When consent is denied, no PII is collected or stored |
| ATT (iOS) | SDK integrates with ATTrackingManager; IDFA only collected with ATT + SDK consent |