Privacy Policy: Rummy House - Card Games

Effective date: 14 October 2026
Applies to: the Android app Rummy House - Card Games (com.lelobyte.ellibir). On the device it is listed as Rummy House, or under its local name: Rommé in German, Rummy clásico in Spanish and 51 in Turkish. The source build described here has advertising and purchases disabled; builds that enable them are covered by the relevant sections below.
Developer / contact: Altug Ataalp — ataalpaltug92@gmail.com

The short version

Rummy House has no developer account system, chat, or game server. Google services may process the technical, usage, nearby-peer, Play Games, purchase, and advertising data described below. The developer can see service-console reports but does not receive card details or build a named player profile.

The app integrates these Google services, depending on the feature being used:

1. Google Analytics for Firebase for consent-controlled usage measurement;
2. Google Play Games Services for optional sign-in, achievements and leaderboards;
3. Nearby Connections for local multiplayer over Bluetooth/Wi-Fi;
4. Google Play In-App Review for the occasional "rate this game" prompt;
5. Google Play Billing when the optional remove-ads purchase is enabled; and
6. Google AdMob when advertising is enabled.

They are described below. Consent categories start denied. The app does not infer analytics, user-data, or personalization consent merely because UMP says an ad request is permitted.

The developer operates no game backend. Some local preferences and progress may be restored by Android backup after reinstall. Play Games data stays in the signed-in Google account, and the app reads part of it back onto the device, as described under Play Games Services below.

What the app keeps on your device

A few small files in the app's private storage, which no other app can read. They hold:

• Your player name and your list of bot opponent names, as typed in Settings.
• Game settings — language, sound, vibration, animation speed, theme, table appearance and the optional house rules.
• Your progress — level, total EXP, wins, your current and best win streak, prestige, unlocked achievements and daily challenge progress.
• Your lifetime statistics — rounds and matches played and won, by game, table size and mode, your best scores, and the days you played.
• An unfinished match, stored as a validated local checkpoint and excluded from Android backup.
• The result of the last finished match, so its results screen can be opened again; also excluded from Android backup.
• Which win milestone the rating prompt was last shown at, so it is not shown again from the start.
• Purchase entitlement and pending acknowledgement state when billing is enabled; these are excluded from Android backup and rechecked with Google Play.
• Your consent answer, recorded by Google's consent SDK.

There is no address-book or photo access. On Android 12 and below, local multiplayer requests the legacy location permission Android requires for nearby discovery; the app does not read GPS or use that permission for tracking.

Ads

When enabled in a production build, ads are served by Google AdMob. The reviewed source build has monetization disabled and does not request ads or connect to Play Billing. An enabled build shows:

• a banner at the bottom of the menu, setup, settings, help, progress, lobby and results screens — never during a hand of cards;
• an occasional full-screen ad between matches: never the first one of a session, and at most one every few minutes.

To fill an ad slot, the AdMob SDK sends Google what an ad request is made of: your device's advertising ID, its IP address, the app and its version, and technical details such as device model, operating system version, language, screen size, and the coarse (city-level) location derived from the IP address. Google acts as an independent controller of that data; what it does with it is governed by its own policies:

• Google's advertising privacy terms: https://policies.google.com/technologies/partner-sites
• Google's ad technology providers: https://support.google.com/admob/answer/6128543

Ads are capped at Google's "T" (teen) content rating or lower.

The developer never sees this data, receives no report identifying you, and cannot connect an ad request to a player.

Analytics

Usage measurement is Google Analytics for Firebase, in the developer's Firebase project ellibir-f5342. It records:

• automatic events — first open, session start, app updates, and time spent in the app;
• screen views, named by screen (menu, setup, table, results, settings, and so on);
• three custom events:
  • match_start — the mode (single player, remote host or remote guest), the number of players, the difficulty of the hardest bot, and which game was chosen with the version of its rules;
  • match_end — the mode, the number of players, the game and its rules version, how many rounds were played, the place you finished in, and whether that was a win or a loss;
  • app_exit — sent on the next launch when the app's previous run ended in a crash or stopped responding (Android 11 and newer). It carries which of the two it was and, if you were at a table, that match's mode, number of players, game and rules version. It carries no crash log, no stack trace and none of the cards. Android keeps that short note about the open match on the device until the next launch reads it;
