Health & Screen Time
Sensitive activity stays where Apple designed it to stay.
- Version
- 1.0
- Effective
- 29 August 2026
- Last updated
- 7 October 2026
This plain-language summary helps you navigate. The complete document below, not the summary alone, governs.
On this page
1. Why this separate notice exists
Screen Time and Health information is sensitive and governed by Apple permissions as well as Aheno choices. This page explains the technical boundary in direct language and supplements the Privacy Notice.
2. Family Controls authorization
Aheno asks Apple for Family Controls authorization when you choose to configure protection. You choose applications, categories, and websites through Apple's system picker. You can deny or revoke authorization; planning and other features that do not require it can continue, while protection and reports may stop.
Authorization does not give Aheno's backend a list of your apps. Apple's opaque tokens remain inside the device and approved extensions.
3. What the app and extensions do
Managed Settings and shield extensions apply and explain local restrictions. DeviceActivity monitoring identifies local schedule or threshold events. A report extension calculates and renders activity inside Apple's protected reporting flow.
The main app can display the rendered report but does not receive raw per-app durations or pickup values from that extension. The report extension has no network access.
4. Exact Screen Time boundary
The following is processed on this iPhone and does not leave the device: selected application/category/website tokens and resolved labels or icons; per-app/category/domain duration; pickups; notification counts; reflex-opening estimates; shield events and attempts; temporary-access history; report output; and values derived from those reports.
These categories are not accepted by Aheno backend routes, remote notification payloads, community records, account analytics, or support by default. If you voluntarily send a screenshot to support, it becomes information in that email; redact private apps first whenever possible.
| Information | Processed where | Sent to Aheno backend |
|---|---|---|
| Selected apps, categories, and websites | Apple picker and device extensions | No |
| Usage duration, pickups, and notification counts | DeviceActivity report extension | No |
| Shield and temporary-access state | Device extensions | No |
| Focus-session timing and completion | Aheno app and account service | Yes, when account sync is used |
| Nightly sleep summary | Aheno app; conditionally service | Only after separate sharing choice if offered |
5. HealthKit permission and categories
Current local sleep and movement features may request read access to sleep analysis and Apple Watch standing-hour records. These features do not request step-count access. Aheno does not request write access and does not write to Apple Health. Movement measurements stay on the device. Apple controls the permission sheet, and Aheno cannot determine whether you denied reading or simply have no matching samples beyond what the framework reveals.
Measured sleep and movement displays require a paired Apple Watch, compatible measurements, and Health permission. Local Pro routine-time suggestions can read permitted sleep records separately and do not use that Watch-pairing requirement. Pairing alone does not establish that the Watch is being worn or that measurements are available.
6. The nightly summary
On-device processing may derive only the calendar night, asleep minutes, bedtime minute-of-day, wake minute-of-day, and awakening count. Raw `HKCategorySample` records, detailed sleep stages, heart rate, and unrelated Health categories are not part of the backend contract.
The summary supports personal sleep display and an optional connection feature; it is not a diagnosis, medical record, or guarantee of measurement accuracy.
7. Conditional sleep sharing
If a build offers sleep sharing, transmission requires an accepted statistics-sharing connection and a separate sleep-sharing choice for at least one connection. A connection alone is not sleep consent, and each person's choice is independent.
The current shipping application wiring does not instantiate the sleep uploader. If a build activates it later, only the listed nightly summary may be sent. Turning off the last sleep-sharing choice deletes shared sleep-night rows; account deletion also removes them through the account cascade.
8. Uses Aheno does not permit
Health information is not used for advertising, marketing, data-broker disclosure, eligibility, public ranking, generalized product analytics, or a legal or similarly significant automated decision. Screen Time information is not used for those purposes because it does not reach the service at all.
9. Controls and revocation
Use iOS Settings to revoke Family Controls or Health access. Revocation stops future access but can also stop local protection, reports, or sleep refresh. Remove selected items or rules inside Aheno when you want to clear local configuration. Turn off sleep sharing for every connection to remove shared sleep rows, and delete the account for cascading service deletion.
Apple Health records remain controlled by Apple and your Health settings. Deleting Aheno does not delete the original records Apple or another health source owns.
10. Accuracy, safety, and support
Screen Time and Health values can be delayed, incomplete, changed by Apple, affected by device state, or unavailable. Aheno does not diagnose addiction, sleep disorders, or another condition. Seek qualified or emergency help when appropriate.
For permission or privacy help, email ahenoapp@gmail.com. Describe the screen and error without attaching private app lists or raw health screenshots unless necessary and voluntarily chosen.
Can Aheno see which app I used for an hour?
Aheno's backend cannot. Apple calculates and renders Screen Time values inside a protected report extension on your iPhone, and the underlying values do not leave the device.
Does Aheno write sleep information to Health?
No. Aheno may read the sleep and movement categories described above but does not request HealthKit write access.
Does accepting a connection automatically share sleep?
No. Sleep requires a separate choice for that connection, and current shipping wiring does not activate the uploader. Each person controls their own sharing direction.
