PodPilot
English

Privacy policy

For the Android app PodPilot (from version 1.1) and the website podpilot.pro. Last updated: 18 November 2026.

In short

  • Your AirPods data stays on your device. PodPilot processes battery levels, settings, equalizer, automations and sound ratings locally only.
  • Analytics, crash reports and ad measurement only with your consent – in the app and on the website, each one separately, everything starts off. Without consent neither the app nor the website sends anything to Google, Meta or TikTok, and everything works the same – including buying. Withdraw any time: in the app under Settings › Privacy, on the website via “Cookie settings” at the bottom of every page.
  • Never transmitted: the names and Bluetooth addresses of your devices, phone numbers, call data, head movements, your sound ratings, contacts or your precise location.
  • If you buy PodPilot Pro in the app, Google Play handles purchase and payment (section 2.4). If you buy PodPilot Pro Lifetime on the website, you pay at Stripe; we receive no card details and need neither your name nor your email address (section 4.4).
  • A PodPilot Pro account is optional and only needs a username and password (section 4.5).
  • Without consent the website only stores what the site and what you do there need: your cookie choice, the start time of the offer, your sign-in and the pick-up data for your purchase (section 4.2).

1. Controller

Geitau 21 GmbH & Co. KG, Geitau 21, 83735 Bayrischzell, Germany, represented by Geitau 21 W GmbH (Munich Local Court, HRB 300144), itself represented by its managing director Sebastian Wagner. Email: servus@sebastianwagner.net.

We have not appointed a data protection officer because the legal requirements for this are not met. Please send any questions to the address above.

2. The PodPilot app

2.1 What stays on your device only

To show battery levels and change settings, PodPilot reads the Bluetooth signals your headphones broadcast anyway (model, battery levels, charging state, whether the case is open and whether the earbuds are in your ears) and, on supported devices, connects to them directly. This data is processed only on your device and is not stored permanently – except for the last known battery levels for the tile and widget.

Also stored locally in the app's private storage: your settings, for each pair of AirPods the date it was first detected and a purchase date you entered (AirPods age), your equalizer settings, your automations (for triggers like “car connected” also which of your paired Bluetooth devices is meant), your sound ratings from “How does it sound?” with time, device, AirPods age, noise mode and EQ setting, and your privacy choice. None of this is transmitted, and it's gone when you uninstall the app or clear its data.

Bluetooth signals from other nearby devices that aren't AirPods are filtered out as soon as they are received. Signals from other people's AirPods in range are discarded as soon as it's clear they aren't yours.

The legal basis for this local processing, insofar as personal data is involved at all, is providing the features you asked for (Art. 6(1)(b) GDPR); access to information on your device is strictly necessary for this (Section 25(2) no. 2 TDDDG).

2.2 Analytics, crash reports and advertising – only with your consent

These sections apply from version 1.1. Version 1.0 contains none of these services and has no internet access.

PodPilot is a small project. To know what works, which devices our users have and which advertising pays off, we ask for your help on first launch. In the consent dialog you can choose “Allow all” or “Only necessary” – both equally prominent – or switch on each of the three services individually under “Details”. Everything is off by default. Declining does not limit the app.

Technically we use Google Consent Mode v2: the signals analytics_storage, ad_storage, ad_user_data and ad_personalization are set to “denied” until you agree, and Firebase data collection is switched off until then.

a) Usage statistics (Google Firebase Analytics)

  • What: a random app instance ID; events such as app start, setup steps, the detected AirPods model (model identifier, not the name of your headphones), features used (only that, not with what content), viewing the Pro page, starting a trial and purchases (product, price, currency – no payment details); device data such as manufacturer, model, Android version, language, app version; the approximate location (country/region) Google derives from the IP address – Google Analytics does not store the IP address itself.
  • Why: to understand how PodPilot is used, which models and Android versions matter, where users get stuck and how many trials and purchases there are.
  • Retention: event data is deleted automatically after 2 months; aggregated reports without personal reference remain.

b) Crash reports (Firebase Crashlytics)

  • What: in case of a crash or serious error, the technical error trace (stack trace), app version, device model, Android version, free memory, orientation, time and a random installation ID.
  • Why: to find and fix bugs.
  • Retention: 90 days.