• two user properties — the game being played and the version of its rules, set while you are at a table and cleared when you leave it, so the events above can be compared between games.

Alongside those, the SDK sends a randomly generated app instance identifier, the device model and operating system, the app version, the language, and the coarse (country/region) location derived from the IP address.

None of it contains your name, the names you gave your bots, or the cards you were dealt. The random identifier and technical data can still be personal data under privacy law. It is used to see which features are used and where players stop playing — and it is not sold or shared with anyone beyond Google, which processes it for the service. Uploaded analytics is retained according to the Firebase console configuration; source code cannot prove that setting and this policy does not promise a specific duration.

The app instance identifier is not permanent, and you control it: Settings → Reset analytics ID throws it away and starts a new one that cannot be joined to the old. See Your rights, below.

Your consent, and how to change it

Where the GDPR or UK GDPR applies, the app shows Google's certified consent message on first launch and requests no ad and stores no analytics identifier until you have answered it. Until then all four consent categories — analytics storage, ad storage, ad user data and ad personalisation — start denied. That is the app's declared default, not something you have to switch off.

• If you consent, ads may be personalised according to the deployed consent message. Analytics storage remains denied unless the app obtains a separate affirmative analytics signal; the current build does not treat permission to request ads as that signal.
• If you refuse, the app works in full and still shows ads, but non-personalised ones: a request is still sent, because that is how any ad arrives at all, but it is not selected from a profile of you, and analytics keeps no identifier.

You can reopen the choice at any time in Settings → Ad privacy settings, which appears wherever a consent form exists for your region.

Independently of the app, Android lets you reset or delete the advertising ID itself, in *Settings → Privacy → Ads*. That stops personalised ads on the device for every app, not just this one.

What else leaves your device

Local multiplayer. A two-player match over Bluetooth or Wi-Fi uses Google Play services' Nearby Connections to talk directly to the other player's device in the same room. What crosses that link is:

• the player name you chose, which is also the name your device is found under while it is hosting or searching;
• if you host a table with bots, the bot names from your list that are seated at it;
• the rules of the match the host proposes, and the version of the app's connection protocol;
• the game in progress — the moves, and the part of the table and the scores each player is shown.

It goes to that one device and nowhere else. There is no relay server, no matchmaking service, and no copy kept by the developer. Nearby Connections is a part of Google Play services running on your device, and Google's privacy policy governs that service.

Play Games Services. Signing in is optional. Play Games may sign you in automatically when the app starts, or you can sign in from the Progress screen. While you are signed in:

• The app uploads the achievements you have unlocked and three leaderboard scores: matches won, your best win streak, and total EXP (one number that also counts your prestiges).
• The app downloads the same things from your Play Games account — its unlocked achievements and those three scores — and raises the progress on the device to match where the account is ahead. It never lowers anything. This is what brings trophies, level, prestige, wins and best streak back after a reinstall or on a new device.
• Play Games keeps the highest value it has seen, so progress made on two devices is not added together. Your current streak, daily challenges, detailed statistics and chosen cosmetics are not sent to Play Games and cannot be recovered from it.
• The device keeps one set of progress. If a different Google account signs in to Play Games on the same device, that progress is published to the new account, and the new account's achievements and scores are merged into the device in the same way.

The app does not read your Play Games name, picture or email address. Google controls the account identity, visibility, retention, and deletion tools.

Rating the game. After some wins the app may ask Google Play to show its rating prompt, and Settings can open the game's store page. Any rating or review you give goes to Google Play under your Google account; the app is not told whether you rated or what you wrote.

Sending feedback and telling a friend. Two rows under Settings → About hand you to another app, and neither sends anything by itself. Send feedback opens a draft in your own email app, addressed to the developer. Under the space for your message, the draft names the app's version, your Android version and the manufacturer and model of your phone. You can delete that line, and nothing is sent unless you send the email. If you do, the developer receives it as any email arrives — with your address — and uses it only to answer you and to fix the app. Tell a friend opens Android's share sheet with one sentence and a link to the game's store page. Who it goes to, and through which app, is your choice.

