Last updated: 11 August 2026
This policy covers Human Hours on iOS and Android.
Human Hours is provided by Anand Sharma.
Human Hours does not operate an account system or a backend that receives your wellness data.
Purchase processing and Apple-managed backups are separate and are explained below.
Human Hours stores the information you enter and the state needed to provide its features in the app’s local container.
This includes your onboarding answers, appearance and day-start settings, Journal notes and triggers, Pause outcomes, Flow timing and reflections, Story progress, selected protection rules, and diagnostic or session history.
Human Hours has no first-party cloud sync service.
On iOS, Human Hours uses Apple’s Screen Time APIs, including Family Controls, Device Activity, and Managed Settings.
Depending on the feature and authorization Apple grants, Human Hours can handle usage and category totals, app display names, bundle identifiers, opaque Family Controls tokens, selected apps, categories and web domains, domain names, durations, pickup and notification counts, hourly or daily history, and rule selections.
That information is processed in the app sandbox and its shared App Group container.
Human Hours does not send Screen Time data, selected app or website identifiers, Journal content, or protection rules to RevenueCat, analytics services, advertisers, or a Human Hours server.
On Android, Mindful Pause is optional and uses an Accessibility Service only after you read the in-app disclosure, affirmatively consent, and enable the service in Android Settings.
When enabled, the service receives the foreground package name after a window-state change and compares it locally with the apps you selected.
The Accessibility Service cannot retrieve screen content.
It does not read text, keyboard input, messages, screenshots, website addresses, or browsing history.
The app picker queries launchable apps and reads their package names, labels, and icons so you can choose which apps to protect.
Human Hours stores selected package identifiers but does not persist package names for unselected foreground apps.
Human Hours does not request broad package visibility.
Android can ask for notification permission to show an ongoing Flow countdown and completion actions.
On Android versions that require it, Human Hours checks whether exact-alarm access has already been granted; it does not open the system screen to request that access.
You can grant Alarms & reminders manually under Android Special app access where that setting is available.
If notification permission is declined, Flow can still run and record locally without those notifications.
If exact-alarm access is unavailable, the system fallback can deliver the completion alert late.
These permissions do not give Human Hours access to your notifications, alarm history, Journal content, or screen content.
Human Hours Pro is sold through the Apple App Store or Google Play and managed with RevenueCat.
RevenueCat is initialized during normal app startup or foregrounding so Human Hours can determine whether Pro is active.
Apple or Google processes your store account and payment method under its own privacy policy.
Human Hours does not receive your complete payment-card details.
Human Hours supplies no custom user identifier, name, or email address to RevenueCat, so the SDK creates a random anonymous App User ID.
RevenueCat processes purchase history, product, transaction, subscription and entitlement information, Apple receipts or Google purchase tokens, device and OS information, locale and currency information, and connection information.
This processing validates purchases and restores, determines entitlements, supports fraud controls, and provides RevenueCat purchase analytics and dashboard functionality.
On Android, RevenueCat’s prebuilt paywall automatically processes paywall presentation and interaction events, including impressions, closes, and purchase cancellations.
These events include the anonymous App User ID, an event identifier, a paywall session identifier, a timestamp, the offering identifier and paywall revision, display mode, light or dark appearance, and locale, and RevenueCat uses them for paywall analytics and functionality.
Human Hours does not provide RevenueCat with your name, email address, Journal, Screen Time data, foreground app activity, or a custom account identifier.
RevenueCat documents that it may use a customer’s last-seen IP address to determine country when transaction country is unavailable, and that it drops the raw IP address after determining country.
See the Apple Privacy Policy, Google Privacy Policy, RevenueCat’s Privacy Policy, Customer Profile documentation, automatic paywall impression guidance, and Apple App Privacy guidance, plus its paywall event reference.
Where this policy refers to a logical day, it means a day that follows the day-start time you choose in Human Hours rather than always changing at midnight.
On iOS, Human Hours stores data in the app sandbox and shared App Group using operating-system data protection.
Depending on your Apple settings, this app data can be included in an iCloud Backup or a device backup.
Human Hours does not control retention of those Apple-managed backup copies.
On Android, Human Hours stores state in its private sandbox, excludes it from cloud backup and device transfer, and disables cleartext network traffic.
On iOS, Settings > Clear Journal removes all locally stored Journal entries.
You can delete protection rules and revoke Screen Time access separately.
Human Hours does not currently offer one in-app control that erases every category of iOS state.
To remove other iOS app data, delete Human Hours from the device rather than offloading it, because offloading can preserve app data.
Apple-managed backup copies must be managed separately through your Apple backup settings.
On Android, Settings > Delete local data removes the primary state and its Human Hours recovery copies.
You can also delete individual Android Journal entries or remove the app through Android.
Disabling Android Mindful Pause stops future foreground app access, but saved app selections remain local until you change them, delete local data, or remove the app.
Deleting Human Hours or its local data does not cancel a subscription and does not delete purchase records held by Apple, Google, or RevenueCat.
Those providers retain purchase records under their own policies and legal obligations.
For questions about an anonymous RevenueCat purchase profile, contact us.
Because Human Hours does not send RevenueCat your email address, an email address alone may not identify that profile.
Human Hours has no advertising SDK, does not sell personal data, and does not share data with data brokers or advertising networks.
Human Hours does not use your on-device attention data to track you across other companies’ apps or websites.
The app does not ask for your name or email address.
If you choose to email support, we receive the email address, message, and attachments you send and use them only to answer your request and maintain support records.
You may ask us to delete a support conversation unless we must retain it for security, fraud prevention, or legal reasons.
Local data is protected by the operating system’s app sandbox.
No storage or transmission method can be guaranteed completely secure.
We may update this policy when Human Hours features, platform permissions, or service providers change.
The date at the top identifies the current version.
Material changes will also be described through an app update, release notes, or an in-app notice when appropriate.
Anand Sharma is the provider of Human Hours and the controller for the data Human Hours itself handles.
For privacy questions or deletion assistance, email anandvsharma@icloud.com.