Ashta Chamma Back to Home

Privacy Policy

Effective Date: 28 September 2026

Last Updated: 16 October 2026

Data Controller

This app is operated by One Point Five Pixels.

Data Usage

Ashta Chamma is a turn-based board game and does not require account sign-up to play. During normal gameplay, we do not ask for your phone number, contacts, photos, or precise location. You may optionally choose a display name (in Settings or for online multiplayer); this name is visible to other players in the same game room and is not required for offline gameplay. If you set one, it is also stored with the game-server account described in "Game Recordings" below, even if you only play offline.

Data is used only to operate core app features, improve reliability, and (as described below) show advertising, analyze gameplay, and publicly feature selected games. We do not sell personal information. Game recordings are stored grouped by a random app identifier (see "Game Recordings" below) so we can analyze gameplay and handle deletion requests, but we do not use them to profile you or for advertising. Advertising-related processing is performed by Google’s advertising services as described below.

  • Locally stored settings and app state: language, AI difficulty, audio volume and similar preferences, plus the items listed in "Storage" below.
  • Display name (optional): shown to other players in your game room while a match is active, and stored with your game-server account, where it is used to show your name in matches.
  • Online multiplayer session data: room codes, in-match game state, and connection metadata needed to create rooms, synchronize gameplay between players, and maintain active matches — see "Online Multiplayer" below.
  • Game recordings: the move history of each game you play, uploaded to our game archive under a random app identifier, without your name or display name in the recording — see "Game Recordings" below.
  • Mobile telemetry (iOS and Android only): selected Firebase Analytics gameplay events, Firebase Crashlytics diagnostics, and Firebase Remote Config requests.
  • Web analytics (only if you accept analytics cookies): Google Analytics 4 page-view and usage metadata for website/app performance measurement — see "Cookies (Web)" below.
  • Basic delivery metadata on web: IP address, browser type, and request timestamp handled by hosting infrastructure.
  • Advertising (iOS and Android only): Google AdMob may show ads during gameplay, processing advertising identifiers and device data as described in "Google AdMob (Mobile Advertising)" below.
  • Advertising (web only): this website has applied to Google AdSense, and no ads are shown on it yet. Once they are, Google AdSense may process cookies and device data as described in "Google AdSense (Web Advertising)" and "Cookies (Web)" below.

Online Multiplayer

Online multiplayer features may require temporary processing of gameplay data necessary to create rooms, synchronize game state between players, and maintain active matches. We do not use this information to identify you personally, and gameplay session data is retained only as long as necessary to operate the service.

The only personal information involved is the display name you optionally choose (see "Data Usage" above), which is visible to other players in your game room while a match is active. Multiplayer is entirely optional — offline gameplay against computer opponents does not use any of this, except that the app signs in to our game server (which, like any web service, sees your IP address) with a random app identifier to upload game recordings (see "Game Recordings" below).

Multiplayer session data, and the game-server accounts described in "Game Recordings" below, are processed on our own game server, not a third-party multiplayer platform. That server is hosted by DigitalOcean in its Bengaluru, India data centre.

Game Recordings

When a game ends — whether it is won, or left before it finishes, and whether it is played offline or online — the app saves a recording of it on your device and uploads a copy to our game archive. A recording contains only gameplay information:

  • the moves played, dice rolls, and the game's outcome;
  • each seat's pawn color and whether it was a human or a computer opponent (and the computer's difficulty level);
  • the game's start time, game type (offline or online), for online games the room code, and technical details needed to replay it exactly.

Recordings do not contain your name, your multiplayer display name, email address, device details, or location.

To upload a recording, the app signs in to our game server using a random identifier it generates and stores on your device. This happens even if you only play offline: if you have never played online, the first upload creates an account for you on our game server keyed to that identifier. The identifier is not derived from your name, email, or device hardware, but it is pseudonymous rather than anonymous: your uploaded recordings are stored under the game-server account ID linked to it, and if you have chosen a display name, that name is stored with the same account. The identifier may persist after you reinstall the app (for example through the iOS Keychain or Android backup). We never publish these IDs; during online matches, other players' apps receive your account ID so the game can run.

We use game recordings to:

  • analyze gameplay to improve game balance, the computer opponents, and reliability;
  • feature selected games publicly — for example as replay videos on YouTube or social media. Featured games show only the gameplay and pawn colors, never who played them.

