dreamcatcher app reference: store listings, permissions and updates.
A working reference for adult readers who want to install a rummy app on iOS or Android. The page walks the two official stores, the package-name verification step, the permission requests to scrutinise and the update behaviour to expect.
The two official stores
Apple App Store
Open the App Store, search for the platform by name, and verify the developer name in the listing matches the platform published developer. Apple reviews every submission before listing, which reduces but does not eliminate risk.
Google Play Store
Open the Play Store, search for the platform by name, and verify the developer name and the package name. The package name is a unique identifier; a typo in the package name is the most common sign of an impersonator app.
Permission requests to scrutinise
Network access
Required. The app must talk to the platform servers to load games and process transactions.
Camera
Conditional. Used for KYC document upload. Should be in-app, not background.
SMS or contacts
Refuse. No skill-game app needs SMS or contacts access.
Accessibility service
Refuse. No skill-game app needs accessibility service access. Apps asking for it are reading the screen.
Device admin
Refuse. No skill-game app needs device admin. Apps asking for it can lock the device or wipe data.
Update behaviour
Auto-update on
Default for store-installed apps. The Play Store or App Store applies updates in the background. Disable auto-update only if you want to review the release notes of each update before applying.
Pin a sideloaded version
If you installed the app from outside the official stores, pin the version number on a sticky note. Each time the platform publishes a new version on its official site, download the new APK, verify the package name, then install over the existing version.
How a rummy platform's app reaches a reader.
Most rummy platforms distribute their app through two channels: the official app stores and the platform's own APK. The two channels carry different trust signals. The desk walks through the four checks a reader makes before installing from either channel.
App store installation
Search the official app store for the platform's published company name. Read the publisher field on the app store listing; the publisher should match the platform's published company name. Read the app's data-handling disclosure; the disclosure should name the categories of data the app collects.
APK installation
Where a platform distributes an APK directly, the APK URL should sit on the platform's registered domain. Compare the APK URL to the home URL; both should sit on the same registered domain. An APK URL that points to a third-party host is a warning sign.
Version policy
Most platforms publish a minimum-version policy on the platform's own page. The platform deprecates old versions on a published schedule. Where the reader's installed version is below the minimum, the platform asks the reader to update before the next login.
Mobile permissions
The app should request only the permissions the platform's product needs: camera (KYC document capture), network (table connectivity), storage (KYC document storage on the device). Where the app requests permissions the product does not need — contacts, microphone, location — the desk recommends the reader decline the permission.
What the desk does not publish
The desk does not publish app-store ratings, install counts or download links not already published by the platform itself. Where the reader wants to verify an app-store rating, the desk directs the reader to the platform's app-store listing.
Why side-loading carries a higher risk than the official app store.
App store review
Apps distributed through the official app stores go through a review process that includes a malware scan and a permissions audit. Apps distributed through a side-loaded APK do not go through the same review process; the APK is delivered as published by the platform.
Updates
App store apps update automatically via the app store's update channel. Side-loaded APKs require the reader to download and install each update manually. Where a reader misses an update, the APK falls behind the platform's minimum-version policy.
Device trust
Android asks the reader to confirm "install from unknown source" before installing a side-loaded APK. The reader should enable the setting only for the duration of the install; the reader should disable the setting again after the install is complete.
What the desk recommends
The desk recommends installing from the official app store wherever the app store carries the platform's app. The desk recommends side-loading only where the platform publishes the APK on the platform's own domain and the reader trusts the platform's domain. The desk does not recommend side-loading from a third-party APK host.
What the reader should know about a rummy platform's mobile app.
Mobile permissions
The mobile app should request only the permissions the product needs: camera (KYC document capture), network (table connectivity), storage (KYC document storage on the device). Where the app requests permissions the product does not need — contacts, microphone, location — the desk recommends the reader decline the permission.
Mobile data handling
The mobile app should publish a data-handling disclosure on the app store. The disclosure should name the categories of data the app collects. Where the disclosure does not name the categories, the desk recommends the reader contact the platform's data-handling inbox before installing.
Mobile notifications
The mobile app sends push notifications for table invitations, withdrawal status updates and responsible-play prompts. The reader can disable notifications at the operating-system level without losing access to the platform. The reader can also disable category-by-category notifications inside the app's settings.
Mobile battery and data
The mobile app runs in the foreground while the reader is at a table; the app uses network bandwidth for table connectivity and battery for the foreground process. The reader should close the app when the reader steps away from a table; the platform's session-time prompt is the platform's reminder to the reader.
What the desk does not recommend
The desk does not recommend installing a mobile app from a third-party APK host. The desk does not recommend granting permissions the product does not need. The desk does not recommend leaving the app open while the reader is not at a table. The desk publishes these recommendations on this page so the reader can decide.
The settings a reader reviews before the first session.
Notification settings
The reader reviews the notification settings before the first session. The reader disables categories the reader does not want to receive — for example, marketing notifications or table invitations from unknown players. The reader enables categories the reader does want to receive — for example, withdrawal status updates and responsible-play prompts.
Security settings
The reader enables two-factor authentication on the platform's security settings page. The reader sets a strong password that the reader does not reuse on any other site. The reader enables biometric login if the reader's device supports it. The reader does not save the password on a shared device.
Responsible-play settings
The reader sets a daily deposit cap, a session-time prompt and a weekly cool-off period before the first session. The reader sets the controls on the platform's responsible-play tab. The reader reviews the controls at the start of every quarter to confirm the controls still match the reader's budget.
Table settings
The reader sets a default table stake that fits the reader's daily deposit cap. The reader sets a default format — Points, Pool, Deals — that the reader wants to play. The reader reviews the table settings before the first session so the reader does not join a table that exceeds the reader's budget.
How to read this app reference.
The reference above walks through the four checks a reader makes before installing a rummy platform's app, the side-loading considerations a reader weighs before installing an APK, and the version policy the platform publishes. Verify each step before you install on any device.
How the desk handles an app question
The desk reads app questions sent to the editorial email. The desk does not host the app; the desk directs the reader to the platform's own published install page and to the official app store listing. Where the reader has a specific complaint about an app's behaviour, the desk directs the reader to the platform's support channel.
How the desk handles an app-store impersonation
Where the desk becomes aware of an impersonation on an app store, the desk reads the report sent to the editorial email. The desk does not host the impersonated app; the desk directs the reader to the app store's abuse-reporting channel and to the CERT-In incident reporting portal.
Three pages that complete the picture.
The rules ledger, the safety explainer and the responsible-play framework.