RivalsPulse

The short version

  • The RivalsPulse desktop app is not released yet. It is in development testing and is not on Overwolf. Where this page says what the app uploads, it describes how the app is designed to work at launch.
  • You never need an account to read this website. You can sign in with Discord if you want an account; see Accounts and signing in below. Reading the site sets no cookies of its own; only starting to sign in does (a short-lived rp_pkce cookie, then the rp_session sign-in cookie), and while you sign in your browser talks to Discord and to Supabase, our database service, directly. Like any website, its host may keep short-lived technical request logs.
  • This website counts page views with Vercel Web Analytics, without cookies. It keeps only aggregate counts; see Page view counts below.
  • Every page loads Google AdSense, so your browser also talks to Google; see Advertising below.
  • Hero pages fetch video pictures from YouTube (Google), and their players load only when you press play. Players on hero guide, strategist guide and video tutorial pages load without a press. See YouTube videos below.
  • Apart from Pulse Records (next point), the community pages show anonymous totals: no names, no player ids and no individual matches. A total for a map, a day or a time shows once 10 matches are behind it. Once the app launches and while few players upload, such a total can come from one player's matches, so it can show when that player played and how they did on a map. A signed-in player's own matches and insights are on the Profile page, which only that account can see.
  • Pulse Records is the exception: a public page of the highest single-match figures. A player's name is shown on it only if that player linked an account and switched on "Show me in Pulse Records", and some entries come from players who never agreed to anything and show as "Anonymous". See Pulse Records below.
  • The totals come from matches uploaded by the RivalsPulse desktop app, a separate product that runs inside the Overwolf client.
  • Fair play and privacy says in plain words what the app does and does not show about other players, and what it stores about them.
  • The desktop app's own privacy policy is the full account of what the app collects and how to ask for deletion. This page describes the upload and the site, and does not replace it.

What the app uploads at launch

At launch, the desktop app will upload the matches it records by default, and the other players in an uploaded match will not be asked. A player can turn uploading off in the app's Settings, under Privacy, with the "Upload my matches" switch, which is on until they turn it off. While it is off, nothing will be uploaded and matches will still save on that player's own PC. A match finished while it is off will never be uploaded later, even if the switch is turned back on, and restoring a backup file can turn uploading off but never on. A match that was already waiting to upload when the switch was turned off will be sent once it is turned back on. Turning it off will not delete matches that were already uploaded. For each uploaded match the app will upload the scoreboard line of every human player in it, on both teams, and a few facts about the match. The scoreboard figures are what the game itself shows.

  • In-game name. As the game shows it on the scoreboard.
  • Player id. The number the game uses to identify a player.
  • Team. Which side of the match the player was on.
  • Hero. The hero the player had picked.
  • Kills, deaths and assists. The scoreboard figures.
  • Final hits. Killing blows, counted from the kill feed. Left blank when the game hides a name.
  • Result. Win or loss, worked out from the result the uploading player saw.
  • Game mode. For example Quick Match or Competitive. Shared by every line in the match.
  • Map. The map name. Shared by every line in the match.
  • When it was played. The match time and the half-season it belongs to.
  • Match length. How long the match lasted.
  • Match id. The identifier the game gives the match.

The upload also carries a short-lived Overwolf sign-in token, which our server checks with Overwolf and does not store. We keep a one-way code made from the uploading player's Overwolf username, never the username itself, to limit how many matches one player can send. The same code is stored on every scoreboard line that player records and, once the app sends hero changes, with every hero change that player uploads.

For the uploading player we also keep a record of their own match history: the match facts and their own whole scoreboard line (player id, hero, team, kills, deaths, assists, final hits and result), under the name they play with. The same one-way code described above is also kept next to each match in that history, so that the history can be shown to the player once they link a website account. That history, and the code kept with it, has no time limit; it is capped per player (currently the most recent 5,000 matches).

The desktop app builds made so far, none of them released, read match histories with the public key built into the app, so anyone who takes that key out of the app can read every uploaded match history and the names stored with it. We are moving those reads behind the player's own Overwolf sign-in, which our server checks: the app will then read only the matches that player uploaded, plus the kills, deaths and assists of a player it looks up. Once the builds in use have moved, the public key will no longer read match histories.

Names and player ids are stored so that players can be looked up inside the desktop app. This website never publishes a player id. It publishes an in-game name only on Pulse Records, and only for a player who linked an account and switched their name on.

What the app will also upload

