Last updated: October 15, 2026
TimeGuard is an Android application that helps users monitor application usage, set time limits and schedules, and manage access to selected applications. This Privacy Policy explains what information TimeGuard accesses, how it is processed and stored, and what choices users have.
With the permissions enabled by the user, TimeGuard may access information about installed and active applications, application identifiers, usage durations, activity transitions and relevant timestamps. This information supports usage statistics and enforcement of user-configured limits and schedules.
TimeGuard uses an Android Accessibility Service to identify the application and window currently in use and help enforce restrictions configured by the user.
The service may access application identifiers, window focus, window position and dimensions, including information relevant to picture-in-picture and split-screen modes.
Although Android Accessibility APIs can technically expose window content, TimeGuard's current implementation does not read text or buttons displayed inside other applications.
Users can disable the service in Android Accessibility settings. Some restriction features may then stop working.
When permission is granted, TimeGuard reads Android usage information, including application identifiers, usage durations, activity events, timestamps and activity class names used to reconstruct usage durations.
This information is used for statistics and determining when configured limits have been reached. TimeGuard does not intentionally transmit monitored-app usage histories to Google advertising or analytics SDKs.
TimeGuard stores information required for its functionality locally on the device, including:
The PIN is not stored in plain text. TimeGuard uses a salted PBKDF2 hash for PIN verification.
The application's principal private data and databases are excluded from Android backup and device transfer through its configured backup rules. This does not necessarily cover every file managed by third-party SDKs.
TimeGuard uses Google AdMob to request and display advertisements.
Google's advertising SDK may process IP addresses, technical device and application information, identifiers and advertising interactions for ad delivery, measurement and fraud prevention, subject to applicable settings and consent requirements.
TimeGuard does not intentionally provide users' PINs, monitored-app usage histories or phone numbers entered in the TimeGuard Alert preview to AdMob.
TimeGuard uses Google's User Messaging Platform (UMP) to obtain and manage advertising consent where applicable.
UMP may communicate with Google to determine consent requirements and retrieve consent forms. Available advertising privacy choices can be reviewed through the application's Privacy Options control.
TimeGuard includes Firebase Analytics for limited measurement of application feature usage.
Analytics collection is disabled by default and is enabled only after the user grants separate consent.
The current implementation may record these TimeGuard Alert preview events:
TimeGuard does not attach phone numbers, PINs or selected preview options to these events.
Firebase Analytics may independently process application-instance identifiers, device information and automatically collected events. This information should not be considered completely anonymous.
Users can withdraw Analytics consent in TimeGuard settings. The application then disables collection and resets local Analytics data. Previously processed information retained by Google is not automatically deleted.
TimeGuard Alert is currently a preview of a possible future feature.
It does not send SMS messages, activate paid subscriptions or provide an active remote monitoring service.
Phone numbers entered in the preview are processed temporarily for format validation. They are not saved or transmitted by the current implementation and are cleared when the preview closes.
If TimeGuard Alert becomes available in a future version, this Privacy Policy will be updated to describe the additional processing and service providers involved.
The optional Audio Pause feature processes media-session and playback-state information locally.
TimeGuard can create temporary statistics exports. Exports older than seven days are cleaned up when another export is generated.
If users choose to share an export through another application, that receiving application's privacy practices may apply.
TimeGuard currently integrates services that may independently process technical, advertising, consent or measurement information:
TimeGuard does not currently operate a developer backend for uploading monitored-app usage histories or sending SMS alerts.
Third-party SDK data processing and server-side retention depend on the providers' services, configurations and policies.
Additional information:
Local settings and usage data generally remain on the device until removed through application functionality, Android storage controls or application uninstallation.
Data previously received by third-party services may be retained according to their respective policies.
Users can remove locally stored private application data by clearing TimeGuard's storage or uninstalling the application.
These actions do not automatically delete exported files already shared with other applications or information previously processed by Google services.
Users can manage or revoke Accessibility, Usage Access and notification permissions through Android settings.
Revoking permissions may prevent features that depend on them from functioning correctly.
Advertising privacy choices and optional Firebase Analytics consent can be managed separately through the available application controls.
TimeGuard does not intentionally send the contents of its local monitored-app usage history or the user's PIN to advertising or analytics SDKs.
TimeGuard does not operate a service for selling this local usage history.
The application uses Android security mechanisms and protects PIN verification through salted PBKDF2 hashing.
No electronic storage or transmission method can guarantee absolute security.
Depending on applicable law, users may have rights concerning access, correction, deletion, restriction of processing and withdrawal of consent.
Users control locally stored TimeGuard data through application and Android controls. Information processed independently by Google may be subject to Google's privacy controls.
Use involving children should be supervised by an appropriate parent or guardian. TimeGuard's advertising and distribution settings must correspond to the audience selected in Google Play Console. This policy does not describe TimeGuard as a child-directed service.
This Privacy Policy may be updated to reflect changes in TimeGuard functionality, third-party services or applicable requirements.
The latest revision date will be displayed at the beginning of this document.
For questions about TimeGuard or this Privacy Policy, contact the developer using the support email address published on TimeGuard's Google Play store listing.