Effective date: November 17, 2026
Triggerwave ("we", "us", "our") operates the mobile game Quarterback Clash, also called QB Clash (the "Game"), on iPhone, iPad and Android. This page describes what data is collected when you use the Game, why, who it is shared with, and the choices you have.
The Game never asks for your email address, phone number, contacts or location, and it has no ads. On Android it measures our own ads (section 1), and it doesn't track you in any other way. It doesn't need a login: the first time you play, it creates an anonymous player ID for your installation (with Firebase Authentication's anonymous sign-in: no email, password or other account). If you choose, you can save your progress with an account you already have, as described below.
To run the Game, our server stores:
To see how the Game is played, so we can fix problems and improve it, the Game also sends the following to Google Analytics for Firebase and Firebase Crashlytics. In the EEA, the UK and Switzerland, and wherever the Game can't tell your country, it sends nothing until you say yes when it asks:
Tutorial recordings (while analytics is on). When you play the tutorial, a recording of each of its throws (where you aimed and when you let go, the play and what happened) is uploaded to our server with your player ID, so we can see where new players have trouble and make the tutorial better. It's never shown to other players.
Measuring our ads (Android only, outside the EEA, the UK and Switzerland, while analytics is on). We advertise the Game with Google Ads. If you installed the Game from one of our ads, Google Play gives the Game that ad's click ID (through Google Play's Install Referrer), and Google Analytics tells Google Ads whether that install went on to open the Game, finish the training and play five duels. That lets us see which of our ads bring players who keep playing, and lets Google show our ads to people likely to enjoy the Game. It sends nothing more than the analytics above: never your name, your player ID or your device's advertising identifier. Ad personalization is switched off, so Google doesn't use it to choose ads to show you, and we don't receive anything that identifies you. Where the Game asks about analytics, and on iPhone and iPad, it doesn't do this.
You can turn analytics off, or on again, at any time in the Game's settings. While it's off, the Game sends nothing to Google Analytics, Google Ads or Crashlytics, and no tutorial recordings to our server, and turning it off resets the Game's analytics identifier.
To run the Game: to save your game and bring it back with the accounts you choose, find you rivals and run duels, deliver what you buy, check names and photos before other players see them (section 4), and look into the reports and feedback you send. And, through the analytics and crash reports in section 1, to understand how the Game is played so we can fix problems and improve it. We use it for advertising only to measure our own ads on Android, as section 1 describes. We don't build advertising profiles, nobody is shown ads because of it, and we don't sell it.
When you duel, your rival sees your name and your photo (if you chose them), your team with its colours and kit, your quarterback with your name on his shirt, your trophies and league, and your recorded plays as they play against them. A recording can be played against by many players, for as long as it's used for duels. You don't have to use your real name or a photo of yourself, and please don't put other personal details in either.
Names are checked before other players see them: by a word filter in the Game and on our server, and then by OpenAI, a service provider, which reads the name and tells us whether it breaks our community rules. We send OpenAI only the name and a scrambled (hashed) form of your player ID, never anything else about you. OpenAI keeps what it is sent for up to 30 days to watch for abuse of its service, and under its terms for businesses doesn't use it to train its models. A name that doesn't pass is never shown, and the Game says it isn't available. If a name is reported, we may check it again, and a name that breaks the rules is taken away and your team's name shown instead.
Photos are checked the same way before other players see them: OpenAI looks at the picture and tells us whether it breaks our community rules (for example nudity, violence, hate symbols, rude gestures, drugs, or words in the picture that break the rules). We send OpenAI only the picture and the hashed form of your player ID, and OpenAI keeps them as it does names. A photo that doesn't pass is never shown or kept. If a photo is reported, we may check it again, and a photo that breaks the rules is taken off and can't be used again.
If you report a rival's name or photo, they aren't told who reported them. If you block a player, their player ID and name are kept with your game so that you're never matched with them again; they aren't told either.
The Game keeps your settings, a copy of your game and your last few plays on your device, so that it can start quickly and a play report can include them. If you've saved your progress with an account, it also keeps which accounts those are and the addresses of their pictures, to show them in the Game's settings.
We share data only with these service providers, which process it to run the Game, each under its own privacy policy:
We may also disclose information if the law requires it, or to protect the rights and safety of our players and ourselves.
In-app purchases are processed entirely by the App Store on iPhone and iPad, and by Google Play on Android, under their own terms and privacy policies. We receive confirmation of what was bought, with its transaction ID and date, never your payment information.
Apple may share anonymous crash reports and app analytics with us if you have chosen to share them with app developers in your device settings. If you test the Game through TestFlight, Apple may also share crash reports, usage information and any feedback you choose to send with us, as described in Apple's TestFlight terms. On Android, Google Play may share crash reports and performance statistics with us from devices whose owners have chosen to share usage and diagnostics with Google. We use this information only to fix problems and improve the Game.
The Game is intended for players aged 13 and over and is not directed at children. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has used the Game and you would like their information deleted, please contact us.
Deleting your account. In the Game, open Settings and choose Delete account, under Account. It deletes your game, your duel and tutorial recordings, your photo and your reports from our server straight away, with the sign-in behind your player ID and the accounts you saved your progress with, and the Game's copy on your device. If you saved your progress with Apple, the Game asks you to sign in with Apple once more, so that Apple stops sharing your Apple account with the Game. It can't be undone, and anything you bought goes with it.
If you no longer have the Game, email us at qbclashsupport@triggerwave.com with your player name and team so we can find it, and we'll delete the same. Deleting the app on its own doesn't delete them. What's kept after your account is deleted is in the list above: records of purchases, under an anonymous identifier, and the record of game events, for up to 14 months.
Depending on where you live (for example under the GDPR in the EEA and UK, or California law), you may have the right to access, correct or delete your information, and to object to or restrict its use. You can delete your account in the Game (section 11), or contact us to make a request, with your player name and team so we can find your data.
Where the GDPR applies, we process your game's data to provide the Game you chose to play; check names, look into reports and keep logs in our legitimate interest in keeping the Game safe, fair and working; and send analytics and crash reports only with your consent.
Data is sent over encrypted connections and stored with Google Cloud in the United States. Names and photos are checked by OpenAI, and analytics and crash reports are processed by Google, in the United States and other countries.
We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated effective date.
If you have questions about this Privacy Policy, or want to make a request about your data, contact us at: