Privacy
Last updated 15 November 2026
Preset Garage is a fan-made site that shows Rocket League car presets read from replay files. This page says what it keeps, why, who else sees it, and how to have it removed.
What it keeps
When you sign in with Discord
- Your Discord user ID, display name and avatar, through Discord's “identify” permission only: not your email, servers or messages.
- When you first signed in, and your sessions: a hash of each session's token and when it expires.
- The presets you like and favorite, the replays you upload, and the builds you publish.
- Each sign-in is noted for the site's admins on the site's Discord, with your Discord display name and avatar.
- While you're signed in, your avatar shows at the top of each page; your browser loads it from Discord's image server (cdn.discordapp.com), as Discord's own app does.
- If an admin bans your account for breaking the terms, that's kept with it: it can't sign in, and the builds it published are hidden.
From uploaded replays
A replay file is read and then thrown away. What the site keeps from it, and shows to everyone:
- Each player's platform (Epic, Steam, PlayStation, Xbox or Switch) and account ID there, and the names they played under and when.
- The car each player drove: its items, paints, colors and finishes.
- The match: when it was played, the map, the score, the team names and who played.
Who uploaded a replay is shown with the presets from it, by their Discord display name. When an upload adds new presets, the site also posts them on its Discord with the uploader's display name and a mention of their Discord account. When it was uploaded is kept too, but not shown.
When the site can't read an uploaded file, it tells its admins in a private channel on the site's Discord why it failed, the uploader's Discord display name and user ID, and the file's name, type (found from its first bytes) and size, so they can tell a fault in the site from a file that isn't a replay. A file named .replay is sent too, unless it's over 8 MB.
When you publish a build
A preset you make in the builder and publish is kept and shown to everyone like any other preset, credited to your Discord display name; your Discord user ID is never shown on the site. The site also posts it on its Discord with your display name and a mention of your Discord account. Looking at a build or sharing its link keeps nothing: it lives in the link until you publish it.
Logs
The site keeps no access logs: no record of the pages you open. It counts page views by the hour and by kind of page, how fast it answered, and which sites links came from, with nothing about who.
To count how many different people visit each day, it keeps a hash of your IP address and browser, made with a key that is new each day. The key and the hashes are deleted when the day ends (UTC), leaving only the day's count.
Pages with the 3D turntable report whether it started, how long it took, its frame rate, and whether the device is a phone, with nothing that identifies you.
Its own logs note errors and sign-in attempts with their time. The web server's error log can hold an IP address for a short while when a connection fails.
Why
To run the site: to show presets and the players who wear them, to keep you signed in, to save your likes and favorites, to stop abuse (uploads are limited per account), and to see how much the site is used and whether it runs well. Showing what players already show in public matches is the site's legitimate interest; your account exists because you chose to sign in.
Who else sees it
- Everyone sees what's on the site's pages: presets, players' names and platforms, matches, and the display name of whoever uploaded a replay or published a build.
- Members of the site's Discord: each upload's new presets and each published build, with the uploader's or builder's display name and a mention of their Discord account.
- Discord, when you sign in there, under its own privacy policy.
- The site's admins, and Discord, which hosts their channel: a .replay file the site couldn't read, with who uploaded it.
- The hosting company whose server runs the site, and Cloudflare, which answers the domain's DNS (it doesn't see the site's traffic).
The site's public pages are open to search engines: a search for a player's in-game name, or for a builder's Discord display name, can find their page, their presets and their builds, and engines keep copies for a while after a page changes or goes. Pages for signed-in use (your favorites, your replays, search results, sign-in, the admin's) ask engines to stay away. A hidden player or preset is taken out of the site's pages, its sitemap and its link previews at once; engines drop their copies as they next visit. To have your name, presets or builds hidden, ask as under Your choices.
No ads, no third-party analytics, no trackers: the counts above stay on the site's own server. Nothing is sold or shared for marketing.
How long
- Sessions: 30 days, or until you sign out.
- Daily visitor hashes: until the end of the day (UTC). Traffic counts: 90 days.
- Your account, likes and favorites: until you ask for them to be deleted.
- What replays carry, and published builds: while the site runs, unless the player or builder has it hidden.
- A .replay file the site couldn't read: on the site's server until it's posted to the admins' channel (a week at most), then there until they delete it.
Your choices
- Sign out at any time: your session ends at once.
- Take back a like or a favorite whenever you like.
- Ask the site's admin, on the site's Discord, what's kept about you, for a copy of it, or to have it corrected, hidden or deleted: your account, or the presets and names that show you. Where data protection law gives you more (in the EU and UK, the right to object and to complain to your data protection authority, for example), you have that too.
Children
Signing in needs a Discord account, which Discord allows from age 13 (older in some countries). The site doesn't knowingly keep anything about younger children; tell the site's admin on its Discord and it's deleted.
Changes
Changes are posted here with a new date. Cookies and the terms of use have their own pages.