The game
Runway Grove works without a player account. The installed game can be played offline; optional advertising, crash reporting and gameplay analytics on Android use an internet connection. The browser version needs a connection to download its files from this website and does not include AdMob, Firebase Crashlytics or Google Analytics.
We do not operate a player-profile database or a cloud-save service. The game does not include in-app purchases. Android version 0.13.0 (21) and later offers optional Google Analytics for Firebase; earlier Android versions do not include gameplay analytics. Your saved airport is not uploaded to us. Android advertising and optional technical reports are described separately below; turning off crash reports does not control Google's advertising-related processing.
Progress stays on your device
The game stores completed and unlocked flights, star results, coins, airport facilities and service research, career experience, the current flight or shift (including crew choices), and preferences such as language, sound and animations locally on your device.
These saves make it possible to resume a flight and keep your progress between sessions. In the installed game, they remain until you clear the app’s data, remove the saved files, or your device removes them. Removing the app can also remove its local data.
The browser version uses local browser storage for this website’s origin, games.corehive.org. Saves are separate for each browser profile and are not synchronized with the installed game or other devices. Private browsing, clearing site data or browser storage cleanup can remove them.
Sphere Games does not have a remote copy to restore after local progress is deleted.
Optional rewarded ads on Android
The Android version supports Google AdMob rewarded ads. You choose whether to watch an available ad for the reward described on its button. Ads do not appear automatically during play, and retrying a shift remains free. Once advertising requests are allowed, the game may preload an ad at startup or between views so it is ready when requested. Google can therefore process advertising data before you choose to watch. Rewarded ads may be unavailable because of your connection, privacy choices or ad availability.
Google's advertising SDK can process IP addresses, which may indicate approximate location, device or account identifiers, interactions and diagnostic information to provide and measure advertising and prevent fraud. This processing is separate from the optional Firebase crash-reporting setting. We do not add a player name, email address or a saved airport to advertising requests.
The game requests restricted advertising treatment for everyone and does not ask for your age. This disables personalized advertising and remarketing; Google's documented protections also disable requests to third-party advertising vendors and transmission of the Android advertising ID. Other SDK data processing described above still applies. The game checks advertising eligibility at launch before requesting ads. With this restriction, Google's consent system does not ask you for advertising consent. You can open Ad privacy choices from the game's privacy settings if Google requires that option. Ordinary play and free retries remain available without watching ads.
For Google's handling and retention of information, see Google's Privacy Policy and the Mobile Ads SDK data disclosure, together with its restricted advertising treatment. Android also offers advertising ID controls in device settings.
Optional crash reports on Android
Crash reports are off by default. You can enable them in the game's privacy settings to help us investigate technical failures using Firebase Crashlytics. Reports can contain crash traces, the app version, device and operating-system information, installation identifiers and limited technical context. We do not attach your name, email, saved airport or a custom player identifier, or enable gameplay analytics through the crash-reporting choice. If you separately enable gameplay analytics and crash reporting, Crashlytics can include recent Analytics events as breadcrumbs to help diagnose a crash.
You can turn reports off again in settings. The change takes effect the next time you start the game, as the settings notice explains. Reports may still be sent during the current run. At the next launch with reports turned off, the game asks Firebase to delete unsent reports stored on the device. This does not delete reports already sent. Crashlytics may store technical information locally before it is sent or discarded. Firebase's installation and session components also support crash reporting and app stability metrics.
Reports are used to diagnose faults and improve reliability. Google's data handling is described in Firebase Privacy and Security and its Crashlytics data disclosure. Contact us below with questions about information already sent; we do not maintain a player account that can be used to look up every report.
Optional gameplay analytics on Android
Gameplay analytics is off by default in Android version 0.13.0 (21) and later. In Settings → Privacy, an explanation appears before you choose Enable analytics or Not now. This is separate from crash reporting and advertising choices. Declining does not restrict play.
If enabled, Google Analytics for Firebase helps us understand game use and improve it. Events describe starting or completing campaign shifts, introductory play, opening help, using hints, and actual optional rewarded-ad presentation and completion. Game events contain a bounded shift number where relevant. We do not attach your saved airport, routes, free-form text, name, email or a user ID.
The SDK also processes automatic app and session events, app/version and device information, an app-instance identifier and network information used to deliver the service and derive approximate location. This data is not anonymous. Analytics advertising-ID collection is disabled, and Analytics advertising storage, advertising user data and ad personalization consent remain denied. These Analytics controls do not disable the separate advertising SDK described above.
Turning analytics off immediately blocks new game events, disables SDK collection, denies Analytics storage and resets Analytics data on this device, including its app-instance identifier. Events that occurred while analytics was off are not backfilled by the game. This local reset does not delete data already sent to Google. If the game reports a preference-saving error, collection is stopped for the current run; retry saving the choice so it persists after restart.
Google processes Analytics information under its Privacy Policy and the Google Analytics terms described by Firebase. Server retention and available deletion controls depend on the Analytics service and property settings, not the local switch. See Analytics data retention and Analytics SDK data disclosure. For questions or requests about information already sent, contact games@corehive.org; the game has no player account for locating every event.
Optional Google Play reviews
Android version 0.13.0 (21) and later may request Google's standard in-app review flow after several sessions and completed shifts. Session, foreground-time and progress counters used to limit these requests stay on the device. Google Play handles ratings and reviews under its own policies. The game does not read your rating, know whether you submitted a review, or offer a reward for reviewing.
Website hosting
Cloudflare delivers and protects this website. When you visit, routine technical information such as your IP address, requested address, browser information and request or security records may be processed to deliver the pages and keep the service working securely.
Cloudflare’s handling of this information is described in its Privacy Policy, including its international processing and retention practices.
We have not added advertising scripts, website analytics, tracking cookies or embedded third-party media to these pages. The site’s images, styles and font are served from this website.
Information you send to support
If you contact games@corehive.org, we receive your email address, message and any attachments you choose to send. We use this information to answer your request and investigate reported problems.
Support correspondence is retained for handling the request and necessary follow-up. Please share only what is relevant and remove unrelated personal information from screenshots or recordings. We do not need passwords or payment information.
Control and deletion
On Android, use the game's privacy settings to change optional crash reporting, change gameplay analytics in version 0.13.0 (21) and later, and reopen advertising choices when available. These controls are separate. You can continue playing without enabling analytics or crash reports, or watching a rewarded ad.
To remove local game data on Android, use the device’s app settings to clear Runway Grove’s storage. To remove browser saves, clear site data for games.corehive.org in your browser settings. This can also remove local saves for other games hosted on the same website.
Clearing local game data resets progress, coins, decorations and preferences. It does not delete messages you have already sent to support or information already processed by Google or the website's hosting provider.
For questions or requests concerning support correspondence or other information you have shared with Sphere Games, email games@corehive.org. Tell us which message or issue your request concerns without including sensitive account details.
The service providers' available privacy controls and retention practices are described in the policies linked above.
Changes to this policy
We will update this page if Runway Grove’s data practices change and revise the date at the top. You can contact games@corehive.org with questions about the current policy.