At launch the app uploads these fields in addition to the ones above. Builds made before launch may not send them.

  • Damage. Damage dealt by the uploading player.
  • Healing. Healing done by the uploading player.
  • Damage blocked. Damage blocked by the uploading player.
  • Time played per hero. How long the uploading player spent on each hero.
  • Kill feed. Which hero defeated which hero, and how many times, with no player names or ids.

Damage, healing, damage blocked and time per hero describe only the player who uploaded the match, the one person the app has those figures for. The app does not upload them for other players. The kill feed is reduced to hero against hero counts before it is sent, so it holds no player names or ids at all. These figures are used for community benchmarks, such as damage per minute, and for hero-against-hero counter numbers.

Further fields are planned for launch. They are not uploaded yet:

  • Ability and ultimate use. How often the uploading player used each ability and their ultimate on each hero, with the kills and assists soon after each use. This shows that an ability was used, not whether it hit anyone. Never uploaded for other players.
  • Hero changes during the match. For every player, the heroes they played and how many seconds into the match each pick happened, grouped by team. It carries no player names or ids and is stored once per match, with the one-way code of the player who uploaded it (described under what the app uploads at launch). It is stored under the same match key as the scoreboard lines of that match, so it can in practice be linked back to a scoreboard line, and anyone who reads both can tell which player made which hero changes and when. It is used to count how often switching to a hero while an enemy hero is in play goes on to win.

What this website publishes

  • Apart from Pulse Records, only anonymous aggregates: counts and sums over matches, such as how often a hero is picked or wins, or the average match length of a game mode.
  • Never player ids, match times, links to a match or the stored rows behind the totals. In-game names appear only on Pulse Records, and only for a player who switched their name on.
  • A figure is shown only once it rests on a minimum number of matches. Below that the page says there is not enough data yet instead of showing a number. Pulse Records is the exception: one match is enough for an entry there.
  • On the community Matches and Insights tabs that minimum is 10 matches, from any number of players. Once the app launches and while few players upload, a map, game mode, day or time can rest on one player's matches, with no name or id attached.
  • How a match that two players both uploaded is counted depends on the page:
    • Hero win rates, pick rates, tiers and counters, the role averages, the kill feed and the "Community matches" section of the Stats overview count it once.
    • The damage, healing and damage blocked per minute count each uploading player's own figures, so it counts once for each of them.
    • The "When the community plays and wins" section of the Stats overview (day of the week, time of day, place in a play session) counts it once for each player who uploaded it, because it uses that player's own result. One match can therefore weigh twice there, and can count as a win for one player and a loss for another.
  • Map win rates on the Stats Maps tab and the Overview count each match once, from the side of the player who recorded it; when players on both teams uploaded a match, the earliest upload is the one that counts, so a match is never both a win and a loss for a map. A map's rate is a whole percentage pulled toward the average of the maps that show (50% while fewer than five show) while the map has few matches, and a map appears once it has 10 matches in one game mode and 10 with a result. A map that is still short is named, never counted. While few players upload, a map's rate can describe how one player did on it, with no name or id attached.
  • Hero averages and the scores worked out from them are built from each uploading player's own figures. A hero's figure is shown once 2 different players have contributed, but one player can supply nearly all of it, so once the app launches and while few players upload it can mostly reflect that player's games, with no name or id attached.
  • Specialist and flex win rates. For each hero the site can compare the win rate of players who mostly play it with the win rate of players who play many heroes. The database works out which group a player is in, by the player id on their scoreboard lines, each time it builds the numbers, and never stores which group a player is in. Players who are neither are left out. Only each group's win rate on a hero and a rough match count (50+, 100+, 250+ or 500+) are published, for a hero once each group has at least 2 players, 2 uploading players and 50 matches. A line with no player id is left out.

Pulse Records

