Arrow Relax Maze
ARROW RELAX MAZE · PRIVACY

隐私政策

了解游戏、广告与统计服务中的信息处理,
以及你可以作出的选择。

审阅日期:2026.11.20Android 已扫描 · iOS 待核验正式生效日期待确认
浏览目录 · 17 节
  1. 01适用范围与负责主体
  2. 02我们处理哪些信息
  3. 03处理目的与法律依据
  4. 04第三方 SDK 与接收方
  5. 05广告、归因与追踪
  6. 06设备权限与本地访问
  7. 07你的选择与同意
  8. 08保存期限与存储位置
  9. 09删除数据与账户
  10. 10安全措施
  11. 11你的隐私权利
  12. 12美国州法与广告数据共享
  13. 13儿童与未成年人
  14. 14跨境传输与其他披露
  15. 15外部服务与本政策网页
  16. 16政策更新与联系我们
  17. 17发布前核验清单 · 审阅附录
无需游戏账户游戏进度与偏好保存在设备;这不等于没有第三方数据处理。
广告与归因有披露Adjust、TopOn 及 11 个广告来源,按实际启用和系统限制处理信息。
01

适用范围与负责主体

本隐私政策说明 Arrow Relax Maze(下称“本应用”)如何处理与游戏、统计及广告服务有关的信息。“我们”指提供本应用的开发者或运营主体:待填写:与商店开发者信息一致的完整名称。

Android 包名为 com.maze.arrowrelax。本文以当前 Unity 工程及最近 Android 测试构建为依据;尚未核实正式发行包和 iOS 最终构建。iOS 条款仅在相应版本实际提供时适用,不表示当前已有通过审核的 iOS 版本。

草稿状态:审阅日期为 2026 年 11 月 20 日;正式生效日期待确认。开发者地址、隐私联系邮箱、目标年龄和发行地区尚未确定,本文不能直接作为已生效政策发布。

02

我们处理哪些信息

以下区分游戏代码明确处理的信息,以及集成 SDK 在服务启用、系统允许和相关配置下可能处理的信息。标识符与行为信息可能关联到同一设备或用户,不应笼统称为“完全匿名数据”。

信息类别内容与来源用途与去向
本地游戏与偏好关卡、体力、体力恢复时间、声音与振动设置、图片/视频模式;由游戏操作产生。保存在设备 PlayerPrefs 中,用于恢复游戏;未发现自有账户或云存档接口。
使用与留存统计首次启动、冷启动、进入第 1–30 关、图片/视频内容入口、D1–D14 留存、累计前台时长里程碑。本地保存统计状态;SDK 启用后,配置的事件经 Adjust 发送,用于使用情况及营销衡量。
广告与收益信息展示、点击、加载错误、奖励回调、广告位、展示标识、广告来源、金额及币种;部分由广告 SDK 产生。用于展示与奖励校验、频控、排错和收入衡量;单次展示收益可由 TopOn 转交 Adjust。
SDK 标识及设备/网络信息广告标识符(如 Android 广告 ID;iOS 的 IDFA 仅在允许时)、SDK 生成标识、设备型号、系统/应用版本、语言、时区、IP 地址、网络类型及由 IP 推断的大致地区。广告请求、衡量、安全及反作弊。哪些字段实际取得取决于系统限制、许可、SDK 与后台设置。
SDK 的其他技术信号合作方政策可能涵盖设备容量、运行状态、加速度计/陀螺仪等信号、广告交互,以及受系统可见性限制的应用兼容/安装状态信息。可能用于可玩广告、兼容性或反作弊;不能仅凭声明推断本应用逐项收集。实际调用须发布前核验。
媒体与诊断内置图片/视频的本地缓存、由你下载到应用目录的文件;内部测试包的 SDK 错误摘要。媒体播放、下载及问题定位。诊断文本仅在你点击复制按钮时写入剪贴板,未发现读取个人剪贴板内容的业务。
你主动提供的信息如你通过未来公布的联系渠道提交问题,可能包含邮箱、问题描述及自愿提供的截图或日志。处理咨询或权利请求;当前项目未提供应用内客服表单。

当前游戏代码未发现注册/登录、聊天、支付、通讯录上传,或主动读取相机、麦克风和精确位置的功能。这不表示广告 SDK 不处理个人信息,也不表示第三方广告落地页不会另行请求信息。

03

