本隐私政策说明手机限时锁 Android 海外版（亦称「TickLock」「本应用」「我们」）在您使用我们的移动应用程序及相关服务时，如何收集、使用、存储与共享信息。TickLock 定位为自律与亲友/伴侣监督工具。我们仅收集实现核心功能所必需的信息，并就平台权限保持透明。
应用与开发者信息 / App & Developer
- 应用名称 / App Name：手机限时锁（TickLock）
- 应用包名 / Package Name：com.haloutongxue.offly
- 开发者名称 / Developer：杭州哈喽同学网络科技有限公司
- 开发者联系方式 / Contact：server@haloutongxue.com（或应用内「设置 → 反馈」）
- 官方网站 / Website：https://global.haloutongxue.com/discipline.html
1. 我们是谁
本应用「手机限时锁」（包名：com.haloutongxue.offly）由杭州哈喽同学网络科技有限公司开发并运营。官方网站为 https://global.haloutongxue.com/discipline.html。如您有隐私相关问题，可通过应用内「反馈」功能联系我们，发送邮件至 server@haloutongxue.com，或访问我们的官方网站。
2. 我们收集的信息
视您使用 TickLock 的方式，我们可能处理下列类别的信息。我们不会出售您的个人信息。
我们仅在实现对应功能所必需时处理信息。无障碍、使用情况访问与软件安装列表等敏感能力，仅在您使用相关锁定功能并授权时访问。激励广告相关 SDK 仅在您主动进入激励广告流程时初始化。
- 账号与身份：Google 账号标识（及可选的邮箱 OTP 标识）、您授权的显示名/头像，以及维持登录状态所需的会话令牌；由 Google Sign-In 或海外认证后端（Supabase）提供。
- 监督关系数据：您的 6 位监督码、邀请、您为监督人设置的昵称/头像，以及关系状态（「监督我的人」/「我监督的人」）。
- 应用锁定配置：锁定规则、时间表、时长限制、所选应用令牌/标识符、您选择的解锁密码或验证输入，以及执行状态。
- 软件安装列表：在您使用「选择应用 / 应用锁」功能时，通过系统 PackageManager 查询本机可启动应用列表（含应用名称、包名与图标），用于配置锁定目标。
- 本机安装标识（installId）：应用在本机生成的随机标识，用于匿名建户与会话恢复；非 IMEI / IMSI / MAC 地址。
- 您创建的 Safebox 内容：私人笔记、私人联系人（您输入的姓名/电话/邮箱），以及您导入的私人照片/视频。上述内容主要为您使用 Safebox 功能而存储。
- 锁定所需的使用与设备信号：无障碍服务事件与使用情况访问（PACKAGE_USAGE_STATS），用于检测前台应用并施加屏蔽。前述使用情况访问仅在您开启相关权限且使用锁定功能时发生。
- 会员与商业数据：VIP/会员状态、到期时间，以及通过 RevenueCat 与 Google Play 结算处理的购买相关记录（付款明细由 Google 按其政策处理）。
- 广告互动数据：当您通过广告聚合合作伙伴（GroMore / Pangle 技术栈）观看激励广告（例如免费锁定时长奖励）时，可能在适用的同意框架下处理广告标识符与广告事件信号。
- 您提交的反馈：消息内容、可选联系方式与时间戳。
- 本地偏好：语言、小组件配置等存储于设备本地的设置（例如通过本地数据库 / SharedPreferences）。
- 技术日志：有助于保障服务稳定的基本诊断信息，例如 API 错误或执行失败。此类信息不会用于广告画像。
3. 我们申请的权限
TickLock 仅在功能需要时申请系统权限。您可在系统设置中拒绝或撤销权限；部分功能届时将不可用。
- 无障碍与使用情况访问（Android）：检测前台应用并持续执行锁定。
- 悬浮窗（Android）：在部分机型上展示锁定遮罩页。
- 忽略电池优化（Android）：保障锁定拦截在后台持续生效。
- 开机相关（Android）：开机后检测无障碍服务是否仍开启（详见「自启动与关联启动」）。
- 前台服务与精确闹钟（Android）：有锁规则时保活进程，并准时执行锁定（详见「自启动与关联启动」）。
- 通知与全屏通知（Android）：提醒锁定状态，并在需要时拉起锁定/解锁页。
- 照片与视频图库：选择个人头像与监督人头像；为意见反馈添加图片。
- 照片与视频图库（Android）：将照片/视频导入 Safebox；确认后可删除图库原件。
- 网络访问：登录、数据同步与激励广告等联网功能。
- 主屏幕小组件：使用共享本地数据展示 TickLock 小组件内容（系统刷新小组件时可能短暂拉起本应用进程，详见「自启动与关联启动」）。
自启动与关联启动（Android）
为保障应用锁定在系统清理后台后仍可生效，本应用（Android）可能于下列合理场景下发生自启动或关联启动（含进程被系统或小组件框架短暂拉起）。我们不会在无对应功能需求时无故频繁拉起；亦不会将自启动用于广告。
- 场景与目的：您已创建并启用限时锁 / 手机锁等锁定规则时，为重绑无障碍服务、检测前台应用并展示锁定页，可能通过开机广播、精确闹钟与前台服务进行保活；开机后若发现无障碍被系统关闭，可能发通知引导您重新开启。
- 桌面小组件：若您已将「限时锁」小组件添加到桌面，系统或小组件框架（含 androidx.glance.appwidget 相关组件）在更新卡片内容时，可能短暂启动本应用进程；目的仅为展示您配置的锁任务预览，不用于广告或与锁定无关的关联启动第三方应用。
- 同意要求：仅在上述锁定规则和/或桌面小组件场景下产生相关行为；不会将自启动用于广告或无关关联启动。
4. 我们如何使用信息
我们将信息用于：
- 提供应用锁定、时间表、使用限额、屏蔽与解锁流程。
- 启用您选择配置的监督邀请、监督码与远程问责功能。
- 运营 Safebox（密码门禁、私人笔记/联系人/媒体）。
- 维护您的账号、会员权益与购买状态。
- 在您选择参与时投放激励广告并提供相关免费时长奖励。
- 回应反馈，并提升可靠性与安全性。
- 遵守法律、防止滥用，并保护用户、监督人与服务。
5. 本地处理与云端同步
TickLock 的许多敏感功能依赖端侧机制：Android 上的无障碍服务与使用情况访问（PACKAGE_USAGE_STATS），以及用于规则与 Safebox 内容的本地 SQLite 存储。
账号、监督关系、会员状态及其他服务功能可能与我们的后端服务器同步，以便在与您登录关联的会话与设备间正常工作。我们仅传输上述功能所需的信息。产品信息发布于 https://global.haloutongxue.com/discipline.html。
我们不会声称读取您锁定的第三方应用内容。锁定使用平台令牌/软件包标识符与系统 API，而非截屏或完整抓取其他应用内容。
6. 共享与第三方
我们仅在有限情形下共享信息：
- 服务提供商：托管、支付处理，以及在合同约束下代表我们处理数据的广告合作伙伴。
- Google：若您使用 Google 登录，Google 将依据其条款与隐私政策提供身份验证数据。Supabase：海外账号与会话由 Supabase 按其隐私政策处理。
- 您邀请的监督人：通过监督码连接的人员，可看到监督/解锁流程所需的关系信息与参与情况。请谨慎选择监督人。
- 法律要求：在适用法律、法规、法律程序要求下，或为保护权利与安全，我们可能披露信息。
7. 第三方 SDK 清单
为实现登录、云同步、应用内购买与激励广告等功能，本应用在 Android 海外版集成下列第三方 SDK。广告相关 SDK 仅在您主动进入激励广告流程时初始化。本应用不将广告相关数据用于跨其他公司的 App 或网站跟踪用户。
7.1 Google Sign-In
- SDK名称：Google Sign-In / Google Play services identity
- 开发者：Google LLC
- 收集信息范围：您授权的 Google 账号标识与基本资料信息
- 使用目的：海外 Android 主登录与账号绑定
- SDK隐私政策链接：https://policies.google.com/privacy
7.2 Supabase（认证与后端）
- 服务名称：Supabase Auth / Backend
- 开发者：Supabase, Inc.（及相关基础设施）
- 收集信息范围：账号标识、邮箱 OTP 相关字段（如使用）、会话令牌，以及海外同步所需的应用数据（如监督关系、会员状态镜像）
- 使用目的：认证、会话保持与海外数据同步
- 隐私政策链接：https://supabase.com/privacy
7.3 RevenueCat / Google Play Billing
- SDK / 服务：RevenueCat；Google Play Billing
- 开发者：RevenueCat, Inc.；Google LLC
- 收集信息范围：购买令牌、商品标识、权益状态，以及购买校验所需的有限设备/应用标识
- 使用目的：处理与恢复海外 Android 会员购买
- 隐私政策链接：https://www.revenuecat.com/privacy ；https://policies.google.com/privacy
7.4 Pangle / GroMore 广告 SDK
- SDK名称：Pangle Ads SDK（含 GroMore 聚合）
- 开发者：Beijing ByTEDANCE Network Technology Co., Ltd.（Pangle / GroMore）
- 收集信息范围：广告投放、归因与反作弊所需的设备与广告事件信号（具体以该 SDK 隐私政策为准）
- 使用目的：激励广告及您选择参与时的相关免费时长奖励
- SDK隐私政策链接：https://www.pangleglobal.com/privacy
8. Safebox、媒体与敏感内容
Safebox 用于存放个人私密内容。您自行决定导入内容。请勿存储您无权合法持有的内容。
（Android）若您授权在导入后从系统相册删除原件，该操作将按您的请求执行。确认删除前请备份重要媒体。
Safebox 密码保护是产品安全功能，并不能保证在设备被入侵、越狱/Root、取证提取，或他人已知您的解锁方式时仍绝对安全。
9. 儿童与家庭使用
TickLock 可用于个人自律或相互监督。若您与儿童一起或为儿童使用本应用，您有责任依据适用法律取得所需同意，并合理配置监督。
我们不会在知情情况下将本应用营销为以广告为目的收集儿童个人数据的服务。家长或监护人应在儿童设备上启用锁定或媒体功能前审阅权限。
10. 数据保留
在您的账号保持有效且为提供服务所需期间，我们保留账号与关系数据。本地 Safebox 与锁定配置会保留在您的设备上，直至您删除、清除应用数据或卸载本应用（受操作系统备份行为影响）。
在法律、会计或安全原因要求时，我们可能更长时间保留有限记录（例如购买历史、防欺诈日志或反馈）。
11. 您的选择与权利
您可以：
- 在 Android 系统设置中撤销平台权限。
- 在应用内断开监督关系。
- 编辑您控制的个人资料昵称/头像与 Safebox 内容。
- 通过「反馈」提交请求或问题。
- 停止使用本应用，并在法律要求且技术可行时请求协助进行与账号相关的删除。
12. 安全
我们采取与数据性质相适应的合理管理、技术与组织措施（例如经验证的 API 访问，以及 Safebox 的端侧访问控制）。任何传输或存储方式都无法做到百分之百安全。
13. 国际用户
服务器与服务提供商可能在与您居住地不同的司法管辖区处理数据。使用本应用即表示您理解，您的信息可能被传输至隐私法律不同的地点。
14. 本政策的变更
我们可能更新本隐私政策，以反映产品、法律或运营变化。我们将修订「最近更新」日期，并在适当时就重大变更提供应用内通知。
15. 联系方式
开发者：杭州哈喽同学网络科技有限公司。隐私咨询：请使用应用内「设置 → 反馈」，或发送邮件至 server@haloutongxue.com，或访问 https://global.haloutongxue.com/discipline.html。请提供足以识别您请求的信息（请勿发送不必要的敏感内容）。
This Privacy Policy explains how 手机限时锁 (also referred to as “TickLock”, “the App”, “we”, “us”, or “our”) collects, uses, stores, and shares information when you use our Android overseas edition and related services. We designed TickLock as a self-discipline and parental/partner supervision tool. We aim to collect only what is needed to operate core features and to be transparent about platform permissions.
应用与开发者信息 / App & Developer
- 应用名称 / App Name：手机限时锁（TickLock）
- 应用包名 / Package Name：com.haloutongxue.offly
- 开发者名称 / Developer：杭州哈喽同学网络科技有限公司
- 开发者联系方式 / Contact：server@haloutongxue.com（或应用内「设置 → 反馈」）
- 官方网站 / Website：https://global.haloutongxue.com/discipline.html
1. Who We Are
The App is operated in connection with the TickLock / Discipline Lock service. Our official website is https://global.haloutongxue.com/discipline.html. If you have privacy questions, contact us through the in-app Feedback feature, email server@haloutongxue.com, or visit our official website.
2. Information We Collect
Depending on how you use TickLock, we may process the categories below. We do not sell your personal information.
We process information only as needed for each feature. Sensitive capabilities such as Accessibility, Usage Access, and the installed-app list are accessed only when you use related locking features and grant the corresponding permissions. Ad-related SDKs initialize only when you enter a rewarded-ad flow.
- Account & identity: Google account identifiers (and optional email OTP identifiers), display name/avatar when provided, and session tokens; provided by Google Sign-In or our overseas auth backend (Supabase).
- Supervisor relationship data: your 6-digit supervise code, invitations, nicknames/avatars you set for supervisors, and relationship status (“people supervising me” / “people I supervise”).
- App-lock configuration: lock rules, schedules, duration limits, selected app tokens/identifiers, unlock passwords or verification inputs you choose, and enforcement status.
- Installed app list: when you configure app locks, the App queries launchable apps via PackageManager (name, package name, icon) so you can pick apps to lock.
- Safebox content you create: private notes, private contacts (name/phone/email you enter), and private photos/videos you import. These are stored primarily for your use of the Safebox feature.
- Usage & device signals needed for locking: Accessibility Service events and Usage Access (PACKAGE_USAGE_STATS) needed to detect foreground apps and apply shields.
- Membership & commercial data: VIP/membership status, expiry, and purchase-related records processed through RevenueCat and Google Play Billing (payment details are handled by Google under its policies).
- Advertising interaction data: when you watch rewarded ads (for example, free lock-time rewards) via our ad mediation partner (GroMore / Pangle stack), advertising identifiers and ad event signals may be processed under applicable consent frameworks.
- Feedback you submit: message content, optional contact details, and timestamps.
- Local preferences: language, widget configuration, and similar settings stored on device (for example via local database / SharedPreferences).
- Technical logs: basic diagnostics such as API errors or enforcement failures that help us keep the service reliable. These are not used for advertising profiling.
- Device install identifier (installId): a random on-device installId used for anonymous account bootstrap and session recovery (not IMEI / IMSI / MAC).
3. Permissions We Request
TickLock requests system permissions only when a feature needs them. You can deny or revoke permissions in system settings; some features will then be unavailable.
- Accessibility & Usage Access (Android): detect app usage and enforce locks consistently in the background.
- Photo Library: choose a profile or supervisor avatar; attach images to feedback.
- Photo Library (Android): import media into the private album; optionally remove originals from the system gallery after a confirmed import.
- Notifications: remind you about lock state and help open the unlock flow.
- Home-screen widgets: show TickLock widget content using shared local data (the system may briefly start the app process when refreshing widgets; see Autostart notes).
4. How We Use Information
We use information to:
- Provide app locking, schedules, usage limits, shields, and unlock flows.
- Enable supervisor invitations, supervise codes, and remote accountability features you choose to set up.
- Operate Safebox (password gate, private notes/contacts/media).
- Maintain your account, membership benefits, and purchase status.
- Deliver rewarded ads and related free-time rewards when you opt in.
- Respond to feedback and improve reliability and safety.
- Comply with law, prevent abuse, and protect users, supervisors, and the service.
5. Local Processing vs. Cloud Sync
Much of TickLock’s sensitive functionality relies on on-device mechanisms: Accessibility Service and Usage Access (PACKAGE_USAGE_STATS) on Android, and local SQLite storage for rules and Safebox content.
Account, supervisor relationships, membership status, and other service features may sync with our backend servers so they work across sessions and devices associated with your login. We transmit only what those features require. Product information is published at https://global.haloutongxue.com/discipline.html.
We do not claim to read the contents of third-party apps you lock. Locking uses platform tokens/package identifiers and system APIs, not screenshots or full content capture of other apps.
6. Sharing & Third Parties
We share information only in limited situations:
- Service providers: hosting, payment processing, crash/diagnostic tooling, and ad mediation partners that process data on our behalf under contractual controls.
- Google: if you sign in with Google, Google provides authentication data according to Google’s terms and privacy policy. Supabase: overseas accounts and sessions are processed according to Supabase’s privacy policy.
- Supervisors you invite: people you connect via supervise codes can see relationship information and participation needed for supervision/unlock flows you enable. Choose supervisors carefully.
- Legal requirements: we may disclose information if required by applicable law, regulation, legal process, or to protect rights and safety.
7. Third-Party SDK List
To provide sign-in, cloud sync, in-app purchases, and rewarded ads, the Android overseas edition integrates the third-party SDKs below. Ad-related SDKs initialize only when you enter a rewarded-ad flow. This app does not use ad-related data to track users across other companies’ apps or websites.
7.1 Google Sign-In
- SDK name: Google Sign-In / Google Play services identity
- Developer: Google LLC
- Data processed: Google account identifiers and basic profile information you authorize
- Purpose: Overseas Android primary sign-in and account linking
- SDK privacy policy: https://policies.google.com/privacy
7.2 Supabase (auth & backend)
- Service: Supabase Auth / Backend
- Provider: Supabase, Inc. (and related infrastructure)
- Data processed: account identifiers, email OTP related fields when used, session tokens, and app data required for overseas sync (e.g. supervisor relationships, membership status mirrors)
- Purpose: Auth, session persistence, and overseas data sync
- Privacy policy: https://supabase.com/privacy
7.3 RevenueCat / Google Play Billing
- SDK / service: RevenueCat; Google Play Billing
- Providers: RevenueCat, Inc.; Google LLC
- Data processed: purchase tokens, product identifiers, entitlement status, and limited device/app identifiers needed for purchase validation
- Purpose: Process and restore membership purchases on overseas Android
- Privacy policies: https://www.revenuecat.com/privacy ; https://policies.google.com/privacy
7.4 Pangle / GroMore ad SDK
- SDK name: Pangle Ads SDK (including GroMore mediation)
- Developer: Beijing ByTEDANCE Network Technology Co., Ltd. (Pangle / GroMore)
- Data processed: advertising and device signals needed for ad delivery, attribution, and anti-fraud (details per the SDK privacy policy)
- Purpose: Rewarded ads and related free-time rewards when you opt in
- SDK privacy policy: https://www.pangleglobal.com/privacy
8. Safebox, Media & Sensitive Content
Safebox is intended for personal private content. You control what you import. Do not store content you are not legally allowed to possess.
(Android) If you authorize deletion of originals from the system photo library after import, that action is performed at your request. Back up important media before confirming deletion.
Safebox password protection is a product security feature, not a guarantee against a compromised device, jailbreak/root, forensic extraction, or someone who already knows your unlock method.
9. Children & Family Use
TickLock can be used for personal discipline or mutual supervision. If you use the App with or for a child, you are responsible for obtaining any consent required under applicable law and for configuring supervision appropriately.
We do not knowingly market the App as a service that collects personal data from children for advertising purposes. Parents or guardians should review permissions before enabling locking or media features on a child’s device.
10. Data Retention
We retain account and relationship data while your account remains active and as needed to provide the service. Local Safebox and lock configurations remain on your device until you delete them, clear app data, or uninstall the App (subject to OS backup behavior).
We may retain limited records (for example, purchase history, fraud-prevention logs, or feedback) for longer when required for legal, accounting, or security reasons.
11. Your Choices & Rights
You may:
- Revoke platform permissions in Android system settings.
- Disconnect supervisor relationships in the App.
- Edit profile nickname/avatar and Safebox content you control.
- Submit requests or questions through Feedback.
- Stop using the App and request account-related deletion assistance where legally required and technically feasible.
12. Security
We use reasonable administrative, technical, and organizational measures appropriate to the nature of the data (for example, authenticated API access and on-device access controls for Safebox). No method of transmission or storage is 100% secure.
13. International Users
Servers and service providers may process data in jurisdictions different from where you live. By using the App, you understand that your information may be transferred to locations where privacy laws differ.
14. Changes to This Policy
We may update this Privacy Policy to reflect product, legal, or operational changes. We will revise the “Last updated” date and, where appropriate, provide in-app notice for material changes.
15. Contact
For privacy inquiries: use Settings → Feedback in the App, email server@haloutongxue.com, or visit https://global.haloutongxue.com/discipline.html. Please include enough detail for us to identify your request (without sending unnecessary sensitive content).