Privacy Policy

for the Migraine Compass app and the website migraenekompass.bk-apps.online

In short: Everything you enter in the app stays on your device. There is no account and no sign-in, and there is neither a cloud nor a server for your entries. There are connections only in two cases, which you trigger yourself and to which you expressly consent beforehand: if you use the weather with Plus, a rounded location goes to my own weather server in Germany. If you consent on the Plus page, the app asks for prices and your purchase status through the service provider RevenueCat. You can withdraw both consents in the settings. The details are below. So that the app can keep and analyse your diary on your device, it also asks for your explicit consent (section 3).

1. Controller

Benedikt Koßmann
Schaurain 4 1/2
83101 Rohrdorf
Deutschland
Email: info@stavau.com

Further details are in the Legal Notice. You can also contact this address with any questions about data protection.

2. This website

Hosting

The website is a static site on a server of Hetzner Online GmbH, Industriestraße 25, 91710 Gunzenhausen, in the data centre in Helsinki, Finland, i.e. within the EU. There is no transfer to a third country. The website of the app PillenKompass by the same provider is also on this server.

A data processing agreement pursuant to Art. 28 GDPR is in place with Hetzner.

Server logs

On every request, the web server (nginx) stores in its access log: the IP address of your device, the time, the request line (method, path, protocol), the status code, the amount of data transferred, the previously visited page (referrer) and the identifier of your browser (user agent, i.e. browser and operating system). A field for a user name always stays empty, because the website has no sign-in. The log is shared by all websites on this server. If an error occurs, the error log also contains the IP address.

Purpose: operating and delivering the website, troubleshooting and defending against attacks. Legal basis: Art. 6(1)(f) GDPR; the legitimate interest is the secure operation of the website.

Storage period: The logs are rotated daily, and 14 daily archives are kept. An entry is therefore stored for at most 15 days and is deleted after 30 days at the latest.

No cookies, no tracking

The website sets no cookies, uses no local storage and no JavaScript, loads no external fonts and nothing from third-party servers (CDN), and contains no tracking. The website stores nothing on your device and reads nothing from it; that is why there is no cookie banner.

3. Your data in the app

Everything you enter in the app stays on your device. There is no account, no sign-in and no cloud; there is no server for your entries. I do not receive your entries.

What the app stores

Legal basis and consent

Your entries are health data. The app processes them on your device so that you can keep and analyse your diary. The legal basis is your explicit consent under Art. 9(2)(a) GDPR, together with your use of the app under the terms of use (Art. 6(1)(b) GDPR). You give it with the “I consent” button: on first start, once after the update if you already used the app, or at any time under “Settings > Consents > Diary on this device”. Nothing is preselected, and “Do not consent” has the same weight. The app stores on your device when you consented and to which version of the text.

Without consent you cannot record new entries or view analyses: the home screen, calendar, statistics including weather, the PDF overview and the import are locked. Exporting as JSON or CSV and “Delete all data” remain possible. Your reminders keep running but then show only neutral texts (“Reminder”, “A reminder is due”), and the “Reminders” page shows no medication names. The name you gave a reminder stays stored on your device.

Withdrawal: You can withdraw your consent at any time under “Settings > Consents > Diary on this device”, as easily as you gave it; the lawfulness of the processing before the withdrawal is not affected. You choose: with “Withdraw, keep entries” you request restriction of processing (Art. 18 GDPR). Your existing entries then stay locked and stored on your device; the app only stores them and exports or deletes them only if you want. With “Withdraw and delete all data” the app takes you to “Delete all data” (below); if you cancel the deletion, the app asks again whether you keep the entries or delete all data; until then they stay locked and stored. If you do not consent after the update, you choose in the same way between “Keep entries” and “Delete all data”. If you consent again later, your entries are unlocked again.

Security

