Effective Date: August 23, 2026
This Privacy Policy explains how GridRail: Train Dispatcher (“the Game”, “we”, “our”, or “us”) handles information when you use the mobile game.
GridRail: Train Dispatcher is an offline-focused puzzle/strategy game in which players control railway junctions, route trains to matching stations, avoid collisions, and attempt to achieve higher scores.
We designed the Game to minimize the collection of personal information. The Game does not require users to create an account, provide their name, email address, phone number, physical address, or other personal information in order to play.
We do not directly collect personal information through the Game.
The Game does not provide user-registration, account creation, social networking, messaging, chat, or user-profile functionality.
The game itself does not request access to:
Contacts
Camera
Microphone
Photos or media
Location
Phone/SMS
Calendar
Bluetooth
Files or storage permissions requiring user authorization
The Game stores certain gameplay statistics locally on the user's device.
These include:
Best score
Lifetime number of trains successfully routed
These values are stored using Flutter's shared_preferences package and are used to preserve gameplay statistics between sessions.
The relevant implementation retrieves locally stored values such as best_score and lifetime_trains when the game starts.
The Game does not upload these statistics to our own servers.
During a game session, the Game maintains temporary gameplay information such as:
Current score
Combo chain
Active trains
Train positions
Train colors
Junction directions
Current game tick
Number of trains routed during the current session
Collision location
This information is required for the game engine to operate.
The Game uses these values to calculate scores, detect collisions, process station arrivals, and control train movement.
Gameplay-session information is not submitted to a developer-operated server.
GridRail generates its daily board using the current date.
The game creates a deterministic seed from the year, month, and day and uses that seed to generate the day's junction configuration and station positions.
The Game therefore uses the device's current date/time locally for gameplay generation.
This does not mean that the Game collects or transmits the user's location. The implementation does not request location permission or use a location API.
After a collision, the Game provides an optional “Copy Crash Log” function.
If the user chooses this function, the Game places a generated gameplay summary into the device clipboard.
The generated text contains gameplay information such as:
Number of trains routed
The collision junction
Score achieved
The Game does not automatically transmit this crash log to the developer.
The clipboard action occurs only when the user explicitly selects the copy function.
Users should remember that copied information may remain available in the device clipboard according to the device operating system's clipboard behavior.
The Game includes functionality to check for an available update through the Google Play in-app update mechanism.
The implementation calls the in_app_update package to check whether an update is available and, when appropriate, requests the Google Play update flow.
This functionality is provided through Google Play's update infrastructure.
The developer does not use the Game's own server to collect personal information through this feature.
Google may process information in accordance with Google's own privacy policies and the services required to provide Google Play functionality.
The Game uses the following relevant software components:
Flutter / Flutter SDK
The Game is developed using Flutter.
Shared Preferences
Used for locally storing gameplay statistics such as the best score and lifetime trains routed.
Google Fonts
The Game uses the Poppins typeface through the google_fonts Flutter package.
In-App Update
The Game uses the in_app_update Flutter package to check for and initiate Google Play application updates.
The Game does not implement its own advertising SDK, analytics SDK, social-login SDK, or third-party user-tracking system in the supplied source code.
The supplied implementation does not contain an advertising SDK or advertising functionality.
There are no advertisements displayed by the game code provided for review.
The supplied implementation does not contain an analytics or behavioral-tracking SDK.
The Game does not implement functionality to create an advertising profile or track users across other applications or websites.
GridRail: Train Dispatcher does not require an account.
Users can start and play the game without registering with the developer.
No developer-operated username, password, email account, or user profile is created by the Game.
GridRail: Train Dispatcher does not knowingly request personal information from children.
Because the Game does not require registration and does not provide chat, messaging, social networking, or user-generated-content features, it is designed to minimize exposure to personal-data collection.
Parents and guardians should nevertheless supervise children's use of mobile devices and applications according to their own preferences and applicable requirements.
Because the Game does not operate a developer-controlled account or backend system for player data, the developer does not maintain a central database of player information through the Game.
Locally stored gameplay statistics are maintained by the application on the user's device.
Users should understand that no electronic storage system can be guaranteed to be completely secure, and device-level security depends partly on the user's operating system and device configuration.
We do not sell, rent, or trade users' personal information.
The Game does not provide a developer-operated mechanism for sharing player gameplay statistics with third parties.
Certain technical interactions may occur through platform services required to operate Android/Google Play functionality, such as application update services. Those services are operated according to the respective platform provider's terms and privacy practices.
The Game retains locally stored gameplay statistics until:
The user clears the application's data;
The application is uninstalled;
The application overwrites or resets the relevant values; or
The operating system removes the application's stored data.
The developer does not maintain a separate server-side copy of these statistics based on the supplied implementation.
Because the Game does not maintain a developer-operated account containing personal information, there is no separate online account deletion process.
Users can remove locally stored Game data using the Android device's application settings, where supported.
Uninstalling the Game also removes its application data according to normal Android behavior, subject to the device and operating system.
We do not intentionally collect personal information from children through the Game.
If a parent or guardian believes that personal information has been provided to us in connection with the Game, they may contact us using the contact information provided below.
We may update this Privacy Policy when the Game's functionality, services, or applicable legal requirements change.
When changes are made, the updated policy will be published with a revised effective date.
Users are encouraged to review the Privacy Policy periodically.
If you have questions, concerns, or requests regarding this Privacy Policy or KinetiPush: Block Puzzle, please contact the developer through the support contact information provided on the application's Google Play listing.