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. Every game plays offline as a guest. Signing in is optional and only keeps a cloud copy of your progress so it can move to another phone (§4). Online tables against other people are optional too (§5).
- We never sell your data, and we do not build advertising profiles from it.
- Coins cannot be bought. They are earned by playing. No plan or purchase adds coins, and coins cannot be transferred between players or cashed out.
- Money buys plans, through the stores only. From version 0.9.11 the app sells plans that unlock games and, with the Adda Pass, remove forced ads. Google Play or the App Store takes the payment; we never see your card, bank or UPI details (§9).
- There is no chat between players.
- An account is optional, and you can delete it in the app or by email. Uninstalling the app removes everything it keeps on your device; §11 covers the rest.
2. What the current build collects
What the app has, 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. In versions 0.9.11 to 0.9.14 other ad networks could also bid to fill an ad through AdMob and received the same kinds of data (§7); from version 0.9.15 AdMob alone serves the ads. Where a privacy regulation requires it, Google’s consent form is shown first, and neither the ads SDKs nor the analytics below run 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, when the “our other games” prompt was shown, waved away or its Install button tapped, and, from version 0.9.11, that the plans sheet was opened (from where, and for which game), that a purchase was started (the product) and how many games were chosen for a plan. Google’s Analytics SDK can also record in-app purchase events on its own. 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)
- Online tables, only when you choose to play online: the nickname you sit down with, the table options and your moves go to our match server (§5).
- The optional account, only when you sign in: the account and the cloud copy of §4.
- Purchases, only when you buy a plan: the store handles the payment and tells the app what you own (§9).
- News notifications (from version 0.9.15), only if you switch them on: a Firebase messaging token (§8).
- Your account photo link, only if you choose to share your photo at online tables (§5).
- A report, only when you report another player at an online table (§5).
A link to one of our other games opens the Play Store app or the App Store.
From version 0.9.15 it carries a campaign label naming Taash Adda, so the
store can tell us the visit came from the app (on Google Play
utm_source=taash_adda&utm_medium=cross_promo&utm_campaign=games_tile and
the game’s name; on the App Store Apple’s campaign token
ct=taash_adda_tile). An invite from a game card, or the link on a result
you share, goes to https://taashadda-24.web.app/get?game=<game>&from=<tile or results>,
a page on the game’s own hosting that sends Android to Google Play with
utm_source=invite&utm_campaign=app_invite and the game’s name, and the
iPhone to the App Store with ct=invite_<tile or results>. None of these
carries anything about you. A shared result is a picture the app draws and
hands to your phone’s share sheet; the app sends it nowhere itself. A link to one of our pages opens your
phone’s browser or mail app, and the app sends nothing with it.
Not collected: messages, contacts, photos from your phone, precise location, or your payment details. Our answers on Google Play’s data-safety form and Apple’s App Privacy form follow this policy.
This policy is updated before a feature that collects anything more is released, not after.
On iPhone. The iPhone app shows ads from version 0.9.1 and uses the same services as Android. Google’s ads SDK, and in versions 0.9.11 to 0.9.14 the mediation networks, receive a device identifier (the advertising identifier only if you allow tracking in Apple’s prompt, otherwise an identifier for this app alone), your IP address (from which an approximate location is derived), advertising data and your interactions with the ads, and diagnostics about the SDK. It is used for advertising, for the ads to work and to prevent fraud, and it is not linked to your name or to an account. From version 0.9.11 the app also lists Apple’s SKAdNetwork identifiers, Apple’s way to credit an install to an ad without the advertising identifier. Version 0.9.0 and earlier showed no ads and sent nothing.
Sharing a result. If you share a result, the game opens your phone’s share sheet with a short text about the match and a link to its page on jogiba.com. You choose where it goes; the game sends nothing itself.
Ratings and reviews. Now and then, after a won match, the game may offer to let you rate it. The rating window is the store’s own (Google Play’s or the App Store’s): the stars and any review you write go straight to the store with your store account, are published there as a public review under the store’s terms, and you can delete them there. The game itself never receives them.
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 goes to the match server only when you play online (§5) |
| 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, and any unfinished match (the game, the deal’s seed and the moves made) | so the lobby can offer to continue it from the same trick |
| Your plan: which plan or Day Pass you hold, the games you chose, and the ids of purchases already applied | so a purchase is applied once and can be restored |
| A random key for online seats (from version 0.9.12) | so a seat held for you after a dropped connection goes back only to this phone |
| Ad pacing: when a full-screen ad was last shown, matches and hands since, when the install was first seen; from version 0.9.15 how many matches you started today and how many ads you watched ahead (§7) | so ads keep to their limits |
| The country you chose in Profile, if any (from version 0.9.15) | to show its flag on your seat at online tables (§5) |
| Players you blocked: each one’s block key and seat name (from version 0.9.15) | so they stay blocked (§5) |
| Tournament entries (from version 0.9.15) | so a tournament’s coins are paid once |
| Your notification switches (from version 0.9.15) | so reminders and news follow your choice (§8) |
| 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.
4. Accounts and the cloud copy of your progress
Signing in is optional, on Android and iPhone, and the game plays fully without it. Its only purpose is to keep a copy of your progress so it can move to another phone.
- Sign-in providers. From version 0.9.2: Google (Android and iPhone) and Sign in with Apple (iPhone). From version 0.9.12, where the app offers them: Google Play Games on Android, Game Center on iPhone, and Facebook. Your account is kept by Firebase Authentication, a Google service. It holds what the sign-in provider gives: a user identifier from that provider, your name, your email address (Google and Facebook share it; Apple may share a private relay address or none; Play Games and Game Center give a player identifier and name and no email), a profile photo link when the provider has one, which provider you used, and when the account was created and last signed in. The game never sees a password.
- The cloud copy. While you are signed in, the app writes a copy of your settings (language, sound, table theme, bot difficulty, the name you chose for your seat), your progress (coins, XP and level, daily streak, games played and won, statistics, and the ad and trial counters), from version 0.9.15 your chosen country and the players you blocked, any unfinished matches, the time of the copy and your phone’s model name to Cloud Firestore, a Google service, stored in Mumbai, India. It is one document per account that only that account can read or write. It is written again shortly after any change while you are signed in, and read when you sign in, so a new phone can restore it.
- Your own profile photo (from version 0.9.15). If you are signed in with Google, Facebook or Play Games, you may show that account’s photo on your own profile in the app (Apple gives none). The app draws it from the provider’s own link; it is never copied or uploaded, there is no upload from your gallery. Other players see it only if you choose to share it at online tables (§5).
- Facebook. The app uses Meta’s Facebook Login SDK for signing in only, with its automatic app events and advertising-identifier collection switched off. On Android it contacts Meta only when you tap Facebook. On iPhone the SDK starts with the app and may fetch its own settings from Meta; signing in there uses Meta’s Limited Login, which does not track you.
- The providers’ own policies. Google’s, Apple’s and Meta’s privacy policies cover what they do when you sign in with them.
- Nothing else. No contacts, no location, and nothing in the account is sold or used for advertising. Nothing in it is shared with other players except your photo, and only if you choose to share it (§5). Coins stay earned only: the account changes nothing about money.
- Deleting it. Delete account in the app’s Profile pane removes the cloud copy and then the account; for an Apple account the app also revokes Apple’s sign-in token. The progress on your phone stays until you remove the app. You can also ask us by email (§11).
5. Online play
Since October 2026 some games can be played online against other people, as well as offline against bots. Online play is optional.
- Where. Online tables run on our match server on Google Cloud Run, in Mumbai, India.
- What the app sends. The nickname you sit down with (your own choice, at most 20 characters, “You” until you change it), the game and table options, and your moves. From version 0.9.12 it also sends the random seat key of §3, which is made on your phone and not linked to you or to your device’s identifiers. From version 0.9.15 it also sends the country you chose in Profile, if you chose one, and the block keys of players you have blocked.
- Your country and flag (from version 0.9.15). You may choose a country in Profile from a list, or “No country”. The phone’s region is only offered as a suggestion, and nothing is saved until you tap one. At online tables the other players see its flag on your seat. The server checks the code against the list of countries and holds it in memory only while you are at a table. It is not your location: the app uses no location services.
- Block keys (from version 0.9.15). The other players’ phones know your seat by a 16-digit key that the server makes by hashing your random seat key; the seat key itself never leaves the server. The key is not linked to your device’s identifiers or to an account, and a reinstall gives you a new one.
- Report and Block (from version 0.9.15). Tapping another person’s seat at an online table offers Report and Block. A report picks one of four fixed reasons (no free text) and writes one line to the match server’s log in Google Cloud Logging: the reason, the table, the game, both seats, both players’ nicknames (which other players never see), both players’ block keys, and the reported player’s country and photo link, if any. It is kept for 30 days, Google’s default, and we read reports to act on abuse. A report about a photo also records the reported player’s photo link and an identifier of their account, so that we can act on it; these are kept with the report for 30 days. At most 20 reports an hour are taken from one network address, and one per player, table and seat. Block keeps that player’s key and seat name on your phone (and in the optional cloud copy); from then on they show as “Player N” with no flag or photo, and the app sends your blocked keys when you join so the public queue can try not to seat you together (tables joined by a code, and tournaments, ignore blocks). Profile then Blocked players unblocks. If the player you block shares their photo, the block also remembers a key our server derives from their account (a one-way hash), so the block holds even if they reinstall the app.
- Photos at online tables. If you are signed in with Google, Facebook or Google Play Games and wear your account photo, the app asks you once whether to show it to the players at your online tables, and you can change your answer in Profile at any time. While you share it, each time you join a table the app sends our match server a sign-in token from Firebase Authentication over an encrypted connection. The server checks the token against Google’s published keys, takes only the link to your account photo that the token names (and only when it belongs to one of your own sign-ins), keeps it in memory while you are connected, and passes it to the players at your table. Their phones load the picture from Google or Facebook, at most 256 KB, and do not store it. The token itself is not stored. Apple and Game Center give no photo. If you do not share your photo, no token or photo link is sent.
- Tournaments (from version 0.9.15). Eight places over two rounds, with labelled bots filling empty places. Entry is paid in coins and the top places win coins; coins are earned only, have no cash value and cannot be transferred or cashed out. The server holds a tournament in memory until it ends and writes nothing; your phone records the entry. Nothing is collected beyond online play’s nickname, seat key and moves.
- How many are online (from version 0.9.15). The lobby asks the match server how many people are playing online, at most every five minutes while the lobby is open. The request carries no identifier.
- What other players see. Your seat and your play. Other people at the table see you only as a seat number (“Player 2”, “Player 3”), never by your nickname; the nickname is used only to show you your own seat. Bots keep their bot names. If names are shown at some tables later, the server will mask rude words in them and this policy will say so first. Your nickname does not have to be your real name, and we recommend it is not.
- Inviting friends (from version 0.9.14). When you make a private table
you can invite friends over WhatsApp: the app opens WhatsApp with a ready
message, and you choose whether to send it. Taash Adda sends nothing to
WhatsApp or Meta itself. The message carries the table’s code and a link,
https://taashadda-24.web.app/join/<game>/<code>. On a phone with Taash Adda the link opens the app at that table. Anywhere else it opens a small page on the game’s own hosting (Google’s Firebase Hosting) that reads the game and the code from the address and offers to open the app or the stores. The page sets no cookies, runs no analytics and loads no scripts from anywhere else; Firebase Hosting keeps standard request logs (IP address and time), as it does for any page. On Android the Google Play link carries the table and the word “invite”, so the app’s first launch after installing can offer that table and analytics (§8) can count the install as one that came from an invite; on iPhone the App Store link carries only a campaign label (“table_invite”). - The server does not send you another player’s cards. Redaction happens before anything is transmitted, not in the client.
- What the server keeps. Tables live in the server’s memory for the length of the match, so a disconnected player can rejoin the hand they left. Nothing about a match is written to a database or a file; the only lines written are the reports above. Google Cloud’s request logs record each connection’s IP address and time, kept for 30 days by Google’s default, for security and to prevent abuse.
- Bots fill empty seats and are always labelled as bots.
6. Chat
There is no chat between players: the match server drops every chat message. This policy will be updated before chat is switched on. If it is, the server will send chat only to app versions that can report and block (0.9.15 and later), and never a blocked player’s lines to whoever blocked them.
7. Advertising
Ads are served by Google AdMob, on Android and, from version 0.9.1, on iPhone, in the same places.
- Banner ads appear in a strip with its own space along the bottom of the lobby and the results screen (from version 0.9.2), and inside the scorecard and the quit-confirmation dialog. 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.
- A sponsored card in the lobby (from version 0.9.11): one card in the game carousel, after the third game, can show an ad marked “Ad”. Where no ad fills it, it shows the app’s own Adda Pass card.
- Full-screen ads are an interstitial at a break: once a hand’s scorecard has been closed and before the next deal (from version 0.9.2), or at a match boundary (when you abandon a match, or on the way back to the lobby after finishing one). From version 0.9.15 the match-boundary ad comes as a match starts instead, between the lobby and the table: before every online match, and offline after the day’s first two matches (all games together). While that is on, the ad on the way back to the lobby is off, except for holders of One Game, Any 3 Games or a Day Pass, who keep it as before; a plan or pass starts matches without the ad before them. Never mid-hand, never during a deal, a call, a tutorial or a lesson. How often they come is set remotely and can change.
- Rewarded ads run only when you choose to watch one: for a hint at a table or in Solitaire (the Hint button shows a video mark when the next hint is an ad), for coins or extra matches, or, from version 0.9.15, watched ahead in the Store (up to 50 a day) to skip the ad before one match.
- The Adda Pass removes the forced ads: the full-screen ads, the banners and the lobby card. Ads that pay out stay your choice.
- Mediation (versions 0.9.11 to 0.9.14 only). From version 0.9.15 Google AdMob alone serves the ads. In versions 0.9.11 to 0.9.14 AdMob could let other ad networks bid to show an ad: Unity Ads, Meta Audience Network, InMobi and Liftoff Monetize (Vungle). When one of them supplies an ad, its software in the app may process the advertising identifier (on iPhone only if you allow tracking), your IP address and the approximate location derived from it, device and app information, and how you interact with the ad, to select, measure and protect ads against fraud, under that network’s own privacy policy: Unity, Meta, InMobi, Liftoff. The consent you give or refuse in Google’s form, and your answer to Apple’s tracking prompt, apply to them too. On Android those versions remove the location permissions the networks’ software declares, so no ad network gets your precise location; the game itself never asks for it.
- On iPhone, ads appear in the same places as on Android. Ads on iPhone are limited to general-audience content.
- AdMob may use a device advertising identifier to limit repetition and measure performance. On Android you can reset or delete that identifier in Android Settings → Privacy → Ads.
- On iPhone, once, on first launch, after the consent check and before any ad, the app shows Apple’s App Tracking Transparency prompt. If you allow tracking, the ads use the advertising identifier for more relevant ads; if you do not, ads are not personalised and the identifier is not read. The game plays the same either way, and you can change your answer in iOS Settings → Privacy & Security → Tracking.
- 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, and on iPhone from version 0.9.1, the app uses Google Firebase for:
-
Analytics: which screens are opened and which games are played, in aggregate, what each ad impression paid, the plan events of §2; and, if you use the optional account, that you signed in, signed out or deleted it, with the provider’s name only. 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 (Firebase Crashlytics): when the app crashes or records an error it sends a stack trace, the device model, the OS version and the app version; no game content, no names. Like Analytics, it is off until the ads consent check allows it. It has been in the Android app since version 0.8.6 and is in the iPhone app from 0.9.1.
-
Notifications (from version 0.9.15), two switches in Settings. Reminders (a chest ready, a streak) are scheduled on the phone itself and send nothing anywhere. News from us uses Firebase Cloud Messaging and is off until you switch it on: only then does the app create a Firebase messaging token and subscribe the phone to a news topic for its platform, and switching it off deletes the token. The app asks about reminders only after a finished match, and your phone’s own prompt follows only a yes.
Firebase also gives the app an installation id, a random id per install that is reset by uninstalling, and it goes with every Analytics, Crashlytics and Remote Config request.
The iPhone app uses all three from version 0.9.1, under the same consent switch; version 0.9.0 and earlier used none of them.
Firebase’s privacy information: https://firebase.google.com/support/privacy
9. Plans and payments
From version 0.9.11 the app sells, on Android and iPhone:
- Subscriptions that renew automatically until you cancel them: One Game (one paid game of your choice), Any 3 Games (three of your choice) and the Adda Pass (every game, no forced ads, hints without ads).
- A one-time Day Pass: one paid game for 24 hours, bought with money or with earned coins.
Plans are sold only through Google Play and the App Store, which show the prices and take the payment. We never receive your card, bank or UPI details. The app receives the store’s confirmation of what your store account owns and keeps on your phone which plan you hold, the games you chose and the ids of purchases already applied (§3), so a purchase is applied once and can be restored. Nothing about your purchases is sent to any server of ours. Subscriptions are cancelled in Google Play or in your Apple Account settings, and the app links to both.
Coins are earned in play and cannot be purchased, transferred or cashed out. No plan adds coins.
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
Unless you sign in, there is 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: on Android, reset or delete it in Android Settings → Privacy → Ads. On iPhone, the app reads it only if you allow tracking; change that in iOS Settings → Privacy & Security → Tracking. Where a regulation gives you a choice about personalised ads, Settings → Privacy choices inside the app reopens Google’s form, on both.
- Analytics: 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.
- Your account and its cloud copy (if you signed in): tap Delete account in the app’s Profile pane. It removes the cloud copy and then the account at once; the progress on your phone stays. If you cannot open the app, email us (§15) from the address you signed in with, and we will delete the account and its cloud copy within 30 days.
- Uninstalling does not delete an account, and it does not cancel a subscription. Delete the account as above, and cancel a subscription in Google Play or your Apple Account settings.
- Online tables: the server keeps nothing after a match ends; the connection logs and any report go after 30 days. To ask about a report, email us (§15).
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 |
| Online tables | in the match server’s memory for the length of the match |
| Connection logs (IP address and time) | 30 days, Google Cloud’s default |
| Reports of a player at an online table (from version 0.9.15) | 30 days in Google Cloud Logging, Google’s default |
| Account and its cloud copy of your progress | until you delete your account |
| Purchase records | kept by Google Play or Apple under their own terms; the app’s record is on your phone |
| 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 each cloud copy only by its own account.
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