Your private device activity is not an online profile.

This notice applies to the Aheno iOS app, its extensions, Aheno account and community services, remote notifications, and this website. Apple-controlled App Store, Screen Time, Health, and payment processing have their own terms and privacy information.

Aheno is a product provided by Aheno's independent developer. Privacy and data-rights requests go to ahenoapp@gmail.com. The App Store seller or publisher identity remains the platform record for the individual publishing the app.

• Email a privacy request
• Data Rights & Deletion Guide

The most sensitive information Aheno displays is handled inside Apple's device boundary. Other features intentionally use an online account so plans, focus progress, purchases, notifications, and community participation can work across service components.

The table distinguishes device-only data, ordinary service data, optional sensitive sharing, and provider-controlled information. Later sections explain every category in detail.

Applications, categories, and websites you select through Apple's Family Controls picker are represented by opaque tokens. Aheno's device extensions can apply your rule and Apple can render names or icons in approved interfaces, but the backend does not receive those tokens, resolved app identities, or your selection list.

Per-app, per-category, and per-domain duration; pickups; notification counts; reflex-opening estimates; shield presentations; attempts to open shielded apps; temporary-access history; and DeviceActivity report values are processed on this iPhone and do not leave the device.

Apple asks a DeviceActivity report extension to calculate and render sensitive reports. The main app hosts that rendered report but does not receive the underlying activity values. The report extension has no network access. These values are excluded from Aheno's backend contracts, remote notifications, community, widgets that require server data, and analytics.

• Health & Screen Time Notice

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 HealthKit write access and does not write to Apple Health. Heart rate and reproductive health are not requested by these features. Movement measurements are processed on the device and are not uploaded to Aheno.

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.

On this iPhone, Aheno may derive a nightly record containing the calendar night, asleep minutes, bedtime minute-of-day, wake minute-of-day, and awakening count. Raw HealthKit samples and sleep-stage records are not accepted by the backend contract.

If a build offers sleep sharing and you enable it for at least one accepted statistics-sharing connection, only that derived nightly summary can be transmitted. The current shipping client wiring does not activate this uploader, so this notice does not claim that current builds upload sleep. Turning off the final sleep-sharing choice deletes shared sleep-night rows. Revoking Health permission stops future local reading but does not alter records Apple holds in Health.

Health information is not used for advertising, marketing, eligibility, public ranking, or generalized analytics.

Account services can process an internal user ID and Firebase identity subject; an optional Sign in with Apple email, including a private relay address; private display name; birth year rather than a full birth date; onboarding goals; daily focus goal; locale, country code, and timezone; avatar choices; an editable community handle; community eligibility; and leaderboard visibility choices.

Private display name, email, birth year, onboarding goals, and daily goal are not public community-profile fields. A public handle, generated avatar, country code, and pinned achievement may be visible where you participate in community features.

To protect accounts and APIs, Aheno can process an installation or device UUID, app version, last-seen time, App Attest key and attestation records, assertion counters, short-lived challenge nonces, request digests, hashed refresh tokens, expiry and revocation state, idempotency keys, and bounded replay responses.

Limited network and security information such as IP address can appear where needed for rate limiting, abuse prevention, and infrastructure logs. Plain push tokens and provider response bodies must not be logged. Security information is used to authenticate requests, prevent replay and fraud, diagnose delivery, and protect users and the service.

Account sync can process plan names, modes, dates, timezone, blocks, titles, categories, recurrence, state, and bounded version history; life-project names, categories, optional purpose, targets, dates, status, symbol, and focus allocations; and digital-reset task state that you declare.

Focus-session records can include start and end, planned and completed duration, intensity, completion or safety-exit state, verification, points, and optional plan/project relationships and historical circle links. Current reflection records contain the selected outcome and planned and completed seconds; private notes and locally calculated integrity scores are not in that payload. Legacy clients can still send a normalized score, score version, and strongest component to the older outcome service; those records can remain online. These legacy summaries can reflect local attempts to open blocked apps and temporary unlocks. They do not contain selected app identities or raw Screen Time reports. Achievement keys, unlock/report times, rarity counts, and a pinned achievement can also be stored.

