BTr-RJ

Privacy policy

BTr-RJ website and RedBaron_Recomp · Effective November 6, 2026

On this page

This policy explains the information used by this website, the RedBaron_Recomp online integration and support provided by its maintainer.

Maintainer and scope

BTr-RJ is the independent developer identity used by the maintainer of RedBaron_Recomp. Contact the maintainer for support or data-protection inquiries at peixeurb21@gmail.com.

This policy covers the BTr-RJ website, RedBaron_Recomp and related support. Other projects linked from this website may have different integrations; this policy does not describe their game-data handling. BTr-RJ is not Epic Games or the original game's publisher.

Website visits

This is a static website hosted on GitHub Pages. The website contains no account system, contact form, advertising, analytics scripts, embedded social widgets or tracking cookies added by BTr-RJ. Its fonts and visual assets are served with the site.

Visiting the site involves ordinary network requests to its hosting provider, which can include your IP address, browser information and requested address. The provider's handling of those requests is described in the GitHub privacy statement. External links and email open services with their own privacy policies.

Local game data

The installer uses original game files that you provide to build the game on your PC. Local profiles, saves, settings, controller mappings, caches and diagnostic logs can be stored on your device. They are not uploaded to this website automatically.

Local logs can include hardware information, timestamps, errors and game or service activity. Review them before sharing. The launcher can contact GitHub for release metadata and downloads and obtain required build tools or runtime components from their providers. Those requests disclose ordinary connection information to the services involved.

Online features

When you choose to sign in for online play, RedBaron_Recomp uses Epic Account Services and Epic Online Services (EOS). The integration requests the following account permissions through Epic's consent flow:

  • Basic profile: account identity and display-name information used to authenticate and identify players.
  • Friends list: friend information made available to the application for friends and invitation features.
  • Presence: availability and game-session status for supported social features.

The game also uses account and product-user identifiers, authentication tokens, lobby membership, invitations, session details, connection information and gameplay network messages to establish and run online sessions. Display names and session information may be visible to other participants or people searching compatible public sessions. Peer-to-peer or relay connections involve network addresses and connection metadata.

When enabled and available, the achievement integration can read and synchronize native achievement progress. The statistics and leaderboard integration can submit gameplay statistics and query rankings associated with the signed-in product user. Public rankings may show player identity or display-name information and scores. These integrations remain under testing; this description is not a guarantee of complete functionality.

BTr-RJ's game integration uses tokens returned through the SDK and does not ask you to send your Epic password to the maintainer. Authentication information and local caches must not be shared in support reports.

For the separate relationship between you and Epic Games, consult Epic Games' privacy policy and your Epic account settings.

Support requests

If you email the maintainer, the information you send can include your email address, message, hardware details and any attachments you voluntarily provide. This information is used to investigate the issue, reply to you and handle privacy or security requests.

GitHub bug reports and their attachments are public. Do not post passwords, tokens, EOS configuration, original game files, DLCs or saves. If a private detail is necessary, use email and send only the minimum information needed.

Data sharing

Online game data is exchanged with the services and players needed for the selected feature: Epic Online Services, the session host and other participants. Support email is processed through the maintainer's Gmail inbox; public issues and release downloads use GitHub. These providers and players may be in countries different from yours.

BTr-RJ does not sell player data or use this website for advertising profiles. Account and gameplay information is used for the project features described here, troubleshooting and security. Information may also be disclosed when required by applicable law.

There is no separate BTr-RJ-hosted gameplay server in this integration: a player hosts the game session, with EOS supplying the integrated online services. This does not mean the online game processes no personal data.

Retention

  • Local files: saves, settings, logs and caches remain on your device until you or the relevant software remove them. Keep a backup before deleting files you want to preserve.
  • Session data: lobbies and connection activity are used for online-session operation. Closing the game does not itself erase all service-side records.
  • Account-linked progress: achievements and statistics can persist between sessions. Revoking sign-in consent or removing a local save does not by itself delete previously submitted data.
  • Support: correspondence is kept as needed to handle the request and related follow-up, security or legal obligations. You can request deletion of information held by the maintainer.

For project data processed through integrated services, contact the maintainer to request access or deletion. For your Epic account itself and data handled independently by service providers, use their account controls and privacy-request procedures.

Your choices and rights

You can play offline without completing Epic authentication when online features are unavailable. You can stop using online features and manage the application's account authorization in your Epic account settings. Removing authorization stops future authorized account access; it is separate from requesting deletion of existing project data.

Email peixeurb21@gmail.com with the subject “RedBaron privacy request” to ask what project data is held, request access, correction or deletion, or raise a privacy concern. Describe the request and the account or support conversation it concerns, without sending a password or token. The maintainer may ask for proportionate information to verify that the request relates to your data.

The maintainer handles requests for project data within their control, including use of the relevant service tools or support channels where needed. The maintainer cannot delete another provider's account on your behalf. Where applicable law grants additional rights or a right to complain to a supervisory authority, those rights remain available.

Policy changes

This page will be updated when the website or the project's relevant data-handling practices change. The effective date above identifies the current policy. Contact peixeurb21@gmail.com with questions.