Terms of Service & Privacy Policy

Last updated: September 6, 2026. This document combines our Terms of Service with our Privacy & Cookie Policy, written in plain language so it can actually be read

1. Who we are and what this covers

Vision Force Studio is a fan team of community volunteers running a hobby project. These terms cover visionforceofficial.com and everything on it:

• the studio site at the front, with project documentation, news, a directory of our Discord communities, a contact page and this document, all readable without an account
• the Rocket Racing Revive community hub at /rrr, which holds the roadmap, suggestions, the community board, profiles and account settings, and which needs an account for all of it: only the entry screen and the pages that get you into an account, such as sign-in, invitations, email confirmation and password recovery, open without one
• our status page at status.visionforceofficial.com

Our projects are Vaelora Velocity, a fan-made racing game built in Unreal Engine 5; LUX3, a collection of track recreations built in UEFN; and Rocket Racing Reborn, a preservation project that keeps the original Rocket Racing playable, which sections 12 to 14 cover on their own

We also run the Rocket Racing Archive at rocketracingarchive.com. It is a separate static site with no accounts and no sign-in, but its contribution form sends what you write to us, and mail sent to the archive's own contact address reaches us as well, so section 6 explains what happens to that. Letters the archive sends you carry a send-only reply address, so a reply is rejected and bounces straight back to you rather than reaching us. Use the form again if you need to add something

This is a non-commercial fan project. There are no ads, no paid features and nothing on this site is sold. A personal tip link is offered in the hub footer; it is voluntary, buys no feature, rank or advantage, and the site works exactly the same whether or not you use it. We are not affiliated with, endorsed by, or sponsored by Epic Games, Inc. or Psyonix LLC. "Rocket Racing", "Fortnite", "Unreal Engine", and all related names, logos, and assets are the property of Epic Games, Inc. or their respective owners

By creating an account or using the site, you agree to these terms. If you do not agree, please do not use the site

2. Eligibility and accounts

• You must be at least 13 years old to use this site, or older, if the age of digital consent in your country is higher. Creating an account requires confirming that you meet that minimum age
• Accounts we find to belong to someone under 13 are removed. Content posted from them is taken down by hand, because nothing removes it automatically, so tell us if you see something we have missed
• You create an account by signing in with a Google, Discord or GitHub account. We do not open new accounts from an email address and password. If your account has a password, you can also sign in with your email address or username and that password. Passwords are stored only as a salted bcrypt hash, so we cannot read your password, and no password is stored at all when you sign in with a provider
• If you signed in with a provider you can add a password later from Profile > Sign-in and security, and then sign in either way. Your provider stays connected
• If you add a passkey, you can sign in with it alone. Your device confirms you with a fingerprint, face scan or PIN, your browser signs a one-time challenge, and we check the signature. No password is involved and the passkey's private key never leaves your device
• Signing in starts a session that lasts 24 hours from your last visit. The clock resets every time you load a page, so it is an inactivity timeout rather than a hard limit: stay away longer than 24 hours and you will be asked to sign in again
• You are responsible for activity on your account. Keep your credentials private, and let us know if you believe your account has been compromised
• One account per person. Do not create accounts to impersonate others, evade a mute or ban, or manipulate votes. We may reclaim usernames that impersonate a person or project

3. Community rules and moderation

The site exists so fans can share work, feedback, and ideas. To keep it that way, you agree not to:

• post unlawful, hateful, harassing, threatening, or sexually explicit content;
• impersonate any person or misrepresent your affiliation with any group;
• upload media you do not have the right to share;
• spam, flood, or manipulate votes and suggestions;
• attempt to disrupt, attack, probe, or gain unauthorized access to the service or to other accounts;
• evade a mute, kick, or ban by any means, including new accounts, VPNs, or proxies;
• scrape, crawl, harvest, data-mine, or use bots or any automated means to copy or extract content, media, or data from the site;
• copy, rip, mirror, redistribute, resell, or otherwise steal the site's original code, design, branding, or artwork, or another member's content, whether to pass it off as your own or to reuse it elsewhere, without our written permission (see section 5)

How moderation works:

