← All posts

The privacy screen on RizzStats' upload page, actually explained

GuidesJordan Cole2026-07-04 · 3 min read

Before RizzStats shows you a single number, you get a privacy screen with three switches on it. Most people skim it and tap through. Worth thirty seconds first: one of those three switches starts in the "on" position, and it's the one that decides whether your raw export file leaves your device at all.

What happens before any of this

Tinder's data.json and Hinge's matches.json + account.json are parsed in your browser, not on a server. That's not a privacy pitch, it's just the order of operations: your file is read locally, turned into the numbers RizzStats needs, and only then does anything get sent anywhere. What gets sent depends entirely on how you leave the three toggles on the last upload step.

The three toggles

Anonymize my conversations. Off by default. Flip it on and every message body in your export gets deleted on your device before upload. Only timestamps and counts make it out of your browser. This doesn't break anything: match rate, reply rate, and the "conversation depth" piece of your Rizz Score are all built from counts and timestamps, not from what you actually wrote. The catch is one-directional anyway: both Tinder's and Hinge's exports only ever contain messages you sent, per Tinder's and Hinge's own data-request pages, so this toggle is about hiding your side of the conversation from RizzStats, not the other person's.

Include my bio & city. Also off by default. Leave it alone and your bio, city, and region get stripped out of the extracted data before anything uploads. Turn it on and RizzStats keeps them, which is what powers the sharper AI-generated roast and any city-based context. It's opt-in, not something that happens just by uploading your file.

Contribute to research. This one starts on. Unlike the other two, it isn't about what's stripped out of the parsed data. It governs whether your original export file (the raw data.json, or matches.json/account.json) rides along with the upload at all, alongside the parsed numbers. RizzStats' own copy says this powers cohort benchmarks and dating research, with no names or photos published, and that you can opt out any time in settings. That's a reasonable trade if you're fine with it, but "on by default" means people who click straight through all three steps are sharing their raw file whether they meant to or not.

Why the defaults are set up this way

The two toggles that reduce what's collected default to off; the one that increases what's collected defaults to on. That's a real asymmetry, and it's worth knowing before you hit "See my insights" rather than after. None of this is unusual for a free tool that needs data to build benchmarks. GDPR and CCPA data-portability rules are exactly what make your export requestable from Tinder or Hinge in the first place, and nothing about how RizzStats handles it after upload conflicts with what those exports already contain. It's just that a toggle you don't touch is still a choice, and this is the one screen where all three get made for you if you don't make them yourself.

The thirty-second version

If you want your numbers without your raw file leaving your device, flip "Contribute to research" off before you submit. If you want the fuller AI roast, turn "Include my bio & city" on. If you'd rather RizzStats never sees a word you wrote, anonymize your conversations. Your match rate, reply rate, and Rizz Score will look exactly the same either way. Then head to the upload page and set it up the way you actually want it, not however the defaults left it.