c) Ad measurement & retargeting (Google Ads)

  • What: your device's advertising ID (Android Advertising ID), the install source on Google Play (install referrer, e.g. which ad you came from – only read after this consent) and the events from a), especially install, trial and purchase, are shared with Google Ads.
  • Why: to measure which ads lead to installs and purchases, and to be able to show you PodPilot again later in Google ads (e.g. in Google Search, on YouTube or in other apps) (remarketing).
  • Retention: membership in remarketing lists at most 540 days; conversion data according to Google Ads' retention periods.
  • Google builds audiences from this (profiling for advertising). There is no automated decision with legal or similarly significant effect on you (Art. 22 GDPR).
  • You can reset or delete the advertising ID at any time in Android under Settings › Privacy › Ads.

Recipients and transfers outside the EU

The recipient is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. For Firebase Analytics and Crashlytics, Google processes the data as our processor under the Firebase data processing terms; for Google Ads, Google partly acts as an independent controller (Google Ads Controller-Controller Data Protection Terms). Data may be transferred to Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA. Google LLC is certified under the EU-US Data Privacy Framework; the transfer is based on the European Commission's adequacy decision (Art. 45 GDPR), alternatively on standard contractual clauses (Art. 46(2)(c) GDPR). For the collection of data in the app and its transmission to Google, we and Google may be joint controllers (Art. 26 GDPR); Google is responsible for further processing on its side. You can exercise your rights with us and with Google. More in Google's privacy policy and under Privacy and security in Firebase.

Legal basis and withdrawal

The legal basis is your consent (Art. 6(1)(a) GDPR); for storing and reading identifiers on your device, Section 25(1) TDDDG. You can withdraw any consent at any time with effect for the future in the app under Settings › Privacy (Art. 7(3) GDPR). After that the app sends nothing more through the respective service; the lawfulness of processing carried out until then remains unaffected.

2.3 Permissions

PermissionWhat for
Nearby devices (Bluetooth scan and connect)Receive the AirPods' status signal and connect to them. The permission is requested in a way that it cannot be used to determine your location.
Location – Android 10 and 11 onlyOn these older Android versions, Android only allows Bluetooth scanning with the location permission. PodPilot doesn't determine or transmit your location with it. From Android 12 on it isn't requested.
NotificationsOptional, silent battery notification while your headphones are connected, plus the battery pop-up. Can be switched off in the app.
Companion device presence (REQUEST_OBSERVE_COMPANION_DEVICE_PRESENCE)Android tells the app when your paired headphones are connected, so battery levels and ear detection only run then.
Modify audio settings (MODIFY_AUDIO_SETTINGS)For the equalizer: PodPilot applies a sound filter to playback from player apps that register their audio session with Android. The app doesn't listen in or record anything.
Phone: answer/decline calls (ANSWER_PHONE_CALLS, possibly READ_PHONE_STATE)Only for head gestures for calls: nodding answers an incoming call, shaking your head declines it. PodPilot only asks for it when you turn the feature on, and you can revoke it at any time. The app only learns that a call is coming in. It does not read phone numbers, contacts or call logs and does not store or transmit anything about them.
Run at startup (RECEIVE_BOOT_COMPLETED)After your phone restarts, PodPilot schedules your time-based automations again. No data is collected or transmitted.
Internet and network state (INTERNET, ACCESS_NETWORK_STATE)Only for the services in section 2.2 – and only if you consented. Without consent PodPilot sends nothing through them.
Advertising ID (com.google.android.gms.permission.AD_ID)Only for ad measurement & retargeting (2.2 c), and only with your consent.
Google Play billing (com.android.vending.BILLING)Lets the app start a purchase of PodPilot Pro through the Play Store app on your device and check whether you own Pro. Without a purchase nothing happens through it.

PodPilot does not request contacts, call log, camera or microphone permissions, and from Android 12 on no location permission either. You can always see the exact list in Android under Settings › Apps › PodPilot › Permissions.

2.4 Purchases through Google Play (PodPilot Pro)

You can buy PodPilot Pro in the app – as a subscription or as a one-time purchase. The basic features remain usable without a purchase.

  • Purchase and payment are handled exclusively by Google. You pay with the payment method in your Google account; Google processes account, payment and order data as an independent controller. Google's privacy policy and the Google Play Terms of Service apply.
  • The app only receives the purchase status. Through the Play Store app on your device, PodPilot learns which product you bought, whether it is active, and a purchase token the app uses to acknowledge the purchase with Google. From this the app only remembers “Pro: yes/no” locally, so Pro features also work offline.
  • No server of our own for Play purchases – with one exception from version 1.2: the rent-to-own check (section 2.7). Otherwise the app does not send purchase data to us. If you consented to usage statistics, a trial or purchase is reported to Firebase Analytics as an event (product, price, currency) – without payment details. We never see your card number, bank details or payment method.
  • What we receive from Google: for billing, taxes and refunds, Google provides us with order data in the Play Console (e.g. order number, product, price, date, country or region). We use it only for these purposes and keep it as long as commercial and tax law requires (up to 10 years).