• An automated word filter screens posts, comments and suggestions, and also usernames, display names, pronouns and profile bios. Where it is switched on it can act without any human reviewing first: it can warn, mute, temporarily remove, or permanently ban an account. A username or profile field that trips the filter is refused, so the change is simply not saved, and a serious enough word can still mute or ban the account on top of that. Every hit is recorded against your account, but a refused username or profile field is not counted towards the escalation that makes repeat hits harsher
• An automatic removal or ban also blocks the IP addresses and device signatures that account has been seen from. This is how ban evasion is prevented, and it has a side effect worth stating plainly: other people sharing that connection, such as a household or a school network, can be caught by the same block. If that happens to you, write to us and we will sort it out
• Human staff may remove content and mute, temporarily kick, or permanently ban accounts, at their reasonable discretion. Warnings come from the automated filter only; there is no button for a person to issue one
• Staff at supermod level or above can also permanently delete a member's account, which runs the same scrub described in section 10
• Moderation actions are recorded in an internal audit log so decisions can be reviewed
• If you believe a moderation action was a mistake, write to contact@visionforceofficial.com. The contact page stays reachable when you are signed out or banned

4. Your content and licenses

• You own what you post. Posts, comments, suggestions, and uploaded media (avatars, banners, images, videos) remain yours
• By posting, you grant us a non-exclusive, worldwide, royalty-free license to host, store, display, and reproduce that content as needed to operate the site, for example showing your post to other members
• Deleting a post, comment or suggestion hides it rather than erases it. It stops being shown on the site, and the display part of that license ends there. We keep the stored copy in the database. A deleted post stays visible to staff in the admin tools and can be put back if the removal was a mistake. A deleted comment or suggestion is kept but shown to nobody, staff included, so it cannot be restored from the site. Copies also sit in nightly backups until those age out, as described in section 9. If you want something you posted erased rather than hidden, ask us at contact@visionforceofficial.com
• Content posted in the hub is visible to every signed-in member. The pages that hold member content cannot be read by visitors who are not signed in, and they are kept out of search engines, but anyone can open a free account, so treat anything you post as public: any member can read it, quote it or screenshot it
• Uploaded files are the exception. Avatars, banners and media attached to posts sit in public-read storage, so a file is reachable by anyone who has its address, signed in or not, as described in section 8
• Only post content you created or have permission to share. We may remove any content that violates these terms or that we reasonably believe creates a problem for the project
• If you send us ideas or suggestions for the project, we may use them without obligation or compensation. That is what the suggestions board is for

5. Intellectual property

• "Rocket Racing", "Fortnite", "Unreal Engine", "UEFN", and all related characters, vehicles, tracks, names, logos, and assets are the intellectual property of Epic Games, Inc. and, where applicable, Psyonix LLC. Their appearance in community content does not transfer any rights, and all fan-made content on this site is provided for non-commercial community purposes only
• Vaelora Velocity and LUX3 are unofficial fan creations and are not endorsed by Epic Games. We do not extract, port, or reuse Epic Games assets or code in them
• Original works remain their creators' own. The site's own source code, design, layout, branding, logos, artwork, animations, and the coded 3D globe and interface belong to Vision Force Studio; each member's original content belongs to that member. You are welcome to browse and use the site as intended, but you may not copy, scrape, rip, reuse, redistribute, sell, or pass off any of it, ours or another member's, as your own without written permission. Stealing assets or content is not allowed
• If you are a rights holder and believe content on this site infringes your rights, email contact@visionforceofficial.com and we will review the material and, where appropriate, remove it promptly

6. Privacy: what we collect and why

We collect only what a small community site needs to function. We do not sell your data, we do not build advertising profiles, and we run no advertising or cross-site tracking. We do use a privacy-friendly, cookieless analytics service and keep a minimal first-party usage log, both described below

Account data

