# Privacy Policy (English)
Last updated: March 10, 2026
## 1. Introduction
This Privacy Policy explains how exTaboo (the "App") processes data.
exTaboo is a local-network party word game. Multiplayer sessions can run on
the same Wi-Fi/hotspot without internet for core gameplay. Some optional
features (ads, purchases, analytics) may require internet access.
## 2. Data We Process
### 2.1 Data stored locally on your device
The App can store the following data on-device:
- Nickname (display name entered by the user)
- Age value (used for age-based safety and category rules)
- UI preferences (theme, language, display settings)
- Category visibility preferences
- Reward/badge and daily streak progress
- Parent PIN lock data (stored as hash, not plain PIN)
- Local gameplay/lobby state
### 2.2 Analytics data (Firebase Analytics)
The App uses event analytics for product quality and feature improvement.
Example event parameters include:
- Anonymous analytics identifier (`analytics_id`, rotates on max 90-day cycle)
- Session identifier (`session_id`)
- Gameplay context identifiers (`lobby_id`, `match_id`)
- Nickname and nickname length (subject to age/toggle rules below)
- Age-set event
- Feature usage events (lobby actions, theme changes, help interactions,
fullscreen usage, etc.)
- App version, build number, local timestamp
Custom analytics event parameters intentionally do **not** include:
- IP address
- Precise location
- Network name (SSID/BSSID)
- Device name
Analytics collection rule:
- Disabled until age is declared.
- Disabled for users under age 13.
- Can become active again if age is updated to 13+.
Nickname analytics matrix:
- Age unknown or `<13`: disabled.
- Age `13-17`: limited mode.
- `nickname_saved` may be sent.
- `analytics_id`, `session_id`, `lobby_id`, `match_id`, and client context
are excluded.
- Age `18+`: full mode.
- `nickname_saved` may be sent with normal analytics context.
- For `13+`, if user disables "Include Nickname In Analytics" in settings,
nickname analytics stops.
### 2.3 Advertising data (Google AdMob)
The App uses Google AdMob for post-game ad display. On Android, ad
infrastructure may use Advertising ID (`AD_ID`).
Age/safety ad behavior:
- Under 18: child/under-age safe ad request mode.
- In that mode: non-personalized ads are requested.
- Age not declared: child-safe mode is used by default.
### 2.4 In-app purchase data (Google Play Billing)
The App uses Google Play Billing for support packages and ad-free offerings.
Payment card details are not collected by the App directly; payments are
handled by Google Play.
## 3. Permissions
The App may request/use:
- `android.permission.CAMERA` (QR join flow)
- `android.permission.INTERNET` (ads, analytics, billing)
- `android.permission.ACCESS_NETWORK_STATE` (connection checks)
- `com.google.android.gms.permission.AD_ID` (Android ad infrastructure)
## 4. Why We Process Data
We process data to:
- run local lobby/game synchronization
- provide app functionality and reliability
- improve product quality and UX
- enforce age-appropriate safety behavior
- deliver ads and measure ad-related performance
- support purchase and restore-purchase flows
## 5. Third-Party Services and Data Transfers
The App uses:
- Google Firebase Analytics
- Google AdMob
- Google Play Billing
These services may process data required for their functions under their own
privacy terms. exTaboo does not sell user data as a standalone data broker.
## 6. Retention and Deletion
- Local app data remains on device and is removed when the app is uninstalled.
- `analytics_id` rotates on a maximum 90-day cycle.
- Users can reset anonymous analytics identity in-app.
- Data retention by third-party providers follows their own policies.
## 7. Children's Privacy and Age Compliance
The App uses age input to enforce safety behavior:
- Under 13: analytics disabled.
- Under 18 (or age undeclared): child-safe ad request mode.
- Category visibility/content may be restricted by age rules.
The App is designed to support compliance workflows, but regulatory obligations
may vary by country/region and distribution context.
## 8. Security
Where applicable, data in transit uses secure transport (for example HTTPS/TLS).
No software or network method can guarantee absolute security.
## 9. Your Controls
Users can:
- manage camera permission in device settings
- update age value
- update nickname
- enable/disable nickname analytics for `13+` users
- reset anonymous analytics identity
- set/clear parent PIN lock (where available)
## 10. International Processing
Depending on selected services, data may be processed on infrastructure outside
your country. Processing is governed by the relevant provider terms/policies.
## 11. Contact
For privacy questions or requests:
- Email: contact.arkaneco@gmail.com
## 12. Policy Updates
This policy may be updated from time to time. If material changes are made,
the "Last updated" date will be revised.