Browse contents · 17 sections
- 01Scope and responsible developer
- 02Information we process
- 03Purposes and legal bases
- 04SDKs and recipients
- 05Advertising, attribution and tracking
- 06Permissions and local access
- 07Your choices and consent
- 08Retention and storage
- 09Deletion and accounts
- 10Security
- 11Privacy rights
- 12US state privacy and advertising disclosures
- 13Children and minors
- 14International transfers and other disclosures
- 15External services and this policy page
- 16Updates and contact
- 17Pre-publication checklist · review appendix
No game account foundProgress and settings are stored on-device. This does not mean no third-party processing occurs.
Ads and measurement disclosedAdjust, TopOn and 11 ad networks, subject to actual activation and OS restrictions.
01
Scope and responsible developer
This Privacy Policy explains information processing connected with Arrow Relax Maze (the “App”), its gameplay, analytics and advertising. “We” means the developer or operator: TO COMPLETE: full legal or developer name matching the store listing.
The Android package is com.maze.arrowrelax. This draft is based on the current Unity project and a recent Android test build. The production build and final iOS build have not been verified. iOS-specific provisions apply only if that version is offered; they do not imply an approved iOS release exists.
Draft status: reviewed on November 20, 2026. The effective date is TO CONFIRM. The developer address, privacy contact, target audience and distribution regions remain undecided. This is not yet an effective, publication-ready policy.
02
Information we process
The categories below distinguish observed game behavior from information that SDKs may process when enabled and permitted by the operating system and configuration. Identifiers and activity can relate to the same device or person; we do not describe them as wholly anonymous.
| Category | Information and source | Purpose and destination |
|---|
| Game state and preferences | Level, energy, recovery timestamps, sound/vibration settings and image/video mode, generated through gameplay. | Stored in device PlayerPrefs to resume play. No developer-operated account or cloud-save interface was found. |
| Usage and retention | First launch, cold launches, entry into levels 1–30, image/video content entry, D1–D14 return milestones and cumulative foreground-time milestones. | Local counters and, once enabled, configured events sent through Adjust for usage and campaign measurement. |
| Ads and revenue | Impressions, clicks, load errors, reward callbacks, placements, impression identifiers, network, amount and currency, including SDK-generated records. | Ad delivery, reward validation, frequency limits, troubleshooting and revenue measurement. TopOn can forward impression revenue to Adjust. |
| SDK identifiers and device/network data | Advertising identifiers, such as Android Advertising ID and, on iOS only when allowed, IDFA; SDK identifiers; device model, OS/app versions, language, time zone, IP address, connection type and IP-derived approximate region. | Advertising, measurement, security and fraud prevention. Availability depends on OS restrictions, permission, SDK behavior and dashboard settings. |
| Other SDK technical signals | Partner notices may cover storage capacity, runtime state, accelerometer/gyroscope signals, ad interactions and limited app compatibility or installation signals available under OS rules. | Potentially used for interactive ads, compatibility or fraud prevention. Inclusion in a partner notice does not establish that every field is collected here; verify actual behavior before release. |
| Media and diagnostics | Bundled image/video caches, media you save to the App directory, and SDK error summaries in internal builds. | Media playback, saving and troubleshooting. Diagnostic text is written to the clipboard only when you press Copy; no game feature reading personal clipboard contents was found. |
| Voluntary communications | Email, descriptions and any screenshots or logs you choose to provide through a future published contact channel. | Support and rights requests. No in-app support submission form is currently implemented. |
No game functionality for registration/login, chat, payments, contact upload, camera, microphone or precise-location access was found. This does not mean advertising SDKs process no personal information, or that external advertising destinations never request information.
03
Purposes and legal bases
- Operate the game: restore progress and settings, calculate energy, play media, provide vibration feedback and process ad rewards.
- Measure and improve: understand usage, retention and ad performance, assess campaigns and diagnose problems.
- Advertising: request, bid for, load and display ads, record revenue, limit frequency and prevent fraud. Partners may personalize ads where lawful and subject to applicable choices and permissions.
- Security and obligations: address abuse, disputes, rights requests and legal requirements.
Where a legal basis is required, processing must be matched to valid consent, contractual necessity, assessed legitimate interests or legal obligations, as appropriate. Advertising tracking is not automatically necessary for gameplay. The operator, applicable regions and purpose-specific legal bases must be confirmed before publication.
04
SDKs and recipients
The App uses the Unity engine, Adjust and TopOn. Its TopOn dependencies include the following 11 ad networks. Integration does not mean every network is enabled in the dashboard or receives data in every session. Actual recipients depend on region, placement, bidding, consent and dashboard configuration. Bidding participants may receive information at request time, not only after winning an impression.
Typical categories include advertising/device identifiers, technical device and network data, IP-derived approximate region, ad requests and interactions. Actual processing differs by service and configuration. A partner may act as a processor under contract or determine some advertising processing independently; the relevant roles and agreements must be verified.
These are direct project versions, not a complete transitive-component inventory. Unity engine services are also covered by Unity’s notice. The DT link is a legal center; identify the applicable advertising-service terms. Select the relevant regional Pangle notice. BIGO and some partner pages require JavaScript. External notices do not replace our responsibility for accurate App-specific disclosures.
05
Advertising, attribution and tracking
Rewarded ads can support revival, energy claims and saving bundled media. Interstitial entry points exist in the win-screen Home/Next flow. Rewards depend on a valid reward callback. Ad and attribution SDKs may contact servers before an ad becomes visible. Embedded ad pages may use cookies, WebView storage or similar technologies, subject to actual SDK behavior, OS settings and applicable consent requirements.
Adjust measures attribution and configured events, and can receive TopOn impression revenue, currency, impression identifier, network and placement. The absence of an account does not make this information unlinkable to a device. SDK identifiers and other permitted signals may support measurement or ad matching.
The current internal build starts SDKs after a tester presses an activation control and suppresses interstitial display. This is not a production privacy-consent, CMP or iOS ATT flow. Non-development code still has automatic-initialization paths. Required prior notices, choices and consent signals must be implemented for release; this policy cannot substitute for those controls.
06
Permissions and local access
The developer-owned manifest explicitly declares network access, network state and advertising-ID permission. The recent merged Android test manifest contains 14 permission names, grouped below. Availability and authorization rules vary by Android version.
| Permission (common android.permission. prefix omitted) | Purpose and verification status |
|---|
INTERNET | Network access for ads, analytics and related content; not blanket consent to upload data. |
ACCESS_NETWORK_STATE · ACCESS_WIFI_STATE | Network/Wi-Fi status checks; available fields are restricted by the OS. |
CHANGE_WIFI_STATE | Declared by merged dependencies; no game feature changing Wi-Fi was found. Verify necessity before release. |
VIBRATE | Haptic feedback, controlled by the in-game vibration setting. |
com.google.android.gms.permission.AD_ID · ACCESS_ADSERVICES_AD_ID | Advertising-identifier capabilities where allowed by the OS. |
ACCESS_ADSERVICES_ATTRIBUTION · ACCESS_ADSERVICES_TOPICS | Declared Android advertising attribution/topics capabilities; declaration is not proof of activation. |
com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE · com.android.vending.CHECK_LICENSE | Install-referrer, attribution or store-check capabilities; not evidence of in-app purchases. |
WAKE_LOCK · FOREGROUND_SERVICE | Declared playback/task capabilities; no game-operated persistent foreground-service feature was found. |
com.maze.arrowrelax.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION | Protection for internal dynamic broadcast receivers, not a user grant to read personal information. |
The manifest also contains limited package-visibility queries for ad navigation, stores and security/compatibility checks. These are not QUERY_ALL_PACKAGES or unrestricted access to installed applications. Actual query behavior still needs verification.
The inspected manifest does not declare precise/coarse location, camera, microphone, contacts, phone-state, broad app inventory, shared photo-library/external-storage or notification permissions. IP-derived approximate region and some sensor signals do not require those sensitive permissions; their absence does not establish an absence of such processing.
Media saving currently writes to the App directory and does not scan your personal photo library. The internal Copy error details control writes diagnostic text only on your action; no automatic clipboard-reading game feature was found.
07
Your choices and consent
- You can choose not to use rewarded-ad entry points; the associated optional reward may then be unavailable.
- Device advertising-ID, ad-privacy and app-permission settings can control available permissions and preferences. Names vary by OS. These controls may not stop all non-personalized advertising, fraud prevention or necessary technical processing, and do not automatically erase historical records.
- Where consent is required, the relevant notice and valid choice must precede non-essential processing. Refusal or withdrawal must not be bypassed through alternative identifiers.
- Use the contact channel at the end for withdrawal or objections. A production in-app privacy-choice entry point is not yet implemented and verified.
If a future iOS release tracks across other companies’ apps/sites or accesses IDFA, it must first obtain ATT authorization. A refusal must not be bypassed using fingerprinting. No final iOS ATT implementation or privacy-manifest configuration has been verified; this document does not claim they are complete.
08
Retention and storage
Retention should be limited to what is needed for the relevant function, security/disputes and applicable obligations. The verified local behavior and unresolved server-side details are:
| Record | Observed retention behavior | Required confirmation |
|---|
| Game preferences and local counters | Remain on the device until cleared, overwritten or removed by the OS. | OS backup/restore behavior and production backup exclusions. |
| Saved media and playback caches | Downloads are in the App directory; playback copies are in temporary cache and may be reclaimed by the OS. | Any in-app clearing control and platform-specific uninstall behavior. |
| Adjust / advertising partners’ server records | Depend on contracts, account configuration, purpose and legal obligations. A universal period cannot be inferred from this repository. | Specify actual periods or understandable criteria for events, identifiers and revenue records, including deletion and backup rules. |
| Support, rights requests and diagnostics | Exist if you actually submit them. No support platform or uniform retention period has been confirmed. | Confirm case retention, deletion handling and any legally required preservation. |
OS backups or device transfers may restore some App data, depending on device and release settings. Uninstalling or resetting an ad ID does not erase partner-server records. Data-center countries and transfer arrangements still require confirmation.
09
Deletion and accounts
No developer-operated registration or account feature was found, so there is currently no game login account to delete. You can still manage local data and request action on server records that can be associated with you.
- Local records: OS app-storage controls or uninstalling normally remove local game data, potentially losing progress and settings. Backups may retain or restore data. Files separately saved outside the App directory require separate management.
- Server records: submit a request through the privacy address to be published. Subject to applicable law, we will verify the request, identify retrievable records and act or assist with service-provider requests within our role and authority.
- Exceptions: any legally required retention should have a restricted purpose and an explained basis. Backup-erasure and irreversible-anonymization rules must be confirmed.
Do not send passwords, full hardware serial numbers, identity documents or unrelated information simply to make a request. If additional identification is necessary, use a controlled channel and minimum necessary information. The contact channel, SDK deletion permissions and operating procedure remain to be established. If accounts are later introduced, the applicable in-app and web deletion mechanisms must be implemented before release.
10
Security
Protection should include minimization, restricted access, appropriate credential handling, transmission/storage safeguards and incident handling as required. Developer-owned diagnostic code suppresses verbose SDK logs and redacts some error text; this does not establish a completed security audit of every SDK, endpoint or log.
PlayerPrefs is not a secure vault for sensitive data. No game functionality asks players to put passwords or payment information there. All SDK endpoints, encryption, access controls and backups have not been tested, so we do not claim universal end-to-end encryption or absolute security. Actual production safeguards must be verified and completed before release.
11
Privacy rights
Depending on applicable local law, rights may include notice, access/copies, correction, deletion, restriction, portability, objection and withdrawal of consent, as well as complaints to a competent authority. Their scope, exceptions and verification requirements vary by jurisdiction.
Withdrawal generally does not affect the lawfulness of processing based on valid consent before withdrawal. Requests should use the privacy channel below and be handled within applicable legal deadlines without unfair treatment for exercising legal rights. Until the channel, applicable regions and workflow are established, this section does not represent an already available request service.
12
US state privacy and advertising disclosures
Where relevant US state privacy laws apply to the App and operator, advertising disclosures may qualify as “sale,” “sharing” or targeted advertising even without a direct cash payment for personal information. A free app, no account or no cash transaction does not justify an unqualified promise of no sale or sharing.
Where applicable, required controls may include opt-outs, access/correction/deletion, appeals, authorized agents and recognized preference signals. Applicability, actual disclosure categories and recipients, opt-out controls and signal handling remain unconfirmed. No verified Do Not Sell or Share or GPC implementation was found. Complete the assessment and controls before distribution in relevant regions.
13
Children and minors
Target audience, minimum age, child-directed status and distribution regions are undecided. Visual style or gameplay alone does not establish an adult-only audience, and this App cannot be described as compliant with child-directed-app requirements before the relevant controls exist.
No age screen, verified parental-consent process or child-specific advertising mode was found. Before release, determine the actual audience and store age/family declarations, confirm SDK support for child traffic, restrict identifiers/tracking/personalized ads where required and obtain any legally required parental permission. If inappropriate processing of a child’s information becomes known, stop it and address deletion under applicable law. Guardians should use the privacy contact once formally published.
14
International transfers and other disclosures
Advertising, attribution and technical services may involve partners or servers outside your country. Actual recipients, storage countries, processing roles and transfer safeguards must be confirmed from contracts and configuration, not inferred from SDK package names.
Where legally required, use valid transfer grounds, contracts or other safeguards. Necessary disclosures for legal requirements, protection of lawful interests or business restructuring should be limited to a lawful purpose and accompanied by any required notices, recipient restrictions and rights handling. This document does not claim that particular transfer clauses or certifications are already in place.
15
External services and this policy page
Ads can open external websites, stores or apps. Processing on those destinations is subject to their policies and controls. This policy does not authorize them to access all information on your device.
This index.html file has no analytics SDKs, ad scripts, remote fonts, forms, tracking pixels or cookies. Language selection exists only in page memory. External policy links lead to sites with their own practices. Hosting providers, access logs, IP-address retention and security settings must be confirmed on deployment; an offline file’s behavior is not evidence of the final hosted website’s behavior.
16
Updates and contact
Changes to features, SDKs, processing or applicable requirements should be reflected in this policy, its dates and store declarations. Provide prominent notice or obtain renewed valid consent where required. Revisions cannot retroactively authorize processing that lacked a lawful basis.
These channels are undecided, so this file is for review and does not establish that users already have an effective contact mechanism.
17
Pre-publication checklist · review appendix
This appendix is a developer review note, not a declaration of completed store compliance. Static inspection cannot establish every SDK’s runtime behavior, server setting or contractual arrangement. This file does not guarantee review approval.
- Complete the responsible identity, monitored privacy email, necessary address/representative, effective date and distribution regions.
- Determine the actual audience and assess child/family requirements and SDK restrictions.
- Verify SDK fields, actual recipients, server retention, deletion channels, roles and transfer arrangements. A vendor’s entire list of possible fields is not an App-specific collection inventory.
- Address automatic initialization in non-development builds and implement required CMP/regional choices, withdrawal controls and SDK consent signals. The test button is not a production consent mechanism.
- The project still has an older iOS identifier. Verify final SDKs, usage descriptions, PrivacyInfo.xcprivacy, required-reason APIs and ATT before completing Apple privacy labels against the final binary.
- Complete Google Play Data safety and App Store App Privacy from the production build and actual flows. Do not classify purely on-device storage as server collection or omit SDK processing.
- Review and minimize merged permissions; verify network protection, backups and diagnostic logging.
- Host the policy on a stable public HTTPS page without login or geographic restrictions, and link it from the App and store listing. Production code still points to an older policy URL rather than this file.
- Resolve and verify these issues before revising/removing draft markers and this appendix for publication. Hiding unresolved markers is not compliance.
Inspection evidence
Packages/manifest.jsonAssets/Editor/AdjustDependencies.xmlAssets/Editor/TopOnDependencies.xmlAssets/Plugins/Android/TopOnConfig.androidlib/AndroidManifest.xmlAssets/Editor/TopOnAndroidBuild.csAssets/Scripts/AdjustAnalytics.csAssets/Scripts/AdjustEvents.csAssets/Scripts/AdService.csAssets/Scripts/InternalAdTest.csAssets/Scripts/SagaApp.csAssets/Scripts/Views.csAssets/Scripts/StreamingAssetFile.csAssets/Plugins/iOS/TopOnAdBridge.mmBuilds/InternalAndroidProject/launcher/build/intermediates/merged_manifests/debug/processDebugManifest/AndroidManifest.xml
Scope: current repository sources and a recent Android test build, not a complete dynamic audit of the final Play AAB or App Store IPA. No standalone Unity Analytics initialization was found beyond the built-in engine module declaration; that alone does not establish an enabled analytics service.
Official references: Google Play · User Data ↗ · Apple · App Review Guidelines §5.1 ↗ · Apple · User Privacy and Data Use ↗ · TopOn · Advertising services privacy policy ↗. Recheck external policies before release.