In an online game, each player's app uploads its own recording of that game. Recordings are received and stored by Cloudflare (see "Third-Party Services" below), which, like any web service, processes your IP address and basic request metadata to deliver each upload. If a game has not uploaded yet (for example while you are offline), it waits on your device and is retried later.

Firebase Analytics (Mobile)

In non-debug iOS and Android builds, we use Firebase Analytics to understand high-level gameplay and app reliability trends. It only starts once a player aged 18 or over has agreed to it on the first-launch screen (see "Players Under 18" below).

Current event families include:

  • app_open
  • new_game_start
  • game_end
  • gameplay_milestone

These events are limited to gameplay and system metadata such as player count, AI count, AI difficulty, roll count, and outcome categories. We do not intentionally include names, email addresses, contact data, or free-form personal text in analytics payloads. These event names may evolve as the game develops.

Firebase Crashlytics (Mobile)

In non-debug iOS and Android builds, we use Firebase Crashlytics to receive crash and non-fatal error diagnostics so we can identify and fix stability issues. Like Analytics, it only starts once a player aged 18 or over has agreed to it.

Crash reports can include technical context such as app version, OS version, device model class, stack traces, timestamps, and diagnostic identifiers required for crash grouping and triage.

Firebase Remote Config (Mobile)

In iOS and Android apps, we use Firebase Remote Config to turn features on or off and adjust settings (for example how often ads can appear) without releasing a new app version. To fetch these settings, the app sends Google a Firebase installation identifier and basic app and device information (such as app version and platform). Like Analytics, it only starts once a player aged 18 or over has agreed to it.

Telemetry Purpose and Data Categories

  • Product analytics: aggregated gameplay flow and feature usage to improve game experience and balancing.
  • Reliability diagnostics: crash and non-fatal error context to improve performance, fix defects, and reduce app failures.
  • Operational support: release-health monitoring across app versions and device/OS combinations.

Google AdMob (Mobile Advertising)

In iOS and Android apps, we use Google AdMob to show interstitial ads at natural breaks in gameplay (for example between games). AdMob is a Google advertising service, and showing an ad can cause Google to process:

  • On Android, Google AdMob may use the device’s Advertising ID. On iOS, the app does not ask for App Tracking Transparency permission, so AdMob does not receive your device's advertising identifier (IDFA).
  • Device and app information such as device model, OS version, app version, IP address, and general (non-precise) location inferred from IP address.
  • Ad interaction data, such as impressions and clicks.

We do not control which specific ads Google serves, and Google (not us) determines whether a given ad is personalized based on the advertising identifier above. You can review or reset your device's ad personalization settings, and Google's own privacy practices for its advertising products, using the links in "Third-Party Services" below.

Players under 18 only receive non-personalised ads, marked as directed at children and limited to general-audience (G) content (see "Players Under 18" below).

Google AdSense (Web Advertising)

This website has applied to Google AdSense, and no ads are shown on it yet. While Google reviews the site, our pages load Google's AdSense script, which can contact Google and may set cookies even though no ad is shown. Once the site is approved, we plan to show display ads (for example beside and below the game board on the /play page). Loading an AdSense-served ad can cause Google to set cookies or use similar technologies in your browser and process:

  • Cookie and browser identifiers, used to measure and (depending on your settings and region) personalize ads.
  • Browser and device information such as browser type, device type, IP address, and general (non-precise) location inferred from IP address.
  • Ad interaction data, such as impressions and clicks.

As with AdMob above, we do not control which specific ads Google serves. Ads are personalised only if you accept "Personalised ads" in our cookie banner (see "Cookies (Web)" below); otherwise we ask Google for non-personalised ads only. Non-personalised ads are based on context such as the page and your general location, not your browsing history, but Google may still use cookies for frequency capping, aggregated ad reporting, and fraud and abuse prevention. You can also review or opt out of personalized advertising using the links in "Third-Party Services" below.

On the /play page, no ad is requested until the age question in the game has been answered, and only non-personalised ads are requested for players under 18, whatever their cookie choice (see "Players Under 18" below).

Cookies (Web)