The database is encrypted with SQLCipher. The app generates the 256-bit key randomly on first launch and stores it in storage protected by the Android Keystore. The app is excluded from Android backup and from transfer to a new device: nothing ends up automatically in a Google backup or on another device. Your data only reaches another device if you export it yourself and import it there.

One limitation: the notification library stores scheduled notifications, including title and text, unencrypted in the app's own storage. Without discreet mode, the title is the label you gave the reminder, for example a medication name. This file does not leave the device, but it would be readable for someone with access to the app directory (for example on a rooted device). Discreet mode replaces title and text with neutral texts, in this storage as well.

Export and import

Under “Settings > Back up and transfer data” you can export all entries as a file. Before a JSON file, the app asks whether you want to protect it with a password. With a password, the file is encrypted (AES-256 with a key that is derived from your password using PBKDF2 with 600,000 rounds, protected against modification with HMAC-SHA256); no unencrypted copy of it is created on your device in the process. The app does not store the password. Without this password, the file can no longer be opened. Nobody can recover it, not even me.

Without a password, the JSON file is not encrypted: anyone who has the file can read your entries. In return, it is in a common, machine-readable format. CSV and PDF files are never encrypted. The app hands every export file to the Android share menu; you decide where it goes.

With “Import data” you choose such a file in the Android file picker. The app reads it only on your device, makes no copy and opens no connection for it. If the file is stored with a cloud service, that service’s app downloads it. After a preview and your confirmation, the import replaces all existing entries in the app. Your app PIN, Plus status and settings are not in the file. Nothing reaches me, neither when you export nor when you import. If the file is encrypted, the app asks for the password and decrypts it only in memory.

Deletion and storage period

The data remains stored until you delete it or uninstall the app. The only thing the app deletes on its own is a crash report, once you have decided about it (section 8). You delete individual entries in the app: an attack together with its triggers, a medication, a medication intake from the last 30 days (under "Medications" in "Recent intakes"), a reminder and a symptom entry. If you delete an attack, the medication intakes recorded for it remain stored without the link to the attack; the symptom entries recorded for it currently remain stored. If you delete a medication, the intakes recorded for it so far remain stored.

You remove your own triggers under "Settings > Triggers". If one of your own triggers is not recorded for any attack, it is deleted. If it is recorded for attacks, it is only hidden: it remains stored and stays with those attacks. Once no attack carries it any more, you can remove it there for good. You show hidden triggers and hidden predefined triggers again there.

You delete all data in the app under “Settings > Back up and transfer data > Delete all data”, after two confirmations. This deletes all entries, medications and intakes, reminders including the scheduled notifications, triggers, symptom entries and weather days, the app PIN including the counted failed attempts, all settings and a stored crash report. This cannot be undone; export your data beforehand if you want to keep it.

“Delete all data” also deletes your consents for purchase and weather; after that, the app asks again before it makes any contact. Three items about Plus remain: whether the app may check with RevenueCat, the last known Plus status and the date until which it applies. They are a kind of purchase receipt and contain no information about your health; Google Play restores a purchase anyway, and without your consent the app still does not check with RevenueCat. The database key also remains, so that the emptied database stays encrypted. You also remove these items and the key when you uninstall the app or choose “Clear storage” for the app in the Android settings.

“Delete all data” also deletes your consent for the diary (consent_diary_v1) and the marker diary_consent_asked_v1; after that, the app asks you again when you set it up anew.

Storage on your device is strictly necessary for the diary function you requested (§ 25 Abs. 2 Nr. 2 TDDDG). This concerns access to your device and does not replace the consent above.

4. Weather with Plus (own weather server)

For the weather, the app opens a connection to my own weather server (wetterdaten.bk-apps.online), only with Plus, only in the weather tab of the statistics and only after you have consented there (below). Without Plus or without consent, nothing goes online. That server runs the open-source Open-Meteo software and I operate it myself; it stands with Hetzner Online GmbH in the Nuremberg data centre in Germany, and there is a data processing agreement with Hetzner under Art. 28 GDPR.

