Data & Permissions
A plain-language map of what the current Early Access release can access, what leaves the device, and what remains disabled.
Android permissions
| Permission | Why it exists | Required to play? |
|---|---|---|
| Internet | Supports optional Firebase services, Google Play/web actions and any separately approved online service. Bundled normal gameplay does not depend on a connection. | No for normal bundled gameplay. |
| Vibration | Haptic feedback during the game. | No. |
| Camera | Optional local Highlight reaction clips using the front camera. | No. Requested only when you enable Highlights. |
| Microphone | Adds sound to optional Highlight clips. | No. If denied, Highlights can record silently when camera permission is granted. |
| Accelerometer / gravity sensor | Recognises the Correct and Pass tilt gestures during gameplay. | No runtime permission is required for these motion sensors. |
The app does not request precise GPS location, contacts, phone/SMS access, Android advertising ID or broad photo/media-library access for normal gameplay.
Privacy controls
The latest launch code separates Product Analytics, Detailed Play Diagnostics and Crash Reports. An older Play-distributed Early Access artifact may expose fewer controls; a missing category cannot collect through that path.
| Setting | Default | Off-device in the current release? |
|---|---|---|
| Share play insights | Off | Only if you enable it: approved Product Analytics events may go to Firebase Analytics. A bounded first-party copy is also queued locally; the Kenyan Charades first-party telemetry endpoint is disabled in this release. |
| Share detailed play diagnostics | Off | No Kenyan Charades server upload in the current release. Approved bounded events may be queued locally while consent remains on. |
| Share crash reports | Off | Only if you enable it and Firebase Crashlytics is available. |
Current network-service state
| Service | Current Early Access state |
|---|---|
| Firebase Analytics | Optional; default off; consent-gated. |
| Firebase Crashlytics | Optional; default off; consent-gated. |
| Kenyan Charades first-party telemetry | Endpoint disabled in the current release configuration. |
| Structured in-app Feedback | Enabled (anonymous, HTTPS). Voluntary game-result chips and Help ratings, including an optional explanation up to 280 characters only following a negative Help reason. An app-private retry queue holds unsent reports; no additional Android permission is needed. Processed by Cloudflare, stored in Neon PostgreSQL, deleted within 90 days. |
| Community Suggestions | Enabled (anonymous, HTTPS). Bounded proposals for new decks, cards for an existing deck, and app features. The app does not request contributor identities or permissions to contacts, microphone, camera or media for these submissions. Submissions are checked for contact details, held for human moderation, and never published automatically. Processed by Vercel, stored in Neon PostgreSQL, deleted within 90 days. |
| Remote deck updates | Disabled for the launch catalogue; the bundled game remains the source for normal play. |
Google Play Data Safety
Google Play currently displays Kenyan Charades as sharing no user data with third parties under Play's Data Safety definitions, with data encrypted in transit and a deletion-request route. The public declaration covers the sum of relevant practices across versions distributed on Google Play.
| Play category | How it maps to Kenyan Charades |
|---|---|
| Location | If Product Analytics is enabled, Firebase Analytics may infer a broad approximate region from network/IP information. Kenyan Charades does not request precise GPS permission. |
| App activity | Optional bounded product events can describe screens/funnel steps, decks, rounds, scores or feature outcomes. Separately enabled detailed diagnostics can describe bounded card/gesture outcomes. Feedback and Suggestions you voluntarily submit are other user-generated content and other actions, collected for app functionality and not shared. |
| App info & performance | App/device version and optional crash/reliability context used to diagnose failures. |
| Device or other IDs | Pseudonymous Firebase app/installation identifiers and Crashlytics installation UUIDs used for optional analytics/reliability. Kenyan Charades removes the Android Advertising ID permissions and does not use these identifiers for advertising. |
Data that stays only on the device is not treated as off-device collection. When you deliberately use Android Share for a Highlight, you choose the receiving app/person and initiate that transfer.
Highlights and shared-file metadata
Highlight video/audio stays in app-private storage until you choose Android Share. Shared MP4s can carry bounded game context so the clip remains meaningful outside the app: deck ID/name, game mode, difficulty, score, recording time, round/team/turn context and app/content version. Player/team names, location, ad IDs and analytics identifiers are forbidden from that metadata.
Why the policy can change
Anonymous Feedback and Suggestions endpoints are live in this release; first-party gameplay telemetry remains disabled. Before a future release enables first-party telemetry or another new data flow, the Privacy Policy, this page and Google Play declarations must be re-audited against the exact signed release candidate.