Pulse Records is a public page of the highest single-match figures from matches the desktop app uploaded: kills, assists, final hits, damage, healing and damage blocked. Only Quick Match and Competitive matches count. Each entry shows a hero, a figure and either a name or the word "Anonymous". It shows no player id, no match, map or date, and not who uploaded the match. Each list says which date its matches start from.

  • When your name is shown. Only if you signed in, linked your account to the desktop app, and switched on "Show me in Pulse Records" on your account page. It is off until you switch it on, and you can switch it off at any time. Your name is shown only on entries from matches your own app uploaded. The name is the in-game name stored with your link, which the desktop app reported when you linked; we cannot check that it is yours.
  • Anonymous entries are published lines from players who did not agree. The kills, assists and final hits lists also include scoreboard lines of players who have no linked account, including players who never installed the app. Such an entry shows the hero and the figure as "Anonymous", with no name or id, but it is still a published line from a match that player took part in, and someone who played in it may recognise it. A player whose account is linked is never shown as "Anonymous": if they have not switched their name on, their entries are left off the lists. Lines of yours that another player's app uploaded are left off too, not shown as "Anonymous".
  • Damage, healing and damage blocked. The app uploads these figures only for the player who uploaded the match, so these lists show only players who switched their name on, with their own figures.
  • Taking an entry off. Switching your name off removes your name and your entries within a few minutes. Unlinking or deleting your account removes your name, but a kills, assists or final hits line of yours can then show as "Anonymous" until it is deleted on the schedule below. The "forget me" choice on the account page, or a deletion request made through the desktop app's privacy policy, deletes the lines themselves and takes the entries off.
  • Not proof. Entries come from what the desktop app reports, and a modified app can report false figures or a name that is not its player's. A record on this page is not a guarantee that the match happened as shown.

How long it is kept

  • Scoreboard lines of all players, with names and ids, are deleted once the half-season after the one the match was played in has ended, and in any case no later than six months after the match. The extra figures above, and the hero changes once the app sends them (with the one-way recorder code stored next to each one), are kept for the same time and deleted with them. A Pulse Records entry is read from these lines, so it disappears when its line is deleted.
  • The uploading player's own match history (their name, whole scoreboard line and the match facts), and the one-way recorder code kept next to each of its matches, is not deleted on that schedule. It has no time limit and is removed only when a player passes the cap of 5,000 matches and the oldest are pushed out.
  • Before a half-season's lines are deleted, its totals are saved as anonymous counts that hold no name, id or match. Those counts are what the community pages keep showing.
  • If you have linked your player to a website account, the experience points behind your hero levels are also saved before your scoreboard lines are deleted, so your levels never fall: a total for each hero in each half-season, and the times of your last first win and last match so the bonuses carry on. They hold no name, id or match, belong to your account link, and are deleted when you unlink or link again (even to the same player), or delete your account, or when your scoreboard lines are deleted at your request.
  • A player who does not use the app can ask for their scoreboard lines to be deleted and for their id not to be stored again. How to ask is in the desktop app's privacy policy. That deletion covers the scoreboard lines, and with them any Pulse Records entry made from them, but not the uploading players' own match history above.

Accounts and signing in

Signing in is optional and works with Discord only. The community pages need no account. Only your own stats, on the Profile page, do.

  • What is stored. When you sign in, Supabase, the database service this website runs on, creates an account for you. It keeps your Discord user id, your Discord username, the email address on your Discord account if Discord shares one, the time you signed in, and the date the account was created. Discord also sends a few profile details with these, such as an avatar link; Supabase keeps them, and this website does not show or use them. We add one row of our own: your account id and the date it was created.
  • Your IP address. While you sign in, your browser talks to Supabase directly, not through this website. Supabase Auth records your IP address in its audit log when you sign in, and Supabase's request logs also see your IP address and browser details. We do not read or use them, and we have not set how long Supabase keeps them.
  • What it is used for. Signing you in and showing you your own account page (how you signed in, your email address and when you joined) and your own stats on the Profile page, which includes your My matches and My insights. If you switch it on, it also shows your in-game name on Pulse Records. We send no email, and there is no marketing.
  • Video and sound settings (optional). On your account page you can choose whether hero pages open on the gameplay video and whether the video and the home page banner start with sound. We keep those two choices with your account, so they follow you to any browser you sign in on, and show them to you only. Both are off until you switch them on. Signed out, the switches on those pages are remembered in your own browser instead. Deleting the account deletes them.
  • Linking the desktop app (optional). Until you do it, an account is not connected to your in-game name or to any match the desktop app uploaded. To link, you ask the desktop app for a one-time code and type it on your account page. The app sends us, with the code request, your in-game name and id and the address of your Overwolf account avatar, and we keep them with a code made from your Overwolf username that cannot be turned back into it (the same code that limits how many matches one player can upload). Once you are linked, the app sends your name and avatar address again from time to time, and the new ones replace the ones we stored; the id never changes. The link holds those, the date you linked and your account id; the site shows you your name and avatar in the page header and on your account page, to you only. The link is not used in the anonymous community totals. It picks which matches you see as your own and, only if you switch it on, which entries on Pulse Records carry your name. Your avatar is never shown there. The desktop app can also ask us whether you are linked, and we answer with your in-game name and the date you linked, never your email or account id. A code is kept only as a scrambled value, works once, expires after ten minutes (a code nobody used is deleted within minutes of that), and a list of recent code requests, name and avatar updates, link checks, unlinks and wrong guesses is kept for about an hour at most to limit abuse; deleting your account deletes your wrong guesses at once. You can unlink at any time on your account page, which deletes the link, or in the desktop app, which deletes the link and any code you asked for and have not used; deleting the account deletes the link too. The desktop app's uploaded matches are not removed by any of these.
  • The sign-in cookie. Signing in sets one cookie, rp_session. It keeps you signed in until you sign out, or until 30 days pass without a visit: each visit that renews your sign-in also renews the 30 days. It is hidden from page scripts and sent only to this site's own /api address. While you are in the middle of signing in, a second cookie, rp_pkce, lasts at most ten minutes and is removed when the sign-in finishes. Neither is used for tracking.
  • Who else sees it. Discord handles the sign-in and applies its own privacy policy to it, and Supabase stores the account. Your account details are not shown to other visitors and are not used in the community numbers. The one thing you can choose to make public is your in-game name, on Pulse Records.

