TimeMint: Earn Screen Time

Privacy Policy

Effective October 13, 2026

This Privacy Policy explains how Byeshe (“we,” “us,” or “our”) handles information when you use TimeMint: Earn Screen Time (the “Application”), a freemium app with third-party advertising and optional paid subscriptions. Availability of ads, plans, and features may vary by version, region, and configuration. No TimeMint account is required. For privacy questions, contact play@byeshe.com.

Information you enter and local records

The Application stores selected app package names, limits, session start times and durations, earned minutes, balances, Time Bank transactions, goals, achievements, preferences, journal entries, reading and task progress, step totals, exercise results, running and cycling records, and tidy-up photo comparisons. Call-timer records may include a contact name you enter yourself; TimeMint does not read your phone contacts or call log or record calls. These records support app blocking, rewards, progress displays, and reminders.

If you contact support, we receive your email address, message, and any attachments or other information you choose to send. We use this information to respond to your request and resolve the issue.

Permissions and your choices

App inventory and usage, location, camera input, physical activity, and Health Connect records are treated as personal or sensitive data. We use the relevant access for the features explained below. Android permission requests, special-access settings, Health Connect grants, and any required in-app consent are separate from this document; reading or accepting this policy does not grant them. You can decline optional permissions and revoke access in Android settings. Features that depend on that access may stop working, while unrelated features remain available. Revoking access does not automatically erase records already saved.

App usage and accessibility

Relevant access: android.permission.PACKAGE_USAGE_STATS and the Accessibility Service API. The service is protected by android.permission.BIND_ACCESSIBILITY_SERVICE, which allows Android to bind to the service; it is not a runtime permission that grants access to all device content.

With usage access, TimeMint queries Android app usage statistics and foreground events to display screen time and suggest apps to limit. The queried usage statistics are held temporarily in memory; separate TimeMint app-session records are saved locally. It lists apps with launcher icons so you can choose which apps to limit; their names and icons are obtained on your device.

If you enable the accessibility service, it listens for app window changes to identify the foreground app, show the blocking screen and session timer overlay, and return to the Home screen when a session expires or you end it. With Posture Guard enabled, it may also cover a limited app with a posture lock until you raise your phone or end the session. It does not retrieve screen contents, read messages, passwords or keystrokes, record other apps’ screens, or tap buttons and enter text inside other apps. Foreground package names and TimeMint session times are used locally for blocking and progress, not supplied as advertising data. TimeMint uses accessibility for screen-time management and is not a disability-support accessibility tool. You can disable the service in Android Accessibility settings and revoke usage access in Android settings. Blocking and usage features will then be limited.

The installed-app picker queries apps with launcher icons on your device and does not upload that list. TimeMint does not request QUERY_ALL_PACKAGES. Integrated advertising and attribution SDKs can have separate, limited package-visibility declarations for store or browser integration, compatibility, and fraud checks. Within those Android limits, some advertising SDKs may check whether particular apps are installed and send that result to their provider for ad delivery, measurement, or fraud prevention. This happens separately from TimeMint’s app picker and does not give those SDKs access to other apps’ private content. Timer and posture overlays use accessibility overlays rather than the SYSTEM_ALERT_WINDOW permission.

Health Connect and motion sensors

Relevant permissions: android.permission.ACTIVITY_RECOGNITION, android.permission.health.READ_STEPS, android.permission.health.READ_EXERCISE, android.permission.health.READ_DISTANCE, and android.permission.health.READ_HEALTH_DATA_IN_BACKGROUND.

When you select Health Connect as your step source and grant permission, TimeMint reads recent daily step totals and hourly aggregates to update activity history, goals and earned screen time. When you enable watch synchronization, it reads recent running and cycling exercise sessions and their distances. Workout data can include record identifiers, source app, recording method, activity type, start and end times, and distance. Opening TimeMint synchronizes enabled features. A separate, optional background-read grant allows steps and enabled workout imports to synchronize periodically on supported devices; Android may delay this work. Without that grant, foreground synchronization remains available. Delayed steps are credited to their original day without rewarding the same cumulative steps twice; previous-day rewards are deposited into the Time Bank, and saved daily walking settlement information supports late credit. TimeMint does not write data to Health Connect or access exercise-route data from Health Connect. You can change the step source, turn off watch sync, or revoke background access in Health Connect to stop the corresponding background reads.

Health Connect data is used only for the step, workout, distance, progress, and screen-time reward features you request. We do not sell it, use it for advertising or marketing, provide it to advertising or analytics services, use it for credit or insurance decisions, or use it to train general-purpose AI models. TimeMint’s use of Health Connect data follows the Google Play Health Connect permissions policy, including its Limited Use requirements.