What is transmitted: your current position, rounded to 0.25 degrees (about 25 km), the requested time period and the requested weather fields. The time period always runs from today back over the period selected in the statistics; it is not derived from your attacks. On which days you had attacks does not leave the device; the app matches weather and attacks on the device. As with any connection, my server also sees the IP address of your device.

When: As long as you have not consented, the weather tab only shows the consent; the app then neither determines your location nor contacts my server. After your consent: if you have granted the location permission, the app determines the position once per app session when you open the weather tab, otherwise only after you explicitly tap “Use location” or “Try again”. Without a position, there is no request.

Storage in the app: The rounded position is kept only in memory while the app is running. The app caches the retrieved weather days encrypted and without the position. Only weather days retrieved for the same place in the current app session are analysed; the first successful request of a session replaces the stored weather days. If no request succeeds in a session, the tab says so and does not analyse older weather days. Older app versions had also stored the rounded position; since the database update to schema version 3, these values are removed on first launch.

Where the weather values come from: The values are the ERA5 reanalysis of the Copernicus Climate Change Service. My server downloads them from the open AWS bucket of Open-Meteo; they are available under CC-BY 4.0. This download runs independently of your requests: none of your data goes to Open-Meteo or to AWS in the process.

Recipient: I am the recipient myself, on my own server in Germany. There is no further recipient and no transfer to a third country. No access log is kept on the server (access_log off): position, time and IP address are not written down, so there is no retention period for them either. The server keeps an error log only for serious faults. In rare cases such an error line can contain your IP address and the request with the rounded position. These lines are rotated daily and deleted after 16 days at the latest. These lines are part of the secure operation of the weather server that the weather request needs; I use them only to find and fix serious faults and for no other purpose of my own. They therefore rest on the same legal bases as the weather request (below): Art. 6(1)(b) GDPR and your explicit consent under Art. 9(2)(a) GDPR, whose text names this error log.

Legal basis and consent: The weather request is a function covered by the Plus contract that you request in the weather tab (Art. 6(1)(b) GDPR). Because a request from a migraine app together with your location allows conclusions about your health, I also ask for your explicit consent under Art. 9(2)(a) GDPR before the first request. It is a separate consent, independent of the one for purchases; you give it with the “I consent” button. The app stores on your device when you consented and to which version of the text.

Withdrawal: You can withdraw this consent at any time in the app under “Settings > Consents > Weather analysis”, as easily as you gave it. After that, the app no longer fetches weather data and deletes the stored weather days on your device; your entries are kept. The lawfulness of the requests made before the withdrawal is not affected. My server holds nothing from your requests that would need deleting, except for a possible error line (above), which is deleted after 16 days at most.

Responsibility: I am responsible for collecting the rounded position, for transmitting it and for processing it on my own server. Hetzner Online GmbH processes it on my behalf as the operator of the data centre. No further controller is involved in this request.

What my own server means for you: Until 21 September 2026 this request went through an external weather service operated outside the EU; that transfer no longer exists. In exchange, IP address, rounded position and time now come together at my end, whereas with the external service they never reached me at all. Three things stand against that: the position already arrives rounded to 0.25 degrees, the server writes no access log, and on 21 September 2026 I checked every log source on the server for a test coordinate and for the requesting IP address: neither appears anywhere.

5. Buying Plus: RevenueCat

For buying Plus and for checking whether your Plus is valid, I use the service provider RevenueCat, Inc. (USA). When you open the Plus page, you first see a consent there. Only when you consent does the app start the purchase package and contact RevenueCat; without consent, the Plus page shows no prices and there is no contact with RevenueCat. After your consent, the app checks once whether you have Plus and otherwise loads the prices. After that, it asks for the current status once at every app start, also after a purchase or a cancellation, as long as your consent exists. If Google Play confirms a payment only later, Plus appears without a restart; the app does not send an extra request for this. After a reinstallation or on a new device, the app only makes contact again when you consent again on the Plus page. You can also give consent under “Settings > Consents > Purchase and Plus status”. That does not itself trigger any contact; the app only makes contact on the Plus page or, if you have already used the Plus page before, at the next app start.