Deleting your account. Sign in, open your account page, choose what to remove, type the confirmation phrase and press the delete button. Deleting needs a sign-in from the last ten minutes, so you may be asked to sign in again first. Removing the account deletes your sign-in details from our database service and our own row for you at once, and signs you out. Signing in with Discord again afterwards starts a new, empty account. It does not erase everything: Supabase keeps sign-in and request log entries for its own retention period, which we have not set, and those can include your account id, email address and IP address. Backups can also hold the account until they age out. Deleting the account here does not remove this site from your Discord settings; to do that, open Authorized Apps in your Discord settings and remove it there. A second choice, "Remove account and forget me", will also ask us to forget the matches the desktop app uploaded about you; it cannot be undone, and anonymous totals already published keep their counts. It is switched off until you link the desktop app to your account. Removing the account also takes your name off Pulse Records within a few minutes, but see Pulse Records above: a line of yours can stay there as "Anonymous" until it is deleted.

Advertising

This website uses Google AdSense, so every page loads Google's AdSense script. When it loads, your browser sends Google your IP address, browser details and the page you are on, and Google may set or read its own cookies or similar browser storage. Google handles that data under its own policy, how Google uses information from sites that use its services. We see only aggregate reports, such as ad views, clicks and earnings by page, country or device, never data about you.

Where ads appear. No ads are shown yet. When they are, they will appear in one box in the sidebar, on every page except the home page, and only where Google's consent message (below) allows it.

Your choice. If you are in the European Economic Area, the United Kingdom or Switzerland, Google shows a consent message on your first visit with three choices: Consent, Do not consent, and Manage options, where you pick which uses of your data you agree to, including whether ads are personalised. Google keeps your answer in your browser. Elsewhere Google shows no message, and its own policy decides what ads you see.

Changing your choice. Use the Privacy and cookie settings button at the bottom of any page to see the message again and change your answer. The button appears only where the message applies to you.

Page view counts

This website counts page views and visitors with Vercel Web Analytics, which Vercel, our host, runs. It sets no cookies and does not follow you from one site to another. For each page you open, your browser sends Vercel the page address, the page you came from, and your browser and device type. Vercel works out your country and counts you once a day as a visitor, without keeping your IP address. We see only aggregate figures, such as how many people read each page and from which country, never data about you. Nothing is counted on our own computers while we build the site. Vercel handles the data under its Web Analytics privacy documentation.

YouTube videos

Hero pages show their videos as a picture with a play button. Your browser fetches those pictures from YouTube's image host, which Google runs, when the page shows them, so Google receives your IP address and browser details then, before you press anything.

A hero page's video player loads from YouTube only when you press play on that video. Pressing it starts the video, and from then on YouTube handles the data under Google's own policy, Google's privacy policy. We see nothing about what you watch.

Hero guide, strategist guide and video tutorial pages still show YouTube players that load without a press, when the page opens or as you scroll near the player, so on those pages your browser contacts YouTube without a press.

A YouTube player may set or read YouTube's own cookies or similar browser storage. Google's consent message covers the ad box only: these pictures and players do not wait for your answer to it.

More

The desktop app's privacy policy also covers the ads shown inside the app, the optional voice assistant and Premium, which this website does not have. This page describes the upload and the site as the server handles them today; if you find a difference between this page and the app's policy, this page is the more current account of the server.

RivalsPulse is an independent project and is not affiliated with NetEase, Marvel or Overwolf.

Read the desktop app's privacy policy, the full policy for the app as it is built to work at launch.