QuestPumpDownload

Legal

Privacy

How QuestPump and questpump.com handle personal data.

Last updated: 21 November 2026.

Who is responsible

Pluxia GmbH, c/o RB Swiss Group GmbH, Blegistrasse 7, 6340 Baar, Switzerland, contact@questpump.com.

The add-on

QuestPump runs inside your game client. What you type and what it counts stays on your computer and your paired devices, and goes sealed to your other devices if they sync (see Sync between your devices below), unless you send it to us as feedback. It is kept in the game's own saved-variables file, with QuestPump on your computer and in the phone app. Only the QuestPump card below goes to other players. The add-on sends nothing to Pluxia GmbH on its own: it has no account, and the game gives it no way to go online. Only feedback you choose to send reaches us (see Feedback below). There is one more thing: while its usage statistics are on, QuestPump on your computer sends us daily counts of your pumps in the game, without any id (see Usage statistics below). If you copy an export string or send a share line in chat, you decide where it goes.

The QuestPump card

The add-on shows other players a small card about you and shows you theirs. It carries your QuestPump level, title and portrait border, your Paragon rank, your streak, your active days in the last 28 days, this week's pumps, records beaten and cardio minutes, how many moves you did today, whether you are in a pump right now and whether you did one today, and your character's game id. If you have a pact or a duel with friends, it also says where it stands: whether you did your part today, or your duel score. The counts you type travel only if you turn on "Include my records" (your first and best count on each ladder, marked as typed by you). The card never carries your pain flags, your heart rate or where you are.

By default your friends, your guild and your group see it; you can also show it to anyone who asks. It travels as add-on messages through Blizzard's game servers, which can see them, and never reaches Pluxia GmbH; the add-on forgets other players' cards when you log out. It keeps a pact partner's or a duel rival's name only while the pact or the duel lasts. Cheers travel the same way, and so do a few short notes: that you started a pump, how many moves you did today, a pact or duel offer to a friend and, if you turn it on, a Legendary unlock. To switch the card off, open QuestPump's settings, go to Social and set "Who sees your QuestPump card" to "Nobody (private)": the add-on then tells other players only that your card is private. In dungeons, raids and battlegrounds it sends and shows nothing unless you turn that off.

QuestPump on your computer

QuestPump on your computer, the app for Mac and Windows, runs beside the game. It reads the add-on's status strip in the corner of the game window and never saves or sends a picture. It keeps your progress in the game folder and in its own folder on your computer, with a copy of the pumps you do in the phone app and the pumps you do on the computer itself, which it gives back to your paired phones. Pairing, your pumps, the Body switches, the moves you left out and heart-rate readings go between your computer and your phone and watch on your home network, sealed with the pairing key. With sync on, it also sends your progress, sealed, to your other devices through our server, which cannot open it (see Sync between your devices below); heart-rate readings never go there. While an iPhone follows the game, it also sends each state of the game's pump, sealed, through our server and Apple to that iPhone's Lock Screen (see the same section). Beyond that, it sends us only the feedback you send, from its window or from the game (see Feedback below), a report when it crashes, if crash reports are on or you choose to send it (see Crash reports below), and daily counts without any id while its usage statistics are on (see Usage statistics below). "Copy a report for help" in its Menu puts a report on your clipboard, and you decide where it goes.

While work mode is on, it also notes which app is in front, whether the microphone or the camera is in use, and whether a window fills the screen or you share or mirror your screen. It uses this only to wait during calls, full screen and games, and to bring your app back after a pump. It never hears or sees what the microphone or the camera picks up, and none of this leaves the computer.

Ten seconds after it starts, and then about once an hour, it asks GitHub, Inc. (USA), where its releases are published, whether a new version is out, and downloads it from there. It asks again sooner when a check fails or the game closes. It downloads the films of the moves from there too, once for each new set of films. Its download links on questpump.com lead there as well, and so does the one for the add-on's zip. GitHub then sees your IP address, the time and the updater's identification, and may process them outside Switzerland. See GitHub's privacy statement.

Games on your computer

QuestPump on your computer can offer you a pump when a match ends, or when you close a game, in the games you play there. It watches each game it finds from the day it finds it, and you can turn any game off in its Games tab. For a game it watches:

  • Counter-Strike 2 and Dota 2: it sees when the game closes. Only after you tap "Ask after each match" for the game, it writes one settings file, gamestate_integration_questpump.cfg, into the game's folder. With it, the game sends the state of each match to QuestPump on the computer itself (127.0.0.1), with a code that only the two of them know. QuestPump reads only whether a match is on or over and drops the rest unread: the scores, the match, and your Steam ID or player name should the game send them.
  • Rocket League: it sees when the game closes. After you tap "Ask after each match", it reads the game's own settings files for the match feed (TAStatsAPI.ini, or DefaultStatsAPI.ini without it) and, when neither turns the feed on, writes TAStatsAPI.ini, never over one you made yourself, so that the game tells programs on the computer itself what happens in a match. QuestPump reads only which event it was, never the players' names, ids or scores, and it never sends the game anything.
  • Some games tell other programs on the computer itself (127.0.0.1) how a match goes: QuestPump asks the game's own local game client, or listens on a port you set in a racing game, or reads the race data a racing game shares in memory for other apps, and never writes to it. It reads only whether a match or a race is on or over.
  • Some games write a log of their matches on the computer. QuestPump looks through that log only for the lines that say a match began or ended. It keeps none of it. For one game it adds its own part to the game's log settings file, which other programs use too, and only after you tap "Ask after each match".
  • Any other game it finds, and a program you add: it watches the list of running programs for that program's name, to see it start and close.