Without a connection: With every successful check, the app stores until when your Plus runs. Without a connection, Plus applies until that date and then ends on this device until a check succeeds again. If the app does not know a date yet (purchase with an older app version), Plus applies until the next successful check. If the app does not check because you have not consented, the same applies; the Plus page and the Plus row in the settings then tell you what this means for your Plus.

What RevenueCat receives: device type and operating system, the time of last use, the proof of purchase from Google (purchase token) and a random identifier that RevenueCat assigns to your installation. This identifier is not an advertising ID and not an identifier of the device hardware, but it does link your installation at RevenueCat. As with any connection, RevenueCat also sees the IP address of your device. On iPhone, RevenueCat also receives with every request the identifier for vendor (IDFV), which Apple assigns identically to all my apps on your device; it is not an advertising ID either. The app passes on no user identifier of its own, and the transmission of performance data to RevenueCat is switched off. Your diary data does not reach RevenueCat.

After a purchase, the purchase package also stores this random identifier in Google’s Block Store, a storage area of Google Play services on your device. If your device’s Google backup is switched on, the identifier may be included in that cloud backup and survive a reinstall. It is end-to-end encrypted there only if your device supports this and a screen lock is set. Your diary data is not included. The app cannot delete the identifier there, not even when you withdraw consent or use “Delete all data”.

Purpose and legal basis: preparing, at your request, and performing your Plus contract (Art. 6(1)(b) GDPR). If you have not bought anything yet, this contact is based solely on your consent (Art. 6(1)(a) and Art. 9(2)(a) GDPR; for storing and reading the identifier on your device, § 25 Abs. 1 TDDDG). The app then keeps checking at every start whether there is a purchase, until you withdraw your consent. Because even a purchase or the check of your Plus status in a migraine app allows conclusions about your health, the processing is also based on your explicit consent under Art. 9(2)(a) GDPR. It is a separate consent, independent of the one for the weather; the app stores on your device when you consented and to which version of the text. Without it, Plus cannot be bought, because the purchase needs this contact; you do not need it for the free functions (the diary has its own consent, section 3). From the same purchase data, RevenueCat also creates revenue and subscription statistics that only I see. RevenueCat creates them inseparably from handling the subscriptions; I use them only to keep track of that handling and for no other purpose of my own. They therefore rest on the same legal bases as the purchase: Art. 6(1)(b) GDPR and your explicit consent under Art. 9(2)(a) GDPR, whose text names these statistics. There is no disclosure to others, no advertising and no profile across apps.

Withdrawal: You can withdraw this consent at any time in the app under “Settings > Consents > Purchase and Plus status”, as easily as you gave it. After that, the app makes no new contact with RevenueCat; the withdrawal takes full effect after the app is next started, because the purchase package that is already running cannot be switched off before then. On this device, the Plus status from the last check then stays in place; if the app knew an expiry date at that check, Plus ends on that day. Withdrawing does not cancel your subscription; you can cancel on Google Play (section 6). The lawfulness of the processing before the withdrawal is not affected. I do not learn of your withdrawal, because the app does not report it. If you also want me to delete your entry at RevenueCat, write to me (below).

Processing on my behalf and transfer to the USA: RevenueCat processes this data on my behalf (Art. 28 GDPR) on servers in the USA, among others at Amazon Web Services. The transfer is based on the standard contractual clauses of the EU Commission (Art. 46(2)(c) GDPR), which are part of RevenueCat's data processing agreement. You can find the agreement including the clauses at revenuecat.com/dpa.

