Taash Adda privacy policy

1. Summary

Taash Adda is a card game. It is designed so that most of it works without an account and without a connection, and so that the parts that do need a server send as little as they can.

You can play without an account. The current build has no sign-in at all, and every game plays offline; on Android the only network traffic is the ads, analytics and settings described in §2, and the iPhone app sends nothing at all.
We never sell your data, and we do not build advertising profiles from it.
Coins cannot be bought. They are earned by playing. There is no purchase path, no transfer between players, and no cash-out. Real money buys a subscription and nothing else.
Chat messages are deleted after 180 days, automatically, by the database itself rather than by a cleanup job somebody has to remember to run.
There is no account in the current build. Uninstalling the app removes everything it keeps on your device; §11 covers the rest.

2. What the current build collects

The build described by this policy at the date above has no account system, no sign-in, no online play, no chat and no purchases. The sections that describe those apply from the day each one is switched on. What the build does have, and what each part sends:

Advertising (Google AdMob). The app shows ads (§7). To serve and measure them, Google’s ads SDK receives your device’s advertising identifier, your IP address (from which Google derives an approximate location), and device and diagnostic details about the phone and the SDK itself. Where a privacy regulation requires it, Google’s consent form is shown first, and neither the ads SDK nor the analytics below runs until that check allows ads.
Analytics (Google Analytics for Firebase). Collection is off when the app starts and is switched on only once the ads consent check allows it, and off again if that changes. What is sent is which games are played and finished, whether a tutorial or the daily claim was completed, which theme was chosen, and what each ad impression paid (the ad unit, the currency and the amount: facts about the ad, not about you), whether the tutorial was chosen on the first run, and when the “our other games” prompt was shown, waved away or its Install button tapped. Events carry no identity beyond Google’s app-instance identifier and (because the ads and analytics SDKs are linked) the device’s advertising identifier: no name, no email, nothing you typed. (§8)
Remote configuration (Firebase Remote Config). At most once every twelve hours the app fetches its settings: which contested rule each game plays by, and how ads are paced. The request carries a Firebase installation identifier so that Google can answer it; it carries nothing about how you play. (§8)

Those are the only network calls the Android app makes. A link to one of our other games opens the Play Store app; Taash Adda sends nothing with it.

This matches what we declare on Google Play’s data-safety form: approximate location, app interactions, diagnostics and device identifiers (advertising identifier, app-instance identifier, Firebase installation identifier), collected and shared with Google for advertising, analytics and fraud prevention, encrypted in transit. Not collected: name, email, messages, contacts, photos, precise location, purchases.

This policy is updated before a feature that collects anything more is released, not after.

On iPhone. The iPhone app collects nothing. It shows no ads, runs no analytics, crash reporting or remote configuration, has no account, sign-in or purchases, and asks for no permissions, so it makes no network calls of its own. Its settings and progress (§3) stay in the app’s storage on your phone and are deleted with the app. This matches its App Store privacy label: Data Not Collected. A link to one of our pages opens your phone’s browser or mail app, and the app sends nothing with it.

3. Information stored on your device

Stored locally, never transmitted unless a section below says otherwise:

What	Why
Game settings: theme, card style, bot difficulty, language, sound, haptics	so the app opens the way you left it
The name you chose for your seat	so the table can call you something; it never leaves the device in this build
Local statistics: hands played, games completed, coins, XP, daily streak	to show your own record
Your daily free-hand allowance	to know what you have used today
The last game you opened	so the lobby can offer to continue it
Ad pacing: when a full-screen ad was last shown, matches since, when the install was first seen	so ads keep to their limits
Prompt counters: how often the “our other games” prompt was shown or waved away	so it stops asking
Your ads consent choice, kept by Google’s SDK	so you are not asked again

Uninstalling the app removes all of it.

When online multiplayer is enabled, the app creates an account so that a table can tell players apart and so progression survives a reinstall.

