Privacy Policy

COCKROACH JANTA PLAY · Last updated: 2026

1. Introduction

This Privacy Policy explains what data Cockroach Janta Play (the "Game") collects, how we use it, and the choices you have. We collect only what we need to run the Game and its leaderboards.

2. Data We Collect

Account data — when you sign in with Google or email, we receive your email address and a unique account identifier (Firebase UID). We do not see or store your Google password; email/password sign-in is handled by Firebase Authentication.
Profile data — your chosen nickname, scores, games played, and play time.
Device data — a generated device identifier and device name to map your progress.
Location (optional) — if you allow it, your approximate latitude/longitude is converted to city/state/country for regional leaderboards. You can decline.
Push token (optional) — if you enable notifications, a Firebase Cloud Messaging token so we can deliver announcements.

3. How We Use Data

To run accounts, save progress, and display global/regional leaderboards.
To show how many players are currently online.
To send notifications you opted into (updates, events, important notices).
To detect abuse and keep the Game working.

4. Sharing

We do not sell your personal data. Your nickname, score, and approximate region appear on public leaderboards. We use Google Firebase (Authentication, Cloud Messaging) and Microsoft Azure (storage) as processors.

5. Your Choices

Play as a guest without an account.
Decline or revoke location and notification permissions in your device settings.
Request deletion of your account data by contacting us.

6. Data Retention

We keep account and score data while your account is active. Presence (online) data is held in memory only and expires within seconds of you leaving.

7. Children

The Game is not directed at children under the age required by your local law. We ask players to confirm their age is accurate before playing.

8. Changes

We may update this Policy. Material changes will be reflected by an updated date and, where appropriate, an in-app notice.