Storage period and deletion: RevenueCat stores the purchase data for as long as I use RevenueCat for Migraine Compass. At your request, I delete your record at RevenueCat. To do so, write to me at info@stavau.com and give the order number from your purchase confirmation from Google (it starts with "GPA."). Deleting it there does not end a subscription; you can cancel at Google Play (section 6).

Purchase via the App Store: If you bought Plus on an iPhone via the App Store, RevenueCat receives Apple’s purchase data instead of the proof of purchase from Google. For deletion, you then give me the Order ID from the receipt from Apple, the email about your purchase. Deleting it at RevenueCat does not end a subscription, and withdrawing your consent does not cancel it either; you can cancel with Apple (section 6a).

6. Google Play and Android

Payment for Plus runs through Google Play Billing, not through a server of my own. In Germany and the EU, Google is the contracting party for the purchase. Processing by Google is governed by Google's Privacy Policy. You manage and cancel your subscription at Google Play.

For the location, the app uses the location services of Google Play services on your device. These determine the position not only via GPS but also via Wi-Fi, mobile network and Google's own location database. This is behaviour of the platform, not a network request made by the app itself.

6a. App Store and Apple

On an iPhone, payment for Plus runs through Apple’s in-app purchase, not through a server of my own. If you are a customer of Apple Distribution International Ltd. (Ireland), that company is the merchant of record under the Apple Media Services Terms and Conditions. Processing by Apple is governed by the Apple Privacy Policy. For a subscription, Apple creates a Subscriber ID under this policy, through which I as the developer can receive reports about your subscription and your country of residence. You manage and cancel your subscription with Apple: in your iPhone’s Settings under your name and “Subscriptions”, or online at account.apple.com.

7. Contact by email

If you write to info@stavau.com, I process your address and your message in order to answer your request. This only happens if you write yourself. If you open the email from the app, the app opens your mail app with recipient, subject and a pre-filled first line with your consent (below). It attaches no app or Android version and no data. It only inserts a crash report if you explicitly want to send it (section 8). Nothing is sent until you tap send in your mail app.

I run the mail server myself (Mail-in-a-Box) on a rented server of Hetzner Online GmbH in the data centre in Nuremberg, within the EU. No email service provider receives your message on my behalf.

Consent: The mere fact that you write to me as the provider of a migraine app can reveal something about your health, and the message itself often contains information about your health. I process such information only with your explicit consent under Art. 9(2)(a) GDPR. For this purpose, the email from the app contains this first line:

You see this line before sending and can change or delete it. If you write without it, I will ask you for this consent in my first reply before I go into any information about your health. Withdrawal: You can withdraw your consent at any time with effect for the future, informally to info@stavau.com (Art. 7(3) GDPR). The lawfulness of the processing carried out until the withdrawal remains unaffected. After a withdrawal, I delete your message unless a statutory retention obligation applies.

Legal basis for your address and the rest of your request: Art. 6(1)(b) GDPR if your request concerns a contract (for example Plus), otherwise Art. 6(1)(f) GDPR (interest in answering enquiries). Storage period: until your request has been dealt with; the message is then deleted. If it is a business letter that must be retained for tax purposes (for example about a purchase of Plus), it remains stored until the end of the statutory period of six years (§ 147 AO).

8. Crash report

If the app is terminated by an unexpected error, it stores a technical report on your device. It contains the type of error, where applicable the affected program library, at most 20 lines of the program flow (stack trace), the app version, the platform and the time. The app does not store the text of the error message, because it could contain values you entered. Your entries are not in the report.

The report is kept in the app’s private storage, not in the encrypted database and not in the export. There is only ever the newest one; a new one replaces the old one.

On the next launch or unlock, the app shows you the full report and asks whether you want to send it to me by email. “Send report” opens your mail app with the report below the consent line (section 7); nothing is sent until you tap send there. “Don't send” discards it. In both cases the app then deletes the report from your device; “Delete all data” also deletes it (section 3). The app never sends the report itself and uses no service for crash reports.