• Email address, username, and display name, plus any optional profile details you add: pronouns, region, and a short bio
• For email-and-password accounts: your password, stored only as a bcrypt hash. For Google, Discord or GitHub sign-in: the basic profile the provider shares with us (name, email address, avatar), together with the linked-account identifier and the provider's OAuth tokens (access, refresh, and ID tokens), which our sign-in library stores as part of the link. We do not use them to call the provider, and they are discarded when you unlink or delete the account
• If you turn on two-factor authentication: a one-time-code (TOTP) secret, stored encrypted, and backup recovery codes, stored only as hashes
• If you register a passkey: the passkey's public key and its metadata (a label, the device transports, a signature counter, and last-used time). The private key never leaves your device
• An optional recovery phone number, if you choose to add one. It is stored unverified. There is no SMS provider wired up, so it is never messaged, is never a sign-in method or a second factor, and it is cleared when your account is deleted
• Optional profile media you choose to upload, such as an avatar or banner

Content you share

Posts, comments, suggestions, votes, and uploaded images or videos. Content in the hub is visible to every signed-in member, and uploaded files are reachable by anyone who has their address, as explained in section 4

If you ask for access to Rocket Racing Reborn, we also keep what you wrote on that form: your reason for asking, the region you picked, how you heard about the project, whether you played the original, and the decision we reached with any note attached to it

The Rocket Racing Archive, if you write to us there

You do not need an account to send a correction to the archive, so this part applies to people who have never signed up for anything:

• The contribution form. Your browser sends what you typed to two places at once. One copy goes to Web3Forms, a third-party form-to-email service, which emails it to us. The other copy comes to us directly and is stored so we can see what arrived, what has been answered and by whom. We store your message, the page or section you named together with the address of the archive page you were on, any source or proof link you gave, and whatever you put in the optional contact field, kept exactly as typed whether that is an email address or a handle. The form has no name field. We also store a shortened one-way hash of your IP address, used only to cap submissions at six an hour from one source. We do not store the address itself
• Confirming your address. If what you typed in the contact field is a valid email address, we send one automated message to it with a confirmation link. We store only a hash of that link's token and its expiry, never the link. It works once and expires after 7 days. We will not reply to an address nobody has confirmed, because an address typed into a public form is a claim about a stranger until they prove it
• Email you send to the archive. Mail sent to the archive's own contact address is received by Cloudflare and passed to a small program we run there. That program sends us your sender address, the display name on your From header, the subject, the Message-ID and up to the first 60,000 characters of the message, which we show to moderators. We store it in full when it answers a submission we already hold, and the first 8,000 characters when it starts a record of its own. Cloudflare also forwards the whole message to a Gmail mailbox we operate, so Google receives a full copy. If we do not recognise your address, your message starts a record of its own instead. Mail sent from an address is itself proof that you control it, so here the address counts as confirmed the moment your message arrives, with no link to click, and that is what lets us write back to you. If we already hold a submission from your address, your message is filed against that one and its confirmed status does not change. Letters we send about the archive carry a send-only reply address instead, so replying to one is rejected and you get a bounce back: use the contribution form again if you need to add something

Analytics and performance

• We use Vercel Web Analytics on every page, and Vercel Speed Insights everywhere except the status page. These are cookieless and aggregate: for each visit they record the page visited, the referrer, an approximate country (derived from your IP at the edge), and your device and browser type, along with performance measurements such as loading speed. This is sent to Vercel (section 8); it sets no cookies, uses no persistent identifier, and does not identify you or track you across other sites
• We also keep a small first-party event log, and it is much narrower than that name suggests: it records a handful of specific actions, namely opening a report, disconnecting a sign-in provider, and staff actions on API keys and on game access. It does not record which pages you visit. Each entry holds only an internal account reference, never your name, email, or IP, and that reference is detached when your account is deleted

Email we send you

• Account email is transactional. Password resets, email verification, and security alerts (your password changed, two-factor was turned off, a passkey was added, all sessions were signed out) are sent when the matching action happens on your account, as is an acknowledgement and then our decision if you ask for access to Rocket Racing Reborn. They are part of running the account safely and cannot be switched off while the account exists
• Notification email is opt-in and separate. Announcements and other non-essential mail are off by default and controlled by a toggle in your profile settings, which you can change at any time
• Our outgoing mail is one way. Account mail is sent from a no-reply address. Archive mail is sent from archive@visionforceofficial.com, which we do read, but it carries a no-reply address for replies, so hitting reply does not reach us and bounces back to you. To reach a human, write to contact@visionforceofficial.com, or use the archive's contribution form for anything about the archive
• Mail is delivered by Resend, a third-party email provider (section 8)

