Privacy — Atlas Games: Atlas Maze Asterion and Atlas Rift Runner

Last updated: 11 October 2026. 1. Scope and publisher This shared policy covers Atlas Maze Asterion and Atlas Rift Runner, two Atlas Games titles published by HRS Digital. The publisher’s identity and public contact details appear in the validated HRS Digital publisher profile and legal notices. For privacy questions or requests, use https://hrsdigital.net/contact?ui=en. Name the game and explain your request; never send passwords or payment card details. Each application has its own save files, settings and inventory. A shared policy does not create a shared account, automatic progress transfers, shared advertising consent or purchases valid in both games. 2. Local game data The current test versions require no account. Progress, virtual currencies, unlocked objects and destinations, settings, recorded purchases and a resumable game are stored in the application’s local storage on your device. This supports the game features you use, preserves your choices and prevents duplicate rewards. There is currently no service synchronising profiles between the games. Your operating system may back up device data according to your own settings; this is an Apple or Google feature. 3. Optional advertising and current versions The current testing releases use demonstration or test advertisements. Real-money purchases remain disabled. Test advertisements may still contact an advertising provider: test mode does not mean that no data is processed. Atlas Maze uses the Google Mobile Ads SDK and Google UMP to manage applicable privacy choices. Rewarded videos are optional. A bonus or aid is granted only after a validated reward; closing a video without earning its reward is insufficient. When advertising is enabled, the integration also provides spaced interstitials after certain completed games and a banner on result screens. Game settings allow advertising to be switched off; applicable Google privacy forms must remain accessible when required. Atlas Rift Runner uses Google Mobile Ads and Google UMP and is preparing Yandex advertising mediation. The current test configuration contains no production Yandex advertising identifiers and automatic Yandex initialisation is disabled. A birth month and year are stored locally to determine advertising access: the advertising SDK is not initialised for an unknown age or a player under 18. Yandex location tracking and advertising analytics reports are disabled and the Android AD_ID permission is removed. These precautions do not mean that no technical data is processed when a Google advertisement is requested. Depending on the platform, consent and services actually enabled, Google may process IP addresses, technical device and application information, permitted identifiers, advertising interactions and diagnostics to deliver and measure advertisements and prevent fraud. Playing does not require access to your precise location, contacts, microphone or photos. Provider information: https://policies.google.com/privacy and https://support.google.com/admob/answer/9012903?hl=en. Before production advertising is enabled, identifiers, consent forms, audience settings, store declarations and this policy must match the services actually activated. Yandex is not described as active in production today. 4. Choices and legal grounds Local saving and necessary operations provide the game features you choose to use. Advertising processing requiring consent must follow the applicable choice; refusing or withdrawing consent must not prevent access to the basic game. Change advertising choices in each game’s settings and, where provided, the provider’s privacy options. Choices are stored separately in each application. Necessary security and fraud-prevention processing may rely on the provider’s legitimate interests; its information describes the applicable grounds. 5. Purchases and recipients There are no real-money payments in the current test versions. If in-app purchases are enabled in a published version, Google Play or the App Store will handle payments. HRS Digital will not have access to payment card numbers. Necessary product and transaction information may be used to grant or restore a purchase and prevent duplicates. Virtual currencies and purchases belong to the relevant application unless an offer explicitly states otherwise. HRS Digital does not sell your data. Providers actually used, stores and authorised authorities may receive information necessary for their services or legal obligations. Google and other providers may process data outside the European Economic Area under safeguards described in their own policies. This integration adds no HRS Digital audience-measurement tool to the games. Visits to the HRS Digital website are covered by its separate policy and statistics choice. 6. Retention, deletion and rights Local saves remain on the device until replaced, cleared through operating-system settings or removed by uninstalling the application, subject to operating-system backups. Clearing local data can permanently delete progress. It does not delete store-held transaction records or necessarily remove operating-system backups; also consult Apple or Google settings. Advertising providers apply the retention periods described in their own privacy information. Subject to applicable conditions, you may request access, correction, deletion, restriction or portability, object to certain processing and withdraw consent. Use the HRS Digital contact above. For a local-only profile, we will explain how to manage data on your device; do not send a complete save file unless necessary. You may lodge a complaint with the French CNIL at https://www.cnil.fr or your competent supervisory authority. 7. Changes This policy will be updated when practices change, including enabling in-app purchases or advertising mediation, introducing accounts or online synchronisation. The date above identifies the published version.