Phone step counting uses available step or motion sensors; stair counting uses the barometer when available. Posture Guard uses device orientation or gravity sensors during eligible app sessions and may save a count of posture locks. It estimates phone position, not a medical posture assessment. Raw sensor samples are processed locally. When live step counting is active, as described under foreground services below, step or motion sensors are read in the background; only step totals and their timing are saved. You may revoke activity recognition and Health Connect permissions, change the step source, or turn off watch sync or Posture Guard. Revoking permission stops future access; saved local records remain until deleted. Deleting TimeMint data does not delete records held by Health Connect or their source apps.

Location during running and cycling

Relevant permissions: android.permission.ACCESS_COARSE_LOCATION, android.permission.ACCESS_FINE_LOCATION, and android.permission.FOREGROUND_SERVICE_LOCATION. TimeMint does not request ACCESS_BACKGROUND_LOCATION.

GPS running and cycling tasks require precise location; approximate location alone does not enable distance tracking. After you start a task, TimeMint processes location, accuracy, speed, and time to estimate distance and filter implausible movement. A foreground service can continue recording while the screen is off or you use another app. Finishing the task stops TimeMint’s workout tracking; pausing stops adding distance and route points, but location updates remain active while the task is paused. TimeMint’s workout features do not track location outside an active running or cycling task. Turning off notifications alone does not stop a running task; finish it or revoke location access to stop tracking.

GPS routes are saved locally. The saved record includes time, duration, distance, earned minutes, and a reduced set of latitude and longitude points for the route sketch. A local checkpoint supports recovery if recording is interrupted. Running and cycling each retain the latest 50 records, including GPS routes where recorded; these records have no separate 120-day expiry. Coordinate rounding and fewer points do not make a route anonymous. We do not provide saved routes or workout history to advertising or attribution services. Advertising SDKs may independently process device location accessible under Android permissions and their settings, as described below; Android location services may separately process positioning information under their own policies.

Camera and photos

Relevant permission: android.permission.CAMERA. Camera input is used only while the camera-based task is visible, not for background recording. TimeMint does not request microphone permission for these tasks.

With camera permission, TimeMint uses on-device ML Kit pose detection or image labeling to count exercise repetitions and verify photo tasks. Recognition frames and pose landmarks are processed in memory. Ordinary exercise and verification frames are not saved, and we do not upload camera images or recognition results.

Tidy-up before-and-after photo thumbnails are saved locally in app-private storage so you can review the comparison. The long edge is reduced to at most 480 pixels. Up to 12 completed comparisons and an unfinished draft may be kept; older comparisons are removed as new ones replace them. These thumbnails are not added to your gallery or uploaded by us and are removed when you delete TimeMint activity data or clear Application storage. Camera access is optional; camera-based tasks require it.

On-device recognition does not mean the ML Kit SDK is entirely offline. Google may receive API performance and utilization metrics, and the SDK may contact Google for updates, fixes, or hardware compatibility information. Google’s ML Kit terms and privacy information explain this technical processing and distinguish it from image inputs and recognition outputs.

Notifications, foreground services, and battery settings

android.permission.POST_NOTIFICATIONS supports goal, balance, session, and workout reminders. android.permission.POST_PROMOTED_NOTIFICATIONS supports ongoing task progress on compatible devices. Notifications may contain the name of a limited app, elapsed time, distance, step count, or task progress. You can use Android notification and lock-screen settings to control their visibility. These permissions do not let TimeMint read other apps’ notifications. Denying notifications may hide reminders or normal status notifications without stopping an active foreground service.

android.permission.FOREGROUND_SERVICE and its FOREGROUND_SERVICE_LOCATION, FOREGROUND_SERVICE_HEALTH, and FOREGROUND_SERVICE_SPECIAL_USE types keep TimeMint’s activity features running when you leave the task screen or turn off the display. The location type supports user-started running and cycling tasks. The health type supports stair-counting sessions and live step counting. Live step counting starts automatically, with an ongoing step notification, while a walking goal locks your apps or while TimeMint’s motion-based step counting is selected; it stops when you turn off that goal’s lock or switch to your phone’s step sensor or Health Connect. The special-use type supports user-started timers such as meditation, reading, practice, and a user-entered call timer. These service types do not themselves grant access to other Health Connect data, contacts, call recordings, or microphones. End a task through the Application or its available notification control to stop its service.

