更新日期：2026 年 9 月 18 日 · 版本 3.3（补充 TapTap 登录输入信息说明）
本政策适用于《寂海防线》Android 测试版，包括 Google Play 和 TapTap 渠道。不同渠道使用的服务分别说明。
匿名游玩统计默认关闭。只有在玩家主动勾选后，游戏才在应用私有存储中生成随机安装编号，并记录启动、游玩时长、章节进度、失败点、生存波次、成就和游戏版本。本游戏的一方匿名统计不读取 Android ID，也不收集姓名、手机号、广告标识、位置、通讯录、相册、麦克风、摄像头或精确操作轨迹。
数据只用于估算安装实例数、查看玩家在哪一关卡住，以及改进游戏，并通过 HTTPS 发送。随机安装编号在关闭统计或清除应用数据时删除，不能跨应用跟踪，也不能准确代表真实自然人人数。
首次运行先显示 Android 原生隐私选择页；玩家作出选择前，不初始化游戏框架、渲染、音频或统计。玩家可不勾选匿名统计并正常进入游戏，也可在“设置 → 匿名游玩统计”中随时关闭；关闭后停止发送统计事件，并清除尚未上传的数据和本地随机安装编号。已上传的原始事件最多保存 180 天。
游戏使用开源 LibGDX 处理画面、触控、音频、文件和网络（原测试版 1.12.1，Google Play 双语构建 1.14.2）。LibGDX 只在玩家同意本政策后初始化；本游戏已关闭不需要的运动传感器。LibGDX 不作为独立统计服务向其开发者发送玩家数据。
选择邮箱登录时，TapTap（易玩〔上海〕网络科技有限公司）通过登录页面收集您主动输入的电子邮箱地址和验证码，用于发送登录验证码、验证账号并完成登录；选择手机号登录时，相应处理您输入的手机号和验证码。仅在您选择相应方式并提交时处理这些输入信息，不读取您的通讯录、短信或邮箱内容。实名认证流程会处理您提供的姓名、身份证号码，以完成身份核验和防沉迷要求。本游戏仅请求基础账号标识和认证结果，不自行读取、保存上述登录输入信息或将其发送到游戏统计服务。
上述信息由 TapTap 的登录或认证页面接收和处理；保存期限、账号信息更正及删除方式请参阅 TapTap 隐私政策。您可以取消登录或拒绝登录前的提示，不会因此开始 SDK 初始化或登录，但无法进入需认证的 TapTap 渠道游戏。使用手机号登录不要求额外提供邮箱。
仅 TapTap 渠道包集成 TapSDK（提供方：易玩〔上海〕网络科技有限公司），用于 TapTap 账号登录、实名认证、防沉迷限制及服务安全。Google Play 和未启用 TapTap 的其他渠道包不包含此 SDK。
同意本政策并点击“TapTap 登录”后才调用 SDK 初始化与登录。SDK 会处理账号标识（openId、unionId）、认证状态、游戏时长，以及系统版本、设备型号、CPU 与内存信息、Android ID、网络类型等必要信息，用于身份认证、兼容性及故障排查；与服务器通信会涉及 IP 地址。登录仅请求基础账号标识，不请求昵称、头像或好友列表。实名信息由 TapTap 的认证流程处理，本游戏不自行保存玩家姓名或身份证号码，也不请求精确年龄段。
同意并使用 TapTap 登录后，TapSDK 可能通过设备接口读取 OAID（开放匿名设备标识符），与 Android ID 等设备信息用于登录、实名认证、防沉迷相关的设备识别及服务运行，不用于本游戏的广告或游玩统计。游戏不将 OAID 写入存档或发送至游戏统计服务。
登录前会显示个人信息使用提示，只有点击“同意并登录”才启动 TapTap 服务。不同意则不启动该服务。TapSDK 的可选统计保持关闭，与游戏的匿名游玩统计开关无关。
第三方登录及合规认证与本游戏可选的一方匿名统计分别处理，关闭匿名统计不会免除实名认证和防沉迷检查。首次启动及隐私同意版本更新后，玩家须主动点击同意；浏览政策、切换语言或拒绝均不视为同意。取消登录、认证未完成或受到防沉迷限制时无法进入游戏。SDK 所需的联网和网络状态权限为 Android 普通权限。
SDK 数据处理、保存及用户权利说明请参阅 TapSDK 隐私政策及合规使用说明。可通过 TapTap 账号设置管理账号与授权；也可联系其隐私政策中列明的联系方式行使个人信息权利。
游戏进度仍保存在本机，切换 TapTap 账号不会切换本地存档。卸载、清除应用数据可能删除本地进度；TapPlay 沙箱存档不保证与独立安装互通。
所有渠道均不接入广告或支付服务。
未启用 TapTap 的独立测试版及 Google Play 双语测试版没有接入广告、支付、社交登录、TapDB 或其他第三方统计 SDK，也不会出售统计数据。如需反馈或申请删除，可通过 shudal@qq.com 或 TapTap《寂海防线》页面联系我们；以后增加新的数据收集时会先更新本页。
Updated September 18, 2026 · Version 3.3. TapTap sign-in input disclosure.
This policy applies to Android test builds of Silent Sea Defense (寂海防线), including Google Play and TapTap. Channel-specific services are described separately.
Optional gameplay analytics is off by default. Only after you opt in does the game generate a random installation identifier in private app storage and record launches, play duration, chapter progress, failure points, survival waves, achievements, and game version. Our first-party gameplay analytics does not read Android ID or collect names, phone numbers, advertising identifiers, location, contacts, photos, microphone or camera data, or precise input histories.
Analytics is used only to estimate installation instances, understand where players encounter difficulty, and improve the game. Data is transmitted over HTTPS. The local random identifier is deleted when analytics is disabled or app data is cleared. It cannot track you across apps and does not accurately identify the number of individual people.
On first launch, a native Android privacy screen appears before the game framework, rendering, audio, or analytics is initialized. You can leave analytics unchecked and still play. You may turn it off at any time in Settings → Usage Analytics. Turning it off stops analytics transmission and deletes pending events and the local random installation identifier; it does not automatically erase previously uploaded records. Uploaded raw events are retained for no more than 180 days.
The game uses the open-source LibGDX framework for graphics, touch input, audio, files, and networking (1.12.1 in the original test build; 1.14.2 in the Google Play bilingual build). It is initialized only after you accept the privacy policy. Unneeded motion sensors are disabled. LibGDX is not used as a separate analytics service and does not receive player data for its developers.
If you choose email sign-in, TapTap (Yiwan (Shanghai) Network Technology Co., Ltd.) collects the email address and verification code you enter on its login page to send a login code, verify your account and sign you in. Phone sign-in similarly processes your phone number and verification code. These inputs are processed when you choose and submit that method; this does not involve reading your contacts, text messages or mailbox contents. Real-name verification processes the legal name and ID number you provide for identity checks and play-time restrictions. The game only requests basic account identifiers and verification results; it does not independently read or store these login inputs or send them to gameplay analytics.
TapTap receives and processes these details on its login or verification pages. See the TapTap Privacy Policy for retention, correction and deletion options. You can cancel login or decline the pre-login notice; declining the notice does not start SDK initialization or login, but prevents entry into the TapTap game that requires verification. Phone sign-in does not require an additional email address.
Only the TapTap build includes TapSDK, provided by Yiwan (Shanghai) Network Technology Co., Ltd., for account login, real-name verification, play-time restrictions and service security. Google Play and other builds without TapTap enabled do not include it.
TapSDK initialization and login are invoked after consent and a tap on Sign in with TapTap. The service processes account identifiers (openId and unionId), verification status, play time, system version, device model, CPU and memory information, Android ID and network type for authentication, compatibility and troubleshooting. Server connections involve an IP address. We request basic account identifiers, not profile names, avatars, friend lists or precise age ranges. Identity information is handled by TapTap's verification flow; the game does not independently store your legal name or identity-document number.
After you agree and choose TapTap sign-in, TapSDK may read OAID (Open Anonymous Device Identifier) through device interfaces, alongside Android ID, for device identification and operation of sign-in, identity verification and play-time restrictions. It is not used for this game's advertising or gameplay analytics. The game does not store OAID in game saves or send it to gameplay analytics.
A privacy notice appears before sign-in. TapTap services start only when you choose Agree and sign in. Declining does not start the service. Optional TapSDK analytics remains disabled independently of the game's optional gameplay analytics setting.
Disabling our gameplay analytics does not bypass the required identity and play-time checks. Explicit consent is required at first launch and after the consent version changes; reading the policy, switching languages or declining does not count as consent. Cancelling login or verification, or being subject to a restriction, prevents entry into the game. Internet and network-state access use ordinary Android permissions.
See the TapSDK Privacy Policy and compliance guide for the provider's data handling and retention. Manage your account and authorizations in TapTap, or use the privacy contacts listed in its policy to exercise your rights.
Progress stays on this device. Switching TapTap accounts does not switch local saves. Uninstalling or clearing app data can delete progress. TapPlay sandbox saves are not guaranteed to transfer to a separately installed app.
No channel includes advertising or payment services.
Google Play and standalone builds without TapTap contain no advertising, payments, social sign-in, TapDB, or other third-party analytics SDKs. We do not sell analytics data. For feedback or a deletion request, contact shudal@qq.com or use the game's TapTap page. We will update this policy before adding new data collection.