处理目的与法律依据

  • 提供游戏:恢复进度与偏好、计算体力、播放媒体、提供振动反馈及处理广告奖励。
  • 衡量与改进:了解使用、留存和广告表现,衡量推广效果并定位故障。
  • 广告变现:请求、竞价、加载与展示广告,处理收益、限制频率和防范作弊;在合法且满足必要选择/许可时,合作方可能进行个性化广告处理。
  • 安全与义务:处理滥用、争议、权利请求和适用法律要求。

在适用法律要求法律依据的地区,不同处理应分别依据有效同意、提供服务所必要的合同履行、经评估的合法利益或法定义务。不能把所有广告追踪都视为游戏运行所必需。发布前须确认运营主体、适用地区及各目的的具体法律依据。

04

第三方 SDK 与接收方

本应用集成 Unity 引擎、Adjust 和 TopOn;TopOn 依赖中包含下列 11 个广告来源。已集成不等于已在后台启用,也不代表每次使用都向所有来源传输数据。实际接收方取决于地区、广告位、竞价、同意状态及后台配置。部分合作方可能在竞价/请求阶段接收信息,而不只在最终展示时接收。

典型接收信息包括广告/设备标识、设备与网络技术信息、IP 推断的大致地区、广告请求与交互;各方具体范围依其服务和实际配置。合作方可能按合同作为处理者,也可能就部分广告活动独立决定处理方式,须核实相应角色和协议。

服务 / Android 直接依赖版本用途合作方政策
AdjustUnity 5.8.3归因、使用统计、广告收益衡量隐私政策 / 法律中心 ↗
TopOn6.6.41广告聚合、竞价与广告收益回调隐私政策 / 法律中心 ↗
Unity Ads4.20.0广告投放与效果衡量隐私政策 / 法律中心 ↗
Meta Audience Network6.22.0广告投放与效果衡量隐私政策 / 法律中心 ↗
Google AdMob25.4.0广告投放、衡量与反作弊隐私政策 / 法律中心 ↗
DT Exchange / Digital Turbine8.4.7广告交易与效果衡量隐私政策 / 法律中心 ↗
Mintegral17.1.71广告投放与效果衡量隐私政策 / 法律中心 ↗
AppLovin13.6.3广告投放与效果衡量隐私政策 / 法律中心 ↗
Pangle8.2.0.4广告投放与效果衡量隐私政策 / 法律中心 ↗
ironSource Ads / Unity9.2.0广告投放与效果衡量隐私政策 / 法律中心 ↗
InMobi11.4.0广告投放与效果衡量隐私政策 / 法律中心 ↗
BIGO Ads6.0.0广告投放与效果衡量隐私政策 / 法律中心 ↗
Moloco4.11.1广告投放、竞价与效果衡量隐私政策 / 法律中心 ↗

版本取自项目直接依赖,不是所有传递组件的完整版本清单。Unity 引擎技术服务另见 Unity 政策。DT 链接为法律中心,须确认适用的广告服务条款;Pangle 条款按地区选择;BIGO 和部分合作方页面需要 JavaScript。外部条款变更不免除我们准确披露本应用处理行为的责任。

05

广告、归因与追踪

激励广告可用于失败复活、领取体力和下载内置媒体;插屏入口位于通关页的 Home/Next 流程。奖励仅在有效奖励回调后发放。加载广告和归因 SDK 可能在广告真正出现前与服务器通信。广告内嵌网页可能使用 Cookie、WebView 本地存储或类似技术,受实际 SDK、系统设置及适用的同意要求约束。

Adjust 用于归因及配置事件统计,并可接收来自 TopOn 的单次广告收益、币种、展示标识、广告来源和广告位。没有账户并不意味着这些信息无法关联到设备。SDK 的设备标识或其他允许信号可能用于衡量或广告匹配。

当前内部测试包由测试人员主动点击入口后启动 SDK,并关闭插屏展示。这个入口不是正式的隐私同意、CMP 或 iOS ATT 流程。当前非开发构建仍有自动初始化路径,正式发布前必须根据适用要求落实事前说明、选择及信号传递,不能用本政策代替这些控制。

06

设备权限与本地访问

源码自有清单显式声明联网、网络状态和广告 ID 三类权限;最近 Android 测试构建合并依赖后共有 14 个权限名称,归类如下。不同 Android 版本的可用性与授权规则可能不同。