Safety and moderation data

• IP address and a browser device fingerprint, recorded while you are signed in and using the community hub, and rewritten at most about once every ten minutes for as long as the tab is open. Pages outside the hub record neither. The fingerprint is a one-way hash of several browser signals: your User-Agent, operating system and platform, language list, screen size, timezone, hardware hints (device memory and CPU cores), and a small canvas-rendering signal. Alongside it we store, per device, the raw User-Agent string and the most recent IP address, so you can see and manage your signed-in devices in your profile. These are used to enforce bans, prevent ban evasion, and, briefly, to rate-limit abuse such as repeated failed logins
• Records of moderation actions taken on your account (warnings, mutes, kicks, bans) and an audit log of who took them
• Content flagged by the automated word filter, and warning counts
• Entry scan. The hub runs a check each time a signed-in member loads it. It is on by default and the site owner can switch it off at any time. It does three things. Your IP address is sent to the third-party service ipwho.is, which returns the country, timezone and internet provider. We then judge whether that provider looks like a VPN, proxy or datacenter, by matching its name against a list we keep; ipwho.is does not make that call. An invisible test element is placed in the page to detect whether you are running an ad blocker. And your browser's timezone is compared with the timezone reported for your IP
• What every scan records. Whether or not anything is flagged, we keep one current record against your account holding the three results (VPN or proxy, ad blocker, timezone mismatch), your browser timezone, and the country resolved for your IP address. Each scan overwrites it, so only the latest result is held, and it goes when your account is deleted. Staff at supermod level or above can see it on your account. Separately, the lookup result for an IP address is cached against that address in full, not hashed, and refreshed about every 7 days, so a repeat visit does not trigger another lookup
• What a flagged scan adds. If a scan flags a VPN or proxy, an ad blocker, or a timezone mismatch, we also write an entry to a log that staff at supermod level or above can review. That entry holds your IP address in full, not hashed, its country and internet provider, your browser timezone, which checks tripped, your internal account ID, and the name held on your account at that moment. That name is the one you set when you joined, or the one your sign-in provider gave us if you have not set one yet; if there is no name at all we record your @username, and failing that the email address on file. These entries are deleted automatically after 90 days, and the cached lookups after 30 days; section 10 has the detail
• Staff with moderator access can see, for each account, the email address on file, its mute or ban state and the reason recorded, when it was last active and whether it is online. Staff at supermod level or above additionally see the most recent IP address held for the account and the country resolved for it, how many IP addresses and how many devices are on file for that account, and whether the latest entry scan flagged a VPN or proxy connection, an ad blocker, or a timezone mismatch

Why we process this data

• To provide the service: accounts, sessions, account email, and showing your content
• To keep the community safe: moderation, ban enforcement, and ban-evasion prevention
• To understand and improve the site: the aggregate analytics and usage log described above
• To comply with legal obligations, should any apply

7. Cookies and things stored on your device

Cookies

We use strictly essential cookies only. Two of them are set the first time you load any page, signed in or not, because our sign-in system checks for a session on every page:

• `__Host-authjs.csrf-token`, which protects forms against cross-site request forgery;
• `__Secure-authjs.callback-url`, which holds the address on this site that a sign-in or sign-out should return you to

When you actually sign in:

• a session cookie, a signed token that keeps you signed in, refreshed to 24 hours on each visit;
• while you sign in with Google, Discord or GitHub, a few short-lived functional cookies (one-time PKCE, state and nonce values) that make the redirect secure and are discarded once sign-in finishes

All of these are first-party and HTTP-only. There are no advertising cookies and no cookies that track you across other sites. Our analytics (section 6) are cookieless. Because every cookie above is strictly necessary to provide a service you asked for and to keep it secure, and the analytics set no cookie at all, the site does not show a cookie consent banner. If you block these cookies you will not be able to sign in or stay signed in