You can cancel a subscription, change your payment method or view purchases at any time in Google Play under Manage subscriptions. The legal basis is performance of the purchase contract (Art. 6(1)(b) GDPR) and, for retention, our legal obligation (Art. 6(1)(c) GDPR).

2.5 Google Play

When you install or update PodPilot through Google Play, Google processes data as an independent controller (e.g. your Google account and device data). We have no influence on this. Google's privacy policy applies. From Google Play we receive aggregated statistics (e.g. number of installs).

2.6 Suggest a feature (from version 1.2)

With “Suggest a feature” in the app you can send us an idea, a bug report or anything else. Nothing is sent unless you tap “Send” yourself. Our server receives: your text, the chosen category (feature, bug, other), the app version, the app language, the device model (e.g. “Pixel 9”) and the Android version. The app does not include your name, email address, advertising ID, device identifiers or Bluetooth data. Please don’t put personal data into the text yourself. If you’d like a reply, email us (section 3).

  • Purpose: we read suggestions to improve PodPilot and find bugs. Legal basis is our legitimate interest in developing the app (Art. 6(1)(f) GDPR).
  • Storage: in a database at Cloudflare (Cloudflare D1, location Western Europe). Cloudflare is our processor; for possible transfers to the USA see section 4. Suggestions are deleted automatically after 24 months, earlier on request.
  • Abuse protection: to stop mass submissions, our server accepts at most 5 requests per hour per sender. For this it computes a hash from your IP address and a random value that changes daily. The IP address itself is not stored; the hash is deleted after two hours at most, the random value after one day. The hash is pseudonymous, not anonymous. Legal basis: legitimate interest in secure operation (Art. 6(1)(f) GDPR).

2.7 Rent-to-own check (from version 1.2)

Once you have paid for 12 months of the PodPilot Pro subscription, Pro is yours for good – even if you cancel afterwards (“rent to own”). Google Play doesn’t offer this by itself, so our server checks how many months have actually been paid:

  • What the app sends: the purchase token and the order number of your subscription – only once 12 payments are mathematically possible, and at most once a day. With “Restore rent-to-own” (e.g. on a new phone) you only enter the order number from your Google Play receipt.
  • What the server does with it: it asks Google Play (Google Play Developer API) which orders belong to your subscription and which of them were paid and not refunded or cancelled. The free trial does not count. Google’s answer contains order data such as order number, product, amount, status and date, possibly also country, region and postcode. We only evaluate amount and status and store none of it. We do not receive your name, email address or payment details.
  • What is stored: only the base order number, the number of paid months, the times of the last check and – from 12 payments – since when Pro is yours, plus a hash of the purchase token (not the token itself). It is kept in the same Cloudflare database (processor, see above) for as long as your claim to Pro exists; on request we delete it – rent-to-own can then only be restored through a new check with Google.
  • Proof: from 12 paid months the app receives a proof digitally signed by us (order number, count, time of issue). It stores the proof on your device and in the Android backup of your Google account (Block Store) so Pro survives a reinstall.
  • Legal basis is performance of the contract for PodPilot Pro (Art. 6(1)(b) GDPR). Abuse protection (at most 5 requests per hour, IP only hashed) works as for “Suggest a feature”.

2.8 Unlocking PodPilot Pro bought on the web (code or account)

If you bought PodPilot Pro on podpilot.pro, you can unlock it in the app under Settings › PodPilot Pro – with your licence code or, if you linked the code to an account, with your username and password. Only when you do this does the app send to our server (podpilot.pro):

  • the licence code, or username and password (encrypted via HTTPS; we store the password only as a hash, see 4.5),
  • a random installation ID that the app creates once (no hardware identifier, no advertising ID, no Android ID). Our server stores only a SHA-256 hash of it,
  • optionally a device name such as “Google Pixel 9”, so you can recognise your devices in the device list (at most 5 active devices per licence, managed by you).

