Data Safety
Declaration
Vintorava: Block Routing · Android
Last updated: 3 November 2026.
This is the developer's public explanation of app data handling. Read it with the Privacy Policy and the Data safety panel of the version offered on Google Play. This webpage is not a Google approval certificate or submission of the Play Console form.
Offline play and your choice
Progress, boards, preferences, history, balances and entitlements are stored locally for core puzzle gameplay. No Vintorava account is required. Local storage is not automatically an upload to our gameplay server.
Optional Firebase Analytics, Crashlytics reporting and Google Ads campaign measurement stay off until saved in-app acceptance. Refusal does not restrict gameplay. Review or withdraw your choice in Settings. Advertising personalization remains denied. Website cookie choices never authorize app reporting.
Data categories and purposes
App activity and interactions
With optional measurement accepted: screen categories, sessions and interaction metadata support usage analysis and improvement. Campaign measurement can attribute installations and purchase events. The manual screen event does not contain your full board history.
Device or other identifiers
Accepted Google/Firebase services can process app-instance, installation, session and permitted advertising identifiers for analytics, crash management and attribution. Omitting a personal user name does not make identifiers anonymous.
Approximate location
Accepted Analytics can derive an approximate area from network information. Core gameplay does not request precise GPS location; approximate area is a separate category.
App information, diagnostics and crashes
With reporting accepted: failure stacks/messages, native crash information, relevant app/device/operating-system state, installation/session identifiers and available activity breadcrumbs help investigate failures. Our added fields describe build, consent policy and screen category. Local first-party debug buffers are not automatically attached by the app bridge.
Purchase history and payment-related information
When you use an offered Google Play purchase or restore function, the platform processes transaction and payment information. The game uses product identifiers, purchase status and relevant tokens/entitlements to provide requested content or balances. Full payment-card details are not provided through its purchase interface. This processing is separate from optional Analytics; accepted Analytics may also process purchase-event metadata.
Support and website information
Support email includes your address and what you choose to send. Hosting processes ordinary connection/security data; the website stores essential preferences. These are separate from app telemetry and explained in the Privacy and Cookie Policies.
Recipients and sharing
Data for these functions is transmitted to relevant Google/Firebase, Google Ads or Google Play services. Hosting and email use Namecheap and Google/Gmail. Platform or billing diagnostics may be processed independently of the optional-reporting switch.
Google Play distinguishes collection, sharing, service-provider processing and user-initiated transfers. A technical transfer does not by itself establish a store-checkbox exemption. We do not claim that no data leaves the device, every transfer is anonymous or one consent switch controls all Google services.
Protection, retention and deletion requests
Website and Google/Firebase service connections use encryption in transit. Data follows the local-storage, service-retention and support/transaction criteria in the Privacy Policy.
Withdrawal blocks further optional reporting through the app's controls and requests cleanup of unsent reports. It does not recall in-flight transfers or automatically erase previously received reports. There is no Vintorava account or in-game cloud-erasure button.
Contact 2marcin56@gmail.com for access or deletion requests. Limited information may be needed to identify records. Do not start by sending passwords, purchase tokens, identity documents or complete private logs.
Developer
Marcin Matysek · developer name: rewerantor.
Contact & support · Full Privacy Policy · Website Cookie Policy.