Stored on your device, not sent to us

The site also saves a few small values in your browser's own storage. These never reach our servers, and nothing on the site deletes them, so clearing your browser data is how you remove them:

• your 3D scene quality choice on the homepage, and whether you declined the prompt offering a lighter mode
• whether the homepage music is muted
• recently used colour swatches
• whether an admin sidebar group is open, for staff
• a flag set the first time you pass the hub's entry screen, so the one-off welcome is not shown again
• per tab, and cleared when you close it: that you dismissed the entry screen, and that the intro countdown already played

The Rocket Racing Archive sets no cookies at all. It stores four values in your browser: a short hash of its notice text so its card does not reappear once dismissed, the time of your last contribution so the form can ask you to wait, whether its intro animation has already played for you, and whether you muted that section's sound

8. Third-party services

• Google, Discord and GitHub (sign-in). If you sign in with one of these, that provider confirms your identity and shares your basic profile (name, email, avatar) with us. Your relationship with them is governed by their own terms and privacy policies. We also use a Google service account, server-side and read-only, to read our own site's Search Console statistics; no member data is sent to it
• GitHub (source code and scheduled jobs). Beyond sign-in, GitHub hosts this site's private source repository and runs our scheduled jobs, including the nightly backup described in section 9
• Vercel (hosting, analytics and performance). Vercel hosts the site, so every request you make reaches Vercel first: it sees your IP address and everything you send us, in the clear, on the way to the app, and handles that under its own privacy policy. Separately it provides the cookieless Web Analytics and Speed Insights described in section 6, which receive the page visited, the referrer, an approximate country, your device and browser type, and performance metrics, for every visit, signed in or not
• Supabase (database and file storage). Your account data, posts, and uploaded media are stored in a database and file storage hosted by Supabase, which acts as our storage provider and processes that data under its own privacy policy. The media bucket is public-read, which means an uploaded file is reachable by anyone who has its address
• Resend (email delivery). Account email and archive mail are sent through Resend. Your email address and the message contents pass through Resend so it can be delivered, and Resend handles that data under its own privacy policy
• Cloudflare (inbound email for the archive). Mail sent to the archive's own contact address is received by Cloudflare Email Routing and handled by a small program we run there, as described in section 6
• Google (Gmail). Cloudflare also forwards every message received at that address, in full, to a Gmail mailbox we operate
• Web3Forms (the archive contribution form). If you use the archive's contribution form, your browser sends a copy of your submission, including the optional contact field, directly to Web3Forms, which emails it to us. Because it goes from your browser, Web3Forms receives it independently of us and processes it under its own privacy policy
• Upstash (status page storage). Our status page keeps its records in Upstash, a hosted database service. It stores daily counts of how many automated checks found each component healthy, plus any incident notices we write. It holds nothing about visitors
• ipwho.is (IP lookup, while the entry scan is on). As described in section 6, signed-in members' IP addresses are sent to ipwho.is for a geolocation and provider lookup. It is an independent service with its own privacy policy. While the scan is off, nothing is sent to it
• Ko-fi (voluntary tips). The hub footer links to a personal Ko-fi page. We receive no payment data. If you choose to use it, everything after the click is between you and Ko-fi under their terms
• Externally hosted media. If a member posts media hosted on another website, your browser loads it directly from that website when you view the post, which, as with any image on the web, reveals your IP address to that host. Some images on our own pages work the same way and involve no member at all: the Discord server icons on our community page are loaded from Discord's CDN, and a profile picture from a sign-in provider is loaded from that provider, so your browser contacts those hosts when you open those pages, signed in or not

9. Backups

Every night an automated job takes a complete copy of our database and stores it with GitHub, which keeps it for 90 days before deleting it. Because it is a full copy of the database, it contains everything in section 6 that is held as data: account email addresses, password hashes, two-factor secrets and hashed backup codes, passkey records, any recovery phone number, IP and device records, moderation and audit logs, and everything posted

It does not contain the uploaded files themselves. Avatars, banners and media attached to posts live in separate file storage, which nothing backs up, so the backup holds the link to a file rather than the file. If that storage were lost, the posts would come back and the pictures in them would not