android.permission.WAKE_LOCK supports limited background sensor or breathing-haptic work during relevant active sessions; system scheduling and integrated SDKs may also use it for their work. android.permission.VIBRATE supplies haptic reminders and breathing cues. TimeMint does not request REQUEST_IGNORE_BATTERY_OPTIMIZATIONS and does not show a system prompt asking for a battery exemption. It can only check whether an exemption is active and open the Android battery-optimization list, where you choose whether to exempt TimeMint. An exemption can improve blocking, timers, step counting, and reminders. It is optional, can be reversed in the same Android settings, and grants no additional data permissions. Android may still limit background work.

Advertising, attribution, and technical services

The ad-supported version uses Google AdMob and mediation partners. Depending on the provider, Android version, configuration, region, and consent choices, they may process IP address, approximate region, app and device identifiers, operating-system and device information, network information, ad requests, impressions, clicks, interactions, purchase-related attribution events, and diagnostics. These data support ad delivery, measurement, frequency limiting, attribution, security, fraud prevention, and personalization where permitted. Non-personalized ads can still involve technical data processing.

Advertising providers may infer location from your IP address and may independently access device location when available under Android permissions and provider settings. This is separate from TimeMint’s locally saved GPS routes. We do not send your Health Connect records, journal text, camera images, saved route history, installed-app list, or app-session history as advertising or attribution inputs.

Google’s User Messaging Platform checks at launch whether advertising consent is required in your region, which sends app, device, and request information to Google, and handles consent messages where required. Where consent applies, such as in the European Economic Area and the United Kingdom, you can revisit your choices at any time in Settings → Privacy → Privacy options. You can also adjust Android advertising privacy controls. Availability and effect depend on the region, provider, Android version, and configuration. An ad-removal subscription changes ad display according to its purchase offer; it does not necessarily stop configuration, purchase validation, attribution, or other SDK communications.

Firebase Remote Config obtains configuration from Google and may process Firebase installation identifiers, app or device information, and technical request data. Google Play Install Referrer provides installation source and click or installation timing information, which the Application caches locally. Meta App Events uses automatic app events, and TikTok Business services may initialize and process events depending on configuration. These services may process installation or launch events, available identifiers, IP address, approximate region, and device and app information. Purchase attribution can include transaction identifiers, products, currency, quantity, and attributed value, as explained under subscriptions below.

Firebase Analytics is enabled by default. It collects usage events such as first opens, sessions, screen views (including settings pages), exit prompts, error events, app updates, and advertising and purchase events, together with an app-instance identifier, the Android advertising ID where available, app version, device and operating-system information, and approximate region derived from IP address. We use it to understand feature use, measure advertising and purchases, and support attribution. TimeMint does not send Health Connect records, journal text, camera images, saved routes, installed-app lists, or app-session history to Analytics. The Application currently has no in-app switch for Analytics; clearing Application storage or uninstalling resets the app-instance identifier but does not delete events already sent. Identifiers available to these services depend on Android permissions and privacy controls, as explained below.

Subscriptions and payment information

Optional subscriptions and purchases are processed through Google Play. The Application and purchase services may process product identifiers, purchase tokens, transaction or order identifiers, purchase time, subscription status, and entitlement information to validate or acknowledge purchases, restore paid access, prevent fraud, and provide support. Google processes your payment method and Google account information; we do not receive your full card number or payment credentials.

TimeMint may share subscription or purchase events with Meta App Events and TikTok Business services, where enabled, including an order or transaction identifier, product, quantity, currency, and attributed purchase value for conversion measurement. Attributed value may differ from the amount actually charged. These events do not include Health Connect records, journal text, camera input, or saved routes. Deleting local data or uninstalling TimeMint does not cancel a subscription; manage it through Google Play.

Crash reports

Firebase Crashlytics is enabled by default and automatically uploads diagnostics when the Application crashes or encounters certain errors, so we can identify and fix stability issues. Reports can include app version, device and operating-system information, memory and storage state, timestamps, crash traces, and installation identifiers. Reports that cannot be sent immediately may be kept locally until the next launch. These reports are not guaranteed to be anonymous. We do not intentionally attach journal entries, health records, photos, or location fixes to them.

The Application currently has no in-app switch for crash reporting. Deleting data on this device, clearing Application storage, or uninstalling does not recall reports already sent. For data already sent, Google’s Firebase privacy documentation describes retention and deletion practices.

Additional declared permissions

The permissions below support network services, Google Play, and integrated libraries. Unlike camera or precise-location requests, they generally do not show an individual Android runtime-consent dialog. A declaration permits a capability; actual access also depends on the Android version, SDK configuration, available services, and your privacy choices.

The BIND_ACCESSIBILITY_SERVICE, BIND_JOB_SERVICE, START_VIEW_PERMISSION_USAGE, and DUMP protections restrict access to TimeMint’s system-facing components. They do not grant TimeMint access to all accessibility content, system logs, or other apps’ jobs.