Anonymous by default. An anonymous account is a random identifier. It is not linked to your name, phone number or email.
Optional Google sign-in, only if you choose it, so progress can move to a new device. We receive your Google account identifier and, if you grant it, a display name and profile picture.
A display name you choose. Other players at your table see it. It does not have to be your real name and we recommend it is not.

5. Online multiplayer

To run a table, the server stores while a match is live: which players are at it, whose turn it is, the moves made, and the resulting scores. Move history is kept so a disconnected player can rejoin the hand they left.

The server does not send you another player’s cards. Redaction happens before anything is transmitted, not in the client.

6. Chat

Where chat is enabled, messages are stored so they can be delivered and so a report can be investigated.

Every message carries an expiry of 180 days from when it was sent, and the database deletes it automatically at that point. This is a property of how the message is stored, not a policy somebody has to enforce.

Reported messages may be retained beyond that period while a report is handled.

7. Advertising

On Android, ads are served by Google AdMob. The iPhone app shows no ads.

Banner ads appear in two places only: inside the scorecard and inside the quit-confirmation dialog, in a strip that has its own space. A banner never sits over the table, a card or a control, and never appears while you are making a timed decision. If one fails to load, its space collapses.
Full-screen ads are an interstitial at a match boundary (when you abandon a match, or on the way back to the lobby after finishing one; never mid-hand), and rewarded and rewarded-interstitial ads that run only when you choose to watch them.
AdMob may use a device advertising identifier to limit repetition and measure performance. You can reset or delete that identifier in Android Settings → Privacy → Ads.
Where required, you will be asked for consent before personalised ads are shown, and you can decline and still use the app.

AdMob’s own privacy policy: https://policies.google.com/technologies/partner-sites

8. Analytics, crash reporting and remote configuration

On Android, the app uses Google Firebase for:

Analytics: which screens are opened and which games are played, in aggregate, and what each ad impression paid. Used to decide what to build, not to identify you. Collection is off until the ads consent check allows it (§2).
Remote configuration: the app fetches its settings, at most once every twelve hours. This sends nothing about how you play; it only receives values.
Crash reporting: not in the current build. When it is added, the app will send a stack trace, device model, OS version and app version when it crashes. No game content, no chat.

The iPhone app uses none of them.

Firebase’s privacy information: https://firebase.google.com/support/privacy

9. Subscriptions and payments

Subscriptions are sold through Google Play. We never see your card details. Google tells us that a subscription is active; it does not tell us how you paid.

Coins are earned in play and cannot be purchased, transferred or cashed out. The iPhone app sells nothing.

10. Children

Taash Adda is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe a child has given us personal information, contact us and we will delete it.

11. Your rights: access and deletion

There is no account in the current build, and nothing on our servers that is yours by name. Deleting your data works like this:

On your device: uninstall the app (on iPhone, delete it). Everything in §3 goes with it.
Advertising identifier (Android): reset or delete it in Android Settings → Privacy → Ads. The iPhone app never reads it. Where a regulation gives you a choice about personalised ads, Settings → Privacy choices inside the app reopens Google’s form.
Analytics (Android): email us (§15). We cannot look you up by name, because we never have one; tell us the device and roughly when you installed, and we will ask Google to delete the analytics data we can tie to that app instance, and tell you what was possible. We respond within 30 days.

When accounts arrive, you will be able to delete your account and everything attached to it from Settings inside the app, and this section will say exactly where.

You may also request access to, correction of, or deletion of your data by email at any time. We respond within 30 days.

12. Data retention

Data	Kept for
Analytics events	by Google, under the retention setting for this app in Firebase; we keep no copy
Chat messages	180 days, then deleted automatically
Match records	90 days
Account and progression	until you delete your account
Crash reports	90 days

13. Security

Data in transit is encrypted with TLS. Server-side access rules deny by default: a client can read only what it is explicitly permitted to read, and wallets and entitlements are writable only by the server.

14. Changes to this policy

This policy is updated before a change to what the app collects takes effect, and the date at the top changes with it. Material changes are announced in the app.

15. Contact

Jogiba Gaming, support@jogiba.com