1. Our approach
Art Place (“the developer”) respects the privacy of people who use Migraine Diary (“the app”). The app helps you record and review your own headache symptoms and related context.
No account is required, and the developer does not store your headache diary on a developer-operated server. Device capabilities and third-party services are used only when needed for a feature and based on your permission or action.
Content you enter about headaches or your body is never sent to Google Analytics.
2. Information stored on your device
The app primarily stores the following on your device:
- Pain intensity, time slot, symptoms, locations, and pain-map points
- Medicine use and names, possible triggers, and free-form notes
- Latitude and longitude associated with an entry
- Captured weather, temperature, sea-level pressure, and precipitation (including precipitation probability previously captured by an older version)
- Weather-chart images, typhoon or tropical-cyclone details, and calculated distance to the center
- Device barometer readings and short-term pressure change
- Snapshots of HealthKit data you permitted
- Reminder, display, and Health-integration settings
- Support count and processed purchase identifiers used to avoid duplicate handling
- The date on which the daily free entry was used and the remaining entry credits earned from rewarded ads
This information is used to create, display, edit, delete, and review records and to retry missing captures.
3. Location and weather
With your permission, the app requests your current location when recording and when displaying weather information. For future weather forecasts, coordinates are rounded to four decimal places and sent to MET Norway. For past observations, the app selects the nearest JMA AMeDAS station on the device and sends its station ID and requested time range to JMA. Headache entries, notes, medicine details, HealthKit data, device-barometer readings, and advertising identifiers are not sent to either weather service.
Coordinates are also stored with the on-device entry and used on the device to calculate distance from typhoon-center coordinates supplied by the Japan Meteorological Agency (JMA). Location is not used to personalize ads or track you.
MET Norway may process coordinates, IP address, request time, and request details to provide and operate its weather service. JMA may likewise process standard connection information, station ID, and the requested time range.
4. HealthKit (Apple Health)
If you enable Health integration and permit individual data types in Apple’s authorization sheet, the app can handle:
- Sleep during the preceding 24 hours
- Steps from midnight to the record time
- The latest resting heart rate during the preceding 24 hours
- A headache symptom corresponding to the intensity recorded in the app
Read values are stored as snapshots with the on-device diary entry. Headache symptoms are written to HealthKit and are updated or deleted when the corresponding entry changes.
HealthKit information is never used for advertising, marketing, profiling, or data mining, and is never shared with a third-party advertising service.
You can change Health permissions in iOS Settings or the Health app. Turning integration off does not automatically remove data already stored in HealthKit or existing on-device snapshots.
5. Weather information and past-entry comparison
The Weather view inside the Calendar tab retrieves local pressure, precipitation amount, and weather conditions from MET Norway, and typhoon or tropical-cyclone tracks from JMA. On the device, it compares them with diary entries from the previous year that include weather data, then shows the weather outlook through the same weekday next week, up to seven weather-similar saved entries, and the average and range of their recorded pain values. These past-record summaries are not predictions or assessments of future symptoms or pain.
Future weather forecasts and comparison results are not saved as diary entries or sent to an advertising service or the developer. This feature does not read device calendar events.
You can change location permission at any time in iOS Settings. The observed Calendar view and diary features remain available without it.
6. Device pressure
On a supported device, and with Motion & Fitness permission, the app reads barometric pressure at the time of a diary entry and over approximately 30 seconds. The values are stored with the on-device entry and are not used for advertising.
7. Notifications
If you allow notifications and enable reminders, the app schedules local notifications for 8:00, 12:00, and 19:00. Diary content is not sent to an external server to deliver these reminders.
8. Usage measurement (Google Analytics)
Google Analytics measurement is off by default. The app does not interrupt you with a decision at launch. Measurement is enabled only if you explicitly turn on “Share Usage Data” in Settings, where you can change this choice at any time.
When enabled, Firebase Analytics collects basic usage information—such as app launches, sessions, engagement time, device model, OS and app version, language, and approximate region derived from the IP address—an App Instance ID, and StoreKit in-app purchase and subscription events (such as product ID, product name, and price). The only developer-defined events are the following two, and neither has parameters:
- The number of times you open Calendar from another tab
- The number of times you switch from Observed to Weather in Calendar
The app does not measure pain, symptoms, medicine, notes, pain maps, other entered content, creation, editing, deletion or viewing of entries, selected dates or ranges, precise location, HealthKit, device pressure, weather data, forecasts, analysis results, or payment-card details.None of those values is attached as an event parameter. Automatic screen reporting, IDFV collection, and ad-personalization signals are also disabled.
Analytics uses an app-scoped App Instance ID. It is not a name or email address, but it is treated as a pseudonymous identifier rather than anonymous information. Turning sharing off stops future collection and resets the Analytics identifier stored on the device. Google Analytics event and user data is retained for two months, although aggregated reports created during that period may remain longer.
Data sharing with Google
Google Analytics is a business tool. The developer uses it only for commercial, business, technical, and professional purposes related to operating and improving the app. If you enable sharing, the basic usage information, App Instance ID, purchase and subscription events, and two developer-defined events described above are sent to Google Analytics and become subject to the Google data-sharing settings.
The app’s Google Analytics property uses the default Google Analytics data-sharing settings. The following sharing options are currently enabled:
- Sharing Analytics data with Google to help improve Google products and services
- Sharing Analytics data with Google to enable benchmarking
- Sharing Analytics data with Google to enable technical support
- Sharing Analytics data with Google account specialists
The developer uses Google Analytics after agreeing to the Google Analytics Terms of Service. These settings do not collect new Analytics data from people who turn usage sharing off in the app. The restriction against collecting entered diary content remains in effect under every sharing option.
9. Advertising
Free use includes one ad-free new entry per device-local calendar day, restored at midnight. After that allowance is used, a Google AdMob rewarded ad loads only if you choose it. Completing the ad grants three additional entry credits stored on the device until used. Ads are never inserted automatically into regular screens, no credits are granted if the ad is closed early, editing and deletion do not consume credits, and an active supporter membership provides ad-free unlimited new entries.
Ads are always requested as non-personalized. However, through the Google Mobile Ads SDK and User Messaging Platform, Google may process IP address, approximate region inferred from IP or similar signals, app- or developer-scoped device identifiers, device, OS and app information, ad interactions, consent status, and diagnostic information for ad delivery, frequency control, aggregated reporting, fraud prevention, consent management, and measurement. Consistent with the SDK Privacy Manifest declarations, the App Store privacy label treats Device ID as data used for third-party advertising and measurement and for tracking. Ad-consent information is refreshed at launch, and a consent form and privacy-options entry are provided where legally required.
The app does not send pain, symptoms, medicine, notes, pain maps, precise location, HealthKit, device pressure, weather data, forecasts, or analysis results to advertising services.Publisher first-party ID and ad personalization are disabled. The app does not request App Tracking Transparency (ATT) permission or use IDFA. The Device ID described above may include app- or developer-scoped identifiers other than IDFA.
10. In-app purchases
The app may offer consumable in-app purchases and monthly or annual auto-renewable subscriptions that support development. Apple’s App Store and StoreKit process purchases and billing. The developer does not receive your payment-card details.
If you enable usage sharing, StoreKit purchase and subscription events (such as product ID, product name, and price) are sent to Firebase Analytics, associated with an App Instance ID, and used to analyze app usage. Payment-card details are not sent.
A limited purchase identifier is stored on your device to prevent duplicate handling and update the local support count. To provide the supporter badge and ad-free unlimited-entry benefits, the app also checks the currently active subscription and its expiration date through StoreKit on your device.
Consumable purchases are not restorable. Auto-renewable subscriptions can be restored in the app and reviewed, changed, or canceled in Apple Account subscription management.
11. Contact messages
If you contact us by email, your email address, message, and attachments are used to respond, investigate problems, and improve the app. Please do not send health or location information that is unnecessary for support.
12. Retention and deletion
On-device records remain until you delete them in the app or delete the app’s data. Information may remain separately in an iOS backup or HealthKit after app deletion. Headache symptoms saved to HealthKit can also be reviewed and deleted in the Health app.
To request deletion of information you sent by email, contact the address below.
13. Third-party services
14. Support website
This website is delivered through Firebase Hosting but does not use Firebase Analytics, cookies, contact forms, or advertising. Firebase or Google infrastructure may process standard access-log information such as IP address, access time, and User-Agent for delivery and security.
15. Changes and contact
This policy may be updated when features or applicable requirements change. Material changes will be announced on this website or in the app.
Contact: programmingfeelsgood@gmail.com
Effective and last updated: August 24, 2026