TimeMint does not request background location, microphone, contacts, call-log, SMS, shared-photo-library, or all-files access.

Third-party services and external destinations

The services above process information under their applicable terms and privacy policies:

• Google Play and Google Play services, including billing, payments, and Install Referrer
• Firebase Analytics, Crashlytics, Remote Config, and Installations
• Google ML Kit
• Meta App Events
• TikTok Business, depending on configuration

Advertising providers and mediation partners have separate policies: Google AdMob and its consent services, Meta Audience Network, Pangle (regional policies), AppLovin, Liftoff Monetize (Vungle), Mintegral, InMobi, BidMachine, and Unity Ads and ironSource. Providers used for a particular ad request depend on mediation configuration, region, availability, and privacy choices.

When you open an external link, share a progress image, or export to a cloud-backed destination, the browser, recipient, or storage provider handles the information you choose to disclose under its own policies. This policy website uses Firebase Hosting, which may process IP addresses and technical requests for delivery and security. These pages contain no advertising or analytics scripts and use no external fonts.

Sharing and international processing

Advertising, purchase, and technical information may be processed by the services above for ad delivery and measurement, purchase handling, configuration, analytics, attribution, SDK operation, security, and crash diagnostics. Information you send us for support may be disclosed where legally required, to protect rights and safety, or in a business transfer subject to applicable privacy protections. We do not sell local activity records or Health Connect data or transfer Health Connect data to data brokers; these provisions do not authorize advertising use of Health Connect data. Service providers may process information outside your country under their applicable safeguards. Local activity records are not made available to us merely by using the Application.

Retention, export, deletion, and your rights

Daily summaries and TimeMint app-session details are kept for up to 120 days, with older entries removed when TimeMint updates the next day’s records. Other records have feature-specific limits, including the latest 50 running and 50 cycling records, 100 camera-workout records, 200 Time Bank transactions, and 12 tidy-up photo comparisons. Journals, drafts, preferences, and accumulated progress have no automatic time-based expiry and remain until deleted or reset. App-private data is excluded from Android cloud backup and device transfer.

You can export selected app-session records, daily summaries, task reward totals, and optionally journal entries as JSON or CSV. This is not a complete backup: GPS routes, detailed workout logs, tidy-up photos, books, tasks, and settings are not included.

Settings → Privacy → Delete data on this device resets TimeMint activity records and settings and removes the recovery copy, tidy-up thumbnails, and share-image caches. It does not remove analytics events or crash reports already sent. While the commitment lock is on, in-app deletion is unavailable until the lock is released. Android’s clear-storage and uninstall controls remain available. The in-app reset does not clear all identifiers used by third-party services or installation-source information. Clearing Application storage or uninstalling removes app-private files; it does not erase Android usage statistics, Health Connect source records, third-party server records, or files and images already exported or shared elsewhere. Delete those copies separately. Resetting, clearing storage, or uninstalling does not cancel Google Play subscriptions or erase Google’s transaction history.

Support correspondence and purchase-related information received by us are retained as needed to resolve requests, maintain entitlements, prevent fraud, and meet accounting or legal obligations, then deleted when no longer needed. Advertising, attribution, configuration, analytics, ML Kit, and crash-reporting providers have their own retention periods and deletion controls, described in their policies. Local deletion does not automatically remove previously transmitted events.

TimeMint does not offer a request process for deleting data collected through the Application. Activity records stay on your device, and you can delete them yourself with the controls above. We do not hold an account or profile that links analytics, crash, advertising, or attribution data to you, so we cannot locate or delete that data for a specific person. Those services keep the data for their own retention periods and offer their own controls: you can reset or delete the Android advertising ID, adjust Android advertising privacy controls, and, where consent applies, change your choices in Privacy options. Withdrawing a permission or consent stops future collection but does not delete data already collected.

If the law where you live gives you rights such as access, correction, deletion, objection, restriction, portability, or withdrawal of consent, contact play@byeshe.com. We will respond as that law requires and may ask for information needed to verify the request. This includes support emails you have sent us. You may also contact your local data-protection authority.

Security and children

Local records are kept in Android app-private storage. Protect your device and any exported copies; no storage or transmission is completely secure. The Application is not directed to children under 13. Minors must follow applicable age requirements and obtain guardian permission where required. If you believe a child has provided personal information to us, contact us so we can take appropriate action.

Changes and contact

We may update this policy and its effective date as features or data practices change. We will provide additional notice or request consent when required by law. For privacy questions, contact Byeshe at play@byeshe.com.