Free-text focus intention and recap notes remain on the device. Plan, project, post, and comment text is server data because you intentionally create it as synchronized or shared content. Optional calendar access uses full access permission to export selected plan blocks and update the events Aheno created. Event identifiers are held on the device; Aheno does not browse unrelated calendar events. Calendar import is not available in the current app.

Optional community features can process a public handle, generated avatar, country code, pinned achievement, focus-partner connections, membership, invitations, followers and follow requests, mute state, presence, challenges, verified points, rankings, and visibility choices. City features can store the city identifier, assignment source, catalog version, assignment history, and separate city-ranking visibility choice. If you permit approximate location, the device resolves a city locally; coordinates are not sent to Aheno. You may decline location or use the choices shown in the app.

Community content can include posts up to 280 characters, comments up to 200 characters, moderation appeal notes up to 500 characters, positive reactions, saves, blocks, reports and report reasons, moderation state, and the guideline version and time you accepted. Community content is visible according to the audience shown when you post or join; do not post private information you do not want that audience to see.

Statistics-sharing connections can use invitation or code digests, connection state, each side's separate sleep-sharing choice, and connection-visible daily focus/session/outcome aggregates. Screen Time, selected apps, pickups, notification counts, and app-level activity never become community or connection data.

• Community Guidelines

Apple handles payment credentials, card details, billing address, tax, App Store charging, cancellation, and refund decisions. Aheno does not receive your card number, Apple account password, or complete billing details.

Aheno and RevenueCat process the account mapping, product identifier such as monthly or annual, entitlement state and expiry, provider event ID/type/time, payload digest, and limited reconciliation or audit outcomes needed to grant Pro access.

Deleting your Aheno account does not cancel an App Store subscription. Billing must be managed separately with Apple.

• Subscription Terms
• Manage Apple subscriptions ↗

If you enable remote notifications, Aheno can process an encrypted device token, a non-reversible token digest, locale, timezone, authorization state, category preferences, quiet hours, an approved destination, a resource UUID where necessary, delivery state, retry count, and a digest of the provider message ID.

Remote payloads must not contain Screen Time or Health measurements, selected app names, private plan or block titles, private free text, payment details, or shaming language. System notification permission and Aheno's plan, social, marketing, and announcement category preferences are separate controls.

The app can send first-party product analytics using an installation UUID, event name, time, and predefined coarse properties. A signed-in event can also be linked to the account. Events cover onboarding, focus, plan completion, purchases, invitations, and, when enabled, community interactions and coarse counts of Aheno’s own foreground use. This is not Screen Time usage of other apps. Events do not contain private text, selected apps, raw Health measurements, precise location, or advertising identifiers. Analytics records expire after 90 days.

You can turn off product analytics in the app’s settings. This stops future client transmission and clears the local pending-event queue; when you are signed in and this choice reaches the service, account-linked analytics records are deleted. Previously received anonymous or unlinked events can remain until their 90-day expiry. Additional engagement and community analytics require the relevant feature to be enabled and the applicable analytics choice. Firebase Analytics, advertising analytics, cross-app tracking, third-party behavioral analytics, and advertising identifiers are not integrated. Contact Aheno for a request concerning stored analytics.

With your permission, the public marketing and legal website uses Vercel Web Analytics for aggregate page-view statistics and Vercel Speed Insights for page-performance measurements. Measurements can include a public page path, referrer, time, approximate location, browser, operating system, device type, network characteristics, and performance metrics. These tools use no analytics cookies and are not used for advertising or tracking across websites. Vercel and network providers can process ordinary request, IP, browser, timing, error, and security metadata needed to deliver and protect the site.

Both measurement tools remain off until you allow them. You can reject measurement or change or withdraw your permission through Cookie preferences in the footer. A browser Do Not Track or Global Privacy Control signal also disables measurement. We remove query strings and URL fragments from measured page URLs and exclude private and unknown routes. No custom events, account data, Health information, Screen Time information, or iOS app data are sent through these website tools. Your measurement choice is stored in your browser as described in the Cookie & Website Storage Notice. The app's separate product-analytics setting does not control website measurement.

• Cookie & Website Storage Notice