Purpose: to understand and fix the error. Legal basis for the processing on my side: your explicit consent under Art. 9(2)(a) GDPR (section 7), which you can withdraw at any time. I am the recipient myself; the storage period is the same as for any email (section 7).

10. Permissions

The app's manifest contains these Android permissions:

Included libraries add the following in the final package: Google Play Billing (purchase), fingerprint (part of the biometrics library) and network state (Google's library datatransport). A permission for the advertising ID is not in the package.

If you open the “Check reminders” page in the app, the app reads the name of the device manufacturer on your device in order to show a suitable power-saving tip for some manufacturers. No permission is needed for this. The value is not stored and does not leave your device. The legal basis is Art. 6(1)(b) GDPR (the app function you open). Reading the value on your device is strictly necessary for this page you requested (§ 25 Abs. 2 Nr. 2 TDDDG) and therefore needs no consent.

11. No advertising ID, no network traffic in the free version

The app uses no advertising ID. The purchase package from RevenueCat brings further modules into the package: a connection to the Amazon Appstore, Google's library for the advertising ID and Play Billing with Google's logging library datatransport. The app itself calls none of these additional modules, and it only starts the purchase package after you have consented on the Plus page (section 5).

When the purchase package is running, Play Billing sends log data to Google via datatransport (firebaselogging.googleapis.com). According to Google, this data shows how the purchase interface is used, for example whether calls succeed or fail and whether there are connection problems. Google uses it to improve the library and to help with errors. As with any connection, Google also sees your device's IP address. This data is covered by Google's Privacy Policy; for users in the EEA, it names Google Ireland Limited as the controller, and Google may also process the data on servers outside your country. The legal basis for including the library is Art. 6(1)(f) GDPR; my legitimate interest is being able to sell Plus through Google Play.

A network capture on the emulator (debug build) has checked this: in the free version, across all main areas, the start and a second start, the app opens not a single connection and resolves no name. This also applies to the libraries mentioned. The Plus page and the purchase were not part of this capture. That the app does not contact RevenueCat without your consent, not even on the opened Plus page, is covered by automated tests.

12. Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on Art. 6(1)(f) GDPR (Art. 21). To do so, write to info@stavau.com.

You can withdraw a consent at any time with effect for the future (Art. 7(3) GDPR); the lawfulness of the processing before the withdrawal is not affected. You withdraw the consents for weather and purchase (sections 4 and 5) in the app under “Settings > Consents”, and the consent in an email (sections 7 and 8) informally to the same address.

You also withdraw the consent for the diary (section 3) under “Settings > Consents”. You choose restriction of processing of your diary data (Art. 18 GDPR) there yourself with “Withdraw, keep entries”: your entries then stay locked and stored on your device until you export or delete them.

You can get your diary data yourself at any time in a machine-readable format: the export in the app (section 3) creates a JSON file that you can take with you and pass on.

Your diary data is stored only on your device; I have no access to it. You manage and delete it yourself in the app (section 3).

You also have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). The authority responsible for me is the Bavarian Data Protection Authority (Bayerisches Landesamt für Datenschutzaufsicht, BayLDA), Postfach 1349, 91504 Ansbach, with an online complaint form at lda.bayern.de.

13. No obligation, no automated decision-making

You are not obliged to provide data or to consent. Without location or without your consent, there is no weather request. For buying Plus, the information named in sections 5 and 6 and your consent (section 5) are required; without them, the purchase cannot be completed (Art. 13(2)(e) GDPR). To record and analyse your diary you need the consent from section 3; reminders, export and “Delete all data” work without it. All functions except weather and purchase work without a connection.

There is no automated decision-making and no profiling (Art. 22 GDPR): your entries do not reach me, and the website uses no tracking.

Migraine Compass is not a medical device and does not replace professional medical advice.

Last updated: 7 November 2026