Privacy Policy
Everything that applies to Migrelog is here. The general part below covers the website and all apps.
Effective from September 19, 2026
This document is translated from the Czech version for your convenience. In case of any discrepancy between language versions, the Czech version is binding.
In short
- Headache records are health data and stay only on your iPhone and watch, without iCloud and without our server.
- The app only records: it does not diagnose, assess your health or recommend treatment.
- Connecting to Health is optional. The app reads only sleep and cycle data and sends none of it anywhere.
- Your doctor, contact details and check-up dates stay on the iPhone and never appear in the PDF export.
- The server receives only anonymous daily screen counts, never record contents.
This summary is for quick orientation. The full text below is what applies.
What the app does
Migrelog is a headache diary. You log an attack and medication on Apple Watch or iPhone, with a tap or by voice. The app adds up monthly totals and, on request, prepares a PDF for your doctor. It only records data: it does not diagnose, assess your health, recommend treatment, and it is not a medical device.
Core principle: records about your health are processed only by your own devices. They are never sent to my server.
Health data stays with you
- Attack records: start and end, type of pain, intensity, location, symptoms and notes
- Medication taken, stock, purchases and their price
- Sleep and cycle day, if the app adds them from Health (section 4)
- Optional “possible trigger” tags, the attack’s impact on your day, pain two hours after medication and preventive treatment doses
This is data concerning health, a special category of personal data under Art. 9 GDPR. It is stored only on your devices (iPhone and Apple Watch) and is not synced via iCloud. It is part of your regular iPhone backup, which you control. Between Apple Watch and iPhone it is transferred directly via Apple Watch Connectivity. I have no access to this data and I am not its controller.
Doctor visits stay on the iPhone
Your doctor, the practice's contact details, appointment dates, questions for the doctor and visit notes stay on your iPhone only. They are not synced via iCloud and never appear in the PDF export.
Apple Health
Connecting to Health is optional and works only with your permission in iOS. The app reads how long you slept before an attack and menstrual data, to add sleep and cycle day to the record. It writes attacks as “Headache” with a severity. It reads nothing else from Health.
Health data is never sent anywhere, never used for advertising and never shared with anyone. You can revoke access at any time in iPhone Settings → Privacy & Security → Health → Migrelog.
Voice entries
A recording from the watch is transferred to the iPhone (or you record it on the iPhone directly) and transcribed on the iPhone itself using Apple's speech recognition. It is not sent to my server. The app extracts pain type, location, intensity and medication from the sentence itself using fixed rules, without cloud AI. The recording is deleted as soon as you confirm the entry. The language model is downloaded by iOS from Apple.
Export for your doctor
The PDF is created on the iPhone. It contains records for the chosen period and monthly totals, without your name, address, national ID number or any details about your doctor. You decide whom you send or print it for.
Reminders
The appointment reminder, the low-stock alert, the next preventive dose reminder and the “How is it now?” question two hours after medication are local notifications scheduled on the device (the answer is only written to the diary). They need no server and can be turned off in the app's or iPhone's Settings.
Subscription
Migrelog Premium is bought through Apple In-App Purchase. Only Apple sees payment details. The app verifies purchases directly with Apple (StoreKit), without other third-party services and without a user account.
Anonymous usage statistics
To improve the app, it sends daily counts: how often each screen was shown, on which screen the app went to the background, and how often the paywall was shown and for which feature it ended in a purchase. Only these totals are sent, without any user or device identifier and without any content of your records. They are stored in Firestore (Google/Firebase, region europe-west3) and cannot be linked to a specific person.
Survey and support
The survey in Settings is optional and does not ask about your health: it asks how you heard about the app, why you use it, how you log and whether it helped at the doctor's. Answers are stored in Firestore with only the app version and language, without an identifier or e-mail. If you want to be contacted, section 4 of the general part applies.
Support chat works as described in section 4 of the general part. The app never attaches your records or recordings; only what you type is sent. Please do not write details about your health into the chat or the survey. If you do anyway, I will use them only to handle your request and delete them on request.
What the app does not collect
- Records, recordings or Health data on my servers
- Name, e-mail or an account (an e-mail only if you give it to support yourself)
- Location
- Contacts, calendar or photos
- Advertising identifiers (IDFA)
Retention and deletion
You delete records, medication and doctor details directly in the app; deleting the app removes everything that exists only on the device. Attacks written to Health are deleted in the Health app. Survey answers and support tickets are kept for at most 24 months; you can ask for earlier deletion under section 7 of the general part. Anonymous daily totals contain no personal data.
Contact
Write via Support or directly from the app (Settings → Contact support).
General part (applies to the website and all apps)
Data controller
The data controller is Vojtěch Landa, a private individual, contact: vojtajess@gmail.com. Neologos Development is not a legal entity or a registered business — it's the name under which Vojtěch Landa, as a private individual, develops and runs neologos.dev and the apps listed below.
What this page covers
This privacy policy is shared across neologos.dev, vejce.neologos.dev, and the apps Blackout, Eco, WorthIt, Blurt, Migrelog, and Limi. Each app also has its own section below, since it processes different data depending on what it does — the general part applies to all of them, and the app section adds to it.
Website traffic
neologos.dev collects basic, aggregate traffic statistics (visit counts, pages visited, approximate geographic area from IP address) via Vercel Analytics and, if enabled, PostHog. This data only exists to show whether the site is being used at all — it isn't sold, isn't shared with ad networks, and isn't linked to a name or email unless you provide one yourself (e.g. via the support chat).
Support chat and tickets
The Support section on the website and the support chat inside the apps let you report a bug, suggest an app improvement, ask about legal information or ask a general question. Chat messages are saved as a ticket in Firestore (Google/Firebase, see point 5). Messages in every category are answered by an AI assistant through the Anthropic (Claude) API. Anthropic acts as a processor: it handles the message, including the earlier conversation, only to produce a reply and does not use it to train models.
When you report a bug directly from an app, a technical app log (error messages and app state) is attached to the ticket so the problem can be traced. An email or name is stored only if you type it into the form yourself — it is never collected automatically.
Blackout, WorthIt, Blurt and Migrelog also include a short, optional in-app survey. At the end we ask whether you'd like us to get back to you. If you choose "No", your answers are sent without an e-mail address or any contact detail, i.e. anonymously. If you choose "Yes", your answers are sent the same way and the app opens the support chat with your answers pre-filled in the message and the e-mail address you enter yourself. The message and e-mail are then stored as a ticket as described in this section, and the e-mail is used only to reply to your feedback. The survey record itself stays without an e-mail address.
Shared infrastructure
The website and apps run on Firebase/Google Cloud (Firestore, Cloud Functions, Cloud Messaging) — the servers for the apps and site are set to a European region (europe-west3) wherever Firebase allows it. Google acts as a processor there under its own privacy policy (firebase.google.com/support/privacy).
Push notifications (where an app offers them) use the Apple Push Notification service — Apple only needs an anonymous device token for this, not personal data.
Advertising and cookies
The /brief page (Brief → Prompt) is funded by ads through Google AdSense so it can stay free. No ad script or third-party cookie loads until you consent in the cookie banner at the bottom of the page.
Once you consent, Google and its ad partners may set cookies to measure and personalize ads under their own policies (policies.google.com/privacy). You can manage ad personalization or opt out at adssettings.google.com.
You can withdraw consent at any time by clearing this domain's cookies in your browser — the banner will show up again.
Your rights
Under GDPR, you have the right to:
- access your data
- correct inaccurate data
- erasure ("the right to be forgotten")
- restrict processing
- data portability
- object to processing
- withdraw consent at any time, where processing was based on it
- lodge a complaint with the Office for Personal Data Protection (uoou.gov.cz)
You can exercise any of these rights simply — write to vojtajess@gmail.com or via Support (category "Legal information").
What to expect from me: I'll reply no later than 30 days after receiving the request — either sending, correcting, or deleting the data right away, or explaining why (and on what grounds) that isn't possible. For a more complex request this deadline can be extended once by another two months, which I'll tell you about within the first 30 days. To verify identity I may ask for extra information (e.g. the email or nickname used in the app), so the data doesn't end up with someone else under your name.
Data retention
Tickets and incidents are kept for as long as needed to resolve the request, plus a reasonable period after for traceability (typically up to 24 months), then deleted. Data stored directly in the apps (see the app sections below) follows each app's own rules — most of it can be deleted immediately right in the app.
A conversation with the assistant where you leave no email is kept on the server only as a hidden draft, so it can still be handed to a person if you add an email. Nobody reads it, and it is deleted automatically after 7 days.
Changes to this policy
This policy may change as the site and apps evolve. The current version is always on this page; the date of the last change is shown in the header.
Change history
- First version
Where next