权限(省略通用 android.permission. 前缀)目的与核验状态
INTERNET联网请求广告、统计和相关内容;不表示无条件同意上传。
ACCESS_NETWORK_STATE · ACCESS_WIFI_STATESDK 网络连通性与 Wi‑Fi 状态判断;可用字段受系统限制。
CHANGE_WIFI_STATE第三方依赖合并声明;未发现游戏主动修改 Wi‑Fi 的业务,发布前须核验必要性。
VIBRATE按声音/振动设置提供触觉反馈,可在游戏设置关闭。
com.google.android.gms.permission.AD_ID · ACCESS_ADSERVICES_AD_ID在系统允许时访问广告标识相关能力。
ACCESS_ADSERVICES_ATTRIBUTION · ACCESS_ADSERVICES_TOPICS依赖声明的 Android 广告归因/主题相关接口;声明不证明实际启用。
com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE · com.android.vending.CHECK_LICENSE安装来源/归因或商店校验相关声明;不代表应用提供付费购买。
WAKE_LOCK · FOREGROUND_SERVICE依赖声明的播放或任务执行能力;未发现游戏自建持续前台服务的业务。
com.maze.arrowrelax.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION应用内部动态广播接收器保护,不是读取个人信息的用户授权。

合并清单还包含广告跳转、应用商店及安全/兼容检查所用的包可见性查询。它们不等同于 QUERY_ALL_PACKAGES 或无限制读取已安装应用列表。实际查询行为仍需核验。

最近清单未声明精确/粗略定位、相机、麦克风、通讯录、电话状态、全量应用列表、共享照片库/外部存储或通知访问权限。IP 推断的大致地区和某些传感器信号不依赖这些敏感权限,因此不能据此声称没有相关数据处理。

当前媒体下载写入应用目录,不扫描你的个人相册。内部测试“复制错误详情”只由你的点击写入诊断文本;没有自动读取剪贴板的游戏功能。

07

你的选择与同意

  • 你可以不选择激励广告入口;相应的额外奖励可能不提供。
  • 可通过设备系统中的广告 ID、广告隐私及应用权限设置管理可用权限或广告偏好;名称随系统版本变化。这些设置不一定停止全部非个性化广告、反作弊或必要技术处理,也不会自动删除历史记录。
  • 在需要同意的地区,应先提供必要说明并取得有效选择,再启动相应的非必要处理。拒绝或撤回同意不应被解释为允许其他方式绕过选择。
  • 撤回及反对处理的联系渠道见本文末尾;正式应用内隐私选择入口尚待实现与确认。

如果未来 iOS 版本进行 Apple 定义的跨应用/网站追踪或访问 IDFA,应先取得系统 ATT 授权;拒绝 ATT 不得通过设备指纹等方式绕过。当前没有可确认的最终 iOS ATT 实现或隐私清单,本文不声称它们已经完成。

08

保存期限与存储位置

保存应以提供相关功能、处理安全/争议和履行适用义务所需的时间为限。当前能确认的本地行为和仍须补齐的服务器信息如下:

记录目前可确认的保存规则发布前待确认
游戏偏好与本地统计保留在本机,直到应用数据被清除、记录被覆盖或设备系统移除。系统备份/恢复及正式版备份排除规则。
媒体下载与播放缓存下载保存在应用目录;播放副本在临时缓存,可能由系统回收。是否提供应用内清理入口,及不同平台卸载后的具体行为。
Adjust / 广告合作方服务器数据受实际合同、账户设置、处理目的和法律要求约束,不能从本仓库确定统一期限。填写各类事件、标识与收益数据的实际期限或可理解的确定标准,以及删除/备份规则。
联系、权利请求及排错资料仅在你实际提交后产生;当前没有已确认的客服系统或统一期限。确认咨询处理期限、删除流程及必要的法定保留。

Android/iOS 系统备份或设备迁移可能恢复部分应用数据,具体取决于设备与发布包设置。卸载或重置广告 ID 不等于合作方服务器数据同时被删除。具体数据中心所在国家及跨境安排仍需核实。

09

删除数据与账户

当前没有发现自有用户账户或注册功能,因此没有可删除的游戏登录账户。你仍可管理本地数据,并对可关联到你的服务器数据提出请求。

  1. 本地数据:使用系统的应用存储管理清除本应用数据或卸载应用,通常会移除本地游戏记录;此操作可能导致进度和设置丢失。系统备份可能保留或恢复数据,应用目录外另存的文件需由你另外管理。
  2. 服务器数据:通过待公布的隐私联系邮箱提出删除请求。我们会按适用法律核验请求、识别可定位的数据,并在相应角色和权限内处理或协助向服务提供方转交。
  3. 保留例外:依法确需保留的数据应限定用途并说明原因;备份删除与不可逆匿名化的具体规则需确认。

