Data safety
Data Safety Declaration
App: Express Pro Hexa Puzzle
Developer: Rewernator
Last updated: May 5, 2026
Overview
This Data Safety Declaration explains what data may be collected or processed when you use Express Pro Hexa Puzzle. We designed the app to minimize data collection and to avoid collecting sensitive personal information wherever possible.
Advertising
The app does not load or display third-party advertising. Rewarded ads, interstitial ads, banner ads, and app-open ads are disabled in the application logic. The app does not request advertising content from ad networks during gameplay.
In-App Purchases
The app may offer optional in-app purchases through Google Play Billing or Apple App Store payment systems. Payment processing is handled by Google or Apple. We do not receive or store your payment card number, bank account details, or full payment credentials.
For purchase reliability, the app may process limited purchase-related technical information such as: product identifier, store name, purchase status, validation result category, grant result category, and a hashed transaction deduplication key. Raw receipts, purchase tokens, order IDs, and full billing payloads are not logged to analytics, crash reports, or debug logs by our application code.
Analytics
The app may use Firebase / Google Analytics to understand general app usage, improve gameplay experience, diagnose feature performance, and measure technical events such as app start, shop screen opening, product viewing, purchase flow status, and economy-related events.
Analytics events are designed to avoid personal data. We do not intentionally send names, email addresses, raw purchase receipts, purchase tokens, order IDs, payment information, precise location, contacts, photos, messages, or similar sensitive personal data through analytics.
Analytics data may include app interaction events, device and app information, platform, app version, session-level identifiers, and approximate diagnostic context. Balance or economy values, where used, are reported only in broad buckets rather than exact values.
Crash Reporting
The app may use Firebase Crashlytics to collect crash reports and non-fatal error reports. This helps us identify, reproduce, and fix technical problems, especially issues related to in-app purchases, startup, store connectivity, validation, and entitlement granting.
Crash reports may include technical diagnostics such as device model, operating system version, app version, Unity version, stack trace, crash time, and safe custom keys. IAP-related crash reports use sanitized fields such as product alias, purchase flow step, safe error code, store name, validation category, and grant category.
Crash reports must not contain raw receipts, purchase tokens, order IDs, email addresses, full Google Play Billing payloads, full Apple StoreKit payloads, payment data, or secrets. The app uses sanitization, deduplication, and rate limiting to reduce the risk of sending sensitive or excessive diagnostic data.
Debug Logs
The app may produce Android Logcat / ADB logs for technical debugging. Production logs are limited. Debug-level logs are intended for development and testing builds. These logs are designed to avoid sensitive data and must not contain raw receipts, purchase tokens, order IDs, emails, payment data, or full store payloads.
Data We Do Not Collect
- Precise GPS location
- Contacts
- Photos, videos, or audio recordings
- Messages
- Health or fitness data
- Payment card or bank account details
- Email address, unless you contact us directly
- Raw purchase receipts, purchase tokens, or order IDs in telemetry
Data Sharing
We do not sell personal data. Limited technical data may be processed by service providers used by the app, including Firebase / Google services for analytics and crash reporting, and Google Play or Apple for in-app purchase processing. These providers process data according to their own privacy and security terms.
Data Security
We apply data minimization and telemetry sanitization practices. Purchase diagnostics are reported using safe categories and hashed identifiers where needed for deduplication. Sensitive purchase payloads are not intentionally stored or transmitted by our telemetry code.
Data Retention
Crash and analytics data are retained according to the retention settings of Firebase / Google services and our internal app diagnostics needs. Crash reports are used only for troubleshooting and app quality improvement. You may contact us to request additional information about data handling.
Your Choices
You can limit certain analytics or advertising identifiers through your device settings. You may also uninstall the app to stop further app data collection from your device. For purchase history and payment-related data, please refer to Google Play or Apple App Store account settings.
Contact
If you have questions about this Data Safety Declaration or our data practices, contact us at: [marcin.rewertyn@gmail.com].
Important Note
This declaration reflects the intended data behavior of the app implementation. If new SDKs, ads, backend services, account systems, push notifications, or additional analytics are added in the future, this declaration should be reviewed and updated before release.