Privacy policy
Your records stay local. Optional features use the services explained here.
Auralog stores your migraine history on your device. Health, weather, purchase, feedback, analytics, and natural-language features may process limited information through Apple or the service providers described below.
Who is responsible for Auralog
Auralog is developed and published by Aberfeldy Studios, LLC. Questions about this policy or Auralog’s data practices can be sent to adrian@aberfeldystudios.com.
This policy describes this website and the Auralog 27 codebase. During the preview period, the App Store may still offer an earlier version whose optional integrations differ. The installed app’s permission prompts and the App Store privacy disclosure identify the controls and disclosures for that release; contact us if you need details about an earlier build.
Data practices at a glance
| Information | Why it is used | Where it is processed |
|---|---|---|
| Migraine records, including timing, severity, symptoms, treatments, notes, possible triggers, and saved weather context | To provide history, search, reports, widgets, Live Activities, Siri, and Apple Watch features | Stored by Auralog on your device and in its local app-group storage |
| Optional HealthKit information | To add selected sleep, exercise, active-energy, basal-temperature, menstrual-cycle, and biological-sex context | Read from HealthKit on your Apple devices after permission; Auralog does not write to HealthKit |
| Optional location or chosen city | To request local weather and build weather context | Processed by Auralog and Apple WeatherKit; saved records may include resulting weather conditions |
| Typed or dictated trigger-related text and a limited set of existing trigger labels | To organize possible triggers from natural language | Processed on-device or with Apple Private Cloud Compute when available; an automatic fallback may use AIProxy and OpenAI |
| Onboarding, permission-flow, and technical error events | To understand setup problems and improve the app | Processed by TelemetryDeck in production builds |
| Purchase and subscription information | To show purchase options and verify Premium access | Processed by Apple and RevenueCat |
| Feedback you choose to submit | To receive feature requests, votes, comments, or support details | Processed by WishKit and Aberfeldy Studios |
Local migraine records
Auralog’s SwiftData store is configured for local storage rather than CloudKit synchronization. Your migraine history is not uploaded to an Aberfeldy Studios account or database because Auralog does not create an Auralog account. App extensions may use Apple app-group storage so Auralog, its widgets, and related Apple Watch features can share the information needed to work together.
Your device, backups, operating system, and any exports you create are governed by the settings and services you choose. You can delete individual records in Auralog, export available history in CSV, PDF, or JSON formats, and remove the app and its local data through Apple’s device controls.
Optional HealthKit access
If you enable health context, Auralog may request read access to sleep analysis, workouts, Apple Exercise Time, active energy, basal body temperature, menstrual flow, and biological sex. These categories help create optional condition context. Auralog’s HealthKit write set is empty: it does not add or alter HealthKit records.
You control HealthKit access through Apple’s Health app and device settings. Core migraine logging remains available without granting HealthKit access, although health-context features will have less information.
Location and weather
If you grant location access, Auralog can request conditions for your approximate current location through Apple WeatherKit. You can instead choose a city. Weather results such as pressure, humidity, temperature, and precipitation may be saved as context beside a migraine record; Auralog does not need to store a continuous location history to provide this feature.
Natural-language trigger processing
When you ask Auralog to organize possible triggers from typed or dictated text, Auralog first uses available Apple processing paths, which can include on-device models or Apple Private Cloud Compute. If those paths are unavailable or do not produce a usable result, Auralog can automatically use a remote fallback through AIProxy and OpenAI.
The fallback request can include the trigger-related text you entered and a bounded subset of saved trigger names, descriptions, and aliases needed to classify or merge suggestions. It does not intentionally send your complete migraine database. AIProxy is configured without its optional stable identifier, but its published policy states that it logs the originating IP address and response status for routed calls. Do not place information in a trigger note that you do not want processed in this way.
Analytics, purchases, feedback, and diagnostics
TelemetryDeck
Auralog sends defined onboarding and permission-flow events, plus associated technical error text, to TelemetryDeck in production builds. Auralog does not intentionally place migraine-record text or HealthKit values in these analytics events. TelemetryDeck describes its service as privacy-focused and anonymizes identifiers under its published practices.
RevenueCat and Apple
Apple processes App Store purchases. RevenueCat helps Auralog display purchase options, restore purchases, and determine whether Premium access is active. These providers may process transaction, app, device, and account-related information under their policies.
WishKit
If you open the feedback feature, WishKit processes the feature request, vote, comment, contact information, or related technical information you choose to provide. Avoid including private health details in product feedback.
Apple diagnostics
If you choose to share analytics and diagnostics with developers through Apple’s settings, Apple may provide crash and technical diagnostic information. Auralog uses that information to investigate reliability problems.
Service providers
- Apple Privacy Policy — App Store, HealthKit, WeatherKit, Private Cloud Compute, Siri, Apple Watch, diagnostics, and device services.
- RevenueCat Privacy Policy — subscription and entitlement management.
- TelemetryDeck Privacy Policy and Privacy FAQ — product analytics.
- WishKit Privacy Policy — product feedback.
- AIProxy Privacy Policy — remote AI request routing.
- OpenAI Privacy Policy — remote model processing used by the AIProxy fallback.
Sale, disclosure, and retention
Aberfeldy Studios does not sell personal information. Limited information is processed by the service providers listed above to operate features you use. Local Auralog records remain until you delete them or remove the app and its data. Information processed by Apple or third-party providers is retained according to their policies and your account or device settings.
Your choices
- Use core logging without HealthKit or location permission.
- Change HealthKit, location, notification, Siri, and diagnostic permissions in Apple’s settings.
- Choose a city rather than current location for weather context.
- Review and delete migraine records in Auralog.
- Export available history before deleting the app if you want to keep a copy.
- Contact us about support records, correction requests, or privacy questions.
This website
The Auralog website does not use advertising trackers or first-party analytics cookies. The hosting provider and third-party assets used by some blog pages may receive standard request information such as IP address, browser type, and requested URL. App Store and policy links take you to external services governed by their own policies.
Changes to this policy
We may update this policy when Auralog’s features, processors, or legal obligations change. The effective date at the top identifies the current version. Material corrections will be reflected on this page.
Contact
Email adrian@aberfeldystudios.com or use the Auralog support page. Developer: Aberfeldy Studios, LLC.