ScreenTime Privacy Policy
This Privacy Policy explains how ScreenTime accesses, collects, uses, shares, stores, and deletes data related to users. ScreenTime is a screen time statistics and app limit tool. Its core features include viewing app usage, setting limits for apps or categories, showing a blocking screen when a limit is reached, displaying monitoring notifications, and providing local gesture verification.
ScreenTime does not sell user data, does not use screen time records for advertising, and does not upload detailed app usage duration, opening counts, foreground app history, or gesture patterns to the developer server. If the user accepts app category lookup, package names of launchable apps may be sent to ScreenTime's app category service only to identify app categories.
1. Developer
ScreenTime is provided by the developer listed for this app on Google Play.
2. Data We Access or Process
| Data type | Purpose | Processing method |
|---|---|---|
| App usage data | Show daily and weekly screen time, calculate usage by app or category, identify the current foreground app, and determine whether a user-configured limit has been reached. | Read and calculated locally on the device through Android Usage Access. ScreenTime does not upload detailed usage duration, opening counts, foreground app records, or usage history to the developer server. |
| Launchable app list and package names | Allow users to choose apps for limits, display app lists, identify app categories, and configure always-allowed apps. | The app list is mainly processed locally. If the user accepts app category lookup, ScreenTime sends package names only to the app category service to return category, developer, and age-rating information. Usage duration and account information are not sent. |
| User-configured limits and preferences | Save app limits, category limits, daily total limits, allowed hours, temporary extensions, dismiss-for-today choices, notification preferences, theme preferences, and always-allowed apps. | Stored in the local database or local preferences on the device. If the user enables system backup, these local settings may be backed up by Android or Google account backup mechanisms. |
| Gesture verification data | Verify user actions before extending or dismissing limits, helping prevent unauthorized changes. | The gesture is not stored in plain text. ScreenTime stores only a salted hash locally on the device for local comparison and does not upload it to the developer server. |
| Permission state and in-app interaction events | Understand whether core features are available, analyze feature usage, and improve product experience and reliability. | Processed through Firebase Analytics. Events may include screen views, feature entry clicks, permission states, whether limits are enabled, rule count buckets, duration buckets, and target types. ScreenTime does not intentionally send specific package names, exact usage duration, or gesture patterns through analytics. |
| Crash and diagnostic data | Identify crashes, errors, and compatibility issues. | Processed through Firebase Crashlytics. This may include crash stack traces, device model, operating system version, app version, crash time, and related diagnostic identifiers. |
| Network request technical data | Complete app category lookup, maintain service security, prevent abuse, and troubleshoot service errors. | When the app accesses the ScreenTime category service or Firebase services, servers and service providers may process IP address, request time, app version, and device or network-related technical information. |
3. Permissions We Use
Usage Access (PACKAGE_USAGE_STATS)
ScreenTime needs this permission to read app usage statistics on the device, display screen time, calculate app or category usage, identify the current foreground app, and enforce limits configured by the user. Without this permission, core statistics and limit features cannot work properly. Detailed usage records are processed locally and are not uploaded to the developer server.
Foreground Service (FOREGROUND_SERVICE, FOREGROUND_SERVICE_SPECIAL_USE)
ScreenTime uses a foreground service to continuously monitor whether the current app has reached a user-configured limit. A persistent notification is shown while monitoring is active.
Notifications (POST_NOTIFICATIONS)
ScreenTime uses notifications to show monitoring status, today's usage summary, and alerts when a limit is reached or user attention is needed. Notifications are not used for advertising or marketing.
Display Over Other Apps (SYSTEM_ALERT_WINDOW)
When a user-configured limit is reached, ScreenTime may show a full-screen blocking page to help the user stop using the limited app. This permission is used only to enforce limits configured by the user and is not used for ads, promotional content, or unrelated pop-ups.
Internet (INTERNET)
ScreenTime uses network access for the app category service, Firebase Analytics, and Firebase Crashlytics. The app category service returns category, developer, and age-rating information based on package names. Firebase is used for aggregated analytics and crash diagnostics.
Start at Boot (RECEIVE_BOOT_COMPLETED)
After the device restarts, ScreenTime uses this permission to restore limit monitoring so enabled limits can continue without requiring the user to manually reopen the app.
App Visibility Queries
ScreenTime queries launchable apps on the device so users can choose which apps to track, limit, or add to the always-allowed list. This does not grant access to SMS, contacts, photos, location, microphone, or camera.
4. How We Use Data
- Provide screen time statistics, app details, category statistics, and usage trends.
- Enforce app, category, and daily total screen time limits configured by the user.
- Display monitoring notifications and blocking screens when limits are reached.
- Save user settings, including limits, always-allowed apps, theme, notifications, and gesture verification preferences.
- Identify app categories based on package names to support category statistics and category limits.
- Improve app experience, reliability, and compatibility through aggregated analytics and crash reports.
- Maintain service security, prevent abuse, and troubleshoot network service issues.
5. Data Sharing and Third-Party Services
ScreenTime does not sell user data, does not share screen time records with advertising networks, and does not share personal and sensitive user data for advertising purposes. To provide and maintain app features, limited data may be processed by the following services:
- ScreenTime app category service (https://screentime.alwaysgreenwater.info/): after user consent, receives package names of launchable apps and returns category, developer, and age-rating information. This service does not receive detailed usage duration, opening counts, foreground app history, or gesture verification data.
- Google Firebase Analytics: processes aggregated in-app events, permission states, and feature usage metrics for product analysis and improvement.
- Google Firebase Crashlytics: processes crash and diagnostic data to identify and fix errors.
- Android/Google system backup: if the user has enabled backup on the device, this app's local settings and database may be backed up to the user's Google account according to Android system rules.
6. Data Security
- ScreenTime keeps app usage statistics and limit rules primarily on the device.
- Gesture verification data is stored locally as a salted hash and is not stored in plain text.
- Network requests are sent over HTTPS.
- We limit data use to providing core features, analyzing aggregated usage, diagnosing errors, and maintaining service security.
7. Data Retention and Deletion
- Local limits, app category cache, always-allowed apps, notification preferences, theme preferences, and gesture hashes remain on the device until the user changes or clears the related settings, uninstalls the app, or clears app data.
- Android system usage records are managed by the operating system. ScreenTime reads those records for local calculation but does not control the system retention period.
- Package names sent to the ScreenTime app category service are used only for category lookup and service security, not for ad targeting or sale.
- Firebase Analytics and Crashlytics data are processed by Google Firebase according to its service terms and retention settings. Users may reset advertising identifiers, restrict tracking permissions where available, or clear app data to reduce future association.
- To request deletion of data that may be retained by the developer server in connection with app category lookup or support requests, contact us at [email protected] and describe the scope of your request.
8. User Choices and Controls
- Users can grant or revoke Usage Access, Notifications, and Display Over Other Apps permissions in Android system settings.
- Users can enable, pause, or delete limit rules in the app, modify always-allowed apps, disable detailed monitoring notifications, or remove gesture verification.
- Users can decline the app category lookup disclosure. If declined, ScreenTime will not send package names to the category service, but some category displays may be incomplete.
- Users can delete locally stored app settings and cache by uninstalling the app or clearing app data.
9. Children's Privacy
ScreenTime is designed for users who want to manage screen time on their own devices. We do not knowingly ask children to provide names, email addresses, phone numbers, precise location, contacts, photos, audio, video, or similar personal information. If a parent or guardian believes a child has provided personal information to us, contact us at [email protected], and we will handle deletion requests according to applicable law.
10. International Processing
Firebase services and the ScreenTime app category service may process data outside the user's country or region. By using the app, relevant data may be processed where these services operate, as described in this Privacy Policy. We take reasonable measures to protect data and limit processing purposes.
11. Changes to This Policy
We may update this Privacy Policy when app features, permissions, third-party services, or legal requirements change. When updated, we will revise the effective date on this page. If a change involves new access, collection, use, or sharing of personal or sensitive user data, we will provide appropriate notice in the app or on the store listing.
12. Developer Contact
If you have questions about this Privacy Policy, data processing, or deletion requests, contact us at [email protected].