Backups exist so that a mistake or an outage does not destroy the community's work. It also means that when data is deleted from the live site, copies can survive in backups until those backups age out

10. Data retention and deletion

• Account data is kept for as long as your account exists
• You can request deletion of your account at any time. While the account is in good standing you can do it yourself from Settings > Account. If you are banned, or your network is blocked, that page is closed to you, so email contact@visionforceofficial.com and we will do it for you. Deleted accounts are deactivated and removed from public view
• Deleting your account clears your email address, password, recovery phone number, display name, avatar and banner links, bio, pronouns and region, removes your two-factor settings and any passkeys, and unlinks any Google, Discord or GitHub sign-in, which discards the stored OAuth tokens. You are removed from public view and can no longer sign in
• Your avatar and banner files are deleted too, not just unlinked. That matters because our media storage is public-read: a file that is only unlinked stays downloadable by anyone who kept its address, so deleting the account deletes the objects themselves
• Images attached to your posts stay, because the posts stay. Removing them would leave holes in conversations other members took part in. If you want them gone as well, ask us at contact@visionforceofficial.com, ideally before you delete the account, because afterwards we can no longer confirm they were yours
• Some records survive deletion, on purpose. Your username is kept, because it is the byline on everything you posted, and removing it would fill old threads with blanks; it is no longer attached to an email address or a usable account. Anything you posted, meaning posts, comments, suggestions and votes, stays on the site, so that conversations other members took part in do not collapse into gaps; it is no longer linked to a usable account or to any contact detail. Banned IP and device records are kept so bans remain enforceable, moderation audit logs are kept so past decisions stay accountable, and reports you filed or that were filed about you are kept for the same reason. So are your warning history and the word filter's records of content it flagged, which include a short excerpt of what was written and the name on the account at the time; a ledger of files you uploaded; and any API keys issued to the account, including a Rocket Racing Reborn access key. Ask us if you want any of those cleared as well
• If you want something you posted taken down as well, ask before you delete the account. Once it is deleted we can no longer confirm the content was yours
• Usage events record only an account reference, never your name or address, and that reference is detached when the account is deleted
• Entry scan records age out on their own. A flagged-scan entry in the detection log is deleted after 90 days, long enough to recognise a pattern of ban evasion across repeat visits and no longer. The per-address lookup cache is deleted after 30 days without being seen; separately, an entry still in use is refreshed about every 7 days, which is a freshness check rather than a deletion. You can also ask us to remove entries relating to you sooner
• Archive correspondence. A submission you send to the Rocket Racing Archive is kept indefinitely as a record of what was reported. Replies attached to it are deleted 14 days after the conversation is closed, and nothing is deleted within 14 days of arriving
• Rate-limit counters expire between a minute and an hour after they are written, depending on what is being limited, and are cleared opportunistically. The sign-in counter's key contains the IP address together with the email address or username that was typed
• Backups hold copies of deleted data for up to 90 days, as described in section 9

11. Your rights over your data

If you are in the UK, the EU, or Switzerland, data protection law gives you rights over information about you, and we will honour them wherever you are:

• See it. Ask for a copy of what we hold about you
• Correct it. Most of it you can edit yourself in your profile; ask us for anything you cannot reach
• Delete it. Delete your account yourself. Your avatar and banner files and your current entry-scan record go with it automatically. Ask us for the things that do not: images attached to posts you made, and flagged-scan entries in the detection log, which otherwise age out after 90 days
• Object or restrict. Tell us to stop using your data a particular way, and we will unless we have a reason we can point to
• Take it with you. Ask for your content in a portable form

Write to contact@visionforceofficial.com. We will answer within a month. If you are unhappy with how we handle it you can complain to your data protection regulator, which in the UK is the Information Commissioner's Office at ico.org.uk

12. Meridian, the launcher

Meridian is a free, optional Windows program we make for playing Rocket Racing Reborn. You never need it to use this site, and nothing here changes if you never install it. It is only offered to members who have been granted access.

Windows only. There is no macOS or Linux build, and there is unlikely to be one: the launcher works by changing Windows-specific things on your machine, and the game itself is a Windows build.