The server replies with a digitally signed proof that the app stores on your device so Pro also works offline. Occasionally (at most about every three days while you are online) the app refreshes it. We store the licence (hash of the code, its last 4 characters), the device assignment (hash of the installation ID, device name, timestamps) and – only if you create one – your account. The legal basis is the performance of the purchase contract (Art. 6(1)(b) GDPR). We keep this as long as the licence exists; you can remove a device yourself at any time.

3. Contact by email

If you write to us, we process your email address and the content of your message to reply to you (Art. 6(1)(b) or (f) GDPR). We delete the message once the request is resolved and no statutory retention obligations apply.

4. This website (podpilot.pro)

4.1 Hosting with Cloudflare

The website and its interfaces (offer, purchase, account, unlocking the app) run on Cloudflare (Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA; Cloudflare Pages, Pages Functions and the Cloudflare D1 database, stored in Western Europe). When you visit, Cloudflare processes technically necessary connection data: IP address, time, requested address, browser identifier (user agent) and referrer. This is needed to deliver the site and protect it against attacks. Cloudflare keeps this data in server logs only briefly and for security purposes; we do not analyse these logs.

To stop anyone from calling our interfaces en masse, our server limits requests per sender. For this it creates a hash from your IP address and a random value that changes daily and keeps it for at most two hours; we do not store the IP address itself. The hash is pseudonymous, not anonymous.

The legal basis is our legitimate interest in a secure and fast website (Art. 6(1)(f) GDPR). Cloudflare is our processor (Art. 28 GDPR). For transfers to the USA, Cloudflare is certified under the EU-US Data Privacy Framework; standard contractual clauses apply in addition.

4.2 What is stored in your browser without consent

Only what is strictly necessary for the site or for a feature you use (Section 25(2) no. 2 TDDDG, the German implementation of Art. 5(3) ePrivacy Directive). None of it goes to analytics or advertising providers.

Name, typePurposeHow long
pp-consent, local storageyour choice in the cookie banner with time and version of the banner text (proof of your consent)12 months, then we ask again
pp_offer, cookie; pp.offer, local storagestart time of the first-visit offer, signed by our server (section 4.3)1 year
pp.orders, local storagepick-up key your browser uses to fetch your licence code after payment (section 4.4)until you delete it
__Host-pp_sess, cookieyour sign-in to the PodPilot Pro account (section 4.5)30 days or until you sign out
pp-langhint, local storagethat you closed the hint about another language versionuntil you delete it
pp-utm, session storageonly with consent (statistics or advertising): which campaign brought you to the site, for the link to Google Play (section 4.7)until you close the tab

4.3 Offer for first-time visitors

On your first visit the website may offer you PodPilot Pro Lifetime at an offer price for 5 hours. To make this honest – a real countdown, no resetting – the website stores when the offer started for you: as a value signed by our server in the cookie pp_offer and as a copy in local storage. At checkout our server uses it to check the price. It contains only the start time, expiry and a random identifier – no name and no device or advertising identifier. After 5 hours the regular price applies; the value stays stored for one year so that the offer does not start again in this browser.

The legal basis for storing it is Section 25(2) no. 2 TDDDG (necessary for the offer you are using), and for processing our legitimate interest in a fair offer that cannot be manipulated and steps prior to entering into a contract (Art. 6(1)(f) and (b) GDPR). You can delete the cookie in your browser at any time; this does not restart the offer, though.

4.4 Buying PodPilot Pro on the web (Stripe)

On the website you can buy PodPilot Pro Lifetime. You pay on the checkout page of Stripe (Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland), to which we redirect you. We do not load any Stripe code on podpilot.pro itself.

  • What Stripe processes: what you enter on the checkout page – e.g. email address for the receipt, payment details, country and, where applicable, billing address (for VAT, Stripe Tax) – plus device and connection data for fraud prevention. Stripe sets cookies on its own pages for this. Stripe is an independent controller for payment processing and fraud prevention; Stripe's privacy policy applies. Stripe may transfer data to Stripe, Inc. in the USA (EU-US Data Privacy Framework, alternatively standard contractual clauses).
  • What we store: the order (amount, currency, time, Stripe payment ID, your consent to the immediate start of performance with its time) and the licence (hash of the licence code and its last 4 characters). We do not store name, address, email address or payment details in our database; we can view the details of a payment in our Stripe account, e.g. for refunds, taxes or queries.
  • Licence code: after payment the website shows your licence code. For this your browser keeps a pick-up key (pp.orders). Keep the code safe – we only know it as a hash.
  • Withdrawal: if you use the withdrawal function on the website, we process the details from the form to handle your withdrawal.
  • Legal basis is the performance of the purchase contract (Art. 6(1)(b) GDPR) and, for retention, our legal obligation (Art. 6(1)(c) GDPR). We keep order and accounting data as long as commercial and tax law requires (up to 10 years). In case of a refund or chargeback the licence is blocked.
  • If you consented to statistics or advertising, we report checkout start and purchase (amount, currency, a random order identifier to avoid double counting – no payment details, no name) to the services you chose in section 4.6.

