Mancala KayPrivacy Policy
Effective starting from: 2025-10-27 · If there is any inconsistency, this English version controls.
1) Who We Are
“Mancala Kay” (the “App”) is a mobile board game. “We”, “our”, and “us” refer to the App’s publisher. You can contact us at support@mancala-kay.com.
2) Scope
This Policy explains what information the App and our service providers process, how we use it, and your choices. This version of the App is primarily offline; limited cloud services are used for stability (crash reports) and updates, and the App displays non‑personalized ads.
3) Information We Collect
- Crash logs: device/OS information, error details, and diagnostics via Firebase Crashlytics to improve stability.
- Advertising identifiers (technical): identifiers used by the Google Mobile Ads SDK to request and deliver ads (banner, interstitial, rewarded). We request non‑personalized ads by default and filter ad content for general audiences.
- Device identifiers (limited use): a non‑advertising device identifier (e.g., platform identifier, App Set ID, or a locally stored anonymous ID) may be processed to protect integrity (e.g., abuse prevention) and to attribute rewarded‑ad grants.
We do not collect precise location, contacts, photos, microphone/camera recordings, or your address. If you email us, we will receive your email address and any information you include.
4) Data Stored On Your Device (Not Collected)
- Coins/balance and simple settings are stored locally on your device. This information is not sent to us and is removed when you reset or uninstall the App.
5) How We Use Information
- Operate and improve the App (e.g., fix crashes, ensure compatibility, and show a force‑update prompt if needed).
- Show ads and rewarded videos within reasonable limits to keep the experience respectful (e.g., cooldowns and daily caps).
- Maintain basic integrity (e.g., prevent abuse of rewards) using limited device‑level signals.
6) Legal Bases (EEA/UK)
- Legitimate interests: operating the App (stability, security), and measuring crashes.
- Consent (where required by local law): ads. If consent is not provided, ads remain non‑personalized.
7) Sharing & Disclosures
We do not sell personal data. We share limited information with service providers solely to operate the App:
- Google Firebase (Crashlytics) for crash reporting; and, when online features are enabled in future versions, Firebase Auth/Firestore/Messaging for basic operations.
- Google Mobile Ads (AdMob) to request and display ads. We request non‑personalized ads by default and set a general audience content rating.
We may disclose information if required by law or to protect the rights, property, and safety of users and the service.
8) Retention
- Local data (coins, settings) remains on your device and is removed on reset/uninstall.
- Crash reports are retained by Firebase for the period necessary to analyze stability and improve the App.
9) International Transfers
Firebase and AdMob may process data on servers located in the US/EU and other regions. Appropriate safeguards (e.g., standard contractual clauses) may apply as provided by those services.
10) Your Rights & Choices
- Ads: the App requests non‑personalized ads by default. Where consent is required, your choice is honored.
- Access/Correction/Deletion: Depending on your region (e.g., GDPR/CCPA), you may request access or correction of information we control (for example, crash reports linked to a device/session). If applicable, provide your device ID so we can locate records.
- Email: if you contact us, we will use your email to respond to your request.
See https://www.mancala-kay.com/data-deletion.html for the full deletion workflow.
11) Kids & Families
The App is suitable for ages 10+. We request non‑personalized ads by default and do not use sensitive data for ad personalization. If we learn we collected information from a child, we will delete it within a reasonable time.
12) Security
We use reasonable technical and organizational measures to protect information. However, no method of transmission or storage is 100% secure.
13) Changes to This Policy
We may update this Policy. We will update the “Effective” date above and may provide an in‑App notice for material changes.