This Privacy Policy is based on the current implementation of the TimeBack app. TimeBack provides screen-time review, daily goals, reclaimed-time records, reflections, challenges, notifications, sharing, and advertising features.
TimeBack provides the following features:
If the user grants Android PACKAGE_USAGE_STATS permission, the app may read the following information from the device:
This information is used to provide usage statistics and compare usage against user goals.
The app may store the following information in a local SQLite database or SharedPreferences:
Based on the current implementation, these local records are not automatically uploaded to frog-im servers.
When Google Mobile Ads SDK (AdMob) and UMP are used, Google or its affiliates may process information such as:
The app processes information for the following purposes:
TimeBack stores user data primarily in the app’s internal storage on the device. Based on the current implementation, usage records, goals, reflections, and challenge information are not automatically uploaded to frog-im servers.
Local storage may include the following.
| Storage | Stored items | Purpose | Deletion method |
|---|---|---|---|
| SQLite database | App usage records, package names, app names, usage time, date-based aggregates | Show usage statistics and compare usage against goals | In-app deletion features, clearing app data, or uninstalling the app |
| SQLite database | Reclaimed-time activities, reflections, challenge progress, checklist entries | Show records and manage progress | In-app deletion features, clearing app data, or uninstalling the app |
| SharedPreferences | Onboarding completion state, reminder settings, hard-limit warning settings, status-bar display settings, overlay exception app list, local ad-consent state | Keep app settings | Clearing app data or uninstalling the app |
| Temporary files/cache | Shared usage-stat images and similar temporary files | Perform sharing requested by the user | Deleted after sharing where possible, or according to OS/app cleanup policies |
When the user clears app data or uninstalls the app, data stored in the app’s internal storage is generally deleted. However, Android backup, manufacturer backup, cloud backup, or files directly shared by the user may be retained separately according to the policies of those services.
Usage records and reflection text may reveal personal routines or interests. On shared devices, users should use appropriate safeguards such as device lock or separate OS accounts.
Based on the current project, TimeBack does not automatically upload usage records, reflections, or challenge records to frog-im servers. If the user uses the sharing feature, a generated statistics image may be transferred to the external app or service selected by the user.
Google AdMob and UMP are used for in-app advertising and consent management. Advertising-related information may be processed on Google infrastructure.
Purpose:
Information that may be processed:
If the user directly uses the usage-stat image sharing feature, the selected external app or service may process the shared image. That processing is governed by the privacy policy of the selected service.
Information may be processed outside the user’s country in the following cases.
| Item | Details |
|---|---|
| Recipient | Google LLC and its affiliates |
| Destination | United States and other countries/regions where Google infrastructure is located |
| Timing | When the app runs, requests ads, shows or measures ads, processes clicks, or handles consent |
| Method | Encrypted network communication (HTTPS/TLS) |
| Purpose | Ad delivery, personalization state handling, measurement, analytics, service stability improvement, legal compliance |
| Data | Advertising identifiers, device/app/network information, ad interaction information, consent state, approximate location, etc. |
| Retention | In accordance with Google’s policies and applicable law |
For details, please see the Cross-Border Transfer Notice.
On Android, if the user configures overlay exception apps, the app may read the package names and app names of launchable apps on the device to display a selection list. Package names selected by the user as exceptions are stored in SharedPreferences on the device and are used only to avoid showing hard-limit warning overlays on top of those apps.
The app retains information under the following standards:
The app may use the following permissions:
PACKAGE_USAGE_STATS: read app usage timePOST_NOTIFICATIONS: show usage reminders and status-bar notificationsSYSTEM_ALERT_WINDOW: show hard-limit warning overlaysINTERNET: communicate with ad SDKs and show legal notice pagesACCESS_NETWORK_STATE: check network statecom.google.android.gms.permission.AD_ID: use advertising identifiersPermissions are used only as needed for app features. Users may revoke permissions in device settings, but related features may be limited.
Users may:
Contact email: g.ns.0700g@gmail.com
The app applies or may apply the following safeguards:
Device security conditions such as rooting, jailbreaking, malware, or shared-device use may create additional risks.
TimeBack is not designed primarily for children. Age-related settings or platform policies of Google Mobile Ads SDK and UMP may apply during advertising and consent processing.
This Policy may be updated due to changes in law, third-party service configuration, or app features. Material changes will be notified through in-app notice or by updating this page.