Migraine Meta

Legal

Privacy Policy

Effective 8 August 2026 · Last updated 8 August 2026

The short version. Migraine Meta has no account and no server. Your migraine record — attacks, symptoms, doses, notes, check-ins, health figures — is stored on your own device and is never transmitted to us or to anyone else. Two optional features use the network: subscription verification, which sees a store receipt and an anonymous identifier, and barometric pressure, which sees a place and a date. Neither can see your record.

1. Who this is

Migraine Meta (“the app”) is published by Siddhant Singh (“we”, “us”), an independent developer. For anything in this policy, including privacy requests, write to sidd.develops@gmail.com. We are the data controller for the limited processing described in section 4.

2. Contents

  1. What the app stores, and where
  2. What touches the network
  3. Health & fitness data
  4. What we never do
  5. Legal bases (GDPR)
  6. Your rights and how to use them
  7. Retention and deletion
  8. Security
  9. Children
  10. Changes to this policy

3. What the app stores, and where

Everything you log is written to a single file in the app's private storage on your device: attacks and their symptoms, severity and duration; medications and doses; free text and voice notes; daily check-ins; your profile answers; and any figures imported from Apple Health or Health Connect. There is no account, no sign-in, and no copy of this file held by us.

The record is deliberately kept out of cloud backup on both platforms — excluded from iCloud and iTunes backups on iOS, and excluded from cloud and device-to-device transfer on Android. This means your migraine diary is not uploaded to Apple or Google as part of a device backup. It also means that if you lose the device, the record is gone unless you exported it. Export, in Settings, is the backup, and the file it writes goes wherever you send it.

The app also keeps a local error log — stack traces from failures on your device only. It contains no diary content. It is never sent automatically; you can read it in Settings and decide whether to share it with us.

4. What touches the network

Two features make network requests. Both are described here in full, and the boundary between them and your record is enforced by an automated test in our source, not merely promised.

The only two network features, and exactly what each one sends.
FeatureWho receives itWhat they receiveWhy
Subscription RevenueCat, Inc., plus Apple or Google as the store The store purchase receipt, an anonymous app user ID that RevenueCat generates itself, purchase and renewal events, and standard technical data such as app version, platform and country of the storefront To verify the purchase server-side, keep the entitlement current across renewal, refund and revocation, and restore purchases on a new device
Barometric pressure (off by default) open-meteo.com A place name you type when searching, and thereafter a coordinate rounded to roughly a kilometre plus the dates being asked about To attach the pressure change for that day to the day you logged, so pressure can be tested like any other exposure

Nothing about your attacks, symptoms, medications, notes or health figures is included in either request. No advertising identifier is collected. We do not call logIn on RevenueCat, so no identity of yours is ever attached to the subscription record — the identifier is opaque and generated on the device.

Traffic to both services is encrypted in transit. Their own handling of what they receive is governed by their policies: RevenueCat and Open-Meteo.

5. Health & fitness data

With your explicit permission, the app reads sleep and step figures from Apple Health (HealthKit) or Health Connect. The permission is read-only. The figures are used for one purpose: to prefill your own daily check-in so you don't type what your phone already knows. They are stored with the rest of your record on the device.

We never write anything back to Apple Health or Health Connect, never transmit health data anywhere, and never use it for advertising, marketing, profiling or any purpose beyond showing you your own numbers. You can revoke the permission at any time in your platform's health settings; the app continues to work, and you type the figures yourself instead.

6. What we never do

7. Legal bases (GDPR / UK GDPR)

For data kept only on your device we are not processing it — you are, on your own equipment. For the two network features:

Health data in the app is special-category data under Art. 9. It is processed on your device with your explicit consent (Art. 9(2)(a)) and is never transmitted to us.

RevenueCat operates in the United States; transfers of the limited purchase data described above rely on the European Commission's Standard Contractual Clauses.

8. Your rights and how to use them

Depending on where you live you have rights to access, correct, delete, port, restrict or object to processing of your personal data, and to withdraw consent. Because your record lives on your device, most of these you exercise directly and instantly, without asking us:

For the purchase data held by RevenueCat, email us at sidd.develops@gmail.com and we will action it within 30 days. Note that we cannot identify you from that data on our own — the identifier is anonymous — so we may need the store transaction details from you to find the record. Residents of the EEA and UK may complain to their supervisory authority; residents of California may exercise CCPA/CPRA rights without any change in service or price, and we do not offer financial incentives.

9. Retention and deletion

Your record is retained on your device for as long as you keep it, and is destroyed when you delete it or uninstall the app. Purchase records held by RevenueCat and by the app stores are retained as long as needed for subscription management and for the tax and accounting records the stores are required to keep. Pressure lookups are stateless requests; the resulting number is stored with your record on the device.

10. Security

The record is written atomically, so an interrupted write cannot corrupt it, and a file that fails to parse is quarantined rather than discarded. On iOS the app requests the default data-protection entitlement, so the file is protected by the device's own encryption; on Android it sits in app-private storage on an encrypted device. Optional biometric or passcode lock is available in Settings. Network requests use TLS.

No system is perfectly secure, and the strongest protection here is architectural: there is no central store of anyone's migraine diary to breach.

11. Children

The app is rated 12+ and is not directed at children under 13. We do not knowingly collect personal information from children. Since there is no account and no server, a child using the app on a family device leaves nothing with us; a parent or guardian can delete the record in Settings at any time.

12. Changes to this policy

If this policy changes materially we will update the date at the top and, where the change affects what leaves your device, note it in the app's release notes. Continuing to use the app after a change means you accept the updated policy.

13. Contact

sidd.develops@gmail.com — for privacy requests, questions about any of the above, or to tell us this document is wrong somewhere.

This policy is published in English. Your in-app rights — export, correction and erasure in Settings — are labelled in German, Spanish, French, Italian, Japanese, Korean, Portuguese and Chinese inside the app. Do not machine-translate this page; human translation per locale is required.