Time Guard Privacy Policy

Last Updated: 2026-07-27

1. Information We Collect

To provide account access, parent-child device binding, timer control, scheduling, reminders, membership features, troubleshooting, and security protection, we may process:

Account information: email, username, nickname, avatar, and account role.
Device identifiers: a stable device identifier generated by the app and an anonymous guest identifier; on Android, ANDROID_ID may be read during guest sign-in to recognize the same device.
Device and runtime status: device name, platform, online status, permission status, lock status, timer rule status, and heartbeat timestamps.
Usage and business records: timer history, task records, reward redemption records, binding records, notification records, feedback records, and order/payment verification records.
Push identifiers: JPush registration IDs and related push tokens for reminders and device status notifications.
Location information: after you grant location permission, we may collect the latest device coordinates, accuracy, and sampling time to show the distance between parent and child devices, location loss states, and safety alerts.
App usage and installed app information: after you grant usage access, we may read foreground app usage duration, package names, app names, and installed app lists for app limits, foreground app detection, schedule enforcement, and device control.

2. When We Collect Information

Before you agree to this Privacy Policy, we do not initialize the push service for push-related collection.
Before you agree to this Privacy Policy, we do not collect device identifiers, location data, push identifiers, or app usage data for ordinary feature use.
Permissions such as location, notifications, overlay, usage access, accessibility, and device administration are only activated after you choose to authorize the related feature.

3. How We Use Information

To complete registration, sign-in, guest sign-in, account binding, and identity recognition.
To reuse the same guest account on the same device.
To build parent-child device relationships and enforce timers, locks, unlocks, and schedule templates.
To provide reminders, permission alerts, distance display, offline alerts, and safety notifications.
To support tasks, rewards, history, reports, membership, payment verification, and customer support.
To maintain system operations, troubleshoot issues, perform risk control, and satisfy compliance obligations.

4. Permissions and Their Purposes

Notification permission: timer reminders, status reminders, and message notifications.
Camera permission: scanning device binding codes.
Location permission: distance display, location-loss states, and safety alerts between parent and child devices.
Usage access permission: foreground app detection, app usage statistics, app limits, and rule enforcement.
Overlay permission: Android countdown overlays and lock reminders.
Accessibility, device admin, and Device Owner capabilities: Android locking, rule enforcement, foreground app control, and recovery.
Battery optimization exemption and boot/background recovery capabilities: to keep child-side controls, locking, and state sync working more reliably in the background.

5. Sharing, Storage, and Third Parties

We do not sell your personal information.
After you agree to this Privacy Policy and enable related features, we use JPush for message delivery.
Information may be processed by our servers or necessary service providers for push delivery, payment verification, cloud sync, compliance review, or legal obligations.
We retain data only for as long as necessary to provide services, maintain security, resolve disputes, and comply with law.

6. Child Information

Child-side data is used only for guardian-configured family management scenarios. Guardians can manage bindings, delete accounts, or request export/deletion of related data.

7. Your Rights

access, correct, and update account information;
delete your account and related data;
export privacy-related data;
turn off certain permissions or stop certain data processing, although related features may become unavailable.

8. Contact

If you have questions, comments, or complaints about this Privacy Policy or our personal information handling practices, please contact us using the app store developer contact information or the project maintainer contact information.