不要为提出请求发送密码、完整设备序列号、身份证件或无关信息。若必须补充定位信息,应仅通过受控渠道收集最少必要内容。实际接收渠道、SDK 删除权限及操作流程尚待建立。如未来加入账户,发布前还需配置适用的应用内及网页账户删除机制。

10

安全措施

个人信息保护应包括最小化收集、受限访问、妥善保管密钥、合理的传输与存储保护,以及按适用要求处理安全事件。当前自有诊断代码抑制 SDK 详细日志,并对部分错误文本进行脱敏;这不是对所有第三方 SDK、端点或日志已经完成安全审计的保证。

PlayerPrefs 不是为敏感信息设计的加密保险箱。本项目没有让玩家向该存储输入密码或支付信息的业务。尚未完成所有 SDK 传输端点、加密、访问控制及备份的实测,因此不声称“所有数据端到端加密”或“绝对安全”。正式发布前须验证并补齐实际安全措施。

11

你的隐私权利

依你所在地的适用法律,你可能享有知情、访问或获取副本、更正、删除、限制处理、数据可携带、反对处理及撤回同意等权利,也可能有权向所在地监管机构投诉。权利范围、例外和身份核验要求并不在所有地区相同。

撤回同意通常不影响撤回前基于有效同意进行处理的合法性。可通过本文的隐私联系渠道提出请求;我们拟按适用法律时限答复,不因依法行使权利而给予不公平待遇。在联系渠道建立、适用地区和处理流程确认前,本段不能视为已经提供了可用的请求服务。

12

美国州法与广告数据共享

若适用的美国州隐私法律覆盖本应用及运营主体,广告合作中的数据披露可能构成法律意义上的“出售”“共享”或“定向广告”,即使没有直接收取出售个人信息的价款。不能仅因应用免费、没有账户或没有现金交易就作出“绝不出售/共享数据”的承诺。

在适用时,应支持退出相关处理、请求访问/更正/删除,以及法律要求的申诉、授权代理和有效偏好信号。是否属于相关法律适用主体、前期实际披露类别、具体接收方、退出入口和信号处理尚待确认;当前未发现可确认的“请勿出售或共享”或 GPC 实现。如拟在相关地区发布,须完成评估与实现后再更新本节。

13

儿童与未成年人

目标年龄、最低使用年龄、是否面向儿童及发行地区尚未确定。不能仅凭游戏画面或玩法把本应用认定为成人应用,也不能在尚未实现儿童保护控制时宣称符合儿童应用要求。

当前未发现年龄筛选、可核实的监护人同意或儿童专用广告模式。发布前须按实际受众完成商店年龄/家庭类别声明,确认合作 SDK 对儿童流量的支持,并在需要时限制标识符、追踪和个性化广告,取得适用法律要求的监护人许可。若知悉不应处理的儿童信息,应停止相关处理并依法处理删除;监护人可通过正式公布的隐私联系渠道提出问题。

14

跨境传输与其他披露

广告、归因与相关技术服务可能由位于你所在国家或地区以外的合作方或服务器提供。实际接收主体、存储国家/地区、处理角色及适用的跨境保障机制须按服务合同与后台设置确认,不能从 SDK 包名推断。

适用法律要求时,应采取有效的传输依据、合同或其他保障。经法律要求、保护合法权益或企业重组而进行的必要披露,应限定在合法必要范围,并按适用要求通知、约束接收方及处理权利请求。本文不表示已经签署了任何特定跨境条款或已完成相关认证。

15

外部服务与本政策网页

广告可能带你前往外部网站、应用商店或其他应用。第三方在这些页面的处理由其政策和选择机制约束;本政策并不授权这些页面访问你设备上的全部信息。

本 index.html 文件不包含统计 SDK、广告脚本、远程字体、表单、追踪像素或 Cookie;语言切换仅使用当前页面内存。点击外部政策链接后,相应网站可能进行自己的处理。部署网站后的托管商、访问日志、IP 地址保留和安全配置仍需确认;不能把离线文件的行为直接等同于最终网站的行为。

16

政策更新与联系我们

