PRIVACY

Privacy Policy

Effective: July 28, 2026 · Applies to the Aescle iOS app

Short version: Aescle reads your health data — including Apple Health and clinical records from your providers — and computes your risk profile on your device. A small, named set of data leaves your device only to power specific features you turn on, and only to the processors listed below. We never sell your data, never use it for advertising, and never send your health values to our analytics.

1. On-Device by Default

Aescle is a local-first app. The health inputs it works with — Apple Health metrics, Apple Health clinical records, and any bloodwork, genome, or demographic data you provide — are read and processed on your device to build your mortality and risk profile. This computation does not require an account and does not send your health data to us.

Your profile, self-reported updates, and preferences are stored locally on your device (in the app's storage). We do not operate a server that holds your health data.

If you use the Aescle Mac companion app, your desktop-activity and coding-work summaries — along with a small set of derived readiness and activity signals (for example, whether recovery is low or steps are behind pace, never your raw health metrics) — sync between your Mac and iPhone through your own private iCloud account (Apple's CloudKit private database). Your underlying health data (such as heart-rate variability, resting heart rate, sleep, and step counts) is evaluated on-device and does not leave your device through this sync. This data stays inside your Apple account — it is stored in your personal iCloud, not on our servers, and we cannot access it. Syncing requires both devices to be signed in to the same Apple ID, uses your iCloud storage, and stops if you sign out of iCloud or stop using the Mac app.

If you use Aescle on more than one iPhone, your routine and your self-reported check-ins (the readiness score you enter yourself) also sync through that same private iCloud account, so you do not have to re-enter them on each device. As above, this covers only what you tell us directly — your raw health metrics stay on your device and are never included.

2. Apple Health & Clinical Records

With your permission, Aescle reads data from Apple Health to personalize your risk profile and trends. This includes:

Aescle requests read-only access and uses this data solely to estimate your personal risk and prefill your health profile. In keeping with Apple's requirements, health and clinical data obtained through HealthKit is never used for advertising or marketing, is never sold, and is never sent to our analytics. If you enable AI-powered coaching, limited health summaries may be processed solely to provide that user-facing feature as described in Section 3; clinical records are never included in that transfer. You can review and revoke Aescle's access at any time in the iOS Health app or Settings.

3. What Leaves Your Device

A few optional features rely on external services. These are the only paths by which data leaves your device, and each is tied to a feature you choose to enable:

Clinical records, genome data, and bloodwork are not part of these transfers. If you do not enable AI-powered features, calendar and health-summary data does not leave your device through this path.

Google user data. Aescle's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use the calendar.readonly scope to read calendar names and event identifiers, titles, start and end times, all-day status, and event status. If you separately choose “Add to calendar,” we also request the calendar.app.created scope to create a dedicated Aescle calendar and create, update, or remove only the protocol events you ask Aescle to place there. We use this data solely to provide user-facing time categorization, schedule-pressure analysis, routine inference, and coaching recommendations and requested calendar write-back. We do not modify your other calendars or events, use this data for advertising, sell it, or allow humans to read it except as required for security, to comply with law, or with your explicit consent.

4. Email & Notifications

You can optionally provide an email address and allow push notifications. There is no login or password. Email is collected only when you request an email-based action, such as sending the Mac app link.

Requested transactional emails are handled by Resend, while device tokens are handled by OneSignal. No health data is attached to either.

5. Analytics

We use PostHog to understand how the app is used. The events we send describe interactions with the interface — for example, "onboarding step completed" or "tab viewed" — along with standard technical metadata. They never include your health values, clinical records, demographics, genome, or any identifier you entered. This helps us improve the product, not profile you.

6. Third-Party Processors

We rely on the following processors, each for a limited purpose:

7. Your Choices & Data Control

Health access, calendar, notifications, and requested email actions are all optional and independently controllable. You can revoke Health access in the iOS Health app, revoke Aescle's Calendar access from your Google Account, and turn off notifications in iOS Settings. Revoking Google access prevents Aescle from obtaining new Calendar data. Using Aescle's reset control deletes its locally stored Calendar snapshot and removes its Google OAuth credentials from the iOS Keychain. Locally stored Calendar snapshots are otherwise retained until they are replaced by a later sync or you reset or delete the app. Because your profile lives on your device, deleting the app removes that locally stored profile. In internal builds, the integrations reset also attempts to delete the dedicated Aescle calendar before removing Google credentials. If Google access is unavailable, you can remove that calendar manually in Google Calendar.

8. Children's Privacy

Aescle is not directed at children under 13 and we do not knowingly collect data from them.

9. Security

We use technical and organizational safeguards designed to protect Google user data and other sensitive data against unauthorized access, alteration, disclosure, loss, or destruction.

10. Changes to This Policy

If we change how Aescle handles data, we will update this page and adjust the effective date above. Material changes will be surfaced in-app before they take effect.

11. Contact

Questions about this policy can go to richard@snowsignals.com.