Meridian signs you in, it never signs you up. Accounts are created here on the website and nowhere else.

Because the game was built to talk to Epic's servers, the only way to point it at ours is to change some things on your computer while you play. All of it is listed below. Closing the launcher normally undoes the changes, with two exceptions named at the end of this section.

What it changes while you play

• A certificate. Meridian creates a certificate authority on your machine and adds it to your user account's trust store, not the computer's. It is restricted to five Epic domains (`ol.epicgames.com`, `ak.epicgames.com`, `on.epicgames.com`, `game-social.epicgames.com` and `epicgames.dev`) and cannot vouch for any other site or for any IP address. Meridian refuses to install one that is not restricted. It is removed when you close the launcher
• Your hosts file. Around 119 Epic service names are pointed at your own computer so the game reaches us instead. This needs Administrator, so Windows asks your permission twice per session, once to apply it and once to undo it. The work is done by a small separate program, `meridian-hosts.exe`, so that the rest of the launcher never runs with those rights
• A local server. A bundled copy of Node runs on your machine and answers those redirected names on ports 443 and 80. Traffic between the game and us is decrypted there, on your computer, so it can be translated for our servers. That includes the sign-in tokens the game uses
• Running programs. When you press Launch, and again when Meridian exits, Meridian closes the Epic Games Launcher, Fortnite, and the anti-cheat helper processes. Any unsaved state in those is lost. Simply opening the launcher closes nothing. It also starts the game with two helper processes deliberately frozen
• The game process. Meridian loads our code into the running game. This is the technique antivirus and endpoint security products are built to notice, so yours may warn you or block it

What it deliberately does not touch

• Anything not on that list of 119 names passes through untouched, with no certificate substitution. Your browsing is unaffected
• Epic's payment site, `accounts.epicgames.com`, `www.epicgames.com` and the anti-cheat download servers are on a list that is never intercepted, as is any address whose name begins with `ocsp` or `crl`, which is how certificate revocation is checked. That last one is a rule about the name rather than a list we maintain, so a revocation responder named some other way is not covered by it
• Epic's telemetry addresses are intercepted specifically so that your gameplay telemetry does not reach Epic. We do not store it either, it is discarded
• One address, `api.epicgames.dev`, is allowed through to the real Epic servers for requests we do not answer ourselves. This is on by default and can be turned off in the launcher, at the risk of the game not starting

What it keeps on your computer

Two folders, not one, and deleting one does not empty the other.

`%LOCALAPPDATA%\RocketRacingReborn` holds your settings, the certificate and its private key, and logs from the local server and from the game. In plain text in those settings are the key the local server uses to reach our backend and the password your game client signs in with. Treat that folder as you would any file containing a password.

`%LOCALAPPDATA%\com.visionforce.meridian` holds the launcher's own browser storage, and that is where the key you paste at sign-in is kept, along with the email address on your Vision Force account.

One more thing is left outside both: a copy of your original hosts file, saved as `hosts.rrr-backup` next to the real one in `%SystemRoot%\System32\drivers\etc`. It is plain text, it holds nothing about you, and nothing removes it.

If it does not shut down cleanly

Before the first change to your hosts file, Meridian asks Windows to restore the original at your next restart. If the launcher is ever killed rather than closed, your hosts file repairs itself on reboot without any of our software running.

The certificate is not covered by that. It is removed only when Meridian closes normally, so a launcher that was killed leaves it in your user's trust store until the next time you run and close Meridian. It stays restricted to those five Epic domains the whole time. You can also remove it yourself at any point with `certutil -user -delstore Root "Rocket Racing Reborn Local Root CA"`.

13. What you are actually running

Read this part before you install anything.

You do not sign in to Epic, and we never ask you to

Rocket Racing Reborn does not use Epic accounts. When the game starts, it signs in against our server with a display name you choose in the launcher, and our server identifies you by that name alone. At no point do you give Epic credentials to us, to the launcher, or to the game, and the launcher closes the Epic Games Launcher if it is running.

