This is an English translation of the German original. If the two versions differ, the German version applies.
In short
The following is a summary. It does not replace the sections below, but it puts the most important points first.
- We read only your step count — on an iPhone from Apple Health, on an Android phone from Health Connect. We have not read calories or floors since 25 September 2026; we have deleted the stored floors. We only write to Apple Health if you save a hunt as a workout on your Apple Watch.
- Step counts are health data. We process them only with your explicit consent, which you can withdraw at any time.
- Your step counts and everything else in your profile are visible to everyone. Anyone who signs in sees the same figures as you do in the leaderboard, the round and the profile — steps, rank, level, rating and what you have achieved in competition.
- So that the competition stays fair, our anti-cheat checks the steps of all players automatically. Whether anyone is suspended is decided by a human. More under Anti-cheat.
- We do not sell any data and we do not show any advertising in the app. We do, however, advertise Pyron on Facebook, Instagram and TikTok. So that we can see whether this advertising works, the iPhone app reports to Meta and TikTok and the Android app to Meta that it has been installed and opened and whether an account was created, the initial setup was completed or the free trial was started in it. Meta and TikTok never receive your steps or any other health data. More under Ad measurement with Meta and Ad measurement with TikTok.
- To keep the app running reliably, we send technical diagnostic data to Sentry in Frankfurt — up to and including a screenshot taken at the moment of the error. What exactly this covers is set out under Crash reports.
- The app's data is stored on servers in Ireland, i.e. in the EU. The exceptions are purchases and the attribution to Apple ads: they are stored by RevenueCat in the USA. Emails we send you are sent by Resend from the USA.
- You can delete your account yourself in the app. Then we delete your data, at RevenueCat too, which we instruct to delete it. A few things remain, such as your rating standing as “Unknown” or fight reports of players who attacked you in Pyron Legends; what and why is set out under Delete your account. Only the stores keep purchase records according to their retention periods. If you are a creator, we keep your credit notes for as long as tax law requires.
Who is responsible
The controller within the meaning of Art. 4(7) GDPR is:
Neurolytix GmbH
Hauptstraße 127
68259 Mannheim
Germany
Managing Director: Jonas Reggelin
Email: hello@pyron.app
We have not appointed a data protection officer. The requirements of Art. 37 GDPR and Section 38 of the German Federal Data Protection Act (BDSG) are not met in our case; for all questions about data protection, you can reach us at the address given above.
Overview of all processing
The table lists every processing activity with its legal basis. The sections below explain each of them in detail.
| What | Purpose | Legal basis |
|---|---|---|
| Email address, password, or Apple or Google identifier | So that you have an account and can be recognised again | Art. 6(1)(b) GDPR (contract) |
| Username, time zone | Display to others, assigning your days | Art. 6(1)(b) GDPR |
| Step counts from Apple Health or Health Connect | Rank, level, XP and competition scoring | Art. 9(2)(a) GDPR (explicit consent), together with Art. 6(1)(a) |
| Daily totals of your steps for the last twelve months, read once; after that, the daily totals of the last seven days at every sync | Our analysis of whether Pyron gets people moving — not part of any competition scoring | Art. 9(2)(a) GDPR (explicit consent), together with Art. 6(1)(a) |
| Steps per day from the step counter of your phone or Apple Watch while the hunt is “Live” | So that the others see you live — none of it is scored | Art. 9(2)(a) GDPR (explicit consent), together with Art. 6(1)(a) |
| “Outdoor Walk” workout with duration, distance and calories — only on the Apple Watch, only if you save it; it stays in Apple Health | Your hunt appears in Apple's Fitness app | Art. 9(2)(a) GDPR (explicit consent) |
| Rank, level, rating, placings | Competition, leaderboards, profile | Art. 6(1)(b) GDPR |
| Steps per hour and per day, which device and which app they come from, your step history | Detecting cheating so that the competition stays fair (anti-cheat) | Art. 9(2)(a) GDPR (your consent for the competition), together with Art. 6(1)(f) (legitimate interest in a fair competition) |
| After removing an account for cheating: a copy of its data, plus its login details and device identifier on a block list | Evidence in case the suspension ends up in court; enforcing the suspension | Art. 9(2)(f) and Art. 6(1)(f) GDPR (legal claims), for the block list Art. 6(1)(f) |
| For Pyron Legends: your steps per day, per hour and per minute, started hours, the daily totals of the last twelve months and the steps per hour from the last year that the app reports once for everyone; plus when the game last asked for your minutes | Gold, Experience and Pyronite for your hero, the times in the game's sync and the recommendation of a class — not part of any competition scoring | Art. 9(2)(a) GDPR (explicit consent), together with Art. 6(1)(a) |
| Description of the computer when signing in to Pyron Legends: browser, operating system, approximate location; when you last signed out all computers | So that you see in the app which computer wants to sign in, and sign-ins from before no longer count | Art. 6(1)(f) GDPR |
| Friendships and invitations | Friends list, club and teams, mutual visibility | Art. 6(1)(b) GDPR |
| Messages in the club chat with time, sender and mentions; read marker; when you accepted the chat rules | Your club's chat, mentions and the notification about them, number of unread messages | Art. 6(1)(b) GDPR |
| Reports about chat messages, statements of reasons to those affected, notices to authorities | Obligations under the Digital Services Act | Art. 6(1)(c) GDPR with Art. 16 to 18 DSA |
| Copy of reported messages including up to five messages before them, word filter, mutes, log of deletions in the chat | A safe community, preventing abuse | Art. 6(1)(f) GDPR |
| Device token for notifications | Push notifications to your phone | Art. 6(1)(a) GDPR (consent) |
| Bug reports, crash logs | Finding and fixing bugs | Art. 6(1)(f) GDPR (legitimate interest in an app that works) |
| Reports about other users | Following up on abuse | Art. 6(1)(f) GDPR, also in fulfilment of Art. 16 DSA |
| Pseudonymous usage events | Detecting whether the competition works technically | Art. 6(1)(f) GDPR |
| App installation, app launches, accounts created, completed initial setup, free trials started and purchases in the App Store, with technical device data (iPhone app only) | Measuring whether our advertising on Facebook and Instagram works | Art. 6(1)(f) GDPR (legitimate interest in effective advertising for the app) |
| Which pages of the initial setup and which areas of the app you open and on which days you open the app, with your player ID | Recognising where new players get stuck and whether they come back — and thus which advertising brings players who stay | Art. 6(1)(f) GDPR |
| Whether you downloaded Pyron via an ad in the App Store, and which one (campaign, ad group, keyword), iPhone app only | Measuring which advertising on Apple brings players | Art. 6(1)(f) GDPR |
| Purchase records: subscription bought, price, time, your player ID | So that a purchase reaches your account | Art. 6(1)(b) GDPR (contract) |
| Username and title when you earn a legendary title; club names for completed dungeons and new clubs | Posts by the Pyron bot on the Discord server | Art. 6(1)(f) GDPR |
| Discord ID and display name, if you connect your account to Discord | Permission to write and roles (rank, founding member) on the Discord server | Art. 6(1)(a) GDPR (consent) |
| Figures for the WhatsApp channel (followers, reach, regions, reactions) and your WhatsApp profile name if you react there | Seeing whether updates in the WhatsApp channel reach people | Art. 6(1)(f) GDPR |
| Creator code entered by a player | Reward for the player, commission for the creator | Art. 6(1)(b) GDPR |
| Creator application: channels, reach, message | Deciding whether you become a creator | Art. 6(1)(b) GDPR (steps prior to a contract) |
| Name or company, address, email, tax details and tax numbers (encrypted) of creators, VAT ID check results | Contract with creators, commission, credit note, payout | Art. 6(1)(b) GDPR; the VAT ID check (c) |
| Credit notes and statements to creators | Statutory retention | Art. 6(1)(c) GDPR |
| Sign-in to the creator area, log of changes | Account security, preventing misuse | Art. 6(1)(f) GDPR |
| Email address on the waitlist for Pyron Legends, with the time you signed up | Seeing who would like to play Pyron Legends in the beta | Art. 6(1)(a) GDPR (consent) |
| Server logs of this website | Operation and security of the website | Art. 6(1)(f) GDPR |
Your account
Pyron does not work without an account: a competition needs someone to compete, and a rank needs someone it belongs to. There are three ways in; which ones you see depends on your phone.
With email address and password
We store your email address and your password. We never store the password in plain text, only as a cryptographic hash (bcrypt) — we can neither read it nor tell it to you. To confirm, we send you an email with a six-digit code, through our email service Resend.
With “Sign in with Apple”
Apple sends us a user identifier that is unique to Pyron and, if you agree, your email address. If you choose “Hide My Email” at Apple, we only receive a forwarding address from Apple and never your real one. Apple only releases your name the very first time you sign in; we then use it as a suggestion for your username.
With “Continue with Google” (Android only)
Google sends us a user identifier that is unique to Pyron, your email address and the name stored in your Google account. We use the name only the very first time you sign in as a suggestion for your username; if you have given yourself a name of your own, it remains untouched. We never get to see your Google password — sign-in works via a signed identity token that we have Google verify.
In all cases
In addition, we store your username and the time zone in which you registered. The time zone is not a location lookup — it is the setting your phone comes with anyway, and we need it to know when a day begins and ends for you. Someone walking in Tokyo should not find their steps in a German calendar day.
Steps from Apple Health and Health Connect
This is the core of the app and the most sensitive part of this policy.
Exactly which data
From Apple HealthKit we read only one value: your step count (HKQuantityTypeIdentifierStepCount). No calories, no floors, no heart rate, no distance, no sleep, no weight, no workouts, no locations. Older versions of the app still ask for active energy and flights climbed in the Apple Health dialog; you may leave both switched off — Pyron no longer reads them there either.
On an Android phone, the step count comes from Health Connect, Google's store for health data (StepsRecord). There too, Pyron requests read permissions only and never writes anything back. Two further permissions are added because Android requires them separately: reading data older than 30 days — so that days filled in later are not lost, for the comparison over twelve months and for the steps per hour from the last year that Pyron Legends needs for choosing your hero — and reading in the background, so that your steps arrive even when the app is not open. You can revoke both at any time in Health Connect under “App permissions › Pyron”; the app will then tell you that nothing is arriving any more.
Anything someone enters by hand in Health Connect is not counted by us: Pyron recognises such entries and excludes them. On Android, too, we read which app or device measured the steps, and only count recognised sources — the same rule as on the iPhone.
Until 25 September 2026 we also read your active energy — only on your device, it never reached us — and your floors climbed. We no longer do either, and we deleted the floors stored until then on 26 September 2026.
For an analysis for our own purposes — whether the people who use Pyron move more than before — we read your steps for the last twelve months once as daily totals, i.e. also from the period before you installed the app, and after that the daily totals of the last seven days at every sync. That is how we compare the average before with the average after. These figures are kept separate from everything the app calculates with; they do not appear in any leaderboard or profile. The anti-cheat looks at them too, and if you play Pyron Legends, the game shows you your year from them before you choose your hero.
In addition, we read which source measured the steps — i.e. whether they come from the iPhone, from an Apple Watch or from another app. We need this because exactly one source always counts in the scoring; otherwise the same walk would be counted twice.
The hunt “Live”: the step counter of your phone and watch
If you switch on “Live” in the hunt, Pyron also counts with your phone's step counter so that your steps appear on the lock screen straight away — on the iPhone with the “Motion & Fitness” permission, on Android with the “Physical activity” permission. So that this keeps running while the screen is locked, Pyron starts a walking workout on the iPhone; it is not saved. The app on the Apple Watch also counts how far you are behind the next player, for as long as you have the hunt open there.
Only the total per day goes to our server, so that the others see you in their live view. None of it is scored — rank, level and competition keep calculating only with what is in Apple Health or Health Connect. On the phone, Pyron only counts while “Live” is running.
On the Apple Watch, you can save a hunt at the end as an “Outdoor Walk” workout in Apple's Fitness app — with duration, distance and calories. This is the only place where Pyron writes anything to Apple Health, and only if you allow it. The workout stays in Apple Health on your devices; it does not go to our server.
How we collect them
If you allow it, iOS notifies us in the background that your step count has changed (“Background Delivery”). The app then asks HealthKit for the totals for certain time windows and sends them to our server. What is transmitted are hourly totals, not individual movements and not the times of individual steps. If you play Pyron Legends, the app also sends the totals per minute of the last 48 hours and the totals of started hours the game asks for.
On Android, there is no such automatic notification. There, Pyron checks Health Connect at a fixed interval — at most every 15 minutes — to see whether anything has changed, and only then fetches the totals. The same is transmitted as on the iPhone.
What for
Exclusively to calculate your rank, your level, your XP and your placing in the competition from them, so that the others see you live in the hunt, for the anti-cheat, so that this competition stays fair, for our analysis of whether Pyron gets people moving, and for our game Pyron Legends. For no other purpose.
On what legal basis
Step counts are health data within the meaning of Art. 4(15) GDPR and therefore a special category of personal data under Art. 9 GDPR. Processing them is prohibited in principle and only permitted if one of the exceptions in Art. 9(2) applies. We rely on Art. 9(2)(a) GDPR — your explicit consent.
You give this consent in two deliberate steps: first on the welcome screen of Pyron, where we tell you that step counts are health data and what we use them for, and then in the iOS or Health Connect dialog in which you grant read access. Without both steps, we do not process any step data. For the live hunt you additionally allow the step counter, and for a workout on the Apple Watch writing to Apple Health — each only once you use it.
How to withdraw your consent
At any time and without giving reasons. You have three options, and they differ in how far they go:
- Revoke access: iPhone Settings → Apps → Health → Data Access & Devices → Pyron → set Steps to “Don't Allow”. From then on, no new values arrive. The existing ones remain stored. You withdraw the step counter for the live hunt under iPhone Settings → Privacy & Security → Motion & Fitness, on Android in the app permissions of Pyron under “Physical activity”.
- Delete your account: in the app under Profile → Settings → Delete account. This also removes all existing values. See Delete your account.
- Write to us: at hello@pyron.app.
The withdrawal takes effect for the future. It does not make our processing of the data up to that point unlawful (Art. 7(3) GDPR).
Anti-cheat
So that everyone has fun and things stay fair, we automatically check the steps of all players for anything unusual. For this we use the same data as for the competition: your steps per hour and per day, which device and which app they come from, and your step history. Nothing is added.
The check only reports a suspicion. Whether we suspend an account for cheating is decided by a human after looking at the case — never by the software alone.
If we remove an account for cheating
- Beforehand, we secure a copy of its data as evidence in case the suspension is later reviewed in court. The copy is kept separately in our database; neither the app nor our admin tool can reach it, and it is only read by hand. We delete it automatically after three years.
- Login details and device identifier are put on a block list for as long as the suspension applies, so that nobody can get around it with a new account: no account can be created with blocked login details, and if a blocked device delivers steps to another account, we suspend that account immediately.
This one suspension happens automatically. A human then reviews every such case and lifts the suspension if it hits the wrong person — for example because a used phone has changed hands. You can ask at any time for a human to review it and tell us your point of view (Art. 22(3) GDPR).
On what legal basis
The check is part of the competition for which you gave us your consent (Art. 9(2)(a) GDPR); at the same time, we and all other players have a legitimate interest in a fair competition (Art. 6(1)(f)). The evidence copy serves solely to establish, exercise or defend legal claims (Art. 9(2)(f) and Art. 6(1)(f), Art. 17(3)(e) GDPR). The block list is based on our legitimate interest in enforcing a suspension (Art. 6(1)(f)); the immediate suspension for a blocked device is an automated decision within the meaning of Art. 22 GDPR that is necessary to enforce the Terms of Use (Art. 22(2)(a)).
If you delete your account yourself, the results of the check go with it — including an open suspicion.
Pyron Legends
Pyron Legends is our role-playing game in the browser: your hero grows stronger the more you walk. You sign in there with your Pyron account: a QR code appears on the computer, you scan it with the Pyron app and confirm the sign-in. So that you can see in the app which computer wants to sign in, Pyron receives a short description of the computer with the code: browser, operating system and the approximate location the game's hosting provider derives from the IP address.
What the game reads from Pyron
As soon as you sign in there, the game reads from Pyron:
- your Pyron username, your time zone, your current day and when your app last synced
- your steps per day and per hour from the day you created your hero
- for choosing your hero: your daily totals of the last twelve months and your steps per hour from the last year
- as long as you have played in the last 30 days: your steps of the last 48 hours per minute, and the steps of a started hour when the game asks for them
What the Pyron app reports for this for everyone
So that the game can recommend a class to you, the Pyron app sends your steps per hour from the last year to our server once. This happens for everyone who has allowed Pyron to read their steps, so also for you if you never open the game. Pyron itself calculates nothing with these hourly values; they do not appear in any leaderboard or profile.
What for
So that your hero gets Gold, Experience and Pyronite from your steps, so that the game shows you in its sync when you walked the steps it credited, and so that it shows you, before you choose your hero, which class suits the way you walk.
On what legal basis
On the same explicit consent as for all step data in Pyron (Art. 9(2)(a) GDPR, together with Art. 6(1)(a)), see Steps from Apple Health and Health Connect. The description of the computer and the moment you last signed out all computers protect you from sign-ins by others (Art. 6(1)(f) GDPR).
How long
The hourly values of the last year stay stored until you delete your Pyron account. Pyron keeps the values per minute for 8 days, and started hours for 40 days after their end. But it only deletes older ones when new ones arrive: the app sends minutes as long as you have played in the last 30 days; the game asks for started hours when you accept a quest there. If no new ones arrive, the last ones stored stay until you delete your account or ask us to delete the game data. For just as long, Pyron remembers when the game last asked for your minutes; that is how the app knows whether to send minutes. Pyron keeps the description of the computer for one day and deletes it as soon as the next code is fetched after that. If you sign out all computers in the app, Pyron remembers the moment until you delete your account; sign-ins to the game from before it then no longer count. What the game itself stores is set out in its own privacy policy at pyron-legends.vercel.app/datenschutz — it is shown in English unless your browser is set to German, and DE / EN at the top of that page switches the language.
Deletion
If you delete your Pyron account, your hero and your game data are gone too, as is everything Pyron keeps for the game. What remains after that: fight reports of players who attacked you, with your name and your hero's values on the day of the fight, and your Help tickets without any link to you. More on this under Delete your account and in the game's privacy policy.
We delete only the game data on request: write to us through Help in the game or to hello@pyron.app. We then also delete, at Pyron, the minutes and started hours Pyron measured for the game and the note that the game asked for your minutes; after that the app sends no more until you play again. Pyron keeps the hourly values of the last year and the moment you last signed out all computers until you delete your account.
The waitlist for the beta
On pyron.app/legends you can put your email address on the waitlist for the Pyron Legends beta. You do not need a Pyron account for this. We store the address and the time you signed up in our database in Ireland; a server of our hosting provider Vercel in the USA passes it on there. We send you nothing in return, neither a confirmation nor a newsletter, and we do not link the address to any account. Only we see the list, in our operator portal.
What for: so that we see who would like to play Pyron Legends in the beta. The legal basis is your consent, which you give by signing up (Art. 6(1)(a) GDPR). You can withdraw it at any time: write to hello@pyron.app and we will take your address off the list. Otherwise it stays stored; there is no period after which we delete the list ourselves.
Who sees what about you
Pyron is a competition, so part of you is visible to others. Which part depends on how you are connected to each other. The limits are set on the server and not merely in what the app displays.
| Who | Sees |
|---|---|
| Every signed-in player | Username, rank, level, title, crest and frame, rating, competition record, achievements earned, your position in leaderboards, the gap to you in steps, as well as your club, your role in it and since when you have been in it |
| Your friends, in addition | your step statistics: daily steps, total steps, best day, number of days walked, longest streak, average of the last seven days, time of the last sync |
| The members of your club, in addition | your messages in the club chat with username and time — including anyone who joins later, as long as the message is stored; not anyone who has blocked you or whom you have blocked |
| Only you | your hourly values, your email address, your reports and your account settings |
| We as the provider | all of the above, to the extent necessary for operation, scoring and preventing abuse |
Choose your username accordingly. It is visible to everyone and can be found via the people search; you do not have to use your real name for it.
Friends and invitations
We store who is friends with whom, pending invitations and — if you state it when registering — who referred you. Friendships are always mutual. You can unfriend someone at any time; the other person is not told.
We do not match any address book and do not read any contacts. You can only find friends via the people search by username.
Club chat
Every club has one shared chat. What you write there is seen by the people who are currently members of your club — including anyone who joins later, as long as the message is stored. No player outside your club sees it. The chat rules are set out in the Terms of Use.
What we store
- every message: the text, when and in which club you wrote it, whom it mentions with @Name and whether it goes to everyone with @everyone (in the German app @alle)
- whether and when a message was deleted and by whom — its text is gone at once
- up to which message you have read, so that the app can count the unread ones
- when you accepted the chat rules
- reports about messages and mutes imposed by us, each with the reason
Messages consist of text and emoji; pictures cannot be sent. They are stored on our server and are not end-to-end encrypted — otherwise new members could not read them and we could not review a reported message. So do not share personal contact details in the chat, such as your phone number, address or email address.
Mentions and notifications
If someone mentions you with @Name, or the chief and deputies call the whole club with @everyone, you get a notification. It only says who mentioned you and in which club — never the text of the message. Like every notification, it is delivered via Apple or Google (see Notifications); so neither of them learns the content of your messages. You can switch these notifications off in the app under Settings → Notifications with the “Club chat” switch.
How much is written
For our overview we count, per club and day, how many messages were written and how many different members wrote. These numbers contain no text and no names. We do not analyse content or the writing behaviour of individual players. The legal basis is our legitimate interest in seeing whether and how the chat is used (Art. 6(1)(f) GDPR).
Word filter, deleting and muting
Before a message is sent, our server automatically checks it against a list of offensive words. If it contains one, it is neither stored nor sent. Anyone who sends a great many messages in a short time is slowed down for a moment.
The chief and deputies can delete any message in their club. If they delete someone else's, we record who deleted which message and when — without its text. We likewise record, with the reason, when we remove a message or mute someone in the chat; the person affected is told in the app.
Reporting and blocking
If you report a message, we store, as with every report (see Reporting bugs, reporting people), who made the report, whom it concerns, the reason and your optional description. In addition, we keep a copy of the reported message and of up to five messages before it in that chat, as you could see them — with usernames and times. This lets us assess the report even if the message has since been deleted. The reported person is not told who made the report.
If you block someone, we store whom you have blocked. In the chat, this means the two of you do not see each other's messages and cannot mention each other.
If a message gives rise to the suspicion of a criminal offence that threatens the life or safety of a person, we pass the message and the necessary details on to the competent authorities (Art. 18 DSA).
Who receives the data
Your messages are received by the members of your club. Like all of the app's data, they are stored at Supabase, Inc. in Ireland (AWS eu-west-1) (see Who else sees the data). Apple and Google only deliver the notification about a mention, without the text of the message.
On what legal basis
The chat is part of Pyron. We need to store and deliver messages, handle mentions and the notification about them, the read marker and your acceptance of the rules to perform the contract with you (Art. 6(1)(b) GDPR); whether your phone receives push notifications at all is up to you, as described under Notifications. Handling reports, sending those affected a statement of reasons and informing authorities are obligations under the Digital Services Act (Art. 6(1)(c) GDPR with Art. 16, 17 and 18 DSA). The copy kept with a report, the word filter, the slow-down, the log of deletions and muting serve our legitimate interest, and that of all players, in a safe community (Art. 6(1)(f) GDPR).
How long
We delete messages automatically after 90 days. If a club is dissolved, we delete its chat. If you delete your account, all your messages are gone at once, as are your read marker, your acceptance of the rules and any mute. A copy made for a report is kept as long as the report itself; the periods are set out under How long we store data.
Notifications
If you allow push notifications, we store the device token that Apple or Google issues for this, and the platform. The token is not a name and not an identifier of your device, but an address to which notifications are delivered; it changes from time to time.
On the iPhone, notifications are sent via Apple's Apple Push Notification service, on Android via Google's Firebase Cloud Messaging. In the process, the content of a notification passes through the servers of Apple or Google respectively. The legal basis is your consent under Art. 6(1)(a) GDPR, which you can withdraw at any time in your phone's settings.
Reporting bugs, reporting people
Bugs and ideas
If you shake your iPhone, a report box opens. Along with your text, we transmit: which screen was open, the app version, the device class (such as “iOS phone”), the iOS version and the app's most recent log lines. If the app crashes, you can send the same report with one tap on the error screen, then with the error message. These reports are linked to your account. What you write to us through Help in Pyron Legends lands in the same inbox; what the game sends along is set out in its privacy policy.
The legal basis is our legitimate interest in an app that works (Art. 6(1)(f) GDPR). An app whose crashes nobody hears about does not get fixed.
Reporting a person
If you come across a username that is insulting or deceptive, you can report the person via their profile. We then store who made the report, who was reported and why. The reported person does not find out who the report came from. Details of the procedure are set out in the Terms of Use. What we store when you report a message in the club chat is set out under Club chat.
Anonymous usage events
We keep count of whether the competition works technically: how many rounds start, are scored or fail. These events are not linked to your player ID but to a pseudonymous identifier derived from it (HMAC-SHA256 with a secret that never leaves the server). The server explicitly removes step counts, player IDs and display names from every event, even if the app sent them. Rating values are only included in bands (“250–399”), never as an exact number.
Before sign-in, we count how far a visit gets: whether the app was opened, which page of the introduction was reached and whether “Sign in with Apple” or email registration was tapped. For this, the app generates a random visit ID at every launch, which exists only in memory and is not stored on your device. Only this ID, the step reached, the build and app version and the iOS version are transmitted — no player ID, no name, no advertising ID. We do not store an IP address with it. The entries are deleted after 400 days at the latest.
Apart from the Meta SDK and the TikTok SDK for ad measurement (see Ad measurement with Meta and Ad measurement with TikTok), we use no third-party analytics or advertising service. The app does not ask for tracking permission — and without it, your iPhone does not hand out an advertising ID.
How you use the app
After sign-in, the app additionally records which page of the initial setup you are looking at and when you have completed it, which area of the app you switch to (for example from “Home” to “Club”) and on which days you open the app. These entries carry your player ID, the same visit ID as before sign-in, the build and app version and the version of your operating system.
They do not contain your answers in the setup — neither whether you grant access to Apple Health or Health Connect, nor your name or your look —, no step counts and nothing you write. The entries stay with us and are not passed on to anyone, not to Meta or TikTok either.
We use them to see where new players stop, whether they are still around after a week and which advertising brings players who stay. The legal basis is our legitimate interest in aligning the app and our advertising accordingly (Art. 6(1)(f) GDPR). We delete the entries on pages and areas after 400 days, and the days on which you opened the app together with your account. You can object at any time (Art. 21 GDPR) — a short message to hello@pyron.app is enough.
Crash reports
To keep Pyron running reliably, we send technical diagnostic data to Sentry (Functional Software, Inc. dba Sentry). Without such reports, we only learn about an error when someone reports it — and most errors are never reported by anyone.
We have deliberately configured these diagnostics broadly. The following is transmitted:
- the error message and the place in the program where it occurred
- app version, operating system version, device model, time
- your IP address
- your player ID and your display name, so that a report can be linked to your account
- the last actions before the error: which screens you opened, what you tapped and which server calls the app made
- a screenshot of the moment of the error and the structure of the screen at that instant — not pixelated
The data is stored in Frankfurt am Main (Sentry's EU region) and is not used for advertising purposes, not sold and not combined with data from other services. The legal basis is our legitimate interest in a stable app (Art. 6(1)(f) GDPR). We delete error reports after 90 days, together with the screenshots belonging to them.
You can object to this processing at any time — write to us at hello@pyron.app. More under Your rights.
Ad measurement with Meta
We promote Pyron with ads on Facebook and Instagram. To find out how many people find their way to the app through such an ad, the software toolkit of Meta Platforms Ireland Limited (Meta SDK) is built into the iPhone app and, since October 2026, into the Android app.
The SDK transmits to Meta:
- that Pyron has been installed and opened on a device,
- that an account was created, the initial setup was completed or the free month was started in the app — only the event itself, without name, email address or account ID,
- purchases and subscriptions made through the App Store or Google Play (product and price),
- technical device data: device model, version of iOS or Android and of the app, language, time zone and the IP address of your device,
- on Android, your device's advertising ID (Google's advertising ID). You can reset or delete it in the Android settings under “Privacy → Ads”; after that, Meta no longer receives an advertising ID.
Not transmitted are your steps, floors, calories or other health data, your username, your email address and anything else you see or do in the app. On the iPhone we do not ask for app tracking permission. The SDK does ask your iPhone for its advertising ID, because Meta only accepts an install report with this field — but without your tracking permission, iOS only answers with zeros. So no advertising ID is sent to Meta from an iPhone. Meta therefore only evaluates these reports in aggregated form (“Aggregated Event Measurement”) and additionally attributes them to an ad via Apple's SKAdNetwork. On Android, Meta attributes an install to an ad through the advertising ID and through Google Play.
The legal basis is our legitimate interest in measuring the effectiveness of our advertising and using the advertising budget sensibly (Art. 6(1)(f) GDPR). We and Meta are joint controllers for the measurement (Art. 26 GDPR); any further processing at Meta is governed by Meta's data policy (facebook.com/privacy/policy). Meta may also process the data in the USA; see Transfers outside the EU.
You can object to this processing at any time (Art. 21 GDPR) — a short message to hello@pyron.app is enough.
Ad measurement with TikTok
We also advertise Pyron on TikTok. To learn how many people find the app through such an ad and how many of them go on to play, the software toolkit of TikTok Technology Limited (TikTok SDK) is built into the iPhone app. The Android app does not contain it.
The SDK transmits to TikTok:
- that Pyron was newly installed on a device, when the app is opened, moves to the foreground or background, and whether you come back on the day after installing it, and whether the app was opened via a link,
- that an account was created, the initial setup was completed or the free month was started in the app — only the event itself, without a name, email address or account ID,
- purchases and subscriptions made through the App Store (product and price), and that a purchase dialog was shown,
- technical device data: device model, versions of iOS and of the app, language, time zone, your device's IP address, the identifier your iPhone assigns only to our apps (IDFV), your iPhone's browser identifier (user agent) and technical reports of the SDK about its own operation.
Not transmitted are your steps, floors, calories or any other health data, your username, your email address and anything else you see or do in the app. Two functions TikTok could switch on remotely in the SDK — screenshots and reading the text on the screen — we have switched off in the SDK itself, as well as its own crash reporter. We do not ask for app tracking permission; without it, iOS only answers the question for the advertising ID with zeros. So no advertising ID is sent to TikTok. Which ad led to an install is additionally reported to TikTok by Apple in aggregated form via SKAdNetwork; for this, the SDK sets the number Apple provides for it.
The legal basis is our legitimate interest in measuring the effect of our advertising and using the advertising budget sensibly (Art. 6(1)(f) GDPR). We and TikTok are joint controllers for the collection and transmission to TikTok (Art. 26 GDPR); any further processing at TikTok is governed by TikTok's privacy policy (tiktok.com/legal/privacy-policy-eea). The SDK sends to a TikTok server in the USA, and TikTok may also process the data in other countries outside the EU; see Transfers outside the EU.
You can object to this processing at any time (Art. 21 GDPR) — a short message to hello@pyron.app is enough.
Ad measurement with Apple
We also advertise Pyron with ads in the App Store. Apple gives every installation a marker that shows whether it followed such an ad — and if so, which one: campaign, ad group, keyword and country. The iPhone app passes this marker once to RevenueCat, Inc., which asks Apple and stores the result with your player ID. Of this, we only copy campaign, ad group and keyword into our database.
This requires no advertising ID and no permission for app tracking; Apple names neither your name nor your Apple ID, and health data plays no part. If you did not download Pyron via an ad, it only says that no ad was involved.
This way we see which ad brings players who stay and where the advertising budget is worth it. The legal basis is our legitimate interest in this (Art. 6(1)(f) GDPR). You can object at any time (Art. 21 GDPR) — a short message to hello@pyron.app is enough.
Discord
There is a Pyron community server on Discord. Discord is a separate service; what you write there and who sees what is processed by Discord Netherlands BV (Schiphol Boulevard 195, 1118 BG Schiphol, Niederlande) under its own responsibility and its own privacy policy (discord.com/privacy).
What our bot posts there. In the “pyron-live” channel the Pyron bot posts when a club completes a dungeon or is founded (with the club’s name), when the donation pot is full, and when someone earns a legendary title — then with username and title. Once a week it sums this up, plus numbers without names. Step counts, flames and any other data about your movement are never sent to Discord. If an account is banned or deleted, the bot deletes its posts about that person. The legal basis is our legitimate interest in fostering the Pyron community (Art. 6(1)(f) GDPR). You can object at any time (Art. 21 GDPR) — a short message to hello@pyron.app is enough; the bot will then no longer name you and deletes what it wrote about you.
Connecting your account. In the app you can voluntarily connect your Pyron account to your Discord account — from age 13 in the English app, and from age 16 in the German app, because Discord is only allowed from 16 in Germany. We then store your Discord ID and display name, and the bot gives you roles on the server: “Verbunden” (so you can write), your rank and, if applicable, “Gründungsmitglied”. Others on the server can see your rank; when asked on the server, the bot also shows your username, profile picture, club and titles. If you connect via the Discord login, Discord gives us a one-time access token; we use it to get your ID and add you to the server, never store it, and revoke it right away.
The legal basis is your consent (Art. 6(1)(a) GDPR), given when you connect. You can withdraw it at any time by disconnecting in the app (Profile → Settings → Discord); the bot then removes your roles and the connection is deleted. It is also deleted with your account.
WhatsApp channel
News about Pyron is also posted in the WhatsApp channels “Pyron Updates | EN” in English and “Pyron Updates | DE” in German. The app, the changelog and pyron.app/whatsapp only link to them: tapping the link opens WhatsApp, and we send nothing to WhatsApp. Whether you follow a channel is up to you, in WhatsApp. WhatsApp is a separate service: WhatsApp Ireland Limited (Merrion Road, Dublin 4, D04 X2K5, Irland) processes your data there under its own responsibility and its own privacy policy (whatsapp.com/legal/privacy-policy-eea), also in the USA — WhatsApp LLC and Meta Platforms, Inc. are certified under the EU-US Data Privacy Framework.
What we see. Only we post in the channels. Followers can read, react with an emoji and vote in polls. Other followers only see how many reactions a post has, not who reacted. WhatsApp shows us how many people follow each channel, from 100 followers also figures for the last 30 days (accounts reached, regions, new and ended follows), plus the reactions and poll results. In the list of followers we can recognise people who are saved in the contacts of the phone we run the channels with. If you react to a post, we see your WhatsApp profile name, and, depending on your WhatsApp settings, your profile picture next to reactions and votes. We do not copy any of this into our own systems. We look at it to understand whether the updates reach people — the legal basis is our legitimate interest (Art. 6(1)(f) GDPR). You can unfollow a channel in WhatsApp at any time.
Subscription and purchase
Pyron is offered in the App Store and on Google Play. Anyone who takes out the subscription concludes the purchase contract with Apple or Google respectively, not with us. Your payment data — credit card, billing address, Apple ID or Google account — is processed exclusively by the respective store; we never get to see it.
From Apple and Google, we only receive the information whether a valid subscription exists for your account, as well as aggregated, non-personal sales statistics. The handling between app, store and our server is done for us by RevenueCat, Inc. as a processor: it receives your player ID and the store's purchase records (product, price, time), never your payment data, and uses them to check whether a subscription exists. More about the subscription can be found in the Terms of Use, and about data processing by Apple in Apple's own privacy policy.
Creator programme
Creators recommend Pyron on their channels and earn a commission. Their creator area is at pyron.app/partner.
When you enter a creator code
We store on your account which creator it belongs to and calculate that creator’s commission from your subscription. The creator only sees numbers, such as how many codes were entered and what they earned. They never learn who you are. If you delete your account, the link to you is removed; the commission stays in the creator’s statement without any reference to your account.
Applying
Anyone who wants to become a creator applies in the creator area: with the channels where they can be found, optionally with their reach, and a message. We read the application and reply in the app.
Signing in to the creator area
You open the creator area with the Pyron app: you scan a QR code on your computer and confirm it on your phone. So you can see which computer wants to sign in, we keep its browser, operating system and approximate location (derived by our hosting provider from the IP address) for one day. After signing in, your computer stays signed in for 30 days; “Sign out all computers” in the app ends that at once. That a computer signed in with your account, and when, we keep for 31 days so the app can show you that button.
What we store about creators
- Whether you take part as a person or a company, first and last name or company name and legal form, optionally your channel name, your address, country and email address
- Whether you act as a business, your VAT rule and your tax number or VAT ID — abroad also whether a permanent establishment in Germany takes part, whether you use the cross-border EU small business scheme, and your EX number or your tax or business number. We store these numbers encrypted; the creator area and our operator portal only show the last four characters. In full they appear only on your credit notes, where the law requires them.
- The result of every check of your VAT ID with the EU service VIES (valid, invalid, currently unavailable), with time and reference number; for an EX number the result of our check on the EU page “SME-on-the-web”
- Your confirmation that you are at least 18
- Your acceptance of the contract: version, a checksum of the accepted text, the name you typed, time, IP address and browser identifier
- Your six consents (among them to self-billing and electronic statements), each with time and language
- Once you connect a payout method: your ID at Stripe or PayPal and the status of your payouts. We do not store bank details or ID documents — the payment service checks those itself
- Your credit notes and statements as PDF and e-invoice, stored encrypted, and when we delivered them by notification and email
- A log of every change to these details, without tax number and without address. We also notify your phone of every change
Payouts through Stripe or PayPal
Payouts go through Stripe or PayPal, whichever you choose. With Stripe, we create an account for you and pass on your country, your email address and whether you take part as a person or a company; everything else — name, bank details, ID — you enter directly at Stripe. With PayPal, you sign in with your PayPal account and we only receive your PayPal ID. For each payout, the payment service learns the amount, the credit note numbers and your creator code. Stripe (Stripe Payments Europe, Limited) and PayPal (PayPal (Europe) S.à r.l. et Cie, S.C.A.) process your data there as independent controllers under their own privacy policies; as payment services they are required by law to identify you.
VAT ID check
If you take part as a business from another EU country, we check your VAT ID with the European Commission’s VIES service — often enough that the check is never more than 35 days old at any statement. We send your VAT ID and ours; the answer comes from your country’s tax administration. We are obliged to treat VAT on your credit notes correctly and must be able to prove it (Art. 6(1)(c) and (f) GDPR).
Credit notes and emails
Every month we create your credit note or statement as a PDF with an embedded e-invoice, store it encrypted and send it to you as an app notification and as an email attachment through our email service Resend. Our tax advisor receives it with the booking data for the accounts and is bound to confidentiality.
Why and on what legal basis
We need these details to perform the contract with you, calculate commissions, issue credit notes or statements and pay out (Art. 6(1)(b) GDPR). We must keep credit notes and the details on them under tax and commercial law (Art. 6(1)(c) GDPR with Section 14b of the German VAT Act (UStG) and Section 147 AO). The sign-in and change logs protect your account and prevent misuse, our legitimate interest (Art. 6(1)(f) GDPR).
If you delete your account
Credit notes and the details on them are kept until the end of the retention period. Everything else is deleted once the contract has ended and no retention period applies any more.
This website
pyron.app is an informational site. Its public pages have no login, and what you do there does not end up in our database. The exceptions are the waitlist for Pyron Legends at pyron.app/legends (see The waitlist for the beta) and the creator area at pyron.app/partner (see Creator programme).
- At most one cookie on the public pages, and only if you switch the language at the bottom of the page:
spracheremembers for one year whether you want to read the site in German or in English. It contains only “de” or “en” and no identifier. Apart from that, we do not store anything on your device there and do not read anything from it. As your choice cannot be remembered without the cookie, no consent is needed (Section 25(2) no. 2 of the German Telecommunications Digital Services Data Protection Act, TDDDG), and there is no cookie banner here for you to click away. - Two sign-in cookies in the creator area: one for seven minutes while you confirm the QR code, and one that keeps you signed in for 30 days. Both apply only to the creator area, cannot be read by scripts on the page and contain no advertising or analytics identifier. As signing in does not work without them, no consent is needed (Section 25(2) no. 2 TDDDG).
- No trackers, no tracking pixels, no embeds from YouTube, Google Maps or social networks.
- Fonts are hosted by us. The fonts are delivered along with the site when it is built. Your browser does not fetch anything from Google for them, and no IP address is transmitted to the USA.
When the site is accessed, server logs are created at our host Vercel for technical reasons: IP address, time, requested address, browser type and referring page. They serve the operation of the site and the defence against attacks (Art. 6(1)(f) GDPR) and are deleted after a short time.
Who else sees the data
We do not sell your data. For ad measurement, Meta and TikTok receive the information listed under Ad measurement with Meta and Ad measurement with TikTok. In addition, we use service providers who work for us and on our instructions (processors under Art. 28 GDPR). We have a data processing agreement with each of them that obliges them to a level of protection that corresponds to this policy.
| Who | Purpose | Where the data is stored |
|---|---|---|
| Supabase, Inc. 970 Toa Payoh North, #07-04, Singapore 318992 | Database, accounts, server operation of the app | Ireland (AWS eu-west-1) |
| Functional Software, Inc. dba Sentry 45 Fremont Street, 8th Floor, San Francisco, CA 94105, USA | Crash and error reports of the app | Frankfurt am Main (Sentry's EU region) |
| Apple Distribution International Ltd. Hollyhill Industrial Estate, Hollyhill, Cork, Ireland | App Store, Sign in with Apple, push notifications, subscription | Ireland and other Apple locations |
| Google Ireland Limited Gordon House, Barrow Street, Dublin 4, Ireland | Google Play, “Continue with Google”, push notifications on Android (Firebase Cloud Messaging), subscription on Android | Ireland and other Google locations |
| Vercel Inc. 440 N Barranca Ave #4133, Covina, CA 91723, USA | Operation of this website and of the game Pyron Legends, whose server reads your steps from our database for it (not the app) | European data centres; the game's server in Dublin (Ireland), the waitlist on a server in the USA; logs also in the USA |
| RevenueCat, Inc. 1032 E Brandon Blvd #3003, Brandon, FL 33511, USA | Handling of purchases and subscriptions; attribution of an installation to an ad in the App Store (iPhone app only) | USA (Amazon Web Services) |
| Meta Platforms Ireland Limited Merrion Road, Dublin 4, D04 X2K5, Ireland | Ad measurement for the iPhone app (joint controller, not a processor) | Ireland, also USA (Meta Platforms, Inc.) |
| TikTok Technology Limited 10 Earlsfort Terrace, Dublin, D02 T380, Ireland | Ad measurement for the iPhone app (joint controller, not a processor) | Ireland, also USA and other countries outside the EU |
| Discord Netherlands BV Schiphol Boulevard 195, 1118 BG Schiphol, Niederlande | Community server and posts by the Pyron bot (independent controller, not a processor) | Netherlands, also USA (Discord Inc.) |
| Plus Five Five, Inc. (Resend) 2261 Market Street #5039, San Francisco, CA 94114, USA | Sending our emails: confirmation and password codes, messages about a ban, credit notes to creators, notices to us when a player writes to us | USA |
| Stripe Payments Europe, Limited The One Building, 1 Grand Canal Street Lower, Dublin 2, Ireland | Payouts to creators who choose Stripe (independent controller, not a processor) | Ireland, also USA (Stripe, Inc.) |
| PayPal (Europe) S.à r.l. et Cie, S.C.A. 22–24 Boulevard Royal, L-2449 Luxembourg | Payouts to creators who choose PayPal (independent controller, not a processor) | Luxembourg and other PayPal locations |
For the creator programme, our tax advisor also receives credit notes and booking data for the accounts and is bound to confidentiality. The European Commission and the tax administration in a creator’s country receive, through the VIES service, that creator’s VAT ID and ours to confirm that it is valid.
Beyond that, we only disclose data if we are legally obliged to do so — for example to law enforcement authorities on the basis of a valid order, or under Art. 18 DSA where life or safety is at risk (see Club chat).
Transfers outside the EU
The app's data is stored in Ireland and therefore within the EU. The exceptions are purchase records and the attribution to Apple ads: RevenueCat, Inc. stores them in the USA. Resend sends our emails from the USA. What you enter on the waitlist for Pyron Legends is received by a server of Vercel in the USA. In addition, some of the companies we use are based outside the EU, so access from a third country — in particular the USA — cannot be ruled out. If you live outside the EU as a creator, we send your credit notes there and pay out there; this is necessary for the contract with you (Art. 49(1)(b) GDPR).
For these cases, we base the transfer on the European Commission's standard contractual clauses under Art. 46(2)(c) GDPR, which form part of the contracts with the providers named — in the case of Meta, additionally on the European Commission's adequacy decision on the EU-US Data Privacy Framework (Art. 45 GDPR), which Meta Platforms, Inc. has joined, as have Discord Inc.,Resend and Stripe; for TikTok on the standard contractual clauses in TikTok's business products terms — supplemented by technical measures such as encryption in transit and at rest. A third country outside the EU may not offer a level of protection comparable to that of the EU; in particular, authorities there may be able to access data under less stringent conditions, and legal remedies against this may be limited.
How long we store data
| What | How long |
|---|---|
| Account, profile, friendships, club and teams | until you delete the account |
| Step values, rank, rating, achievements | until you delete the account |
| Connection to Discord (Discord ID and display name) | until you disconnect or delete your account |
| Results of the anti-cheat | until you delete the account |
| Steps per day from the live hunt | until you delete the account |
| Steps per hour from the last year, for the class recommendation in Pyron Legends | until you delete the account |
| For Pyron Legends: your steps per minute and started hours (start, end and the steps in them) | minutes 8 days, started hours 40 days after their end — older ones are deleted when new ones arrive; if none arrive, until you delete the account or ask us to delete the game data |
| For Pyron Legends: when the game last asked for your minutes | until you delete the account or ask us to delete the game data |
| Description of the computer when signing in to Pyron Legends | one day; deleted as soon as the next code is fetched after that |
| When you last signed out all computers from Pyron Legends | until you delete the account |
| Floors collected until 25 September 2026 | deleted on 26 September 2026 |
| Evidence copy of an account removed for cheating, including its check results | three years, then we delete it automatically |
| Block list: login details and device identifier of a suspended player | for as long as the suspension applies |
| Device token for notifications | until you withdraw permission, the token becomes invalid or you delete the account |
| Bug reports and Help tickets you send us, also from Pyron Legends | until one year after the case is closed; the link to your account is removed when the account is deleted |
| Crash reports at Sentry | 90 days |
| Reports about people | until the matter is resolved, then for a maximum of 12 months |
| Messages in the club chat | 90 days; earlier if they are deleted, the club is dissolved or you delete your account |
| Read marker in the club chat, acceptance of the chat rules | until you delete the account |
| Daily club chat counts (messages and writers per club, without text or names) | as long as the club exists |
| Mute in the club chat | until it expires; a permanent one until you delete the account |
| Copy of a reported message and of up to five before it | like the report: until the matter is resolved, then for a maximum of 12 months — even if the message or the account is deleted earlier |
| Log of who deleted someone else's message in the chat or whom we muted (without text) | as long as it is needed for an objection or to defend legal claims |
| Pseudonymous usage events | permanently; after the account is deleted, they can no longer be attributed to anyone |
| Which pages and areas of the app you open | 400 days; after the account is deleted, they can no longer be attributed to anyone |
| On which days you open the app | until your account is deleted |
| Purchase records and attribution to Apple ads at RevenueCat | until your account is deleted — then we instruct RevenueCat to delete them; the stores keep their purchase records according to their own periods |
| Link between your account and a creator code | until you delete your account; the commission then stays in the creator’s statement without any reference to your account |
| Creator application | until you delete your account |
| Browser, operating system and location at sign-in to the creator area | one day |
| That a computer signed in with your account | 31 days |
| Credit notes, statements and the details on them | 8 years from the end of the year they were issued |
| Contract, consents, account and tax details of creators, VAT ID check results, change log | while the contract runs, then until the statutory retention periods end |
| ID at the payment service | while the contract runs and payouts are open |
| Email address on the waitlist for Pyron Legends | until you ask us to take it off the list; there is no fixed period |
| Server logs of this website | a few days |
| Records relevant for tax purposes | statutory retention periods under Section 147 of the German Fiscal Code (AO) and Section 257 of the German Commercial Code (HGB) (6 or 8 years respectively); this data is not accessible for anything else |
What disappears when you delete your account, and what remains and for what reason, is explained in detail under Delete your account.
Age
We do not collect a date of birth and therefore cannot verify age. If we become aware that an account belongs to a child under 16 without parental consent, we will delete it.
Your rights
You have the following rights with respect to us:
- Access (Art. 15 GDPR) — which data we process about you
- Rectification (Art. 16 GDPR) — having incorrect data corrected
- Erasure (Art. 17 GDPR) — the “right to be forgotten”
- Restriction of processing (Art. 18 GDPR)
- Data portability (Art. 20 GDPR) — receiving your data in a machine-readable format
- Objection (Art. 21 GDPR) — to processing that we base on a legitimate interest
- Withdrawal of consent (Art. 7(3) GDPR) — at any time and with effect for the future
For all of this, an email to hello@pyron.app is enough. We reply within one month (Art. 12(3) GDPR). There is no charge to you.
Complaint to the supervisory authority
Independently of this, you can lodge a complaint with a data protection supervisory authority at any time (Art. 77 GDPR), in particular in the EU member state of your place of residence or your place of work. The authority responsible for us is:
State Commissioner for Data Protection and Freedom of Information Baden-Württemberg (Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg)
Lautenschlagerstraße 20, 70173 Stuttgart
www.baden-wuerttemberg.datenschutz.de
Changes
If what the app does changes, this policy changes with it. The date at the top tells you which version applies. For changes that affect you significantly — such as a new type of data or a new recipient — we will point them out to you in the app before they take effect. If the purpose for which we process your health data changes, we will obtain new consent beforehand.
