The current project has no account registration or sign-in system.
Android integrates mediation, ad networks and attribution. Data use depends on activation and applicable choices.
The Android save feature writes game content to your gallery; it does not read your existing photos or videos.
About this policy
This Privacy Policy explains how the operator of Arrow Link Clear (“we”, “us” or “our”) processes information in connection with the game. It covers local gameplay storage and, where activated, advertising and attribution services. The operator is responsible for the processing it determines; some advertising partners also act as independent controllers for their own purposes.
- Application
- Arrow Link Clear
- Android package
com.clear.arrowlink- Operator / controller
- [Operator legal name — to be completed]
- Country / address
- [Operator country and contact address — to be completed]
- Privacy email
- [Monitored privacy email — to be completed]
- Effective date
- [Public policy effective date — to be completed]
Platform and build differences. The inspected Android project integrates Adjust and TopOn with the partners listed below. Its current SDK startup entry is restricted to internal testing; the production regional consent flow is not complete. Testers who start the SDKs can transmit real device and advertising information, including in a measurement sandbox.
The inspected iOS game path does not initialize this Android service layer and uses a placeholder ad view. Android advertising practices described here must not be interpreted as confirmation that the same services are active on iOS. Any iOS release needs a separate final-binary privacy review and an updated policy if its processing changes.
The current game does not provide user accounts, chat, user uploads, in-app purchases or a developer-operated cloud-save service. No payment-card information is requested by the game. The policy does not treat every capability of a bundled SDK as an operation that necessarily occurs in every session.
Information we process
| Category | Examples & source | Where it is used |
|---|---|---|
| Local game state | Level progress, hearts/energy, refresh timestamps, gallery mode, sound and vibration preferences; generated as you play. | Stored on your device to run the game and restore your settings. This game state is not configured for a developer cloud save. |
| Gameplay analytics | App opens, first open, first completion of levels 1–30, return-day milestones on days 1–14, accumulated active-time milestones from 5–60 minutes, and entry into image/video modes. | Queued locally on Android, including before SDK startup; sent to Adjust when measurement is activated. Used to understand engagement and campaign performance. |
| Advertising activity | Ad requests, loads, impressions, clicks, completion/reward signals and failures; SDK impression identifiers, advertising network, ad unit and business placement. The game records impression milestones at 3, 5, 7, 10, 15, 20, 25 and 30 impressions. | TopOn and relevant ad partners deliver and measure ads. The game sends impression milestones to Adjust when measurement is activated. |
| Ad monetization | Publisher ad-revenue amount and currency, network, ad unit, placement and impression identifier supplied by TopOn. | Reported to Adjust as an ad-revenue event and ad-revenue measurement. This is advertising income information, not your bank details or a payment you make. |
| Device & network information | Activated SDKs may obtain IP address, advertising ID where available and permitted, SDK/app-instance identifiers, Android app-set identifiers, install referrer, app version, device model, OS, language, time zone and connection information. | Attribution, ad delivery, frequency control, fraud prevention and technical operation. Exact fields depend on the SDK, operating system and privacy choices. IP addresses may be used to infer approximate region. |
| Technical diagnostics | SDK delivery/error information, device/app compatibility information and operational logs that activated providers generate. | Providers may use these for reliability, debugging, measurement integrity and fraud prevention. No separate Firebase Crashlytics integration was identified. |
| Saved game media | Built-in game images or videos you choose to save. | On Android 10 or later, written locally to the system media collection. Existing personal media is not read or uploaded by this save feature. |
| Support communications | If you contact the operator, the contact details and information you choose to include in that message. | Handling your inquiry or privacy request. Avoid sending passwords, payment information or unrelated sensitive documents. |
The game does not request precise GPS location, contacts, microphone recordings, camera access, health data, SMS or phone-call records in the inspected configuration. Approximate location inferred by a provider from an IP address is different from GPS access. Advertising providers can process additional SDK-derived information as explained in their linked policies; their access must remain within the app’s actual permissions and applicable legal requirements.
Purposes and legal bases
- Provide the game: maintain progress and energy, remember preferences, display media and deliver user-requested rewards and saves.
- Measure usage and acquisition: understand installs, first opens, retention, level progression, engagement and advertising campaign effectiveness.
- Fund the game through advertising: select and display ads, run mediation auctions, verify ad delivery and rewards, and calculate advertising revenue.
- Protect the service: detect invalid advertising activity, troubleshoot errors, enforce applicable terms and comply with legal obligations.
- Handle communications: answer support inquiries and exercise privacy rights.
Where the GDPR or similar laws apply, processing necessary to provide a requested game feature may be based on performance of a contract; optional tracking, device storage/access and personalized advertising require consent where applicable. Limited security, fraud-prevention and support processing may rely on legitimate interests after assessing your rights, or on a legal obligation where required. Legitimate interests are not a substitute for consent where consent is legally required.
Consent can be withdrawn for future processing without affecting processing lawfully performed beforehand. This policy is a notice, not a consent mechanism. Selecting a rewarded ad is not, by itself, agreement to cross-app tracking or personalized advertising.
How ads and measurement work
On Android, the game uses TopOn to mediate rewarded videos and interstitial ads. Rewarded entry points include revival from a failure screen, restoring energy through the energy dialog, and saving gallery content. Interstitials can appear when leaving the win screen through Home or Next, subject to the configured level threshold and cooldown. Available networks can vary by region, demand and mediation configuration.
Adjust measures acquisition and the events described in Section 2. When enabled, the game sends both publisher ad-revenue information and custom monetization events to Adjust. Event and impression identifiers help avoid duplicate reporting. Advertising and attribution providers may associate activity with device or advertising identifiers to measure campaigns and, where permitted, provide interest-based advertising across apps or services.
Non-personalized ads can still involve IP addresses, device information, contextual information, ad delivery measurement and anti-fraud processing. “Non-personalized” does not mean that no personal data leaves your device. Advertising SDKs can use local storage, SDK identifiers and similar technologies; ad creatives may also use web-based technologies.
For any future iOS build that performs tracking as defined by Apple, App Tracking Transparency authorization must be obtained before tracking or accessing IDFA. Denial must be respected, and tracking cannot be replaced with device fingerprinting. The inspected iOS game path does not currently implement this tracking flow.
Partners and information sharing
The following services are present in the inspected Android dependency configuration. Presence in the package does not mean every partner receives data on every launch. Active recipients depend on SDK initialization, mediation selection, geography and privacy choices. Partners may process identifiers, device/network information and advertising interactions for delivery, measurement, fraud prevention and, when permitted, personalization. Adjust also receives the configured gameplay and monetization events.
| Service | Role in this project | Provider information |
|---|---|---|
| Adjust | Install attribution, engagement events and ad-revenue measurement. | Privacy information |
| TopOn | Ad mediation, auctions, ad reporting and reward signals. | Privacy policy |
| Unity Ads | Advertising source; Unity also supplies the game engine. | Player privacy policy |
| Meta Audience Network | Advertising source. | Privacy policy |
| Google AdMob | Advertising source and associated Google advertising services. | Privacy policy · Partner services |
| Digital Turbine / Fyber | Advertising source through the Fyber marketplace dependency. | Advertising privacy & choices |
| Mintegral / MBridge (MTG) | Advertising source. | Privacy information |
| AppLovin | Advertising source. | Privacy policy |
| Pangle | Advertising source; regional end-user notices apply. | Regional privacy notices |
| ironSource / Unity | Advertising source through the ironSource mediation SDK dependency. | Player privacy policy |
| InMobi | Advertising source. | Privacy information |
| BIGO Ads | Advertising source. | Privacy information |
| Moloco | Advertising source. | Privacy notices & choices |
| SmartDigimkttech (SDM) | Additional advertising dependency bundled with the TopOn package; enabled status and provider scope require confirmation. | [Official policy URL and legal entity to be confirmed] |
Ad partners may share information with their demand partners, measurement and fraud-prevention providers, affiliates and infrastructure providers as described in their notices and permitted by law. They may act as processors or independent controllers depending on the activity. The operator remains responsible for selecting and configuring services consistently with the commitments in the final policy and applicable platform requirements.
Information may also be disclosed where required by law, to protect legal rights or safety, to professional advisers under appropriate duties, or in connection with a merger or transfer of the business subject to applicable protections and notice requirements. We do not receive your personal photo library through the game’s save feature. There is no configured developer-operated marketplace for selling player profiles; advertising disclosures can nevertheless qualify as “sale” or “sharing” under some laws, as explained in Section 9.
Device permissions and capabilities
The last exported Android release manifest includes the groups below. SDKs can add permissions during manifest merging. A declaration makes a capability available; it does not prove that the capability is used in a particular session.
| Permission / capability | What it relates to |
|---|---|
| Internet & connection state | INTERNET, ACCESS_NETWORK_STATE and ACCESS_WIFI_STATE: network communication and connectivity information for SDK operations. |
| Advertising & attribution | com.google.android.gms.permission.AD_ID, install-referrer binding, and ACCESS_ADSERVICES_AD_ID, ACCESS_ADSERVICES_ATTRIBUTION, ACCESS_ADSERVICES_TOPICS: Android advertising, attribution and related SDK capabilities. Availability is controlled by the OS and settings. No app-level Topics API call was identified. |
| Vibration | VIBRATE: gameplay feedback, configurable through the game’s vibration setting. |
| Runtime & SDK support | WAKE_LOCK and FOREGROUND_SERVICE: declared runtime capabilities. CHECK_LICENSE, the app-scoped dynamic-receiver permission and Amazon ATTEST are also present as dependency/platform support declarations. Their declaration is not evidence of continuous background tracking. |
| Wi-Fi change capability | CHANGE_WIFI_STATE is present in the merged dependencies. No game-level Wi-Fi changing feature was identified; the necessity of this SDK-added permission must be resolved before production release. |
| Gallery save | The Android save implementation uses MediaStore on Android 10 and later to add the selected built-in image/video. It does not request broad storage access or read access to your photo/video library. Saving is unavailable below Android 10. |
No camera, microphone, precise/coarse location, contacts, phone-state, broad file-management or notification permission was present in the inspected Android merged manifest. There was no final iOS export or app-specific iOS privacy manifest available to establish a complete iOS permission declaration. Any future iOS photo-library or tracking feature needs the appropriate system disclosure and authorization before access.
How long information is kept
- Local progress and preferences: remain in the app’s local storage until that storage is cleared or removed. The current code has no automatic expiry for progress or analytics state.
- Local analytics: pending events are stored before transmission. The app removes its pending records after handing them to the SDK; SDK delivery, retry and server retention are separate. First-occurrence markers, accumulated time and deduplication identifiers remain in local analytics state without a configured automatic expiry.
- Exported media: files saved to your system gallery can remain after uninstalling the game. Delete those files using your gallery or file-management application.
- Provider-held data: retention is governed by the purpose, contractual configuration, provider policy and legal requirements. There is no project-defined universal deletion period covering all SDK providers; see their notices and request deletion through the operator or the relevant provider.
- Support and legal records: retain only as necessary to resolve the inquiry, demonstrate compliance, protect legal rights or meet an applicable legal retention duty, then delete or anonymize as appropriate.
On Android, you can use system app settings to clear the game’s storage. Uninstalling generally removes app-private data, but OS backups or device transfers may retain or restore some data depending on your settings. Clearing storage or uninstalling does not automatically erase information already held by advertising or measurement partners. Removing the local analytics state may cause a later launch to be treated as a new local first open.
There is no account to delete in the current game. For information already transmitted, use the privacy contact in Section 14 once completed, or the provider’s own privacy request channel. Deletion may require proportionate verification and can be limited by applicable legal duties; any retained information should be limited to the relevant exception.
Your choices and privacy rights
Device controls
Use your Android device’s advertising privacy controls to reset or delete the advertising ID and adjust available advertising settings. Menu names vary by Android version and manufacturer. These controls may restrict identifier use but do not necessarily stop all contextual ad delivery or technical data processing. You can stop future app activity by closing and uninstalling the game.
On iOS, system tracking controls are available under Settings → Privacy & Security → Tracking. These settings become relevant if a future release requests tracking. The policy does not represent an iOS tracking prompt or an in-game privacy settings screen as already available.
Requests to the operator
Depending on your location and applicable law, you may request access to your information, correction, deletion, a portable copy, restriction of processing, withdrawal of consent or an objection to certain processing. You may also have rights to opt out of targeted advertising, sale or sharing, and to appeal a rejected request. You can complain to a competent data-protection authority and exercise applicable rights without unlawful discrimination.
Send requests through the completed contact in Section 14. Identify the game, your platform and the request; we may ask for only the information reasonably needed to locate the relevant records and verify authority. Do not send a government ID or an advertising identifier unless specifically necessary and requested through an appropriate channel. Authorized agents may submit requests where permitted, with proportionate authorization checks. Requests and appeals should be handled within the applicable statutory deadlines, with any lawful extension explained.
Additional regional information
EEA, United Kingdom and Switzerland
The operator/controller must be identified in Section 1. Where applicable, optional SDK storage/access, advertising and attribution must be subject to the required consent before activation. You may withdraw consent for the future, object to processing based on legitimate interests and complain to your local supervisory authority. Any legally required EU/UK representative details must be added before serving the relevant market.
United States, including California
Categories potentially disclosed for advertising include online identifiers, IP-derived approximate region, device/network information, app activity and advertising interactions. Recipients include advertising networks, mediation and measurement providers. Local-only game settings and personal gallery contents are not deliberately sent as advertising datasets by the inspected game code.
Sharing identifiers and interactions for cross-context behavioral advertising may constitute “sharing,” “sale” or targeted advertising under applicable state laws even if no money is paid for the information. A blanket “we never sell or share data” statement would not accurately describe every possible ad configuration. Where the law applies, a working way to opt out, a “Do Not Sell or Share My Personal Information” entry where required, and handling of recognized universal opt-out signals must be established before this processing is enabled. These controls are not yet implemented in the inspected build.
Applicable rights can include knowing/accessing, correcting, deleting and obtaining a copy of data, opting out of sale/sharing or targeted advertising, limiting certain uses of sensitive information where applicable, and appealing a denial. The game does not provide a feature for decisions producing legal or similarly significant effects through automated profiling. Specific protections apply to minors; the audience and age-handling configuration remain a release requirement.
Other locations
Rights and lawful bases differ by country. We must apply any additional local requirements for the markets in which the game is made available. The final distribution regions and any mandatory local notices or representatives need confirmation before release.
Children’s privacy
Intended audience: [Audience and minimum age — to be confirmed before release]
The developer has not yet designated the audience or implemented a verified child/age-handling flow. This policy therefore does not claim that the current advertising configuration is suitable for children or eligible for Google Play Families or Apple’s Kids Category. A store age rating alone does not establish a lawful basis to collect a child’s information.
Before distribution, the operator must determine the actual audience, apply the relevant child-privacy laws and platform requirements, and prevent prohibited advertising or tracking of children. Where parental authorization is required, personal information must not be collected on the basis of the child’s consent alone. In particular, the treatment of children under 13 in the US and applicable consent ages in other regions needs to be resolved before activating these services for them.
If you are a parent or guardian and believe a child’s information has been processed inappropriately, contact the operator using Section 14 once completed so the circumstances can be investigated, further processing restricted as appropriate, and deletion requested from relevant providers.
International data transfers
Advertising and attribution services operate internationally. When those services are active, information can be processed outside your country, including locations with different privacy laws. The provider’s applicable entity and processing locations depend on the service and region; their notices describe their arrangements.
For transfers requiring safeguards, the operator and relevant providers must establish an applicable lawful transfer mechanism, such as an adequacy decision, standard contractual clauses and any required UK addendum or equivalent safeguards. This draft does not certify that those agreements have already been executed for the operator. Information about applicable safeguards or a permitted copy can be requested through the completed privacy contact.
Security and external services
The game uses platform-provided app storage for its private local state and platform media APIs for Android gallery exports. Local preferences are not an encrypted vault and should not be treated as suitable for sensitive personal information. Advertising and measurement providers operate their own network services and security controls.
Appropriate technical and organizational measures must be maintained for the processing undertaken, including access restrictions, secure network transport and careful handling of support records. The project scan alone does not establish the security of every third-party SDK or endpoint. No storage or transmission method can be guaranteed completely secure.
Ads and provider links can open services outside the game. Their operators are responsible for their separate services and notices; this does not remove our obligations for disclosures made from the game. This HTML document embeds no external scripts, fonts, images, forms or advertising. If you follow a link, the destination may process connection information. A future web host may also create its own access logs; the hosting arrangement is not yet selected.
Changes to this policy
We may update this policy when the app, service providers, legal requirements or data practices change. The published policy should display its effective date and last-updated date. Material changes must be communicated through an appropriate in-app or other accessible notice, and additional consent obtained before new processing where required. An updated policy does not retroactively provide consent.
Contact the operator
For questions, requests or complaints about Arrow Link Clear and your information:
- Operator
- [Operator legal name]
- Privacy email
- [Monitored privacy email]
- Contact address
- [Country and contact address]
- EU / UK representative
- [Assess applicability; add details or remove if not required]
These are intentional placeholders, not working contact channels. The operator must replace them before publication. Never send private information to a guessed email address.
Release review notes
This appendix records the basis and unresolved items of this draft. It is for the developer’s review and should be resolved before publishing a final consumer policy.
Required before using this policy for a public release
- Complete every highlighted operator, contact, date, audience and representative field. Confirm the operator identity is consistent with the store listing.
- Verify SmartDigimkttech’s legal entity, official privacy URL, activation and data scope, or deliberately remove that SDK from a separate code change. Validate all partner notices for the actual distribution regions.
- Implement and verify the regional consent manager, consent withdrawal, age handling and US opt-outs as applicable; communicate the choices to all relevant SDKs. Disable the internal SDK test entry in production. A non-personalized ad flag alone does not complete this integration.
- Confirm the actual SDK/server retention settings, deletion process, provider contracts and transfer safeguards. Document any mandatory local or representative information.
- Review the final merged manifest and SDK behavior, especially the Wi-Fi change capability, AdServices capabilities and SDK startup before consent. Remove unnecessary permissions through a separate reviewed change.
- For an iOS release, inspect the exported binary and all SDK privacy manifests, required-reason API declarations, permissions, data flows and any ATT/photo-saving implementation. The current Android audit cannot establish iOS compliance.
- Complete Google Play Data safety and App Store App Privacy disclosures from the final behavior, including third-party data collection and tracking. These store forms are separate from this policy.
- Publish the finalized page at a stable, publicly accessible HTTPS URL without login or a geographic gate. Add accessible links within the game and in the store metadata; verify access on mobile. Then remove the draft banner and this development appendix and update the status.
Project evidence used for this draft
Scan date: November 20, 2026. The scan covered dependency declarations, game/SDK integration code and the existing Android export. No network traffic audit or final iOS binary audit was performed.
Packages/manifest.json: Unity, Adjust Unity 5.8.3 and the local TopOn Unity package.Assets/Plugins/Android/mainTemplate.gradleandProjectSettings/AndroidResolverDependencies.xml: Adjust Android 5.8.1, TopOn core 6.5.73.3, eleven requested network integrations and SDM 6.5.80.Builds/Android/Gradle/launcher/build/intermediates/merged_manifests/release/processReleaseManifest/AndroidManifest.xml: permissions in the last exported Android release; recheck after future builds.Assets/Scripts/AndroidServices.cs,AnalyticsState.cs,TopOnAds.csandAndroidSdkConfig.cs: event queues, SDK activation, ad callbacks and configuration gates.Assets/Scripts/ArrowGame.cs,AndroidAssets.csandAssets/Plugins/Android/MediaSave.java: local progress, packaged content and Android media export.Assets/Plugins/iOS/ArrowAds.mmandProjectSettings/ProjectSettings.asset: iOS placeholder advertising and absence of configured camera/location/microphone usage text.
An SDK dependency is evidence of inclusion, not proof of every possible data flow. No SDK keys, app tokens or advertising placement credentials are published in this page.
Official platform policy references
This policy must match actual processing. A document alone cannot guarantee store approval or replace required implementation, SDK review or store declarations.