中文
本政策适用于 Postcard Routes Studio 提供的 Android 游戏《符文封印》（Rune Seal）。
1. 我们处理哪些数据
设备本地数据
游戏使用 Unity PlayerPrefs 在设备本地保存关卡进度、完成记录、音乐与音效、触感、简化动态效果、增强对比、新手引导和广告隐私界面的本地状态。我们不运营玩家账号、云存档或玩家数据服务器，这些本地进度不会发送给我们。
Google 广告服务数据
游戏接入 Google Mobile Ads（AdMob）SDK 和 Google User Messaging Platform（UMP）。Google 可能自动收集或共享 IP 地址（并推断大致位置）、应用启动和广告互动、崩溃及性能诊断信息，以及 Android 广告 ID、应用集 ID 等设备或账号标识符，用于广告投放与个性化、频次控制、衡量、分析、防欺诈、安全和合规。实际处理受地区、同意选择、设备设置和 Google 政策影响。
详细说明见 Google Mobile Ads SDK 数据披露和 Google 隐私权政策。我们不会通过广告获得玩家的真实姓名、通讯录、短信、聊天内容或精确位置，也不会把本地关卡进度提供给广告平台。
可选的 Firebase Analytics 匿名使用分析
只有在玩家明确选择“允许匿名分析”后，游戏才会启用 Google Firebase Analytics。它可能处理随机应用实例 ID、由掩码 IP 推断的大致地区、设备和系统信息、应用启动和会话，以及关卡开始/完成/失败、操作次数、分数和广告奖励结果等自定义事件，用于衡量推广来源、留存、关卡体验和广告效果。
我们不会向 Firebase 发送姓名、邮箱、聊天或自由文本、精确位置或本地存档。Firebase Analytics 的广告 ID 收集、广告存储、广告用户数据和广告个性化均已关闭；推广归因使用 Google Play Install Referrer。拒绝不影响游戏或广告，玩家可在“设置 → 隐私政策”中随时关闭；关闭后停止收集并重置设备上的分析数据。详情见 Firebase 数据收集说明。
2. 广告形式与选择
- 激励广告只在玩家主动选择后请求，Google 确认奖励后才发放礼包或续关奖励。
- 插屏广告只在部分关卡完成后的自然间隙请求。
- 自适应横幅只出现在首页和关卡选择等非对局页面。
适用地区会显示 UMP 隐私或同意界面；需要时可从“设置 → 广告隐私选项”重新打开。玩家也可通过 Google 我的广告中心管理广告选择。拒绝个性化广告不一定移除全部广告；Google 仍可能提供非个性化或受限广告并处理安全、防欺诈等必要数据。
3. 第三方、权限与安全
当前联网第三方服务为 Google Mobile Ads、UMP，以及玩家主动允许后启用的 Google Firebase Analytics。数据会为上述广告、同意管理、归因、衡量、分析和安全目的传送给 Google 及其广告技术合作方。我们不出售个人数据，也不向数据经纪商提供玩家数据。当前版本未接入账号、支付、云存档、Unity Analytics、Unity Ads、Sentry 或开发者自建分析服务。
INTERNET 和 ACCESS_NETWORK_STATE 用于加载广告与同意界面并判断网络状态；VIBRATE 仅用于玩家开启的触感；AD_ID 用于广告投放、衡量和防欺诈。Google 广告 SDK 还会声明 Android Privacy Sandbox 的广告 ID、归因和 Topics 权限，实际使用受 Android 版本、Google 服务、地区、同意和设备设置影响。Unity 或 Google SDK 依赖会声明 WAKE_LOCK 和 FOREGROUND_SERVICE，用于必要的运行时或广告任务，不会让开发者读取额外的本地游戏进度或敏感内容。AndroidX 的应用内签名权限只限制动态广播接收器。应用不请求相机、麦克风、通讯录、短信、通话记录、通知或精确位置权限。Google 表示 Mobile Ads SDK 使用 TLS 加密传输数据。
4. 保存、删除与控制
本地数据会保留到玩家清除应用数据或卸载游戏为止，可通过 Android“应用信息 → 存储 → 清除数据”删除。我们没有服务器副本，无法远程删除、恢复或导出本地数据。Google 依其政策和玩家设置管理广告及 Firebase Analytics 数据；玩家可在游戏中停用匿名分析并重置设备上的 Firebase 分析数据，也可重置或删除 Android 广告 ID，并使用 Google 账号隐私工具或“我的广告中心”。Google 表示相关 SDK 数据使用 TLS 加密传输。
5. 儿童隐私与国际处理
本游戏面向一般成年休闲益智玩家，并非专门面向儿童。我们不会故意收集 13 岁以下儿童（或当地法律规定的更高最低年龄）的个人数据；在完成相应合规评估前，不会选择 13 岁以下 Google Play 目标受众。Google 可能在玩家所在国家或地区之外处理广告数据，并采用其隐私政策说明的保障措施。
6. 联系与更新
如对本政策、广告隐私选择或游戏的数据处理有疑问，请联系 Postcard Routes Studio：weiwei199344@gmail.com。数据实践、SDK、权限或法律要求变化时，我们会更新本政策和日期，并在适当位置通知重大变化。
English
This policy applies to the Android game Rune Seal, provided by Postcard Routes Studio.
1. Data we process
On-device data
Unity PlayerPrefs stores level progress, completion records, audio and haptic preferences, reduced motion, high contrast, onboarding, and local advertising-privacy interface state. We operate no player accounts, cloud saves, or player-data server, and local gameplay progress is not sent to us.
Google advertising data
The game integrates Google Mobile Ads (AdMob) and Google User Messaging Platform (UMP). Google may automatically collect or share IP address (and estimate general location), app launches and ad interactions, crash and performance diagnostics, Android advertising ID, app set ID, and other device or account identifiers. Purposes may include ad delivery and personalization, frequency capping, measurement, analytics, fraud prevention, security, and compliance. Processing depends on region, consent, device settings, and Google policies.
See the Google Mobile Ads SDK disclosure and Google Privacy Policy. We do not receive a player's real name, contacts, messages, chat content, or precise location through the ads, and do not provide local level progress to the ad platform.
Optional anonymous usage analytics with Firebase Analytics
Google Firebase Analytics is enabled only after the player explicitly chooses Allow Anonymous Analytics. It may process a random app-instance ID, approximate region inferred from a masked IP address, device and operating-system information, app launches and sessions, and custom events such as level starts, completions or failures, move counts, scores, and rewarded-ad results. We use this to measure acquisition sources, retention, level experience, and advertising performance.
We do not send Firebase a name, email address, chat or other free text, precise location, or local-save content. Firebase Analytics advertising-ID collection, ad storage, ad user data, and ad personalization are disabled; campaign attribution uses Google Play Install Referrer. Declining does not affect gameplay or advertising. Players can disable analytics at any time under Settings → Privacy Policy; collection then stops and on-device analytics data is reset. See Firebase data collection.
2. Advertising and choice
- Rewarded ads are requested only after a player chooses to watch one; gifts are granted only after Google confirms the reward.
- Interstitials are requested only at natural breaks after selected completed levels.
- Adaptive banners appear only on non-gameplay screens such as home and level select.
Where required, UMP presents a privacy or consent message and can be reopened from Settings → Ad privacy options. Players can also use My Ad Center. Refusing personalized ads does not necessarily remove all ads; Google may still provide non-personalized or limited ads and process data needed for security and fraud prevention.
3. Third parties, permissions, and security
The current networked third parties are Google Mobile Ads, UMP, and Google Firebase Analytics when the player opts in. Information is transmitted to Google and its ad-technology partners for advertising, consent management, attribution, measurement, analytics, and security. We do not sell personal data or provide it to data brokers. The current release has no player accounts, payments, cloud saves, Unity Analytics, Unity Ads, Sentry, or developer-operated analytics.
INTERNET and ACCESS_NETWORK_STATE load ads and consent interfaces and check network state; VIBRATE supports player-enabled haptics; AD_ID supports ad delivery, measurement, and fraud prevention. The Google advertising SDK also declares Android Privacy Sandbox permissions for ad ID, attribution, and Topics; actual use depends on the Android version, Google services, region, consent, and device settings. Unity or Google SDK dependencies declare WAKE_LOCK and FOREGROUND_SERVICE for required runtime or advertising tasks; these permissions do not give the developer additional local game progress or sensitive content. An AndroidX app-signature permission only restricts dynamic broadcast receivers. The app does not request camera, microphone, contacts, SMS, call-log, notification, or precise-location permissions. Google states that the Mobile Ads SDK encrypts data in transit using TLS.
4. Retention, deletion, and controls
Local data remains until the player clears app storage or uninstalls the game and can be removed through Android App info → Storage → Clear data. We have no server copy to delete, restore, or export. Google controls advertising and Firebase Analytics data under its policies and player settings. Players can disable anonymous analytics in the game and reset on-device Firebase analytics data, reset or delete the Android advertising ID, and use Google privacy tools or My Ad Center. Google states that the relevant SDK data is encrypted in transit using TLS.
5. Children and international processing
Rune Seal is intended for a general adult casual-puzzle audience and is not directed to children. We do not knowingly collect personal data from children under 13 or a higher local minimum age and will not select a Google Play audience below 13 without a separate compliance review. Google may process ad information outside the player's country or region using safeguards described in its privacy policy.
6. Contact and changes
For questions about this policy, advertising privacy choices, or the game's data practices, contact Postcard Routes Studio at weiwei199344@gmail.com. We will update this policy and date when data practices, SDKs, permissions, or legal requirements change and will provide appropriate notice of material changes.