Privacy Policy

Version 2026-10-22 · in effect from 22 October 2026

Introduction

This policy covers the MutRadar website and the MutRadar app. It explains what MutRadar collects, why, and what you can do about it. Cloud Native Solutions LLC is the controller of that data. Write to [email protected] about anything here.

What we collect

  • Your email address and password, so you can sign in. The password is stored only as a bcrypt hash and we cannot read it.
  • Your display name, gamertag and console, so your squad and the HUD reader know who you are.
  • Your team abbreviation, so we know which side of the scoreboard is yours.
  • Your country, so we know which privacy rules apply to you and what tax we owe.
  • Your consent record: which documents you agreed to, which version, and when.
  • Each sign-in to your account, and each failed attempt: the time, the IP address and the country it belongs to, and the kind of device and app or browser used, kept for 180 days (and deleted with your account) for your account's security, so that you, on your Profile, and our admins can spot someone else using it.
  • Optionally, your timezone, how you heard about us, and how competitively you play. All three are optional and none of them gate anything.
  • If you arrive through a tagged link (for example one in a MutRadar post) or from another website, we note that link's campaign tags and the website's name when you create your account, so we know which posts bring players.
  • How the website and the app are used: the pages you open, the features you use and the kind of device you use them on, through Google Analytics. The Analytics section says exactly what that covers and how to stop it.
  • If you turn notifications on in the app: a notification token for your phone, which OneSignal, the service that delivers them, holds for us so we can tell you when one of your squad's games ends. It is tied to your account's internal id, never your name or email, and it goes when you sign out or turn notifications off in your phone's settings.
  • Messages we send you in the app and on the website, about your account, your matches and the season; one comes to your phone as a notification, carried by OneSignal, only if you have allowed notifications.
  • Messages you send us from My messages, which are kept with your account and deleted with it.
  • Match data read off your stream: plays, formations, scores, downs, and the gamertags shown on the HUD.
  • Highlight clips: short, silent video clips (usually under 40 seconds) of your team's biggest plays — touchdowns, takeaways, sacks, long gains — cut from the broadcast you made public.
  • End-of-game evidence: a still of the final scoreboard of each game, and for a game that ends early or whose score is reported, the last 30 seconds of the broadcast's picture, with no sound. Only MutRadar's admins can see it.
  • Play-call stills: each time a play is called, one still image of your broadcast's picture at that moment, showing the play-call screen, with no sound and no video. One can show your gamertag, your opponent's gamertag and the plays both sides picked. We keep them to improve how MutRadar reads games.
  • Messages you post in chat — your squad's chat, and a chat between your squad and another squad — and the receipts you send there: your squad's rank, a match result, a highlight clip or a single play. They are kept with your account and deleted with it.
  • Your chat settings: which chats you have muted, how far you have read in each, and the players you have blocked.
  • Your past broadcasts, only if you turn on "Let MutRadar learn from my past Squads broadcasts": we fetch the Madden NFL 27 broadcasts you have saved on your Twitch channel, read them the way we read your live games, and keep the play-by-play (both teams' play calls, formations, downs, yards and results) and short, silent clips around each play. We use them only to improve how MutRadar reads games, including teaching it to recognise players and plays on the field. Nothing from them is shown to other players, and they never count on a leaderboard or a record.

What we do not collect

  • Your date of birth. We ask you to confirm you meet the age requirement and we store the answer, not the date.
  • Your legal name. Your display name is enough for everything the product does.
  • Card or bank details. Our payment processor handles those and we never see them.
  • A recording of your broadcast, or any audio. We read frames as they arrive and keep the numbers. The only pictures from your broadcast we keep are the ones this policy describes: the short, silent highlight clips, the end-of-game evidence and the play-call stills.

Analytics

We use Google Analytics on the website and in the app to see how many people visit, which pages and features get used, where visitors come from and whether things work. Google runs it for us under its data processing terms; Google's own policy on data from sites that use its services covers Google's end of it.

It records the page or screen you open and the one you came from, including the campaign tags on a link you followed; the feature you use, as a plain name and category (that a clip was shared, say, and by which method) and never anything you typed; the kind of device, browser, screen size and language; and a rough location, usually the country and sometimes the region or city, worked out from your IP address, which Google uses for that and does not store.

If you are signed in to the app, those records carry your account's internal id: a random identifier, never your email address, name or gamertag. It lets us see one person's sessions across their devices, it is shared with nobody, and once your account is deleted it points to no one. A page that is only ever reached by a share link is reported as a shared page, not as the link itself.

Google sets its own first-party cookies on your device (named _ga, and _ga_ followed by an id), which last up to two years and tell a returning visitor from a new one. If you are in the EEA, the UK or Switzerland it sets none: visits from there are counted without any cookie or device identifier, as rough aggregate figures. We have switched Google's advertising features off everywhere: nothing here is used to advertise to you, and the data is not joined to a Google account or an ad profile.

Separately, our host, Cloudflare, counts visits to the website from its own network, with no cookies and nothing kept about you beyond the page, where you came from and the type of browser.

To stop analytics, use a content blocker or Google's own opt-out add-on for your browser. The website and the app work exactly the same without it.

Why we are allowed to hold it

Account and match data: because we need it to give you the service you asked for. Consent records and the age confirmation: because the law requires us to keep them. Marketing email: only if you tick the box, and only until you untick it. Analytics: our legitimate interest in knowing how the service is used and whether it works, kept to what the Analytics section describes, with the advertising side switched off and, in the EEA, the UK and Switzerland, without cookies. Play-call stills: our legitimate interest in making MutRadar read games correctly, kept to what the “What we read from your stream” section describes; you can object to it, as “Your rights” says. Learning from your past broadcasts: only if you turn it on, and only until you turn it off.

What we read from your stream

We sample frames from a broadcast you have already made public and read fixed regions of the Madden HUD: the scoreboard, the down and distance, the play-call panel and the gamertag plates.

We keep what those regions said, and we do not read anything outside them. To cut highlight clips we hold the last two minutes of the broadcast's picture in a rolling buffer that is constantly overwritten; when your team makes a big play we keep that play as a short clip and nothing else. We never keep the sound, so a clip carries no voices — yours, your squad's or anyone in your party chat.

At the end of each game we keep a still of the final scoreboard. When a game ends early — your stream drops, or the party is ended mid-game — or its score is reported, we also keep the last 30 seconds of the broadcast's picture before it ended, with no sound. Only MutRadar's admins can see either, and only to settle a disputed result or to keep the league fair; they are never shown to other players or shared. Both are deleted after 30 days. Because a score can be reported after a game ends normally, we hold the last 30 seconds of every game for 48 hours and delete them then if nothing has called for them.

Each time a play is called we also keep one still image of your broadcast's picture at that moment, showing the play-call screen: a single picture, with no sound and no video. It can show your gamertag, your opponent's gamertag and the plays both sides picked. We keep these stills only to improve how MutRadar reads games, by checking and training the part of MutRadar that reads the screen. They are stored on MutRadar's own equipment, not with a cloud provider; only MutRadar staff can see them; they are never shown to other players, published or shared; and they are kept for up to 24 months, then deleted.

Other people in your game

Your opponents' gamertags appear on the HUD and are read along with everything else, so that a match record can say who you played. Those gamertags are used to label your matches and nothing more. We do not create accounts for them, build profiles on them, or sell anything about them, and their names are deleted when the match data they belong to is deleted.

Highlight clips show the game as it was broadcast, so an opponent's gamertag can appear in one. If you are that opponent and want a clip removed, write to [email protected] and we will delete it.

When a squad shows the MutRadar panel on its stream or goes live on MutRadar's channels, its opponent's team abbreviation, score and play calls appear on the panel, with how that opponent has played each situation in the game, and the gamertags on the opponent's side of the screen appear as the game was broadcast. If you are that opponent and want a recording or a replay on MutRadar's channels taken down, write to [email protected].

Clips from past broadcasts that a player let us learn from can show their opponents' gamertags, as the broadcast did. They are used only to teach MutRadar to read games and are seen only by MutRadar staff. If you are that opponent and want them removed, write to [email protected] and we will delete them.

Play-call stills can show an opponent's gamertag too. They are used only to improve how MutRadar reads games and are seen only by MutRadar staff. If you are that opponent and want a still removed, write to [email protected] and we will delete it.

If you are an opponent who wants your gamertag removed from someone else's match history, write to [email protected].

Who we share it with

Your squad sees your match data. That is the point of a squad.

Squads' names, tags, records and placings appear in the league standings, playoffs and tournament results. Anyone can turn those into a share card or link, which anyone with the link can open. Cards show squads, never members' names or email addresses.

Highlight clips are visible to your squad, and the biggest of them — touchdowns, takeaways and the like — are also posted to the MutRadar community Discord as they happen, each with a public link, unless your squad turns that off on the Squads page. Otherwise a clip becomes public only if someone in your squad creates a share link for it. Anyone with a public link can watch and download the clip, and turning the link off makes it stop working. A clip that has already been downloaded or reposted is out of our hands.

Beyond that, we share personal data only with the suppliers who run the service for us: our cloud host, our payment processor, our email provider, Google for the analytics described above, and OneSignal, which delivers the app's notifications: it holds your phone's notification token and the internal id it belongs to, and it carries the text of every notification we send you — that one of your squad's games has ended, and a message from us when we also send it to your phone. They act on our instructions and may not use it for anything else; what Google does with its share is set out in the Analytics section.

We do not sell personal data, and we do not share it with advertisers.

What you post in a chat is seen by everyone in it: your squad in your squad's chat, and the members of both squads in a chat between two squads. A receipt shows the other squad only what is on it — the score, the rank, the clip or the one play you chose to send — and never the rest of your match or your coach board. Anyone in a chat can screenshot or save what you post, and that copy is out of our hands.

A notification about a new chat message carries the sender's gamertag and the start of the message, through OneSignal, to the people in that chat who allow notifications and have not muted it.

In a squad challenge, the other squad sees your squad's name and tag, your gamertags, the score and result of the match, and your big-play clips from it, and never your coach board, your play calls or your tendencies. The record between two squads in their Official challenges (a rivalry, such as 4–1) can be seen by any signed-in player. A member of either squad can also make a share card of it, which anyone with the link can open: it shows the two squads' names and tags and their Official record, streak, points, biggest win and last meeting, and never friendlies or anyone's gamertag. A challenge invite link shows whoever has it your squad's name, tag and record, the message sent with it and the gamertag of the player who sent it.

Any member of a squad can turn on the squad's live panel on the Squads page: a private key and two links that put the MutRadar panel next to your game on a stream you run, in OBS or with irlstream. The panel shows your squad's name and tag, your gamertags, the score, the clock, both play calls of the last play and its yards, how your opponent has played the situation coming up, and replays of your biggest plays. It never shows your coach board, your own tendencies or your playbooks. Anyone with the key can open the panel, so keep it private; any member can make a new key or turn the panel off, and the old links stop working at once. When you paste the key into irlstream, irlstream opens the panel and its replays with it, under your own irlstream account.

With your squad's agreement, the MutRadar team can also put your squad on MutRadar's own channels (YouTube, Twitch, TikTok and Instagram): each member's public Twitch broadcast, with your gamertags, next to the MutRadar panel, whenever your squad plays. Every member sees on the Squads page that it is on, and any member can take the squad off at any time. To run those shows we use irlstream, which takes the broadcasts you have already made public on Twitch, puts them together with the panel and sends the result to MutRadar's channels; it receives your Twitch channel names, the link to the panel and, while a show runs, the short replay clips. Anyone watching MutRadar's channels, or a stream that shows the panel, can see and record what is shown there, and that copy is out of our hands.

Keeping chat safe

Every chat message goes through an automatic filter that hides slurs and abuse before anyone sees it. The words you actually typed are kept with the message, and only MutRadar's admins can see them.

If someone reports a message, our admins see it with the messages around it, and can open the chat it came from to judge it in context; every time they open one is recorded. They may hide or delete messages and stop an account posting in chat for a while. We do not read chats otherwise.

How long we keep it

Account and match data for as long as your account exists. Consent records for six years after your account closes, because that is the evidence that we were allowed to hold anything in the first place.

Highlight clips for 30 days, after which they are deleted automatically. Anyone in your squad can delete a clip sooner, and clips cut from your stream are deleted when you delete your account.

The links to a replay shown on the live panel stop working 24 hours after the play. Recordings that YouTube, Twitch, TikTok or Instagram keep of a show on MutRadar's channels are kept on those services under their own terms; we delete one from MutRadar's channels if anyone who played in it asks.

End-of-game evidence for 30 days, except the last 30 seconds of a game that ended normally and was not reported, which go after 48 hours. Evidence from your stream is deleted when you delete your account.

Learning data from your past broadcasts for up to 24 months from the day we read them. The video we fetch is deleted once it has been read; only the short clips around each play are kept. Turn the switch off, or delete your account, and we stop fetching and delete the clips we kept from your broadcasts; the play-by-play stays only with your name removed.

Play-call stills for up to 24 months from the day they were taken, after which they are deleted automatically. Stills from your stream are deleted when you delete your account, and a match's stills are deleted if that match is removed.

Analytics records, at Google, for no more than 14 months. The totals we draw from them are not about any one person and are kept.

When you delete your account, everything that identifies you goes: your profile, your streams, your memberships and your gamertag wherever it was read off a HUD. The matches themselves are kept without you attached to them, because they are your squadmates' record too.

A report you file is kept after your account closes, with your name unlinked from it. A resolved report is the reason a match was changed or removed, and a record of that change with no reason attached is worse than no record.

Chat messages for as long as the chat exists, and never past your account: when you delete it, everything you posted in chat, your blocks and your chat settings are deleted with it. A report about a chat message is kept after the accounts involved close, with their names unlinked and the closed account's words removed from it.

Security

  • Passwords are hashed with bcrypt and never stored in a readable form.
  • Traffic between you and us is encrypted in transit.
  • The database is not reachable from the public internet.
  • Access to production data is limited to the people who operate the service.
  • We do not write personal data into application logs.

Your rights

You can see and change your details in Settings, change your marketing choice at any time, export your data, and delete your account outright. Deletion removes your profile and your own record, and strips your name from the matches it appears in. It cannot be undone. You can stop analytics at any time with a content blocker or Google's opt-out add-on, with no effect on your account.

If you are in the UK or the EEA you also have the right to object to processing, to ask us to restrict it, and to complain to your data protection authority. In the UK that is the Information Commissioner's Office.

Children

MutRadar is not for children under 13. We do not knowingly collect anything from them. If you believe we have, write to [email protected] and we will delete it.

Changes to this policy

If we change this policy in a way that matters, we will show you the new version and ask you to accept it. The version and date at the top of this page tell you which one you are reading.

Contact

Privacy questions, and any request about your data, go to [email protected].