Privacy Policy
1. Scope
This policy applies to the bauchgefühl app, published on Google Play as Period Tracker & Cycle Diet (package ID com.bauchgefuehl.ios, developer hamstr) and on the Apple App Store as bauchgefühl, and to bauchgefuehl.app (together, the “service”). The app provides menstrual cycle tracking, symptom recording and personalized dietary suggestions based on the cycle phase.
2. Controller
The controller under the GDPR is Josef Haras, operating under the developer name hamstr.
Josef Haras (hamstr)
Dr.-Adolf-Schärf-Platz 10/309
1220 Vienna, Austria
VAT ID: ATU75469459
Email: office@bauchgefuehl.app
Website: bauchgefuehl.app
3. Data collected and purposes
3.1 App usage data
We process the following categories:
- Cycle data, including the start and end of menstruation and cycle days.
- Symptoms and wellbeing, such as pain, mood and energy.
- Basal body temperature (optional), if you enter it in “My day”.
- Daily note (free text) in “My day”.
- Cycle context from “My cycle”: rhythm (regular, irregular, no period right now), your goal (“Understand my body better”, “Preparing for pregnancy – nutrition”, “Support me through menopause”) and, optionally, the reason for an absent or irregular period (for example menopause, PCOS, breastfeeding, pregnancy).
- Dietary preferences and intolerances.
- Ingredients and recipes entered by users.
- Email address when registering an account.
- Device information and anonymized usage statistics.
The purpose is to provide app functions: cycle tracking, dietary suggestions and personalized content. Legal bases: Article 6(1)(b) GDPR (performance of a contract) and Article 9(2)(a) GDPR (explicit consent) for health data.
Cycle context. The app stores rhythm, goal and reason on your device and in the encrypted backup (section 3.7). Your goal and rhythm control which recipes, knowledge content and cycle displays you see. Only if you have shared your cycle with Bauchgefühl AI in the app does the app send rhythm, goal and reason along with each question to the chat assistant, so it can frame nutrition tips to your situation, and store rhythm, goal and the reason for an absent period in your account on our server (Supabase, section 4) for companion features such as daily messages. The reason for an irregular period is not stored in your account. If you withdraw that sharing, the app deletes the server copy at the next sync. Apart from the encrypted backup, the app sends the reason itself only with this sharing enabled. For the recipe generator, the following applies regardless of this sharing: if you have stated an absent period because of a pregnancy, the app sends a fixed list of unsuitable foods with every recipe request, from which the pregnancy can be inferred. The app also sends the same list as a precaution if it cannot read your cycle details (section 4, recipe suggestions).
Basal body temperature and daily note. The app stores both in the encrypted database on your device and in the encrypted backup (section 3.7). The app does not pass them to AI functions (chat assistant, recipe suggestions, proactive messages) or to analytics or advertising services.
3.2 Website usage data
When you visit the website, technical data is collected automatically: IP address, browser type, operating system, referrer URL and time of access. This data is required to operate the website and is deleted within 30 days. Legal basis: Article 6(1)(f) GDPR (legitimate interests).
The French and Spanish pages use the same analytics and advertising tools as the German and English pages, with the same cookie banner. These tools set cookies only after your consent; some tags, however, already run before that without cookies (see the sections on Google Analytics, Google Ads, PostHog, Facebook Pixel, Google Tag Manager and Vercel). When you change language, the NEXT_LOCALE cookie remembers your choice for one year. Temporary session storage restores your reading position. The contact form stores a draft locally on your device, which is restored only for 7 days. You can remove this data in your browser settings. Dates entered in the French and Spanish calculators are processed in your browser and are not sent to our server.
3.3 Contact
When you contact us through the website contact form or by email, we store your details to handle the enquiry and possible follow-up questions. We only share this data with the recipients listed in section 4 that we need to handle your enquiry. Legal basis: Article 6(1)(f) GDPR (legitimate interests). We keep contact enquiries for 2 years after correspondence ends (section 5). Recipients of the contact form are listed in section 4.
Cancellation via the website. If you cancel a subscription purchased on the website via “Cancel contracts here”, we process the details in the form (name, email address, type of cancellation and, where given, desired date, reason and matching details) to find and end your subscription with our payment provider Stripe, and we send a confirmation by email to you and to us (via our email delivery provider, section 4). We keep the cancellation as proof until the statutory limitation period expires (usually three years).
Legal basis: Art. 6(1)(b) and (c) GDPR (performance of the contract, legal obligation under § 312k German Civil Code).
3.4 Newsletter and email communication
Website newsletter. With your consent, we send newsletter emails through our email delivery provider (section 4). You can unsubscribe at any time using the link in each email or by contacting office@bauchgefuehl.app. Legal basis: Article 6(1)(a) GDPR (consent).
App service messages. When you start a trial or free access in the app, we send individual service messages to your account email: confirmation at the start and a reminder before access ends. If you have provided a payment method, the reminder precedes the start of a paid subscription and includes the price and cancellation option. These messages form part of contract performance and contain no advertising. Legal basis: Article 6(1)(b) GDPR.
Accompanying emails, only with consent. You may additionally consent in the app to occasional cycle tips and product updates. We record the time and wording of your consent. For these personalized emails, we use your email address and selected account usage details, such as the number of saved recipes and your access expiry date. Your health data—cycle entries and symptoms—is never used for emails. You can withdraw consent at any time through the unsubscribe link or by contacting office@bauchgefuehl.app. Withdrawal does not affect the lawfulness of processing before withdrawal. Legal basis: Article 6(1)(a) GDPR.
Email provider. All these emails are sent through an email delivery provider based in Germany, acting as a processor under Article 28 GDPR. Processing takes place in the EU. Recipient data is stored while your account exists or until consent is withdrawn and is deleted when the account is deleted.
3.5 Push notifications and automatic backups
We use the Google Firebase push service to deliver push notifications; see section 4. Visible notifications, such as cycle reminders, are sent only if you enable notifications, which you can disable in settings at any time.
We also send invisible system pushes to all devices on which you are signed in, regardless of notification settings. These never display anything and contain no content or health data. They briefly wake the app in the background to prepare an encrypted backup and, if you enabled “Daily AI message” (called “Proactive messages” in older app versions), prepare a proactive message; see the Google Vertex AI subsection below. The backup leaves your device only in encrypted form; section 3.7 explains how it is encrypted and how you can restore it.
Legal bases: Article 6(1)(b) GDPR (contract performance: providing backups); for visible reminders, your consent through notification settings under Article 6(1)(a) GDPR.
3.6 Recipe suggestions based on swipes
When you save a recipe by swiping right or dismiss it by swiping left, our server uses these signals to suggest more suitable recipes in the AI chat. Among similarly suitable recipes, saved recipes are preferred and dismissed recipes avoided. Safety exclusions, such as allergens and intolerances, always apply. This is your own app usage behavior, used only in the recipe function you actively request. The swipes themselves are not transmitted to the AI service. Legal basis: Article 6(1)(b) GDPR.
3.7 Encrypted backup, recovery key vault and restore
Local storage. The app stores your cycle and diary data in an encrypted database on your device.
Encrypted backup. So that your data is not lost if you lose or change your device, the app creates backups automatically. Each backup is encrypted on your device with a backup key before upload and then stored with Supabase (EU, Frankfurt). Your app generates the backup key; it is never stored with us in plain text. Technical details required for storage are not encrypted, such as the link to your account and the time and version details of the backup files.
Ways to restore. To make a backup readable on a new device, the app needs the backup key. The following ways exist:
- Platform key sync, where available: the app stores the backup key in iCloud Keychain (iOS) or Google Block Store (Android). Apple or Google make it available on your other devices, depending on your device and account settings; we have no access to it. The app uses Block Store cloud backup only where Google offers it end-to-end encrypted.
- Personal recovery code, optional: if you set up a recovery code in the app, the backup key is encrypted with this code and stored with Supabase. Only you know the code; without it, we cannot decrypt this copy.
- Recovery key vault, default: as described below.
Rollout note. The recovery key vault, release by email code, the related security emails and the backup status report arrive with an upcoming app update. Until you have installed that update, the app does not store a backup key in the vault and sends no status report; your backup can then only be restored with your recovery code or via platform key sync. We start the automatic deletion of older backups (section 5) on our server when the vault is introduced.
Recovery key vault, default. By default, the app also deposits an encrypted copy of your backup key with us, so you can get your backup back even if your device is lost and no other way is available—for example when switching between iPhone and Android. On your device, the app encrypts the backup key together with your account identifier using the public key of a hardware security module (HSM) in Google Cloud in the EU (Frankfurt). We store this encrypted package with Supabase; it is bound to your account and released only for that account. The matching private key exists only inside the HSM and cannot be exported.
Release only with a code sent to your email. Your app receives the backup key from the vault only if you start the restore in the app and enter a one-time code that we send to your account email address. The code is valid for 15 minutes; we store only a hash and delete it 7 days after expiry. The number of code requests and wrong entries is limited; after repeated wrong entries, we block release temporarily. After a correct entry, our server has the HSM decrypt the package and transmits the backup key to your app over an encrypted (TLS) connection. We record every deposit, code request, wrong entry, block, release and every switch of “Only with my own code” on or off in a separate log (event, time and, where available, platform and an identifier of the affected key); every decryption in the HSM is also recorded in Google Cloud's audit log. We notify you by email of every release.
Email delivery check. Once this check is available in the app, we store a timestamp on your account at which we could confirm that our emails reach you—for example because you entered a test code from one of our emails in the app (if the app asks you to run this check) or used a sign-in link from an email. This is meant to ensure that release by a code sent to your email address works when you need it. As with release codes, we store test codes only as a hash; they are valid for 15 minutes and deleted 7 days after expiry. We delete the timestamp together with your account.
What is technically possible. We do not read your backups. As long as your backup key is deposited in the vault, access by us is, however, not technically ruled out: using our server's credentials for the HSM, we as the operator could have a deposited backup key decrypted. Nobody can copy the private key out of the HSM, and any such decryption would be recorded in Google Cloud's audit log. If you want to rule this out, use “Only with my own code”.
“Only with my own code” (opt-out). You can switch off the deposit at any time in the app settings, provided you have set up a current recovery code. We then delete all vault packages for your account; your backup can no longer be decrypted through the vault. Restoring is then possible only with your recovery code or through platform key sync—if all ways are lost, your backup can no longer be restored. If you switch “Only with my own code” off again, the app deposits a new package. We notify you by email of every change, so you notice a change you did not make.
Backup status report. To detect backup problems, such as devices on which the database can no longer be opened, the app sends a technical status report to our server at launch, at most once per hour: platform, app version, whether the local database could be opened, whether database and backup keys are present on the device, whether Block Store cloud backup is available, whether a vault package and a current recovery code exist, time of the last backup and last restore, and an overall status. The report contains no cycle or health content and no device identifiers. We keep only the latest report per account.
Emails. One-time codes, release notifications and notices about “Only with my own code” are sent through our email delivery provider; see section 4. Replies go to office@bauchgefuehl.app.
Legal bases: Article 6(1)(b) GDPR (contract performance: providing backup and restore, including related security emails) and, where health data is concerned, Article 9(2)(a) GDPR (explicit consent; see section 3.1); for the backup status report, Article 6(1)(f) GDPR (legitimate interest in a working backup and in detecting problems).
3.8 Feedback survey after cancellation
After a cancellation, we invite you by email to a voluntary survey. It asks what led you to cancel, what you liked, what you missed and how likely you are to recommend Bauchgefühl. The survey runs on the form service Tally. The link in the email transfers your email address and a verification identifier so that we can match your response to your account.
Data processed. Your email address, the verification identifier, your answers (free text and rating) and the time of your response. The survey does not ask for health data, and health details are not wanted in the feedback. Please do not enter details about your health or your cycle in the free-text fields. If we find health details entered by mistake in a response, we delete them.
Flow and recipients.
- Tally stores your answers in our Tally account.
- Tally sends the answers to our website. The website forwards them unchanged to two recipients and does not store them in the process:
- An automation at Cursor (Anysphere, Inc., USA) evaluates your answers with the help of AI and writes a thank-you email to you.
- A server function at Supabase checks whether the response belongs to an account. It stores only the time of your feedback on your account and sets the attribute “Feedback given” on your contact at our email delivery provider. We use this to control which further emails you receive after your trial ends. This function does not store your answers themselves.
Purpose: to evaluate your feedback in order to improve Bauchgefühl, and to thank you for your response.
Legal bases: Art. 6(1)(f) GDPR (legitimate interest in improving our service based on your voluntary feedback and in replying to you).
Retention. We keep your answers at Tally and in the evaluation at Cursor for at most 12 months and then delete them.
Transfer to the USA. Cursor also processes the data on servers in the USA. This transfer is safeguarded by the EU standard contractual clauses in Cursor’s data processing agreement. Tally and Supabase store the data in the EU (details in section 4).
4. Services and recipients
Supabase
Supabase provides database infrastructure, authentication and storage for encrypted backups (section 3.7). Our contracting party is Supabase Pte. Ltd. (Singapore). Data is stored in the EU, in Frankfurt, Germany. A data processing agreement is in place. Where Supabase or its sub-processors process data from countries outside the EU, for example for support or maintenance access, this is safeguarded by the EU standard contractual clauses in the data processing agreement (Article 46(2)(c) GDPR).
Google Gemini API and OpenAI: recipe suggestions
To generate personalized recipes in the app, our server transmits the following data to Google’s Gemini API: your cycle phase, your cycle rhythm and goal from “My cycle” (not the reason), symptoms, health details and notes you enter in the recipe function, diet, allergens and dislikes, entered ingredients and requested preparation time. If you have stated a pregnancy as the reason in “My cycle”, the app also sends a fixed list of foods that must not appear in the recipes (for example raw fish, raw-milk cheese, alcohol); it does not transmit the reason itself, but a pregnancy can be inferred from the list. The app also sends this list as a precaution if it cannot read your cycle details. If the Gemini API does not return a usable result, our server sends the same request to OpenAI (USA) instead. The data is used to generate the requested response. Under both providers’ terms it is not used to train AI models; both do, however, retain requests for a limited time to detect abuse (OpenAI for up to 30 days).
Transfer to third countries: processing does not take place exclusively in the EU. Google may cache requests in any country where it maintains facilities; Google LLC is certified under the EU-US Data Privacy Framework (Article 45 GDPR), and Google’s Data Processing Addendum with EU standard contractual clauses also applies. OpenAI processes the data in the USA and is not certified under the Data Privacy Framework; the transfer relies on the EU standard contractual clauses in OpenAI’s data processing agreement (Article 46(2)(c) GDPR).
Legal bases: Article 6(1)(b) GDPR (contract performance) and Article 9(2)(a) GDPR (explicit consent given through active, voluntary use of the AI recipe function by submitting your request).
Google Vertex AI: proactive messages
If you enable “Daily AI message” in settings (called “Proactive messages” in older app versions), which is off by default, the app occasionally prepares a personal push message, for example about a cycle phase transition or your activity. Unlike other reminders calculated entirely on your device, these messages are generated on the server. In the background, including when closed, the app transmits your current cycle phase and, if you additionally enabled Health access, a summary of recent activity and sleep to Google Vertex AI in the EU (Frankfurt). At most one such message is generated per day.
This processes health data: your cycle phase already qualifies as a special category of personal data under Article 9 GDPR, and activity and sleep add further health data when Health access is enabled. Processing relies solely on your explicit consent through the switch. You can withdraw it at any time by switching the setting off; no further data is then transmitted for this purpose. Data is used only to generate the individual message, not to train AI models, either by us or Google. The Google Cloud data processing agreement, including EU standard contractual clauses, applies.
Legal bases: Article 6(1)(a) and Article 9(2)(a) GDPR (explicit consent).
Google Cloud: recovery key vault
For the recovery key vault (section 3.7), we use a key management service from Google Cloud with a hardware security module in the EU (Frankfurt). At the moment of a release, Google processes the encrypted package and returns the decrypted backup key to our server; Google also records key operations in an audit log. Your backups themselves are not transmitted to Google. A data processing agreement, including EU standard contractual clauses, applies under the Google Cloud Data Processing Addendum. Legal bases: as stated in section 3.7.
Email delivery
We use an email delivery provider based in Germany for the website newsletter, the app service and accompanying emails described in section 3.4, and the recovery key vault security emails described in section 3.7. Data is stored in the EU. A data processing agreement is in place. For the feedback survey (section 3.8), the provider also stores the attribute “Feedback given” on your contact.
Tally: feedback survey
For the feedback survey after a cancellation (section 3.8), we use the form service Tally (Tally BV, Sint-Pietersnieuwstraat 11, 9000 Ghent, Belgium) as a processor. Tally stores the form data encrypted in Europe. The data processing agreement is part of Tally’s terms of use. Some of Tally’s sub-processors are located outside the EU, for example in the USA; for such transfers, this agreement provides for EU standard contractual clauses.
Cursor: feedback survey evaluation
To evaluate the answers from the feedback survey and to send the thank-you email (section 3.8), we use an automation by Cursor (Anysphere, Inc., USA) as a processor. Cursor processes your email address and your answers with AI models, including on servers in the USA. The transfer relies on the EU standard contractual clauses (Module 2) in Cursor’s data processing agreement.
Stripe (payments on the website)
For subscriptions you purchase on the website, and for managing and cancelling them, we use Stripe (Stripe Payments Europe, Ltd., Dublin, Ireland). Stripe processes your payment and contact details for this purpose. Transfers to the USA may occur; they are safeguarded by standard contractual clauses. Stripe is also a controller in its own right for payment processing; details at stripe.com/privacy.
Legal basis: Art. 6(1)(b) GDPR (performance of a contract).
Google Analytics
We use Google Analytics (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland) to analyze website usage. Google Tag Manager loads the Google Analytics tag only after you consent to the “Analytics” category in the cookie banner; only then does Google Analytics set cookies. Independently of this, when you click an app store link, the Tag Manager sends the event “cta_download_click” (with the location of the click, platform and page) to Google Analytics, even without your consent. Without consent this happens in Google Consent Mode without cookies; your IP address is transmitted to Google in the process. Legal basis: for the Google Analytics tag and its cookies, Article 6(1)(a) GDPR (consent). You can also object to collection by installing Google’s Analytics opt-out browser add-on. Transfer to the USA: recipients may be Google Ireland Limited and Google LLC (USA); Google LLC is certified under the EU-US Data Privacy Framework (Article 45 GDPR).
PostHog: website analytics and session replay
On pages where it is enabled, PostHog uses EU hosting in Frankfurt. Before consent, we collect only anonymous usage data without device storage, cookies or recognition; your IP address is anonymized and not stored. After consent through the cookie banner, PostHog uses cookies for audience and funnel analysis and session replay: anonymized page interactions, with masked input fields and no recordings of sensitive areas such as quiz, login or checkout. Replay retention is 30 days. A data processing agreement is in place.
Legal bases: before consent, Article 6(1)(f) GDPR (legitimate interest in anonymous reach measurement without accessing your device); after consent, Article 6(1)(a) GDPR. Consent can be withdrawn through the cookie banner.
PostHog: app usage analytics
We use PostHog Inc. to understand app usage, with processing exclusively on EU servers in Frankfurt. IP addresses are anonymized before storage.
We never collect health data for analytics. Cycle data, symptoms, moods and other health information are never transmitted to analytics systems. We collect only usage behavior, such as which functions are used or where problems occur, at two levels:
- Anonymous statistics without consent. During installation, onboarding and registration, technical events are fully anonymous. No identifier is stored on your device, the data cannot be assigned to a person, and each app launch starts a new, unlinkable session. This shows, for example, where users leave onboarding. Since the data is anonymous, no personal data is processed.
- Statistics with consent. Only with your explicit consent after registration do we link usage events pseudonymously to your account—for example, that a function was used or an entry created, never the entry’s content. You can withdraw consent at any time using “Usage statistics” in app settings. Collection stops and the analytics identifier is discarded.
Legal bases: Article 6(1)(a) and Article 9(2)(a) GDPR. Recipient: PostHog Inc. as processor, with EU hosting and a data processing agreement including EU standard contractual clauses.
Google Firebase: app notifications and crash reports
The app uses Google Firebase for push delivery and for crash and performance reports. These process technical device details, such as device token, model, operating system and app versions and crash logs, without health data. Classical scheduled cycle reminders are calculated entirely on your device; server-generated proactive messages are described above. Firebase Analytics is not used.
Legal bases: Article 6(1)(b) GDPR for app functions you enable and Article 6(1)(f) GDPR for the legitimate interest in stability and troubleshooting.
Facebook Pixel
On website pages where it is enabled, Facebook Pixel supports conversion tracking and remarketing with your consent under Article 6(1)(a) GDPR. You can withdraw consent through the cookie banner.
Google Ads: conversion measurement
We advertise Bauchgefühl through Google Ads (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). Through Google Tag Manager we measure whether an ad is followed by a quiz sign-up (event “quiz_lead”) or the start of a purchase (event “begin_checkout”). The Tag Manager is set up as follows:
- The Google Ads tag and the Conversion Linker run when any page loads (except the cancellation pages), including before you have made a choice in the cookie banner.
- The two conversion tags fire on the events named above, likewise regardless of your choice in the cookie banner.
Until you consent to the “Marketing” category, the advertising signals in Google Consent Mode are set to “denied”. Google then neither sets nor reads advertising cookies, but receives cookieless pings with technical information on these calls (for example time, page visited, type of event, browser information and consent status); your IP address is transmitted to Google in the process. Google uses these pings to estimate conversions. With your consent, Google also sets cookies to attribute ad clicks to conversions.
Legal basis: for advertising cookies and the attribution of ad clicks with your consent, Article 6(1)(a) GDPR and Section 165(3) Austrian Telecommunications Act 2021. You can withdraw your consent at any time via the cookie banner. Transfer to the USA: recipients may be Google Ireland Limited and Google LLC (USA); Google LLC is certified under the EU-US Data Privacy Framework (Article 45 GDPR).
Google Tag Manager
We use Google Tag Manager (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland) to load and control the analytics and advertising services named above (Google Analytics, Google Ads, Facebook Pixel). The Tag Manager loads on all pages except the cancellation pages, including before you have made a choice in the cookie banner. When it loads, your IP address is transmitted to Google; recipients may be Google Ireland Limited and Google LLC (USA). Even before your choice, the Tag Manager runs the Google Ads tags and the click event for Google Analytics (details under “Google Ads” and “Google Analytics”). It starts the Google Analytics tag and the Facebook Pixel only after you consent to the respective category. Until you consent, the storage signals for analytics and advertising in Google Consent Mode are set to “denied”. We store your cookie banner choice in the strictly necessary cookie cc_cookie; the Tag Manager reads it to apply your choice (Section 165(3) Austrian Telecommunications Act 2021, permitted without consent because it is strictly necessary).
Legal basis: Article 6(1)(f) GDPR (legitimate interest in technically loading the consent and tag system); the individual services rely on the legal basis stated for them. Transfer to the USA: Google LLC is certified under the EU-US Data Privacy Framework (EU Commission adequacy decision, Article 45 GDPR).
Vercel: website hosting and measurement
The website is hosted by Vercel Inc. (USA). Vercel processes the technical data listed in section 3.2, in particular your IP address. We also use Vercel Web Analytics and Vercel Speed Insights: without cookies, they record page views, clicks on the app store links and website loading times. Both run on all pages except the cancellation pages, including without consent in the cookie banner. Content you enter in website forms (for example in the quiz or when taking out a subscription) and the feedback survey answers that Tally sends to our website (section 3.8) also pass through Vercel’s servers.
Legal basis: Article 6(1)(f) GDPR (legitimate interest in secure operation and in cookie-free reach and performance measurement). Transfer to the USA: Vercel Inc. is certified under the EU-US Data Privacy Framework (Article 45 GDPR).
AppsFlyer: ad attribution in the app
Only if you explicitly consent in the app do we use AppsFlyer (AppsFlyer Inc., USA) to measure which ad led to an app install or a subscription. Without your consent, the app does not start AppsFlyer. AppsFlyer processes device and advertising identifiers (on iOS the advertising ID only if you allow it in the system dialog), technical device data and app events such as install, registration, start of a trial or purchase of a subscription. RevenueCat (see below) reports subscription events to AppsFlyer server-side and also transmits the user ID of your Bauchgefühl account. AppsFlyer reports installs and purchases to the ad networks whose ad you came from (for example Meta, Google). AppsFlyer does not receive your name, email address or any cycle, health or nutrition data.
Legal basis: Article 6(1)(a) GDPR and Section 165(3) Austrian Telecommunications Act 2021 (consent). You can withdraw consent at any time in the app's privacy settings; the app then stops AppsFlyer. Transfer to the USA: AppsFlyer Inc. is certified under the EU-US Data Privacy Framework (Article 45 GDPR).
RevenueCat: subscription management in the app
For subscriptions you take out in the app via the Apple App Store or Google Play, we use RevenueCat (RevenueCat, Inc., USA) as a processor. RevenueCat processes the user ID of your Bauchgefühl account, the stores’ purchase and subscription information (for example product, time, term, status) and technical device data to determine which features you are entitled to. Only if you have agreed to ad attribution in the app does the app also pass RevenueCat the AppsFlyer ID, device and advertising identifiers (on iOS the IDFV and, if you allow it in the system dialog, the IDFA; on Android the advertising ID) and your IP address, and on iOS also the Apple Ads attribution token (see “Apple Ads”). RevenueCat uses them to report subscription events to AppsFlyer (see above) and to determine the Apple Ads campaign.
Legal basis: Article 6(1)(b) GDPR (contract performance); for passing on the advertising identifiers Article 6(1)(a) GDPR and Section 165(3) Austrian Telecommunications Act 2021 (consent, revocable in the app’s privacy settings). Transfer to the USA: RevenueCat is not certified under the EU-US Data Privacy Framework. The transfer relies on the EU standard contractual clauses in the data processing agreement with RevenueCat (Article 46(2)(c) GDPR).
Apple Ads: ad attribution on iOS
Only if you agree to ad attribution in the app does the app, on iOS, request an attribution token through Apple’s “AdServices” interface and pass it to RevenueCat (see above). RevenueCat uses it to ask Apple (Apple Distribution International Ltd., Hollyhill Industrial Estate, Hollyhill, Cork, Ireland) whether the install came from an ad in Apple Ads (formerly Apple Search Ads) and from which campaign. We use this to measure which Apple Ads ads lead to installs and subscriptions. RevenueCat stores the result with your subscription profile, as far as Apple provides it: whether the install was attributed to an Apple Ads ad, campaign, ad group, search keyword, ad, country or region and, for detailed data, the time of the click or impression. Apple processes this request under its own responsibility; for details, see Apple’s Privacy Policy. Your name, email address and any cycle, health or nutrition data are not transmitted. Without your consent, the app does not turn this request on.
Legal basis: Article 6(1)(a) GDPR and Section 165(3) Austrian Telecommunications Act 2021 (consent). You can withdraw consent at any time in the app's privacy settings. After a withdrawal, the app does not turn the request on again. However, the app can only technically turn off a request that is already on when the app is closed: if the attribution token had not yet been transmitted before your withdrawal, it may still be requested and transmitted to RevenueCat until then. From the next app start, no request takes place without your consent. Transfer to the USA: via RevenueCat, see above.
Contact form enquiries
To handle enquiries sent through the website contact form, we transmit the name, email address, subject, message and, where available, an account identifier to these recipients:
- a communication service for the internal handling of enquiries
- an automation and support service for handling contact enquiries
The purpose is handling the enquiry. Legal basis: Article 6(1)(f) GDPR (legitimate interests).
The transfer to these recipients takes place in the United States on the basis of the EU-US Data Privacy Framework or standard contractual clauses. A data processing agreement is in place.
Retention follows section 5 for contact enquiries (2 years after correspondence ends).
App stores
The app is distributed through Google Play and the Apple App Store. When downloading and using those stores, Google’s and Apple’s respective privacy policies apply. We have no influence over their processing.
5. Retention and deletion
We retain personal data only as required for the relevant purpose or statutory retention obligations:
- Account and app data: until account deletion or upon request.
- Backups: per account, we keep the 60 most recent backup versions, the 10 top versions in restore order and all backups from the last 30 days; older backups are deleted automatically every day. We introduce this automatic deletion together with the recovery key vault (section 3.7); until then, backups are kept until your account is deleted.
- Vault packages: until you switch on “Only with my own code” or delete your account. The copy encrypted with your recovery code, the vault log and the backup status report (latest only): until account deletion.
- Vault release codes: 7 days after their 15-minute validity ends.
- Newsletter data: until unsubscription.
- Feedback survey: your answers at Tally and in the evaluation at Cursor for at most 12 months, then deletion; the time of your feedback on your account and the attribute “Feedback given” at our email delivery provider, until account deletion.
- Contact enquiries: 2 years after correspondence ends.
- Technical website logs: at most 30 days.
- Accounting data: 7 years under Austrian tax law.
You can delete your account and associated data in the app under “Profile → Delete account” or through our website. A 7-day grace period applies: signing in again during that period cancels deletion. Afterwards, the account and associated personal data—including all backups, the key copy encrypted with your recovery code, vault packages, the vault log and the backup status report—are automatically and irreversibly deleted from our systems and those of the processors listed in section 4. Deletion is fully completed within 30 days at the latest. Data subject to statutory retention, such as accounting records, is excluded, as are your answers from the feedback survey at Tally and Cursor: they are not linked to account deletion and are deleted at the latest when their maximum period of 12 months ends (section 3.8). Deleting your account does not cancel an App Store or Google Play subscription; cancel any active subscription separately in the store settings.
6. Your rights
Under the GDPR, you have the following rights:
- Access to your personal data: Article 15.
- Rectification of incorrect or incomplete data: Article 16.
- Erasure, unless statutory retention applies: Article 17.
- Restriction of processing: Article 18.
- Data portability in a machine-readable format: Article 20.
- Objection to processing based on legitimate interests: Article 21.
- Withdrawal of consent for the future: Article 7(3).
To exercise these rights, contact office@bauchgefuehl.app. You also have the right to complain to the Austrian data protection authority:
Österreichische Datenschutzbehörde
Barichgasse 40–42
1030 Vienna
dsb@dsb.gv.at
www.dsb.gv.at
7. Data security
We implement technical and organizational safeguards against accidental or deliberate manipulation, loss, destruction and unauthorized access. Data transmissions between your device and our servers use TLS/HTTPS encryption. We adapt our safeguards to technical developments as needed.
8. Updates
This translation reflects the German policy dated November 19, 2026, which describes ad attribution through Apple Ads on iOS (section 4, “Apple Ads” and “RevenueCat”). The previous version was dated November 12, 2026, which names the switch for the daily AI message by its new name, “Daily AI message”, formerly “Proactive messages” (sections 3.5 and 4). The previous version was dated November 9, 2026, which describes the recipients used for enquiries sent through the website contact form (section 4). The version before that was dated October 29, 2026, which describes which tags Google Tag Manager runs before consent and names Google Ads, RevenueCat, the Gemini API and OpenAI for recipe suggestions, Supabase Pte. Ltd. as contracting party as well as Vercel and AppsFlyer (section 4), the 12-month maximum for feedback survey answers (sections 3.8 and 5) and office@bauchgefuehl.app as the only contact (section 2). The version of October 28, 2026 added the basal body temperature and the daily note from “My day” (section 3.1) and the feedback survey after cancellation with Tally and Cursor (sections 3.8, 4 and 5); it also names the email delivery provider as a category and omits technical details. The version before that was dated October 20, 2026 (cycle context from “My cycle”, sections 3.1 and 4). We may update it to reflect changes in our services or applicable requirements. The new version applies on your next visit.