While "Notice games I play" is on, as it is until you turn it off, QuestPump looks at the names and paths of the programs that run. It also reads the lists of games that Steam, Windows and other game stores keep on the computer, and for a Steam program the kind Steam gives it, so that only games count. This way it finds the games you play. It keeps a found game's name, its program, its icon and when it saw it in its own folder, and none of it leaves the computer. While it is off, QuestPump finds no new game. It still reads the records of Steam and other game stores, to see where the games it knows by name are installed. For a Steam game it already watches, it also reads Steam's own records of its games, to know when that game closes. It reads no other list then.

To know how long you sat at the computer, it reads how long ago you last pressed a key, clicked or touched the screen. It never reads which key or where.

It keeps nothing of a match but when it began and that it ended, which offer you the pump and set its size, and nothing of the match reaches Pluxia GmbH. While usage statistics are on, its daily counts say only after which game it offered a pump and whether you took it (see Usage statistics below). When you turn a game off, it removes the file it wrote for it, and on Windows, uninstalling it removes every such file too. The part it added to a shared log settings file stays.

Apple Health and Health Connect

Only if you allow it, the phone app saves each pump it times as a workout in Apple Health or Health Connect. It saves its start and end and, in Health Connect, its title, such as "QuestPump · A match · 2 moves". A play session on the watch is saved there too, with what the watch measured. The app reads QuestPump's own workouts back to show the minutes you played each week. QuestPump keeps this on your phone and sends none of it to Pluxia GmbH.

Your pumps on your phone

The phone app keeps your pumps on your phone. Your pumps, counts and times go into your phone's own backup (iCloud or Google, if you use it), and you can save them as a backup file wherever you choose and read that file back into the app. A pump you start after a game on your phone also holds the game's name, the minutes you played and the matches you said (see Games on your phone). Heart rate, the pain you report, your answers to "Muscles today?" and the times you stopped because you felt unwell stay on your own devices (your phone, your watch, and QuestPump and the game on your computer, which need them to lock pumps after you felt unwell, to leave out the moves a sore joint should skip and to show the heart-rate marks): they go into neither the phone's backup, nor the backup file, nor the sync below. Pluxia GmbH receives none of it, and none of it goes with feedback, a crash report or the usage statistics.

Where a law requires it, the phone app asks your app store for your age range when it opens, uses the answer only to decide whether it may open that time, and keeps or sends none of it.

Sync between your devices

