Data Rights & Deletion
One request should have a clear path and an honest result.
- 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. Rights that may apply
Depending on your location and the processing, you may have rights to know or access personal data, obtain a copy, correct it, request deletion, restrict processing, object, receive portable data, withdraw consent, learn recipients or safeguards, and complain to a competent authority.
Rights are not identical everywhere and can have legal exceptions. Aheno may need to verify identity, preserve another person's rights, maintain a limited security or legal record, or explain why a request cannot be fully granted.
2. How to make a request
Use the in-app deletion control for full account deletion. For another right, email ahenoapp@gmail.com from the account email where possible. State the right, the Aheno account or community handle, the country whose law you believe applies, the information or feature involved, and the format you prefer.
Do not send a password, Apple authentication code, full payment card, raw Health export, or unredacted Screen Time screenshot. Additional verification will be limited to what is reasonably needed to prevent disclosure to the wrong person.
3. In-app account deletion
Use Aheno's account settings and choose the account-deletion action. The app should explain the effect and may require recent authentication. Once accepted, deletion is asynchronous: the Firebase identity is erased and the service account row and related records are deleted through database cascades.
Do not treat uninstalling the app, signing out, revoking a permission, or canceling Pro as an account-deletion request; each action has a different scope.
4. What deletion removes and what can remain
Account deletion removes private profile, plans, projects, sessions, outcomes, achievements, community membership and user records, sharing connections, shared sleep rows, notification registrations, and entitlement mappings according to their database relationships.
A deleted post's body is removed while a tombstone can remain for feed consistency. A limited pseudonymous account-deletion audit receipt can remain to prove completion and support security or legal obligations. Community traffic logs retain IP address, port, action, and target references for one year; after account deletion the direct user link is removed and a pseudonymous subject digest can remain until that period ends. Provider or infrastructure logs and rotating backups may persist for their necessary retention cycle and are not returned to ordinary service use.
Content copied or screenshotted by another person before deletion may remain outside Aheno's control. Law may require limited preservation or disclosure; if that affects a request, the response should explain it where permitted.
| Action | What it controls | What it does not do |
|---|---|---|
| Delete Aheno account | Aheno identity and service records | Cancel Apple billing |
| Cancel App Store subscription | Future Apple renewal | Delete Aheno account or local data |
| Revoke Screen Time | Future Family Controls access and protection | Delete synced plans or account |
| Revoke Health | Future HealthKit reading | Delete original Apple Health records |
| Turn off sleep sharing | Future sharing and shared sleep-night rows when last consent is off | Delete Apple Health source records |
| Uninstall Aheno | Local installed app data subject to iOS behavior | Delete online account or cancel billing |
5. Cancel the App Store subscription separately
Deleting your Aheno account does not cancel an App Store subscription. Apple controls billing, so open Apple subscription settings and cancel separately if you do not want renewal. Aheno cannot perform that cancellation for you.
6. Device-only Screen Time and local notes
Aheno's backend never holds selected apps, Screen Time duration, pickups, notification counts, shield attempts, temporary access, or report values, so an account export cannot include them and a server deletion request has nothing to remove there.
Change or clear local rules in Aheno, revoke Family Controls in iOS Settings, and remove the app when you want iOS to clear its local container according to Apple's behavior. Private focus intention and recap notes are also local rather than account data.
7. Health and sleep controls
Revoke Aheno's sleep and movement reading permissions in iOS Health settings to stop future reads. Manage or delete source Health records with Apple or the source that wrote them; Aheno does not write those records.
If a build offers sleep sharing, turn it off for every connection. Turning off the final sleep-sharing choice deletes the shared nightly rows from Aheno's service. Current shipping app wiring does not activate the uploader.
8. Notifications and community controls
Turn off plan, social, marketing, or announcement categories inside Aheno without necessarily disabling every notification. Use iOS Settings for system permission. Account deletion removes registered notification records through the account lifecycle.
Delete individual posts or comments where the feature allows, block another participant, end a focus-partner connection or leave a challenge, or send a moderation request. Deleted post bodies can leave a tombstone; account deletion addresses the wider account record.
9. Access, copy, portability, and correction
A response can identify relevant account, profile, plan, focus, achievement, connection, community, notification, security, subscription, and conditional sleep-summary categories. Portable output applies to information covered by the relevant law and technically held by Aheno, not device-only Screen Time or Apple-controlled payment credentials.
Correct editable profile information in the app where available. Email when a field cannot be corrected directly or when you need context about source, purpose, recipients, or safeguards.
10. Restriction, objection, and withdrawal of consent
Describe the processing you want restricted or object to and why the right applies. Aheno will assess the request against the applicable legal basis, security, legal duties, and other people's rights.
Withdraw a separate sleep-sharing choice in the feature itself when available. Withdrawal controls future consent-based processing; it does not make earlier lawful processing unlawful. Reading the Privacy Notice or accepting general Terms is not explicit consent to optional sleep sharing.
11. Response, complaints, and request template
Aheno will acknowledge and respond within the period applicable to the request and jurisdiction, subject to permitted extensions and identity verification. The response will state the action taken or explain a refusal and available complaint path where required.
Suggested email: 'Subject: Aheno data-rights request. Right requested: [access/correction/deletion/etc.]. Account email or handle: [value]. Country: [country]. Scope: [feature or data]. Preferred format: [format].' Send it to ahenoapp@gmail.com.
You may complain to the competent privacy authority. Contacting Aheno first is welcome but does not remove a right to contact an authority where the law provides it.
Will deleting my account cancel Aheno Pro?
No. Account deletion and App Store billing are separate. Cancel the subscription in Apple settings if you do not want it to renew.
Can I ask Aheno to export my Screen Time report?
Aheno's service cannot export what it never receives. Screen Time selections and report values stay on your iPhone inside Apple's protected framework.
What should a rights-request email include?
State the right, account email or handle, relevant country, scope, and preferred format. Do not send passwords, Apple codes, card details, or unnecessary sensitive screenshots.
