Rummy Score Card privacy policy
This privacy policy is intended for the current Rummy Score Card Android app build, where score data is stored locally on the device and no account, analytics, advertising SDK, or in-app purchase flow is included at this time.
Scope of this privacy policy
This policy applies to the Rummy Score Card mobile app, its Google Play listing, and related support communication operated by TechRex. It is intended to explain what data stays on the device, what data may be handled by third-party mobile services used in the app, and how users can understand the app’s privacy practices.
No login required
Rummy Score Card does not require account creation or user login to use the core score tracking features.
Game data stored locally on the device
Player names, round scores, drop-related entries, and other scorecard information entered by the user are intended to remain stored locally on the device as part of the app’s core score-tracking functionality. Based on the current product model, this local game data is not intended to be sent to TechRex servers for scorekeeping.
What users may enter into the app
Users may enter player names, round scores, drop-related values, and other game-tracking details needed to manage a local scorecard. This information is entered solely for scorekeeping and is not intended as a profile or account system.
Current build status
The current app build is a local-only scorekeeping utility. It does not include user accounts, server-side sync, analytics SDKs, crash-reporting SDKs, advertising SDKs, or in-app purchase flows at this time.
What TechRex does not use score data for
TechRex does not intend to use locally stored scorecard entries to identify users, build customer profiles, sell user data, or operate a cloud gameplay history for the current version of the app. The score-tracking feature is designed as a local utility and not as a social, account-based, or server-synced gaming service.
Advertising in the free version
The current app build does not include advertising SDKs and is not intended to transmit scorekeeping data off-device for ad delivery. If advertising is introduced in a future version, this policy and the Google Play Data Safety section should be updated before that version is published.
In-app purchases and premium features
The current app build does not include in-app purchases or premium billing flows. If premium features are introduced later through Google Play Billing or a similar purchase mechanism, this policy and the Google Play Data Safety section should be updated before release.
Third-party services and SDKs
The app may rely on third-party mobile services such as advertising SDKs, analytics tools, crash-reporting tools, or Google Play billing components. Under Google Play policy, data collected or handled through third-party SDKs used in the app must also be reflected in the app’s privacy disclosures and Data safety declarations where applicable.
How data may be used
Local score data is used to operate the scorecard features chosen by the user. Third-party advertising, billing, analytics, or technical service providers may use data for purposes such as ad delivery, ad measurement, purchase processing, fraud prevention, security, diagnostics, or service improvement, depending on the SDKs and services included in the released app build.
Data sharing and sale
TechRex does not sell personal data. However, if advertising or measurement SDKs are included in the app, those providers may receive data from the app or device in connection with ad serving, analytics, fraud prevention, or related services. Your Google Play Data safety disclosures should be kept consistent with the actual SDKs and app behavior included in the published build.
Google Play Data Safety summary
Based on the current app build, scorekeeping data remains on the device and is not collected by TechRex for cloud processing. Because the current build does not include ads, analytics, crash reporting, account systems, or billing-related SDKs, the Google Play Data Safety answers for this version should be based on a local-only utility app. The exact Play Console answers must still match the final APK or AAB shipped to users.
Practical disclosure summary
In practical terms, the current app is designed as a local-only scorekeeping utility with no login, no server sync, and no third-party analytics or advertising SDKs. Users should read both the Play Store Data Safety section and this privacy policy together, because the exact disclosures must match the final released Android build.
Security and retention
Because gameplay score data is intended to remain on the device, retention of that local data is generally controlled by the user’s own device, app lifecycle, backup settings, and deletion choices. Any server-side or third-party data handling for ads, purchases, diagnostics, or analytics will depend on the services actually used in the released app. We use reasonable efforts to choose and operate services responsibly, but no system can guarantee absolute security.
Children and audience
Rummy Score Card is not intended for children as a child-directed app. If you target children or families in the future, the app, its SDK choices, and its disclosures should be reviewed separately against the relevant Google Play Families requirements before publication.
User choices, deletion, and support
Users can generally remove locally stored score data by clearing app data, uninstalling the app, or using any in-app reset or delete controls that may be provided in the released version. For questions about this policy, support requests, or privacy-related concerns, users can contact support@techrex.in.
Policy updates and contact
This policy may be updated if the app’s features, advertising setup, in-app purchase model, analytics, data handling, or legal requirements change. The published privacy policy and Google Play Data safety disclosures should always match the actual released build as closely as possible. For privacy-related questions about the app, contact support@techrex.in.
For general company-level information, see the TechRex privacy policy.