当功能、SDK、数据处理或适用要求发生变化时,应更新本政策、页面日期及商店申报;需要时应给予显著通知或重新取得有效同意。政策修订不能追溯性地授权此前未被合法授权的处理。

应用:Arrow Relax Maze

负责主体:待填写完整名称

隐私联系邮箱:待填写可实际收件和处理请求的邮箱

联系地址 / 适用代表:按实际主体与适用法律确认

请求内容:说明你使用的应用、请求类型及回复方式;不要主动提交无关敏感资料。

目前上述渠道尚未确定,因此本文件仅供审阅,不能作为已向用户提供有效联系机制的证明。

17

发布前核验清单 · 审阅附录

本附录是开发者审阅说明,并非已经完成商店合规工作的声明。静态扫描不能证明每个 SDK 的运行行为、服务器配置或合同安排;本文件也不提供任何审核通过保证。

  1. 补齐负责主体、有效隐私邮箱、必要地址/代表、正式生效日期及发行地区。
  2. 确定实际年龄定位,完成儿童/家庭适用性及合作 SDK 限制评估。
  3. 确认 SDK 数据字段、真实接收方、服务器保留期限、删除途径、处理角色和跨境安排;不要仅复制 SDK 的完整可能字段列表作为实际采集清单。
  4. 修复非开发构建的自动初始化路径,完成所需 CMP/地区选择、撤回入口及各 SDK 同意信号传递。测试按钮不能替代正式流程。
  5. iOS 目前仍有旧包标识;需核对实际 SDK、权限描述、PrivacyInfo.xcprivacy、Required Reason API 和 ATT,再据最终二进制完善 Apple 隐私标签。
  6. 依据最终发布构建及实际数据流填写 Google Play Data safety 和 App Store App Privacy;不能把“设备本地存储”直接申报为云端收集,也不能忽略 SDK 自动处理。
  7. 审查合并权限,移除无业务必要的能力;核实网络安全、备份及诊断日志。
  8. 将政策部署到公开、稳定、免登录、非地域限制的 HTTPS 网页,并在商店和应用内提供真实链接。当前正式代码仍指向旧政策网址,尚未接入本文件。
  9. 填妥并验证以上项目后,修订或移除草稿/待补标识及本附录,再用于发布;不是单纯隐藏标识即可完成合规。
本次扫描依据
  • Packages/manifest.json
  • Assets/Editor/AdjustDependencies.xml
  • Assets/Editor/TopOnDependencies.xml
  • Assets/Plugins/Android/TopOnConfig.androidlib/AndroidManifest.xml
  • Assets/Editor/TopOnAndroidBuild.cs
  • Assets/Scripts/AdjustAnalytics.cs
  • Assets/Scripts/AdjustEvents.cs
  • Assets/Scripts/AdService.cs
  • Assets/Scripts/InternalAdTest.cs
  • Assets/Scripts/SagaApp.cs
  • Assets/Scripts/Views.cs
  • Assets/Scripts/StreamingAssetFile.cs
  • Assets/Plugins/iOS/TopOnAdBridge.mm
  • Builds/InternalAndroidProject/launcher/build/intermediates/merged_manifests/debug/processDebugManifest/AndroidManifest.xml

核验范围:当前仓库的源代码及最近 Android 测试构建;并非最终 Google Play AAB 或 App Store IPA 的完整动态审计。未发现独立启用的 Unity Analytics 初始化,仅有引擎内置模块声明,不能据此将其认定为已启用的统计服务。

官方要求参考:Google Play · User Data ↗ · Apple · App Review Guidelines §5.1 ↗ · Apple · User Privacy and Data Use ↗ · TopOn · Advertising services privacy policy ↗。外部政策可能更新,发布前应再次核对。

ARROW RELAX MAZE · PRIVACY

Privacy Policy

Understand information use across the game,
advertising and analytics—and the choices available to you.

Reviewed · Nov 20, 2026Android inspected · iOS unverifiedEffective date pending
Browse contents · 17 sections
  1. 01Scope and responsible developer
  2. 02Information we process
  3. 03Purposes and legal bases
  4. 04SDKs and recipients
  5. 05Advertising, attribution and tracking
  6. 06Permissions and local access
  7. 07Your choices and consent
  8. 08Retention and storage
  9. 09Deletion and accounts
  10. 10Security
  11. 11Privacy rights
  12. 12US state privacy and advertising disclosures
  13. 13Children and minors
  14. 14International transfers and other disclosures
  15. 15External services and this policy page
  16. 16Updates and contact
  17. 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.