The phone app and QuestPump on your computer keep your progress the same on all your phones and computers. So does QuestPump in your browser, once you save your progress there (see QuestPump in your browser). They sync through our server on questpump.com. What syncs: your pumps, counts and times (with the game's name, minutes and matches of a pump after a game on your phone), the game's pumps and your characters' QuestPump sheets from your computer, your setup (your equipment, how hard, the Body switches, the moves you left out and your favourites), work mode (whether it is on, its choices and its clock) and the name of each device. Your watch syncs through your phone. Heart rate, the pain you report, your answers to "Muscles today?", the times you stopped because you felt unwell and anything from Apple Health or Health Connect never sync.

Sync is on unless you switch it off, in the app's Menu under Backup and sync. Switched off, it sends nothing and takes nothing in, and everything stays on your device. The first device that syncs makes an account for your devices by itself. It has no name and no password, only a random number. Its restore code, which the Menu shows under Email, gets you back in on a new device.

Before anything leaves your device, it is sealed with a key only your devices hold. Our server cannot open it. The server keeps the sealed parts and a list of your devices: for each, its kind (iPhone, Android, computer or browser), when it joined and when it last synced. To know your devices, it keeps codes made from their keys, which cannot be turned back into the keys.

An iPhone plans its streak reminder ahead and cannot check anything at the moment the reminder comes. So that it does not remind you after a pump on another device, our server can wake the app. While sync and the streak reminder are both on, the iPhone app gives our server its push token. That is the address Apple gave the app for pushes. With it, our server keeps the time from which the phone waits for news, when news last came for it and when it was last woken. When another of your devices syncs after that time, our server asks Apple to send your iPhone a silent push. The push is empty: it shows nothing and says nothing about your pumps. Apple gets the token and the time of the push, and delivers it under its own privacy policy. Apple may handle it outside Switzerland and the EU, including in the USA. The app then syncs, and takes the reminder back if you have pumped that day. Switch off sync or the streak reminder, and the app takes its token back from our server. The token also goes when the phone leaves the account or the account is deleted. The Android app needs no push: it syncs at the moment its reminder is due.

A locked iPhone does not run the app, so the app cannot hear the game on your computer. So that the game's pumps still show on your Lock Screen, our server can pass them on. The iPhone app follows the game when you ask it to with Follow the game: the button in the app, its control or a shortcut. It also starts to follow when you have the app on screen while the game runs on your computer. While it follows with sync on, and QuestPump on your computer syncs to the same account, the app gives our server the push token of its Live Activity, the pump's card on your Lock Screen. It does not send the token while the app is running and can hear your computer on your home network. It needs no push then, and takes the token back. With the token, our server keeps which computer the phone follows, the names of the alert's two lines and its sound in the app, when the phone asked and when your computer last sent word. With your account it also keeps one number until the account is deleted: the time of its last push, so that each push is newer than the one before. QuestPump on your computer then sends our server each state of the game's pump: the names of its moves, how many are done, the move you are on, its goal and its clock, and between pumps your computer's name. Each state is sealed with a key only your devices hold. Our server cannot open it and keeps none of them. It asks Apple to push each one to your iPhone, which opens it. Apple gets the token, the sealed state, the id of the key that sealed it and, for an alert, the names of its two lines and its sound. Apple delivers the push under its own privacy policy. Apple cannot open the state either. It may handle the push outside Switzerland and the EU, including in the USA. Cloudflare, which runs our server, and Apple can see the token, the key's id, when each push went, its kind and its size. So they can tell when the game offered you a pump, when each of its moves started and ended, and when your phone stopped following. They can read nothing else of the pump: no move, no name, no count, no goal and no record. The alert says the same words for every pump. Tap Stop, switch off sync or unpair your computer, and the app takes its token back from our server. Our server also deletes the token when your computer goes quiet: after 30 minutes if it has sent no word yet, else after 10 minutes without one. It deletes it 8 hours after the phone asked at the latest. The token also goes when Apple says it is no longer in use, when the phone leaves the account or when the account is deleted. Then our server sends one last push that takes the pump off that phone's Lock Screen. The Android app needs no push: it follows the game on your home network.

You can also link your email, to get back in with it. Our server does not keep your address. It keeps only a code made from it with a secret key (a keyed hash), so it can find your account when you sign in with it. When you ask for a code, our server hands your address and the code to Cloudflare's email service, which sends the mail. The code works for 10 minutes. Cloudflare keeps a record of each mail it sends: the address, the sender and the subject line, which holds the code. It deletes that record after 31 days. If a mail to your address bounces or is marked as spam, Cloudflare puts the address on a list, so that no more mail goes there, until we take it off. Our server uses your IP address only as a hash, to limit how often one network may ask for codes. It keeps that hash with a code for 10 minutes, with each ask for an hour, and in the day's count of codes until the day ends (midnight UTC). To stop guessing, it counts the wrong codes typed for your address, for each network or account that typed them and for all together. It keeps each count, with the network's hash, for up to 2 days after the last wrong code.

Cloudflare, Inc. runs the server and sends the mail for Pluxia GmbH, as our processor. It keeps the synced data in the EU. The server's code and the mail run on Cloudflare's network, which may handle them outside Switzerland and the EU, including in the USA (see This website).

We keep an account while its devices use it. A device that has not synced for 24 months is taken off the list by itself. Once no device is left that way, the account is deleted. When the last device of an account signs out, the account is deleted, unless it has a linked email. Then it waits 24 months for a device to sign in. To delete it yourself, open the Menu in the app or in QuestPump on your computer or in your browser, then Email, then Delete account. You can also do it at questpump.com/delete, with your linked email or your restore code. This deletes the sealed parts, the device list and the email's hash at once. The limits above keep their hashes and counts until their time is up, at most 2 days. Cloudflare's backups of the server can hold them for up to 30 days more. Each device keeps its own progress.

We sync on the basis of our legitimate interest in keeping your progress the same on all your devices. You can object to it at any time by switching sync off (see Your right to object). We send the silent push on the same basis, so that a reminder knows what your other devices did. We send the game's pumps to your Lock Screen on the basis of our contract with you, because you ask for it when you follow the game. We link your email and send you codes on the basis of our contract with you, because you ask us to. We use your IP address for the limits on the basis of our legitimate interest in a sync that stays up and safe from misuse.

QuestPump in your browser

At play.questpump.com, QuestPump runs in your browser. What you do there stays in your browser: your pumps, counts and times, your setup, the pain you report and the times you felt unwell. The browser keeps them in its own storage for play.questpump.com, a site of its own where no other code runs, with the films and voice clips of the moves it downloads, so that pumps also work offline. It sets no cookie for this. Nothing leaves your browser until you press Save your progress, or sign in with a link code, your email or your restore code.

If you allow it when your browser asks as you start work mode, your browser tells QuestPump whether you are using the computer, never what you do, so work mode counts only the time you are at it. This stays in your browser too.

Once you save or sign in, your browser syncs as the apps do (see Sync between your devices). The pain you report and the times you felt unwell still stay in this browser alone. To save, you give your email and type the code we send you. Then the page shows your restore code, which the Menu also shows later, and your browser may offer to keep it in its password manager. Save also asks your browser to keep QuestPump's storage.

Browsers can delete what a site keeps. Safari deletes it after seven days in which you use Safari but do not open play.questpump.com. Other browsers may delete it when the disk is full, or when you clear your history. Progress you saved stays on our server and comes back when you sign in again.

QuestPump in your browser sends us no usage statistics and no crash reports.

To delete it, open the Menu and choose Delete progress in this browser. Once you saved your progress, open Email in the Menu and choose Sign out: it first sends what waits, then this browser forgets it, and it stays in your account. If some of it could not be sent, the page asks you first. You can also clear the data of play.questpump.com in your browser's settings. Your browser keeps all this only because QuestPump needs it to run the pumps you ask for, so it asks for no consent.

Games you link

In the phone app you can link Lichess and Steam, and Chess.com and Twitch once the app offers them, under Linked games in the Menu. When a game or a stream there ends, the app offers you a pump. Your phone asks each service itself. None of it goes through Pluxia GmbH, and we never see what the services send back.

  • Lichess: you sign in on Lichess's own page. The app reads your name and your last five finished games, and when each one ended.
  • Chess.com: you type your username, and there is no sign-in. The app reads that player's public profile when you link, and that player's games of this month, which Chess.com shows to anyone, and when each one ended. At the start of a month it also reads the month before. If this month's games cannot be found, it reads the profile again to see whether the player is still there.
  • Twitch: you sign in on Twitch's own page with a code the app shows. The app reads your name, whether you are live, and when your last stream ended.
  • Steam: you type your own Steam Web API key and your Steam profile. The app reads your profile name, whether your profile is public, and the game you are in. Steam shows that game only while your game details are public.

Each service sees your phone's IP address and the time of each request, under its own privacy policy. Your sign-in, key or username stays on your phone, in its secure storage. It never goes into QuestPump's backup file or the sync. On an iPhone it is kept for this iPhone only. It never moves to another phone, and a backup of the phone brings it back only onto the same iPhone. On an Android phone it goes into no backup. Unlink in the app, and the app forgets it. For Lichess and Twitch, the app also asks the service to end the sign-in. A Steam key you end yourself, on Steam's page for your key. On an iPhone, the secure storage can keep a sign-in after you delete the app. A new install of QuestPump then clears it when it first starts.

Games on your phone

The phone app can offer you a pump when you stop playing a game on your phone. It then asks one thing: how many matches you played. It stays off until you set it up, under Games on this phone in the app's Menu. QuestPump uses what it learns here only to ask you after you play and to let your games wait for Pump first (see Pump first).

  • On Android, you turn it on on its page and turn on usage access for QuestPump in your phone's settings. Usage access you gave only for Pump first does not turn it on. From Android 15, the app asks Android only when apps come to the front and go away and when the screen turns off; on older Android, Android hands it all of the phone's usage events of that time. Either way the app keeps only what concerns the games on its list and the apps that wait for Pump first, and drops the rest at once. Its list holds the apps Android marks as games, which you can untick, and the apps you add. To find them, and to let you add others, it reads the names and categories of the apps you can open from your phone's app list. It reads that list only once usage access is on, or while Games on this phone or Pump first is open in the app. It keeps none of that list, only the games you untick and the apps you add. It sees nothing inside an app.
  • On an iPhone, the app sees nothing of other apps by itself. You make two automations in Apple's Shortcuts app. They tell QuestPump when a game you picked there opens and when it closes, and they may name the game.

The app keeps on your phone when a game opened and left until that play is over and its question asked or dropped, your shortest play that gets a question and, for each game, your last five answers, to guess your matches next time. On an iPhone it also keeps when the automations last ran, to show you that they work. It keeps the answers until you uninstall the app. These are not part of your pumps, so they go into neither the backup file nor the sync. On Android they stay out of your phone's own backup too. On an iPhone they are in your phone's own backup to iCloud or your computer, as the app's settings are.

The question may show on your watch too, with the game's name and the minutes you played. When you start a pump from it, the pump holds the game's name, the minutes you played and the matches you said, in your pumps (see Your pumps on your phone), for as long as you keep your pumps. The game's name never goes to QuestPump on your computer, the game, Apple Health, Health Connect or the coach. QuestPump on your computer, if you paired it, learns only when your phone last asked, so that your devices keep an hour between offers. Pluxia GmbH receives none of it. While usage statistics are on, Google Analytics learns when you open Games on this phone, when the phone offered a pump after a game and whether you opened the offer or put it away. Our daily counts say on which days you opened one. Neither says which game, how long you played or how many matches (see Usage statistics).

To stop, untick the games, or turn off usage access for QuestPump in your phone's settings. On an iPhone, turn off or delete the two automations in the Shortcuts app. Uninstalling the app deletes what it keeps for this. The game's name, minutes and matches on your past pumps go when those pumps do (see Your rights).

Pump first

With Pump first, the apps you pick wait each day until your first pump. It stays off until you turn it on, under Pump first in the app's Menu. QuestPump uses what it learns here only to decide whether an app waits.

  • On Android, it uses usage access too, to see when an app you picked comes to the front, and with "Games wait too" the games on your list. When you first turn it on, the big social and video apps on your phone are picked for you, and you can untick each one. It uses "Display over other apps" to show its own screen over that app. It runs only while you allow both, and its notice shows on your phone the whole time it runs. It looks about once a second while your screen is on and an app waits. Once nothing waits (after today's pump, in your quiet hours), it looks only at the games on your list, and only if they ask each time they open. Every 30 seconds while your screen is on, it also notes when the games on your list open and close. The list of apps you picked stays on your phone and out of its backup.
  • On an iPhone, you pick the apps in Apple's own Screen Time list. Your iPhone first asks you if QuestPump may use Screen Time. Screen Time then shows QuestPump's own screen over those apps while they wait. QuestPump never learns which apps you picked. It keeps Screen Time's coded list of them on your phone, with the times when they wait. If you say no to Screen Time, you can make an automation in the Shortcuts app with the apps that should wait. When one of them opens, the automation asks QuestPump if it should wait. QuestPump does not learn which app it was. With "Games wait too", the automations of Games on this phone ask it too, and they may name the game.

To see if today's pump is done, Pump first reads the pumps your phone already keeps, from the phone, the watch, the computer and the game. Before its own screen shows, and when you tap Pump now on Screen Time's screen, it asks QuestPump on your computer, if you paired it, for its latest pumps. That request names no app. It keeps on your phone its switches, when an app may open for 15 minutes, and the last game whose screen you left without an answer. On an iPhone these are in your phone's own backup, as the app's settings are. "I feel unwell" on its screen is kept like the other times you felt unwell (see Your pumps on your phone). None of this reaches Pluxia GmbH. While usage statistics are on, Google Analytics learns each time you open Pump first's page, and whether you saw or took its card in the app. Our daily counts say on which days you answered its screen. Taps on Screen Time's screen are not counted at all. Neither says which apps you picked or which app opened (see Usage statistics).

To stop, turn Pump first off in the app. On Android you can also turn off usage access and "Display over other apps" for QuestPump in your phone's settings. On an iPhone you can also turn off Screen Time access for QuestPump in your iPhone's settings, and turn off or delete the automation if you made one. Uninstalling the app deletes what Pump first keeps.

Work mode on your phone

Work mode asks for a pump after each stretch of time you spend at work. It stays off until you press Start, and it stops when you press Stop. While it is on, the phone app reads a few things, only to know when to ask and when to wait.

  • On Android, if your account has QuestPump on your computer, it uses usage access to count the minutes you spend in your work apps, the same apps as Pump first. It shows its ask over the app you are in, with "Display over other apps". Without a computer it counts plain time, and it reads your steps from Health Connect, if you allowed that, to start the count over after a walk. To wait during a call, it checks whether a call is on, whether an app uses the microphone or the camera, and whether you cast your screen. It never hears or sees what the microphone or the camera picks up.
  • On an iPhone, if your account has QuestPump on your computer, you can pick your work apps in Apple's own Screen Time list. Screen Time counts your minutes in them and tells QuestPump when it is time, and QuestPump then shows its own screen over those apps. QuestPump never learns which apps you picked. Without a computer it counts plain time, and it reads your steps from Motion to start the count over after a walk. To wait during a call, it checks whether a phone call is on.

All of this stays on your phone. Only work mode's switch, its choices and its clock go to your other devices (see Sync between your devices). While usage statistics are on, Google Analytics learns when you open Work mode's page, and our daily counts say on which days work mode was on. Neither says which apps you use or for how long (see Usage statistics).

To stop, press Stop. You can also turn off usage access and "Display over other apps" for QuestPump on Android, or Screen Time access for QuestPump in your iPhone's settings. Uninstalling the app deletes what work mode keeps.

The coach in the phone apps

The coach is part of QuestPump Pro, in the iPhone app and the Android app; without Pro you can try its first talks and its first weekly story. Only if you allow it, the app writes a short talk after a set that matters and, once a week, a short story of your week with Google Gemini, an AI service of Google, which processes it for Pluxia GmbH under the Google Cloud terms in the EU. For a talk your phone sends Google the move you just did, the count you typed, what the set asked, your record and how many days it stood, your family's colour and step and what the next step asks, your streak, how many days you were away after a long break and whether a pump paid a weekly goal. For the weekly story it sends your week's counts (pumps, moves, records, days, steps reached), the families you trained, what you finished before your pumps (such as a match) and the moves with the most records. Both carry the tone you picked, a few facts the coach remembers on your phone (such as how long ago your first record came and your best streak) and its last lines, so it does not repeat itself. That memory stays on your phone: it is not in a backup or a sync. The app never sends your name, an account, quest names or any health data, such as your heart rate, pain settings or a felt-unwell stop. You can turn the coach off at any time in the app.

We use the coach only with your consent, which you give when you allow it and can take back at any time by turning the coach off. Your phone keeps when you answered and which words it showed you. Google keeps nothing of a talk or a story once it has answered: we turned off its cache for QuestPump. If Google's safety checks flag a request, Google may keep it for up to 90 days to look for misuse. Only Google staff who are allowed to may look at it, and Google never uses it to train its models.

While the coach is on, the app uses three Firebase services by Google: App Check, Remote Config and Installations. They prove that a request comes from the genuine app and read the coach's settings. While Firebase runs, the app also uses App Check when you report a talk or a story, when you send feedback and when it syncs. On the iPhone, Firebase runs only while the coach, crash reports or usage statistics are on (see Crash reports and Usage statistics below). With all three off, the iPhone app starts none of Google's Firebase services. On Android, Firebase loads when the app starts. With all three off, the Android app sends Google no crash reports and no usage statistics. It still uses App Check when you send feedback and when it syncs. App Check receives an attestation of the app, from Apple's App Attest on the iPhone or from Google Play Integrity on Android. Google does not keep it. Remote Config and Installations receive a random installation identifier, the app's id and version, and your phone's country, language, time zone and system version. They do not receive your identity. Google keeps the installation identifier until we ask for its deletion. These Firebase services run on Google's servers around the world. They may process this data in any country where Google has data centres, including the USA. Google LLC is certified under the Swiss–US and EU–US Data Privacy Frameworks. Google's data processing terms for Firebase and Google Cloud add the standard contractual clauses. See Firebase's privacy and security page.

If you report a coach talk or story, the app sends its words, whether it was a talk or a story, the reason you chose and the name of the AI model to questpump.com. It mails them to us and keeps nothing. It uses your IP address only to let one report a minute through, and forgets it after that minute. We use these mails only to improve the coach. We do so on the basis of our legitimate interest in a coach that stays safe and useful. We delete each one 12 months after it arrives.

Feedback

You can send us feedback from the game, from QuestPump on your computer or from the phone app. Nothing goes until you press Send. A message holds the text you type, where you sent it from (the game, the iPhone app, the Android app or QuestPump on your computer), the version of that part and the time you pressed Send.

Each new message starts with the tick "Add my numbers" on. Turn it off, and only your text, where you sent it from, the version and the time go. With it on, a message from the game or the phone app also holds these counts, which the window shows in full before you send:

  • the days since you started QuestPump;
  • your pumps finished and banked in the last 14 days, and the moves still unfinished;
  • how many max sets you did on a ladder on a usual day you played in the last 14 days;
  • for each move, how often in the last 14 days you took it as the easier version of a harder move, or stopped it early.

In QuestPump on your computer the tick is "Add my system details". It adds your computer's system (such as macOS 27.0) and whether QuestPump can see the game, not the counts. A message never holds your name, your character or realm, the counts you type in a pump or an id of your phone or computer. It never holds your heart rate, the pain you report, your answers to "Muscles today?" or the times you felt unwell.

We read every message, but we cannot write back: it has no name or address. If you want an answer, write to contact@questpump.com.

The game cannot reach the internet, so it hands your message to QuestPump on your computer, which sends it. QuestPump on your computer and the phone app send it to questpump.com, which runs on Cloudflare (see This website). Our code there mails your message to us and keeps nothing. It uses your IP address only to let one message a minute through, and forgets it after that minute. We use these mails only to improve QuestPump and to check that its rules stay safe. We do so on the basis of our legitimate interest in a game that is safe and fun. We delete each one 12 months after it arrives.

Crash reports

When the phone app crashes, it sends us a crash report by itself the next time it starts. In the EU, the EEA, India and Canada, it asks you first. Google Firebase Crashlytics carries the report to us. A report holds what the app was doing when it crashed: the steps of its code and the error. It says which part of the app was open, whether a pump was running and whether your computer and watch were linked, each in a word from a fixed list. It also holds the app's version, your phone's model, its system version and language, its free memory and which way up it was. It names any test version of the app's settings in use, and holds two random ids of this install of the app. While usage statistics are on (see below), it also holds the app's last usage events before the crash, from the same fixed list as Google Analytics. It never holds your pumps, your counts, your health data, your name or the pairing key. The phone app also sends a report when the system stopped it because it froze or used too much memory. The watch apps send us no crash reports. Apple and Google may also pass on to us the crash reports that their own systems collect from the phone and watch apps, if you chose to share such data with app developers in your device's settings.

QuestPump on your computer does the same with its own crashes. It writes a report when it crashes, or reads the one that macOS or Windows wrote about it. Its report holds when the app crashed, what it was doing and the error, the app's version, and your system with its version, such as macOS 27.0, arm64. The app builds the report to leave out your name, your computer's name and anything from your game. It also takes the name of your home folder out of it. At its next start it sends the report to questpump.com, which runs on Cloudflare (see This website). Our code there mails the report to us and keeps nothing. It uses your IP address only to let one report a minute through, and forgets it after that minute.

You switch crash reports off in the Menu, with "Send crash reports" in the phone app and in QuestPump on your computer. Then nothing about a crash leaves your device, and reports that wait are deleted. Where the app asks first, the switch stays off until you say yes. After a crash the app asks you: Send, Always send or Don't send. On the computer you can read the whole report first. Always send turns the switch on. The app guesses where you are from your device's region and time zone. It does this on your device and never asks a server.

Google LLC runs Crashlytics for Pluxia GmbH, as our processor, under the Firebase terms. It may process the reports in any country where Google has data centres, including the USA, and is certified under the Swiss–US and EU–US Data Privacy Frameworks. Google starts deleting each report after 90 days. We delete each report from QuestPump on your computer 90 days after it arrives. We use crash reports only to find and fix crashes. Outside the EU, the EEA, India and Canada, we do so on the basis of our legitimate interest in fixing crashes. You can object at any time with the switch. Inside them, we do so on the basis of your consent, which you can take back at any time with the switch.

Usage statistics

The phone app and QuestPump on your computer have a second switch in their Menu: "Usage statistics". While it is on, they tell us how QuestPump is used. This shows us what works and what to fix. The add-on itself sends nothing, and neither do the watch apps. The phone counts what you do on the watch.

In the EU, the EEA, India and Canada, both switches stay off until you turn them on. When you first use the app, a window shows them both, off, and asks you. One tap on "Accept all" says yes to both, and one tap on "Reject all" says no to both. If you set them one by one, "Save choices" keeps them as you set them. Elsewhere, they start on, and the same window lets you turn them off. Until you answer, the window comes back each time the app starts. You can change either switch at any time in the Menu. The app guesses where you are from your device's region and time zone, on your device. It does not keep the guess, so it guesses again if you move, until you answer. It keeps your answer on your device, with the time you gave it and the version of these words you saw.

On your phone, the app then uses Google Analytics for Firebase. It tells Google which features you use, from a fixed list: for example, that you opened the Book, linked a game, turned a reminder on or looked at Pro, that the phone offered a pump after a game, or that you saw the card about Pump first. It names the screens you open, also from a fixed list, and a few facts about your setup, such as whether you paired a watch and whether you have Pro. Google also learns when you open the app and how long you use it, the app's version, your phone's model, its system and language, and a random id of this install of the app. Google finds your country and city from your IP address and does not store the address. In the EU, the EEA, the UK, Switzerland, India and Canada, we have it keep only the country, and not your phone's model or brand. Google keeps this data for 14 months.

Google never gets your pumps, your counts, your records, the moves you do, your health data, your name, your character or anything you type. The app uses no advertising id. We turned off Google's ad features and its data sharing for QuestPump.

Both apps also send us counts once a day, to questpump.com, which runs on Cloudflare (see This website). A count holds no id, no name and nothing you type. It names the app, its version and the day, but never the time of day. Our code there holds each day's counts and stores them all together once a day, mixed up, so not even the moment they arrived is kept. Only the count of a new install holds your country, which Cloudflare reads from your IP address. The counts say:

  • that the app was installed, and on each day it was used, the week you started and about how long ago that was;
  • each day, whether you have Pro and whether the app crashed the time before;
  • which features you used that day, from a fixed list, such as answering Pump first's screen;
  • whether a pairing worked and whether the link to your computer held, and on the computer whether it is a Mac or a Windows PC and whether it could see the game;
  • on the computer, after which game it offered a pump, and whether you took it;
  • that you came back after three days or more away;
  • about how long after you started your first pump came;
  • each day, how many pumps were finished or banked, and how many moves were skipped or still unfinished;
  • each day, for each move, how often you took an easier move in its place or stopped it early;
  • each week, about how many of your pumps you finished in the last 14 days, and how many max sets you did on one ladder on a usual day;
  • each week, your setup in rough groups: your pace and focus, whether floor moves, room to move and quiet mode are on, and how many pieces of equipment you have;
  • each day, your best streak in rough groups and the highest colour you reached. A phone sends it, or the computer when no phone is paired, so each player counts once.

QuestPump on your computer counts the pumps you do on the computer and in the game. The phone app counts the pumps you do on the phone and the watch. The phone app sends the counts of your pumps, your moves and your setup only if you said yes to usage statistics yourself. Our code at Cloudflare stores the counts and keeps no IP address. Cloudflare deletes them after 3 months. We never report a group of fewer than 5 counts.

We use usage statistics only to make QuestPump better: to see which features help, where people get stuck and what breaks. From the best streaks and the highest colours, questpump.com works out how many players reached each streak and each colour, which a share card can show, such as "Only 4% of QuestPump players have kept a streak of 30 days". It shows a share across everyone, never anyone's own, and only once 200 counts stand behind it. In the EU, the EEA, India and Canada, we do so on the basis of your consent, which you can take back at any time with the switch. Elsewhere, we do so on the basis of our legitimate interest in making QuestPump better. You can object at any time with the switch. The counts of your pumps from the phone app always need your own yes.

Google LLC runs Google Analytics for Pluxia GmbH, as our processor, under its terms for Firebase and Google Analytics. It may process the data in any country where Google has data centres, including the USA, and is certified under the Swiss–US and EU–US Data Privacy Frameworks. Cloudflare stores the counts for us, as our processor (see This website). Each of them must protect this data as well as this notice does. We never sell or share it, and we never use it for ads.

To stop, turn off "Usage statistics" in the Menu of the phone app or of QuestPump on your computer. The app stops at once. On your phone, Google Analytics stops, and the app deletes what Google Analytics keeps on your phone and starts a new random id. Counts that wait to be sent are deleted. What Google already holds is tied only to a random id, and our counts hold no id at all, so we cannot find yours. Google deletes its data within 14 months, and Cloudflare deletes the counts after 3 months. Every feature, Pro included, works the same with both switches off.

Purchases

You can get QuestPump Pro in the phone apps or on questpump.com/pro. In the phone apps, Pro and the tips are in-app purchases, handled by Apple in the App Store and by Google in Google Play under their own terms and privacy policies. A tip unlocks nothing. The app asks Apple or Google on your phone whether you hold Pro. Pluxia GmbH never receives your payment details. On Android, Google's purchase code in the app also sends Google its own notes on how its calls went, each time the app starts: the app's version, your phone's model and system, your country and network type, and no id of you. The app cannot turn this off.

With Pro on a phone paired with QuestPump on your computer, Pro's extras show on the computer too: Pro's weeks in the Saga, the charts and the share-card styles. For that, the phone hands the computer the record of your subscription that Apple or Google signed: its ids, the product and its dates, never your name or payment details. QuestPump on your computer checks the record itself, offline, keeps it in its own folder so that Pro stays on there, and sends it nowhere. It deletes the record when you make a new pairing code, and the phone tells it when Pro has ended.

With sync on, the phone app also sends our server that record, so that Pro shows on all your devices. Our server checks it and keeps, for your account: until when Pro runs, where it came from (the App Store, Google Play or questpump.com), its state (such as running, in its free start, a payment that failed, paused, ended or paid back) and a code made from the subscription's id, which cannot be turned back into the id (a hash). It keeps nothing else of the record. Each of your devices then gets a note signed by our server that says until when Pro runs, and keeps it so that Pro shows there. Each hour our server also asks Google which Google Play purchases were paid back, so that Pro ends on all your devices when Google ends yours.

On questpump.com, Paddle sells Pro for us. Paddle.com Market Limited (United Kingdom) is the seller: it takes your payment and your email, and your address or country for the tax, under Paddle's privacy notice. Pluxia GmbH never sees your card or bank details. To show the prices and the checkout, questpump.com/pro loads Paddle's script from Paddle, and the checkout opens in a frame from Paddle. Paddle then sees your IP address and your browser's identification. When you buy, renew, cancel or get a refund, Paddle tells our server the plan, its state, its dates and Paddle's ids for the subscription and for you as its customer. Our server keeps those two ids as they are, so that it can open Paddle's page for your plan when you press Manage Pro, and a hash of the subscription's id. It also gets from Paddle the email you paid with, and keeps only a code made from it with a secret key, as for a linked email (see Sync between your devices). Pro goes to the account that links that email: at once if one already has, or when a device of yours links it.

We do this on the basis of our contract with you, to give you the Pro you paid for. We keep Pro's state with your account and delete it with the account. Deleting your account does not end a subscription. End it first: in the App Store, in Google Play, or for Pro from questpump.com in the Menu of QuestPump on your computer, under Pro, then Manage Pro, or with the link in Paddle's email.

This website

This website is hosted by Cloudflare, Inc. (USA). To deliver and protect the site, Cloudflare processes technical data of every request, such as your IP address, the time, the page requested and your browser's identification, and keeps it in its logs. Cloudflare does this for Pluxia GmbH, as our processor, on the basis of our legitimate interest in a website that loads and stays safe. The website sets no cookies and uses no analytics. It loads nothing from third parties, but for Paddle's checkout on questpump.com/pro (see Purchases). It only counts clicks on its own download and post links (see Download and link counts). Cloudflare may process this data outside Switzerland, including in the USA; it is certified under the Swiss–US and EU–US Data Privacy Frameworks and otherwise relies on standard contractual clauses. See Cloudflare's privacy policy.

Download and link counts

The report Worker on questpump.com counts clicks on our own download and post links (/get/... and /from/...). For each click it keeps which link it was, when, the page of this website it was on, your country and the site you came from (only its name, such as reddit.com). It keeps no IP address and no identifier, sets no cookie and stores nothing on your device. One link sends each phone to its own store: for it, the Worker reads what kind of phone you use, and keeps none of that.

Cloudflare runs the Worker for Pluxia GmbH, as our processor, and deletes the counts after 3 months. We use the counts to see which downloads and posts work. We do so on the basis of our legitimate interest in knowing which downloads and posts work.

Story quests

On questpump.com/on-its-own you can leave your email address to hear when Story quests open. The page sends your address to questpump.com, which runs on Cloudflare (see This website). Our code there mails it to our mailbox with the time you sent it and keeps nothing itself. It uses your IP address only to let one sign-up a minute through, and forgets it after that minute. We keep your address and that time in our mailbox only to write you one email when Story quests open, on the basis of your consent, which you give by sending the form and can take back at any time. We send no other email, not even to confirm. We delete your address after that one email, or sooner if you ask (see below).

Email

Messages to contact@questpump.com are forwarded by Cloudflare Email Routing to our mailbox. We use them only to answer you and keep them as long as that and the law require.

Your rights

You can ask what data about you we hold, have it corrected or deleted, and have its use limited. You can ask for the data you gave us in a common file that a computer can read, for yourself or for another service. Write to contact@questpump.com. You can also complain to the Swiss Federal Data Protection and Information Commissioner, in the EU to your national data protection authority, or in the UK to the Information Commissioner's Office.

Your right to object

Where we rely on our legitimate interest, you can object at any time, for reasons that come from your own situation. For the sync and the usage statistics, a switch in the app's Menu does it at once: Backup and sync, and Usage statistics. For anything else, write to contact@questpump.com.

To have your data deleted, write to contact@questpump.com and say that it is about QuestPump. For a coach report, name the talk or story or the day you sent it; for feedback, the day you sent it and what you wrote; for a crash report from your computer, the day it crashed; for the waitlist, the address you gave. We delete your messages, reports, feedback and waitlist address within a month. The Firebase installation identifier is linked to nothing that names you, so we cannot find yours, or your phone's crash reports, from a message. The same goes for the usage statistics: Google's are tied only to a random id, and our counts hold none (see Usage statistics). Uninstalling the app removes these ids from your phone. You delete what QuestPump keeps on your own devices yourself: uninstall the phone app, remove QuestPump from your computer with its folder, or remove the add-on and its saved-variables file. In your browser, open QuestPump's Menu and choose Delete progress in this browser, or Email and then Sign out once you saved (see QuestPump in your browser). To delete the synced copy on our server, open the Menu in the app or in QuestPump on your computer or in your browser, then Email, then Delete account, or go to questpump.com/delete with your linked email or your restore code (see Sync between your devices). Your devices then stop syncing and keep their own progress. Deleting the account does not end Pro's subscription (see Purchases). The server holds nothing that names you, so we cannot find an account from a message: the Menu, or that page with your email or your restore code, is the way to delete it. If a mail to you bounced, write to us, and we take your address off Cloudflare's list of addresses that get no more mail.