PRIVACY
Privacy Policy
Effective: November 19, 2026 · Applies to the Aescle iOS and Mac apps
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 to the services described 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. Companion sync, AI coaching, and requested weekly emails can also transfer personal data as described below.
Companion sync uses Apple CloudKit for desktop activity, routines, preferences, check-ins, and derived coaching context, including readiness, recovery and sleep-related signals. Check-ins can include health information you report. Sync uses your private iCloud database or a CloudKit share you explicitly configure with another Apple account. This is separate from Apple Health's own sync and from the encrypted relay described below. Turning off AI does not turn off sync.
Encrypted companion relay. When configured, the iPhone uploads an encrypted health timeline to our service for the Mac. Approving Mac Coach access also enables a bounded copy of health history (including individual samples), calendar events, profile details, coaching conversation and memory. Structured clinical records, genome and bloodwork stores are excluded; information you type into messages can still be included. Calendar AI permission controls sending titles to OpenAI, not copying calendar events to your paired Mac. Relay copies expire 45 days after their last upload, and continuing sync refreshes that period. Payloads are encrypted before upload, but the service receives a credential from which the encryption key can be derived. This is not a promise that Aescle cannot decrypt them.
2. Apple Health & Clinical Records
With your permission, Aescle reads data from Apple Health to personalize your risk profile and trends. This includes:
- Vitals, activity, and sleep — heart rate, resting heart rate, heart rate variability, VO₂max, respiratory rate, blood oxygen, wrist temperature, steps, exercise time, active energy, time in daylight, sleep, and workouts, along with characteristics such as date of birth, biological sex, height, and body mass.
- Clinical records (US only) — lab results, clinical vital signs, medications, conditions, allergies, immunizations, and procedures that you have downloaded into Apple Health from your healthcare providers.
Aescle requests read access to personalize daily guidance, performance insights and your health-risk profile. With separate write permission, intake entries you log can write caffeine or alcohol records to Apple Health. 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. In addition to companion sync above and analytics below, these features transfer data:
- Calendar and coaching analysis. When you enable Calendar AI, event titles are sent for schedule interpretation. When you separately enable AI coaching or routine editing, your messages and relevant context are sent to our AI provider (OpenAI), through a proxy we operate, to categorize how you spend your time and generate user-facing routine, readiness, and scheduling recommendations. Calendar details may include calendar names and event identifiers, titles, start and end times, all-day status, and event status. Health summaries may include recent sleep, activity, exercise, workout, and recovery information calculated on your device, such as totals, averages, trends and coverage. Coaching tools do not send individual Apple Health samples or full session records to OpenAI. These summaries do not include clinical records, genome data, or bloodwork. We do not add your account email to these requests; names or other identifying details you include in messages or calendar titles can still be present. The data is not used to train the provider's models. The AI proxy is designed not to persist request or response contents. Companion relay storage is separate and has the retention described above. OpenAI may retain API content in abuse-monitoring logs for up to 30 days by default, subject to its published exceptions. Disabling response storage does not remove those logs. You can turn AI coaching off in More → Coaching.
- Voice input. When you use voice input, audio is sent through Aescle to OpenAI for transcription.
- Requested email delivery. If you ask Aescle to email the Mac app link, the email address you enter is sent to Resend solely to deliver that message.
- Weekly review email. If you ask for your Week in Review by email, your address is sent to Resend to deliver a confirmation link. After you confirm, each Sunday your iPhone or Mac sends our server your full weekly review, as the app shows it: each measure with its days, such as productive hours, sleep, distraction, and how you rated your days; each standard with the days you kept or missed it; when in the day you worked or felt best; your focus for next week; and anything else the review noticed. Our server passes the review to Resend to send the email and does not keep the review content in our application store. Email providers and your mailbox may retain delivered content. We store your address, whether you confirmed it, and whether you unsubscribed, so the email reaches only you and stops when you ask. The review never includes clinical records, genome data, or bloodwork from their structured stores.
Structured clinical records, genome data, and bloodwork are excluded from these transfers; anything you include yourself in a message or voice input is sent with that input. Turning off AI features stops transfers through the AI path; companion sync and requested weekly emails are separate.
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 sign in with Apple or Google, provide an email address for a requested email, and allow push notifications. Aescle does not ask you to create an Aescle password. Sign-in is separate from connecting Google Calendar, purchasing membership, and iCloud sync.
If you sign in, our account service stores your provider identifier, an Aescle account identifier, your email address when the provider supplies it, and session information. For Apple sign-in, we also store a refresh token so we can revoke authorization when you delete the account. The app stores its account session in the iOS Keychain. Signing in does not migrate your existing local history or companion data into that account.
- Email is optional and skippable. The only product email Aescle sends is the weekly review, and only after you ask for it and confirm your address from a link. Each one has a one-click unsubscribe link, and you can turn it off in Notification settings. Aescle does not send marketing emails.
- Push notifications require registering a device token with our messaging provider so we can send readiness reminders and re-engagement messages. You can turn off notifications in iOS Settings at any time.
Requested emails are handled by Resend, while device tokens are handled by OneSignal. No health data is attached to device tokens or to transactional emails. The weekly review email carries your full weekly review, as described above.
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:
- Apple: Health permissions and CloudKit companion sync described above.
- Managed storage: our APIs use Redis storage for relay copies and email subscription and sign-in account records.
- Sentry: crash and error diagnostics. The app filters diagnostic metadata and disables screenshots, session replay and default personal-information collection.
- OpenAI — AI classification, coaching analysis, and transcription. If you use the applicable features, receives the limited calendar details and health summaries described above and, if used, voice input. This data is used to return the requested user-facing feature and is not used to train OpenAI's models. See OpenAI's privacy policy.
- OneSignal — push messaging. Receives your device push token and an app-generated installation identifier. See OneSignal's privacy policy.
- Resend: requested email, such as the Mac app link and the weekly review. Receives the email address you enter and, for the weekly review, your full weekly review. See Resend's privacy policy.
- PostHog — product analytics. Receives interaction events and technical metadata, no health data. See PostHog's privacy policy.
- RevenueCat — subscription and purchase management. Receives purchase state and an app-generated identifier that can be linked to product analytics. See RevenueCat's privacy policy.
- Google — optional account sign-in and Calendar access, if you connect it. Account sign-in requests identity and email access separately from Calendar. We request read-only calendar data and, only when you choose calendar write-back, permission to manage events on a dedicated Aescle calendar. We use it only for the user-facing calendar and coaching features described above. See Google's privacy policy.
- Vercel — hosts our APIs, including the AI proxy and companion relay. Receives standard request logs. See Vercel's privacy policy.
7. Your Choices & Data Control
Health access, calendar, notifications, and weekly email are independently controllable. Revoke Health access in Apple Health or Settings, Google access in your Google Account, and notifications in system settings. Turn AI permissions off in More → Coaching. Unsubscribe from weekly email through its link or Notification settings; this stops delivery but does not delete the subscription record or emails already delivered.
Revoking access stops new access through that permission; it does not erase existing copies. Removing a Mac's Coach access blocks its authenticated requests but does not erase downloaded data. Removing the last approved Mac also stops new Coach-context uploads from that iPhone; the separate health timeline relay and CloudKit companion sync are not disconnected. Deleting the app removes its local app storage, not CloudKit records, relay copies, other devices' copies, or source records in Apple Health and Google Calendar. The reset tool is currently available only in internal builds. To request deletion, open More → Request data deletion, or More → Account → Delete account. The request covers your connected Aescle workspace, including paired phones and Macs, and any Aescle account you are signed into. It does not delete another person's workspace. You can submit and check its status in the app without emailing support. We complete deletion within 30 days and show the request's deadline. You can cancel while the request is pending, before cleanup starts. We do not show completion until cleanup is confirmed.
Deletion includes applicable Aescle history, coaching data, synced copies, and the linked sign-in profile. Apple sign-in authorization is revoked when an Apple-linked account is deleted. Source records in Apple Health and Google Calendar remain with their providers. Deleting Aescle data does not cancel an App Store subscription; use Apple's subscription settings to manage billing. We may need device-side steps to remove private iCloud and offline device copies; the in-app request remains pending until applicable cleanup finishes.
Pending requests retain the identifiers needed to carry out your request. After cancellation or confirmed completion, we remove the linked account and installation references from the request body and keep a minimal status receipt for 30 days so this installation can check the result. The receipt lookup is tied to this installation; it is not a public directory. We retain content-free revocation markers for deleted installation and relay credentials to prevent old devices from uploading deleted data again.
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.
- Encryption in transit. Connections to Google APIs, our AI proxy, and our service providers use HTTPS/TLS encryption.
- Protected credentials. Google OAuth access and refresh tokens are stored in the iOS Keychain using secure operating-system storage. We do not store Calendar access or refresh tokens on Aescle servers. Optional account sign-in uses separate server-side credentials and sessions, including the Apple refresh token described above.
- Protected local storage. Locally retained Calendar data is kept within Aescle's private iOS app sandbox and is protected by iOS device-security and Data Protection mechanisms. We recommend keeping iOS current and using a device passcode or biometric lock.
- Least-privilege access. Aescle requests read-only Calendar access by default. Write access is requested separately, only when you choose calendar write-back, and is limited to a dedicated calendar created by Aescle. Access is limited to the data and processing needed for the user-facing features described in this policy.
- Limited server processing. Our proxy processes AI requests over encrypted connections and is designed not to persist request contents or model responses. AI requests are configured not to be stored for model improvement. Human access to Google user data is prohibited except with your explicit consent or when necessary for security or legal compliance.
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.