Android backup. The app allows Android's standard encrypted backup for settings, progress, achievements, daily-challenge data, lifetime statistics and the rating-prompt milestone, including the player name and bot names. Explicit rules leave out saved matches, the last match result, billing/acknowledgement state, and consent records. The developer cannot access the backup.

Nothing else leaves the device, and no data about you is sold to anyone.

Permissions and why they exist

About the location permissions: they are a legacy requirement of older Android versions for Bluetooth scanning. The app never requests your position, never reads GPS, and never stores or transmits a location. On Android 13 and newer they are not part of the app at all, and the scanning permissions it does use are declared neverForLocation.

Children

The app is not directed at children, and neither the developer nor the app builds a profile of anyone. It does carry ads and usage analytics, both of which involve the identifiers described above, and its ads are capped at Google's "T" content rating. If a child uses this app, ad personalisation can be limited further from the device's own Google settings and from the family controls on the Google account.

Purchases

When monetization is enabled, there is one optional product: Remove ads, a one-time purchase that turns off banner and between-match ads. There are no subscriptions. The reviewed source build has this purchase disabled.

The purchase is sold and processed by Google Play. Payment happens inside Play, not inside this app: the developer never receives, sees or stores your card details, billing address or name — only Play's record that the purchase exists. Whether you own it is kept on your device and re-checked with Play at each launch, which is also how it comes back after a reinstall or on a second device signed in to the same Google account.

Buying it stops all ad requests, and with them everything described under Ads above. The analytics described in this policy is unaffected and stays under the same consent.

Your rights (GDPR, KVKK, and similar laws)

The developer does not operate a user database, but may access aggregate or pseudonymous reports in Google service consoles. Rights concerning data processed by Google can also be exercised through Google's account/privacy controls; contact the developer for questions about the configured projects.

What you can do directly:

• Change your consent: Settings → Ad privacy settings, at any time. Withdrawing it stops personalised ads and analytics storage from that moment on.
• Reset the advertising ID: Android Settings → Privacy → Ads.
• Erase local data: use Android's Settings → Apps → Rummy House → Storage → Clear data (the app is listed under its local name where it has one). Uninstalling removes the installed copy, but Android backup may restore explicitly backed-up preferences and progress after reinstall unless that backup is also deleted.
• Manage Play Games data: use Play Games/Google Account privacy controls for achievements, leaderboards, profile, and game data associated with the signed-in account.
• Stop the backup copy: turn off device backup in Android's settings, or delete the app's backup from your Google account.
• Cut the analytics data loose from you: Settings → Reset analytics ID. This deletes the analytics data held on the device and issues a new app instance identifier, so everything recorded from that moment belongs to a fresh identity that cannot be joined to the previous one. Statistics already uploaded remain subject to the Firebase console's retention/deletion configuration; a local reset is not a deletion request for those server records.

A note on requesting erasure by email. What Firebase holds carries no name, no email address and no account — only that random identifier. The developer therefore cannot look you up, cannot tell which rows are yours, and would have to collect more data about you to try. Where a controller cannot identify the data subject, the GDPR does not require them to acquire further data purely to service a request (Art. 11), and the reset above is offered instead: it is immediate, it needs nothing from the developer, and it does not ask you to hand over an email address to exercise a privacy right. Write to the address below with any question about this, of course.

An email you chose to send through Send feedback sits in the developer's mailbox, and is deleted if you ask at the same address.

Questions and requests: ataalpaltug92@gmail.com. Residents of the EU/EEA and of Türkiye may also lodge a complaint with their national data protection authority (in Türkiye, the KVKK — Kişisel Verileri Koruma Kurumu).

Changes to this policy

A revised version is published at the same address with a new effective date and, where the change concerns how data is handled, noted in the app's release notes. This version is published before the first release carrying ads and analytics ships, and the Play Store listing's Data safety declaration is updated to match it.

Contact

Altug Ataalp
ataalpaltug92@gmail.com