When you first visit this website, a banner asks whether to allow optional cookies. Google Analytics and personalised-ad cookies are not used until you choose, and "Reject optional" is as easy as "Accept all". Google's AdSense script loads regardless of your choice (see "Google AdSense (Web Advertising)" above), but only for non-personalised purposes unless you accept personalised ads. You can change your choice at any time with the "Cookie settings" link at the bottom of every page.

  • Essential (always on): browser storage that remembers your cookie choice (ashta_cookie_consent) and, on the /play page, the game's own settings and data listed in "Storage" below. These are needed for the site and game to work and are not used for analytics or advertising.
  • Analytics (optional): Google Analytics 4 cookies (_ga and _ga_<ID>, kept for up to 2 years) that measure page views and usage. Google Analytics is not loaded at all unless you allow this. If you later turn it off, we stop Google Analytics and delete these cookies.
  • Personalised ads (optional): lets Google AdSense use cookies and similar identifiers to personalise ads, once ads are live on this site. Without it, any AdSense ads are non-personalised, which may still use cookies for the limited purposes described in "Google AdSense (Web Advertising)" above.

On the /play page, Google Analytics and personalised ads are only used once the age question in the game has been answered as 18 or over — never for players under 18, even if optional cookies were accepted.

Your choice is stored only in your browser. Clearing your browser storage resets it, and the banner will ask again.

Permissions and Device Access

The game does not require camera, microphone, contacts, or precise location permissions to play core gameplay.

Platform-level services (for example app store delivery, crash reporting at OS level, or network routing) may process technical data according to their own policies.

Storage

The game stores a small set of settings and app state on your device (in browser storage on the web) so your choices persist between sessions. This currently includes:

  • language preference, AI difficulty, and audio volume settings (music and sound effects);
  • your display name, if you set one;
  • your answer to the age question and whether you agreed to this policy (see "Players Under 18" below);
  • the random app identifier and sign-in session for our game server (see "Game Recordings" above);
  • counters used to space out ads and the "rate this app" prompt (for example the number of games played and when an ad was last shown), and small interface preferences such as dismissed confirmation dialogs;
  • on the web, your cookie choice (see "Cookies (Web)" above).

Recordings of your games, and any not yet uploaded to our game archive, are also kept on your device (see "Game Recordings" above).

If you clear browser storage or app data, these saved preferences are removed and reset to defaults. On-device game recordings are removed when you clear browser storage, clear the app's data, or uninstall the app, although device backups may retain copies.

We do not require account-linked cloud sync for these settings.

Retention and Deletion

Locally stored settings and on-device game recordings are retained until you remove app/browser data or uninstall the app.

Any server-side operational logs retained by hosting or app store providers follow those providers' own retention policies.

Firebase Analytics and Crashlytics data retention for mobile telemetry is managed within our Firebase project settings and is governed by Google Firebase service controls and policies.

Online multiplayer session data (room state and connection metadata) is retained only for the duration of an active match and is not kept afterward. Your game-server account — the random app identifier and, if you chose one, your display name — is kept so the app can sign you in again, until you delete it with Settings → Delete My Data or ask us to delete it. The finished game's recording, which does not include display names, is kept separately as described below.

Uploaded game recordings are kept in our game archive indefinitely, because they form a long-term record used for gameplay analysis and replays. Settings → Delete My Data deletes every recording uploaded from your app, together with your game-server account, and removes your display name, on-device recordings and not-yet-uploaded recordings from the device. You can also ask us to delete them (see "Your Choices and Rights" below). Games already featured publicly, for example in a published video, may remain available. Step-by-step instructions are on our Delete Your Data page.

International Users

Your information may be processed in countries where our service providers operate, including countries outside your place of residence.

Depending on your location, local data protection laws may provide you with additional rights.

Jurisdiction and Governing Law

This policy and any privacy-related disputes are governed by the laws applicable in India, without prejudice to any mandatory rights available to users under their local consumer or data protection laws.

Third-Party Services

Our web version is delivered via standard hosting infrastructure and mobile versions are distributed through app stores. These providers may process technical request data (for example IP address, browser, device model, OS version, and timestamps) under their own policies.

For web surfaces, Google Analytics 4 processes page interaction events and related technical metadata only if you accept analytics cookies (see "Cookies (Web)" above).

Third-party terms and privacy policies apply where relevant, including but not limited to Apple App Store, Google Play, and web hosting/CDN providers used to deliver this app.

