GitHub Discord Download
/ privacy

Privacy Policy

Last updated: May 2026. No personal data, no telemetry, no analytics. RLPeak works locally on your machine.

RLPeak is designed with transparency as a core principle. The application works with local files on your machine and does not collect personal data. This policy describes what information, if any, is transmitted when you use RLPeak.

Overview

RLPeak is a Windows desktop companion for Rocket League. It runs entirely on your computer, modifies cosmetic asset files locally, and keeps a backup of your originals. The only outbound network traffic is when you fetch the cosmetic catalog or download an asset you selected.

What RLPeak does not do

RLPeak does not:

  • Collect, store or transmit personal data
  • Track usage, behavior or session activity
  • Include telemetry, analytics or crash reporting
  • Use cookies, local storage tokens or fingerprinting
  • Share data with third parties or advertisers
  • Access your Rocket League account, credentials or online profile

Network communication

RLPeak communicates with a single endpoint:

API: https://api.rlpeak.com/v1

This communication is limited to two operations:

  1. Catalog requests. When you open the Items page, the app sends a GET request to retrieve the list of available cosmetic assets (decals, wheels, boosts). This request contains no user data — only the catalog query.
  2. Asset downloads. When you click Apply, the app downloads the selected cosmetic files from the API. These files are stored in a local cache on your machine. No user identifier, system information or account data is included in the request.
No other network communication occurs. RLPeak does not phone home, does not check for updates silently, and does not transmit any information about your system, your Rocket League installation, or your usage patterns.

Local file operations

RLPeak performs the following operations on your local file system:

  • Cache. Downloaded cosmetic assets are stored in a local cache directory.
  • Backup. Before applying any changes, RLPeak creates a one-time backup of your original Rocket League cosmetic files.
  • Apply. Selected cosmetic files are copied into your Rocket League installation directory.
  • Reset. Original files are restored from the backup.

These operations are limited to cosmetic asset files within the Rocket League installation directory. RLPeak does not modify system files, registry entries, environment variables, or files outside the Rocket League directory.

Third-party components

RLPeak is built with the following open-source components:

  • Tauri (application framework) — does not collect user data.
  • React (user interface) — runs locally, no external communication.
  • TypeScript (application logic) — compiled and executed locally.

No third-party service, SDK, or library included in RLPeak collects or transmits user data.

Data storage

RLPeak stores the following data locally on your machine:

  • Application settings (window size, selected preferences)
  • Cached cosmetic asset files
  • Backup of original Rocket League cosmetic files

All data is stored in standard application directories on your system. No data is stored on remote servers. No data is encrypted because no sensitive data is handled.

Children's privacy

RLPeak does not knowingly collect any personal information from anyone, including children under 13 years of age.

Changes to this policy

If this policy changes, the updated version will be published at this URL with a revised date. Since RLPeak does not collect contact information, we cannot notify users directly — check this page periodically.

Contact

If you have questions about this privacy policy:

Summary

This program will not transfer any information to other networked systems unless specifically requested by the user or the person installing or operating it. The only network communication is the retrieval of cosmetic asset catalog data and asset files from api.rlpeak.com, initiated exclusively by user action.