4.5 PodPilot Pro account (optional)

You don't need an account – the licence code is enough. If you create one so you can unlock Pro in the app with username and password, we store: your username, your password only as a hash (PBKDF2), the hash of your recovery code, and the licences and devices linked to it. We don't ask for an email address. We show you the recovery code once; without it we cannot reset a forgotten password. For signing in on the website we set the cookie __Host-pp_sess.

The legal basis is the performance of the contract for the account (Art. 6(1)(b) GDPR). You can delete your account on the website at any time; the licence remains usable via the licence code.

4.6 Statistics and advertising – only with your consent

On your first visit a banner asks you. You can choose “Allow all” or “Only necessary” – both equally prominent – or switch on Statistics and Advertising & retargeting separately under “Choose individually”. Everything starts off.

  • Nothing happens before: until you agree, the website loads no code from Google, Meta or TikTok, sets no such cookies and sends nothing to these providers. We use Google Consent Mode v2 in “basic” mode: the signals analytics_storage, ad_storage, ad_user_data and ad_personalization are set to “denied” until you agree; Google's script is only loaded afterwards.
  • Global Privacy Control: if your browser sends this signal, we treat it as a no to advertising; that part stays off.
  • Is the app already installed? Only with consent, the site may use a browser interface in Chrome on Android to check whether PodPilot is installed on your device (yes/no only; the site cannot see other apps). The result goes to the services you chose as the attribute “app installed”, so that we don't show install ads to people who already have the app.
  • Withdrawal at any time via “Cookie settings” at the bottom of every page (Art. 7(3) GDPR), with effect for the future. If you withdraw consent, we delete these providers' cookies on podpilot.pro and reload the page without their code. Cookies that providers set on their own domains can be deleted in your browser or in the provider's ad settings (links below).
  • Legal basis is your consent (Art. 6(1)(a) GDPR; for cookies and access to your device Section 25(1) TDDDG). Saying no has no disadvantages.

a) Statistics: Google Analytics 4

  • What: pages viewed and the site's language/market, referring page and campaign (e.g. utm_campaign), how far you read a story (25/50/75/100 %), whether you use the live demo and which control, taps on “Get it on Google Play”, whether you saw the offer and in which state, checkout start, purchase (amount, currency, order identifier) and account creation (only that it happened, not the name); plus browser, operating system, device type, screen size, language and approximate location (country/region, derived from the IP address – Google Analytics does not store the IP address itself). A random identifier in the cookies _ga and _ga_<ID> (up to 2 years) recognises your browser on later visits.
  • Why: to understand how visitors use the site, which languages and stories work and how many find their way to the app or to a purchase through the site.
  • Settings: Google Signals is off, data sharing with Google for its own purposes is off. Event data is deleted after 2 months; aggregated reports without personal reference remain.
  • Website and app: data from the website and – if you consented in the app – from the app (section 2.2) are in the same Analytics property, but under different identifiers. We do not link them through a user ID of our own.
  • Role: Google acts as our processor for this.

b) Advertising: Google Ads

  • What: pages viewed, taps on “Get it on Google Play”, checkout start, purchase and account creation as conversions (with amount and order identifier), the click identifier of a Google ad (gclid) if you came through one, browser and device data, IP address. Cookies _gcl_au and possibly _gcl_aw (90 days) on podpilot.pro; Google may set its own cookies on google.com and doubleclick.net (up to 13 months).
  • Why: to measure which ads lead to downloads and purchases, and to show visitors of this site PodPilot again later in Google ads (remarketing), e.g. in Google Search, on YouTube or on partner sites – for example visitors with an Android phone who don't use the app yet. Membership in such audiences at most 540 days.
  • Role: for advertising and remarketing Google acts as an independent controller (Google Ads Controller-Controller Data Protection Terms). For the collection on this site and the transmission to Google, we and Google may be joint controllers (Art. 26 GDPR). Ad settings: Google My Ad Center.