Information is used to provide requested account, sync, focus, planning, community, notification, entitlement, support, and security functions; fulfill the service agreement; comply with law; prevent abuse; and protect rights and safety. Optional sleep sharing is controlled by a separate, revocable choice and any explicit consent required by applicable law. Optional website measurement is used, with your consent, to understand public-page usage and improve website performance.

Depending on your location, processing may rely on performance of a contract, legitimate interests in secure and reliable service operation, compliance with legal obligations, protection of vital interests in rare safety circumstances, or consent for optional website measurement or a genuinely optional sensitive feature. Withdrawal of consent affects future consent-based processing and does not retroactively invalidate lawful processing already completed.

KVKK disclosure and explicit consent are separate. Reading this notice is not consent to sleep sharing, marketing, or another optional purpose.

Apple provides Sign in with Apple, App Store billing, Screen Time frameworks, HealthKit, and platform delivery. Google Firebase provides authentication and cloud messaging. RevenueCat supports subscription entitlement. Aheno's backend and PostgreSQL hosting process service records. Vercel hosts this website and provides its optional Web Analytics and Speed Insights measurements.

These providers may process information in countries different from yours under their own infrastructure and contractual arrangements. Where GDPR, KVKK, or another applicable law requires a transfer basis or safeguard, the appropriate mechanism must be used. Contact ahenoapp@gmail.com for information about the current arrangement relevant to your request; this notice does not invent an unverified mechanism.

• Firebase privacy and security ↗
• RevenueCat Privacy Policy ↗
• Vercel Privacy Notice ↗

Information is kept only as long as needed for the described feature, security, dispute, and legal purpose. Some verified technical limits are exact: API idempotency records expire after 24 hours; terminal notification-delivery rows are removed after 30 days; and plan history is bounded to the latest 20 snapshots. Community reaction records include a seven-day expiry marker, but physical deletion timing is not promised here because the deployed cleanup behavior is not confirmed. Vercel states that the Web Analytics visitor-session hash is discarded after 24 hours; aggregated website statistics follow the provider's applicable retention and configuration. This is separate from the app's 90-day product-analytics retention.

Deleting a post removes its body and leaves a tombstone needed for feed consistency. Account deletion asynchronously removes the Firebase identity and then deletes the account row and cascading service records. A limited pseudonymous deletion-audit receipt can remain to prove that a request was completed or to meet security and legal needs.

Community traffic logs include the user reference, IP address, port, action, and target reference for abuse prevention, moderation, security, and relevant legal obligations. They are retained for one year. Account deletion removes the direct user link and can leave a pseudonymous subject digest with the remaining traffic record until retention expires. Current reflection records are subject to a 13-month retention limit; historical legacy focus outcomes have a separate lifecycle and are not promised immediate deletion by a client upgrade. Infrastructure and provider logs follow the deployed provider configuration and applicable necessity; this notice does not state an unsupported fixed period for them. Backups may retain deleted records for a limited recovery cycle before rotation, without returning them to ordinary use.

Depending on applicable law, you may request access, a copy, correction, deletion, restriction, objection, portability, information about processing and recipients, or withdrawal of consent. You may also complain to the competent authority. Identity verification and legal exceptions can apply; Aheno will explain the outcome rather than promising that every request must be granted in every jurisdiction.

Community access requires age 13 or older and any higher local minimum or parental involvement required by law. Posting and rankings may require an eligible adult account; younger participants may have view-only access where offered. Follow the eligibility controls shown in the app.

Aheno uses platform authentication, attestation, encryption and hashing where appropriate, access controls, rate limits, and data minimization. No online service can promise absolute security. Report a suspected account or privacy issue promptly to ahenoapp@gmail.com.

• EU General Data Protection Regulation ↗
• KVKK disclosure information ↗
• Data Rights & Deletion Guide

This notice will be updated when product behavior, providers, purposes, rights, or material retention rules change. The version and date at the top identify the text in force. Material changes may also be announced in the app where appropriate.

Privacy, data-rights, provider, transfer, or security questions can be sent to ahenoapp@gmail.com. Include your account email or internal identifier only when needed to locate the account; do not send passwords or payment credentials.