Privacy notice

What the app reads and stores

The tracker connects to Rocket League’s local Stats API on your PC and reads the local game log to identify your account and match context. Setup asks you to confirm the account and any API configuration change.

Local records can contain your account identifier and display name; match identifiers, times, playlists, results and corrections; team scores; player names and available scoreboard statistics; play sessions; rating checkpoints you enter; and preferences. Names of teammates and opponents can be included. These records support the session view, history, Overview, corrections, and exports.

The tracker’s capture code does not upload these records to the project operator or a project cloud service. Diagnostic events use selected fields rather than raw game-log lines or full API payloads. This does not make the files anonymous: identifiers and player names may remain.

Local retention and deletion

App records and settings are stored in %LocalAppData%\RocketLeagueTracker\Tracker. History, preferences, rating checkpoints, CSV exports, and tracker.log have no automatic expiry. Event records in capture-events.jsonl older than 30 days are removed during startup and periodic cleanup while the tracker runs. Unreadable records and failed cleanup may leave older entries.

Portable backups contain history and settings, including account information, but exclude diagnostic event files and raw logs. Backups and exports are readable files, not encrypted vaults. Keep them private. Copies you choose to save elsewhere, pre-restore backups, and game-configuration backups remain until you remove them.

To erase local tracker data, quit the tracker from its tray menu, then delete %LocalAppData%\RocketLeagueTracker. This also removes its separate WebView2 cache/profile folder. You lose saved history and settings; keep a backup first if wanted. Remove separately saved exports/backups yourself. Removing the app folder or uninstalling does not by itself erase all local data. This does not delete Rocket League’s own logs or undo its API configuration.

Microsoft WebView2

The desktop interface uses Microsoft Edge WebView2. Microsoft may receive required runtime diagnostics, optional diagnostics according to your Windows settings, and crash reports. Microsoft Defender SmartScreen is enabled by default and can send information to Microsoft for security checks. See Microsoft’s WebView2 data guidance and Privacy Statement. Optional diagnostics are controlled in Windows Privacy & security, Diagnostics & feedback. These runtime services are separate from the tracker’s local match storage.

Website visits and hosting

This static site has no project sign-in, advertising pixels, embedded payment widget, analytics script, or application-set tracking cookies/local storage. Loading a page still sends ordinary request information to its host.

AWS Amplify/CloudFront serves the primary website. Hosting access logs can include IP address, requested URL and query, request time, browser/device information, referrer, and response details. The operator can access logs for delivery, troubleshooting, security, and understanding site traffic. AWS states that Amplify access logs are retained until the hosting app is deleted; no shorter retention is promised here. Do not put private information in URL parameters. See AWS access-log documentation and AWS Privacy Notice.

The earlier GitHub Pages copy is hosted by GitHub. Providers may process information internationally, including in the United States, under their own policies and applicable safeguards.

Downloads, support, and coffee

• GitHub: downloads and issue reports use GitHub. GitHub receives request/account information when you use it. The operator checks aggregate release-asset download counts through GitHub’s API. These count download requests, not unique people or installs; this website does not fetch that API during a visit. Issue posts, attachments, and account names are public. Do not post credentials, raw game logs, account identifiers, or private reports. See GitHub’s Privacy Statement.
• Buy Me a Coffee: support links open an external service only when selected. That service and its payment providers process the payment. The project does not process card details on this site. The creator may receive supporter details, messages, and transaction information made available by the platform. See Buy Me a Coffee’s Privacy Policy.
• Messages you send: the maintainer receives what you voluntarily provide for support or a privacy request. Email to the published Gmail address is processed by Google under its Privacy Policy. Only share what is needed. Public issue content remains subject to GitHub’s controls; provider transaction records follow the relevant provider’s retention rules.

Your choices and contact

You can stop local capture by quitting the tracker, remove local files as described above, avoid optional external links, and review the providers’ privacy controls. The maintainer cannot remotely retrieve or delete records that remain only on your PC.

Depending on applicable law, you may have rights to request access, correction, deletion, restriction, objection, or portability concerning personal information held by the operator, and to complain to a relevant privacy authority. Rights and exceptions depend on your circumstances.

For private support or a privacy request, email rlstattracker.support@gmail.com. Include only what is needed to explain your request; do not send passwords, authentication tokens, raw game logs, or payment-card details.

For general project questions, use public GitHub issues. Do not include sensitive information.

Changes to this notice will be published here with an updated date. New cloud, analytics, or AI features would need a fresh explanation before they handle your information.