c) Advertising: Meta Pixel (Facebook, Instagram)

  • Provider: Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland.
  • What: pages viewed (address without purchase or sign-in data), the same events as for Google Ads (offer seen, checkout start, purchase with amount and order identifier, account creation, tap on Google Play, demo used, story read), browser and device data, IP address; a random identifier in the cookie _fbp (90 days) and, if you came through a Meta ad, _fbc (90 days). If you are signed in to Facebook or Instagram, Meta may link the visit to your account. We do not pass names, email addresses or phone numbers to Meta (“advanced matching” is off), and automatic click collection is switched off.
  • Why: to measure the effect of our ads on Facebook and Instagram and to show visitors of this site PodPilot there again (website audiences, e.g. Android users; membership at most 180 days).
  • Role: for the collection on this site and the transmission to Meta, we and Meta are joint controllers (Art. 26 GDPR, agreement between Meta and us); Meta alone is responsible for further processing. You can also exercise your rights directly with Meta: Meta privacy policy, ad preferences.
  • Third country: transfer to Meta Platforms, Inc. in the USA possible (EU-US Data Privacy Framework, alternatively standard contractual clauses).

d) Advertising: TikTok Pixel

  • Provider: TikTok Technology Limited, 10 Earlsfort Terrace, Dublin, D02 T380, Ireland.
  • What: pages viewed (address without purchase or sign-in data), offer seen, checkout start, purchase (amount, order identifier), account creation, tap on Google Play, use of the demo; browser and device data, IP address; random identifiers in the cookies _ttp and _tt_enable_cookie (13 months) and ttcsid (session). If you are signed in to TikTok, TikTok may link the visit to your account. We do not pass names, email addresses or phone numbers.
  • Why: to measure the effect of our ads on TikTok and to show visitors of this site PodPilot there again (website audiences; membership at most 180 days).
  • Role: for the collection on this site and the transmission to TikTok, we and TikTok are joint controllers (Art. 26 GDPR, under TikTok's terms for business products); TikTok is responsible for further processing. TikTok privacy policy.
  • Third country: according to TikTok, data is stored among others in the USA, Malaysia and Singapore, and access is possible from further countries including China. There is no EU adequacy decision for these countries; TikTok bases the transfer on standard contractual clauses (Art. 46(2)(c) GDPR). Authorities there might access data without you having the same legal remedies as in the EU.

Recipient and transfer to third countries for Google

The recipient is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Data may be transferred to Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA. Google LLC is certified under the EU-US Data Privacy Framework; the transfer is based on the European Commission's adequacy decision (Art. 45 GDPR), alternatively on standard contractual clauses (Art. 46(2)(c) GDPR). Google's privacy policy.

Profiling: for remarketing, Google, Meta and TikTok build audiences from your visit. There is no automated decision with legal or similarly significant effect for you (Art. 22 GDPR).

The “Get it on Google Play” button is a link. Google Play only opens when you tap it; from then on Google's privacy policy applies. The link contains a campaign note for Google Play (parameter referrer): that you come from podpilot.pro, from which part of the page and in which language, and – if you came through a campaign – its tags (utm_…). Only if you consented to advertising is the click identifier of a Google ad (gclid) added. After installation the app reads this note only if you consent to ad measurement there (section 2.2 c). If you consented on the website, we count the tap as described in 4.6.

5. 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), to object to processing based on legitimate interests (Art. 21) and to withdraw consent (Art. 7(3)). Just write to servus@sebastianwagner.net. Where we are joint controllers (Google, Meta, TikTok), you can contact us or the provider.

Analytics, crash and advertising data are held by the providers only under random identifiers; we generally cannot attribute them to a person ourselves. For questions about a purchase or account, please give us your order number, the last 4 characters of the licence code or your username – that's all we know about you. Independently of that, you can break the link yourself at any time: withdraw consent, delete cookies, reset your advertising ID or clear the app's data.

You also have the right to lodge a complaint with a data protection supervisory authority. The authority responsible for us is the Bavarian State Office for Data Protection Supervision (BayLDA), Promenade 18, 91522 Ansbach, Germany.

6. Changes

If the app or the website changes in a way that involves processing other data, we will update this policy beforehand. If new purposes or providers are added, the website asks for your consent again. The version published here applies.

Last updated: 18 November 2026 · Geitau 21 GmbH & Co. KG