Some traffic still reaches Epic while you play: asset downloads, the anti-cheat module download, voice servers, and one address, `api.epicgames.dev`, for requests we do not answer ourselves. No Epic account is involved in any of it, because there is not one to involve. One thing does travel with those last requests, and we would rather say it than let you find out: they are passed on carrying the sign-in token our own server issued you, and the display name you chose is readable inside that token. If you would rather nothing at all left your machine, that fallback can be switched off in the launcher, at the risk of the game not starting.

The game files are still Epic's

The build you play is Epic Games' software. Your right to have it and run it is whatever your own licence for it says, and this project does not grant you one. We do not distribute Epic's game files, and nothing here changes your obligations to Epic in respect of the copy you already have.

Anti-cheat is switched off, and what that means for you

To let our code run inside the game, Meridian starts it with EasyAntiCheat and BattlEye disabled and closes those programs if they are running. That is not a risk to an Epic account, because no Epic account is signed in anywhere in this. It does mean two other things, and they are worth being clear about:

• You are trusting us with code inside the game process. The protection that would normally stop a program doing that is deliberately off, so what runs there is whatever we ship. Our launcher is the only thing that should be loading anything, and you should get it from us and nowhere else
• Do not use anything from this project against Epic's own services, or against other players anywhere else. Playing a preserved game on our servers is the point; taking the parts that make it work and pointing them at a live service is not, and it is the fastest way to end the project for everybody

If that trade is not one you want to make, do not install the launcher. Nothing else about your membership here changes.

14. Game data, and where the servers are

Playing creates data that lives separately from your website account, on a server we rent in London from Fly.io, not in the database behind this site.

Where the racing actually happens, today. That London machine serves your account, your progress and matchmaking, so menus and loading depend on how far you are from Europe. The race itself does not run there. In the current build it runs on your own PC, which is the honest state of a preservation project still being built rather than a live multiplayer game.

That is also why we are not yet asking where to put servers. When racing moves off your machine, distance will start to matter, and running machines closer to more people will be a cost question on a project with no income rather than a technical one. This section will be rewritten before any of that goes live.

What is kept on the game server:

• a player record identified by your in-game display name
• your progress: cosmetics, in-game currency, quests, and gift boxes, which can contain short messages written by other players
• server logs of every request made while you play: the address asked for, the program that asked, and the network address the request arrived from. Because the server sits behind Fly's proxy, that last one is currently Fly's own address rather than yours

Two things you should know about it:

• The game server does not check passwords. It was built to talk to a game client, not to a browser, and a player is identified by their display name alone. Treat anything you put into the game as public, and do not put anything private in a display name or a gift message. Messages other players send you are their content, and sections 3 and 4 apply to them exactly as they do on the site
• Deleting your website account does not delete your game data, because the two systems are separate. The backups, retention and deletion described in sections 9, 10 and 11 cover the website only. If you want your game data removed, email us at the address in section 16 and we will do it by hand

Section 8's list of services we rely on should be read as including Fly.io, a United States company, for the game server, its player data and its logs. The machine we rent from them is in London.

15. Disclaimers and limitation of liability

• This is a volunteer hobby project. The site is provided "as is" and "as available", without warranties of any kind, express or implied, including availability, accuracy, or fitness for a particular purpose
• We may change, suspend, or shut down the site, or any part of it, at any time. Please keep your own copies of anything you care about
• Content posted by members reflects the views of its authors, not of the project team
• To the fullest extent permitted by law, we are not liable for indirect, incidental, or consequential damages arising from your use of the site. Nothing in these terms excludes or limits liability that cannot be excluded or limited under applicable law

16. Changes and contact

• We may update these terms from time to time. Material changes are announced on the site, and when a new version is published you will be asked to review and accept it before continuing to use your account. Continued use of the site after a change means you accept the updated terms
• The current version is always available on the Terms page of this site
• One address for everything that needs a human: questions, account deletion, moderation and ban appeals, security reports, rights-holder complaints and privacy requests all go to contact@visionforceofficial.com. It is shown on our contact page, which you can reach without signing in and while you are banned

By continuing to use Vision Force Projects, you confirm that you have read and agree to these terms