Privacy

Short version: Rocket LAN has no servers run by the developer, no analytics, no telemetry, and no crash reporting. Nothing about your use of the app is uploaded anywhere.

What stays on your computer

• Your settings. Theme, preferred Rocket League version, display mode, every toggle you've touched. Stored locally under your Windows user profile.
• The map library. Imported and downloaded custom maps live in a local folder you can re-locate any time in Settings.
• The diagnostic log. A rolling local log file for troubleshooting. Useful to paste into a bug report. Never uploaded.

What's read from Discord

Signing in with Discord is optional; sessions work without it. If you sign in, Rocket LAN integrates with Discord via the bundled Discord Social SDK. On your machine, it reads:

• Your Discord friends list and their Discord ids, display names, and avatars, to show your friends and let you invite them.
• Your own Discord id and display name, to identify yourself in the session roster.

All of this happens in-process on your computer, between Rocket LAN and Discord. None of it is sent to the developer.

What's shared with other players

When you host or join a session, the other players in that session learn:

• Your display name (Discord display name if signed in, otherwise a local name), so your roster row identifies you.
• Your Discord avatar, if signed in (the overlay and roster show it).
• Whether your Rocket League is currently in menus, lobby, or in a match (so the host knows when it's safe to swap maps).
• The custom map bytes when you're the host re-sharing them, or the host's bytes when you're a joiner downloading.

That's it. Nothing about your wider system, browsing, or other apps is shared.

Network traffic

Rocket LAN connects players peer-to-peer over its own network using the iroh QUIC stack. When a direct peer-to-peer connection can't be established (NAT, firewall, etc.), traffic falls back to the public relay infrastructure run by the iroh project, operated by the iroh maintainers, not by Rocket LAN's developer. All session traffic is end-to-end encrypted, so relays only carry encrypted bytes.

Discord connectivity is whatever Discord itself does on your machine, governed by Discord's own terms. Separately, Rocket LAN contacts GitHub on startup to check whether a newer version is available; see the FAQ for how auto-update behaves.

Discord rich presence

While Rocket LAN is running, it sets Discord rich presence carrying your connection endpoint id. When you host a session open to friends, that presence advertises the open session so your Discord friends can see and join it. This is visible to your Discord friends (which is the point). Closing the app clears it.

What's not collected

• No analytics, no event pings, no view counts, no "session started" beacons.
• No telemetry, no performance data, no error reports, no usage stats.
• No crash reporting, if Rocket LAN crashes, you can paste the local diagnostic log into a bug report; nothing leaves your machine automatically.
• No third-party advertising or ad-network tags. The app embeds no web content.
• This website (the one you're reading) does not run its own analytics. GitHub Pages may set technically-necessary cookies for the underlying hosting; Rocket LAN does not add any beyond the Buy Me a Coffee widget described below.

Buy Me a Coffee widget

This website embeds the official Buy Me a Coffee floating widget, a third-party script loaded from buymeacoffee.com, on every page. It may set its own cookies or load additional resources from Buy Me a Coffee's servers, separate from anything Rocket LAN itself does. See Buy Me a Coffee's privacy policy for details on what it collects.

Children

Rocket LAN is general-purpose software intended for personal use alongside a copy of Rocket League. It does not knowingly collect personal data from anyone, including children.

Changes

If the privacy story ever changes, this page changes with it, and the change goes into the Terms of Use's "Last updated" log.

The legal version of all this is in the Terms of Use, section 5.