CategoryInformation and sourcePurpose and destination
Game state and preferencesLevel, 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 retentionFirst 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 revenueImpressions, 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 dataAdvertising 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 signalsPartner 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 diagnosticsBundled 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 communicationsEmail, 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.

Service / direct Android versionFunctionPartner information
AdjustUnity 5.8.3Attribution, usage analytics and ad-revenue measurementPrivacy / legal information ↗
TopOn6.6.41Ad mediation, bidding and impression revenuePrivacy / legal information ↗
Unity Ads4.20.0Ad delivery and measurementPrivacy / legal information ↗
Meta Audience Network6.22.0Ad delivery and measurementPrivacy / legal information ↗
Google AdMob25.4.0Ad delivery, measurement and fraud preventionPrivacy / legal information ↗
DT Exchange / Digital Turbine8.4.7Ad exchange and measurementPrivacy / legal information ↗
Mintegral17.1.71Ad delivery and measurementPrivacy / legal information ↗
AppLovin13.6.3Ad delivery and measurementPrivacy / legal information ↗
Pangle8.2.0.4Ad delivery and measurementPrivacy / legal information ↗
ironSource Ads / Unity9.2.0Ad delivery and measurementPrivacy / legal information ↗
InMobi11.4.0Ad delivery and measurementPrivacy / legal information ↗
BIGO Ads6.0.0Ad delivery and measurementPrivacy / legal information ↗
Moloco4.11.1Ad delivery, bidding and measurementPrivacy / legal information ↗

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
INTERNETNetwork access for ads, analytics and related content; not blanket consent to upload data.
ACCESS_NETWORK_STATE · ACCESS_WIFI_STATENetwork/Wi-Fi status checks; available fields are restricted by the OS.
CHANGE_WIFI_STATEDeclared by merged dependencies; no game feature changing Wi-Fi was found. Verify necessity before release.
VIBRATEHaptic feedback, controlled by the in-game vibration setting.
com.google.android.gms.permission.AD_ID · ACCESS_ADSERVICES_AD_IDAdvertising-identifier capabilities where allowed by the OS.
ACCESS_ADSERVICES_ATTRIBUTION · ACCESS_ADSERVICES_TOPICSDeclared 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_LICENSEInstall-referrer, attribution or store-check capabilities; not evidence of in-app purchases.
WAKE_LOCK · FOREGROUND_SERVICEDeclared playback/task capabilities; no game-operated persistent foreground-service feature was found.
com.maze.arrowrelax.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSIONProtection 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:

RecordObserved retention behaviorRequired confirmation
Game preferences and local countersRemain on the device until cleared, overwritten or removed by the OS.OS backup/restore behavior and production backup exclusions.
Saved media and playback cachesDownloads 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 recordsDepend 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 diagnosticsExist 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.

  1. 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.
  2. 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.
  3. 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.

App: Arrow Relax Maze

Responsible developer: TO COMPLETE: full name

Privacy email: TO COMPLETE: a monitored address handling requests

Address / relevant representative: TO CONFIRM under actual identity and applicable law

Request content: identify the App, request type and reply channel; do not volunteer unrelated sensitive information.

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.

  1. Complete the responsible identity, monitored privacy email, necessary address/representative, effective date and distribution regions.
  2. Determine the actual audience and assess child/family requirements and SDK restrictions.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. Review and minimize merged permissions; verify network protection, backups and diagnostic logging.
  8. 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.
  9. 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.json
  • Assets/Editor/AdjustDependencies.xml
  • Assets/Editor/TopOnDependencies.xml
  • Assets/Plugins/Android/TopOnConfig.androidlib/AndroidManifest.xml
  • Assets/Editor/TopOnAndroidBuild.cs
  • Assets/Scripts/AdjustAnalytics.cs
  • Assets/Scripts/AdjustEvents.cs
  • Assets/Scripts/AdService.cs
  • Assets/Scripts/InternalAdTest.cs
  • Assets/Scripts/SagaApp.cs
  • Assets/Scripts/Views.cs
  • Assets/Scripts/StreamingAssetFile.cs
  • Assets/Plugins/iOS/TopOnAdBridge.mm
  • Builds/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.

ARROW RELAX MAZE · PRIVACY BY DISCLOSURE