Key third-party services include:

  • Google Firebase (Analytics, Crashlytics and Remote Config) for mobile apps.
  • Google Analytics 4 for web analytics measurement.
  • Google AdMob for mobile app advertising (iOS and Android).
  • Google AdSense for web advertising (not yet live).
  • DigitalOcean (Bengaluru, India) for hosting our game server.
  • Cloudflare (Workers and R2 storage) for receiving and storing game recordings.
  • Apple App Store and Google Play for app distribution.
  • Web hosting/CDN providers for website and web app delivery.

Relevant third-party privacy resources:

Players Under 18

The first time the app opens (on iOS, Android or the web version at /play), it asks for the player's year of birth. We keep only whether the player is 18 or over, never the year itself, together with whether they agreed to the data uses described in this policy, the app version and the time of the answer. This is stored on the device (in the browser, on the web). For players 18 and over, a copy is also kept with their game-server account once one exists (after the first upload or online game), as our record that they agreed. The app cannot change it afterwards, and it is deleted with the account when you use Delete My Data.

Because only the year is asked, anyone who turns 18 in the current year is treated as under 18. For players under 18, the app runs in a restricted mode:

  • Firebase Analytics, Crashlytics and Remote Config are not started. On the web /play page, Google Analytics is not loaded, even if analytics cookies were accepted.
  • Ads are never based on personal data. In the iOS and Android apps, ad requests are marked as directed at children and under the age of consent, and limited to content rated for general audiences (G). On the web, the /play page requests only non-personalised ads, even if personalised ads were accepted in the cookie banner.
  • Game recordings are not uploaded, and no game-server account is created.
  • Online multiplayer is not available.

Players 18 and over see a short notice of how the app uses their data and are asked to agree before the app continues.

The answer can't be changed in the app. It is reset by clearing the app's data, reinstalling the app, or using "Delete My Data" in Settings.

Children's Privacy

The game does not require account registration and is not designed to collect personal information directly from children. For players 18 and over, the app creates a pseudonymous game-server account, holding no contact details, so it can upload game recordings (see "Game Recordings" above). It does not create one for players under 18 (see "Players Under 18" above).

We do not knowingly collect personal information from children. If you believe personal information has been provided to us by a child, please contact us and we will review and address the request.

This app is intended for a general audience and is not directed specifically at children. Because younger players may still use it, the app asks every player's age first and runs in the restricted mode described in "Players Under 18" for anyone under 18. Advertising provided through Google AdMob and Google AdSense is governed by Google’s own advertising policies and controls; if you believe ads served to a child require review, please contact us.

Security

We take reasonable measures to protect information processed through the app. However, no method of transmission or storage is completely secure.

Your Choices and Rights

  • Local data: clear app/browser storage or uninstall the app (the app's random identifier may survive this — see "Game Recordings"). You can also contact us for privacy-related requests or questions.
  • Mobile telemetry: use device-level privacy settings provided by iOS and Android (including analytics and diagnostics preferences where available on your device/version).
  • Web cookies: allow or refuse analytics and personalised-ad cookies, or change an earlier choice, with (also at the bottom of every page). Browser privacy tools such as tracker blocking also work; disabling JavaScript can affect app functionality.
  • Game recordings and your game-server account: in the app, open Settings → Delete My Data. This deletes every recording uploaded from your app and your game-server account, and removes your display name, on-device recordings and not-yet-uploaded recordings from the device, so a new random identifier is used if you play online again. Language and sound settings are kept. It does not remove other players' own recordings of a shared online game (stored under their accounts), games already featured publicly (for example in a published video), or Firebase Analytics and Crashlytics data, which is not linked to that identifier.
  • If you can't use the app, contact us to ask that recordings uploaded from your app, or your game-server account, be deleted, or that a game be left out of public replays. Because recordings do not include your name, include details such as the approximate date and time of the game and (for online games) the room code. We will make reasonable efforts to find and delete the recordings we can match to your request, and may ask for more details to confirm the games are yours.
  • Advertising:
    • Review and adjust ad personalization across Google's services (including AdMob and AdSense). Google Ads Settings
    • On Android: reset or opt out of your device's Advertising ID in Settings.
    • On iOS: the app does not ask for tracking permission. You can also stop all apps from asking by turning off "Allow Apps to Request to Track" in Settings > Privacy & Security > Tracking.

Contact

For privacy questions or requests, contact us at hello@onepointfivepixels.com.

If we make material changes to this policy, we will update the "Last Updated" date on this page.