Privacy Policy

This is our Privacy Policy, written in plain language so it can actually be read. It covers what we collect when you visit, sign up, post, apply for anything or write to us, why, how long we keep it and what you can ask of us. It sits next to the Terms of Service, and Cookies and local storage covers what the sites keep in your browser

1. Who we are and what this covers

Vision Force Studio is a fan team of community volunteers running a hobby project. This policy covers visionforceofficial.com and everything on it, including create.visionforceofficial.com, meridian.visionforceofficial.com and status.visionforceofficial.com, the Rocket Racing Archive's contribution form and contact address, VF Communities and the VF Relay bot, and the parts of Project Overdrive and the Meridian launcher that talk to us. The Project Overdrive access terms describe in more detail what the launcher keeps on your own computer and what the game server keeps

Who is responsible for your data. Vision Force Studio decides why and how the data described here is used, which makes us its "controller" under data protection law. Every question or request about it goes to contact@visionforceofficial.com

Children. You must be at least 16 to have an account, as the Terms of Service explain. We do not knowingly keep data about anyone younger: an account we find to belong to someone under 16 is removed, and if you think we hold data about a child, tell us and we will delete it

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

2. What we collect and why

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
• If you link Discord, the Discord account's identifier is also what VF Communities uses to check that you run a server you apply for, as section 3 explains

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 the Terms of Service explain

What you write when you apply for anything on the site is covered in section 3

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

Status page updates, if you subscribe

The status page lets anyone ask to hear about incidents, with no account:

• By email. We keep the address you give, whether you have confirmed it, when you subscribed and when we last sent you a confirmation mail. Apart from that one confirmation mail, nothing is sent to an address until its owner presses the button behind the confirmation link, and the button behind the unsubscribe link in every mail deletes the address from the list
• By webhook. We keep the address of the receiver you register and, if you leave one, a contact email we write to if we ever drop that receiver after repeated failed deliveries

These are kept in the status page's own store at Upstash and sent through Resend, both described in section 4

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 4); 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 specific actions, namely opening a report, disconnecting a sign-in provider, sending a creator application, a Project Overdrive request or a VF Communities application, generating a game key, the yes or no notes the send button records (section 3), and staff actions on API keys, game access, game keys, players and game settings, VF Communities and our Discord bot. 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. They are part of running the account safely and cannot be switched off while the account exists
• Application email is transactional too. When you send a creator application, a Project Overdrive request or a VF Communities application, we email an acknowledgement and then our decision. Project Overdrive also mails you if a member of staff invites you, pauses your access or ends it, and VF Communities mails you at every step of a server's application and listing, as the VF Communities terms list
• 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 4)

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 7 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

Decisions made automatically

A few things here are decided by software before a person looks:

• The word filter can warn, mute, temporarily remove or permanently ban an account, and refuse a username or profile field, as the Community Guidelines describe. An automatic removal or ban also blocks the IP addresses and device signatures the account was seen from
• A VF Communities application that fails one of the fixed checks on its invite or server is turned down automatically, with the list of what to fix, and can be sent again as soon as it is fixed
• A relayed Discord post that trips the filter or one of the relay's checks is held until a moderator looks at it. Nobody is punished for it

The entry scan and the notes the send button records never decide anything on their own: they are shown to staff, or to you. Creator applications and Project Overdrive requests are always decided by a person. If an automatic decision affected you, write to contact@visionforceofficial.com and a person will look at it again

Where we get data from, other than you

• Google, Discord or GitHub, when you sign in with them: your basic profile, as above
• Discord, for VF Communities: what it says about a server and the person who made an invite, the public profiles of applicants and server owners, and the announcements we relay, written by people who may never have heard of us
• ipwho.is, while the entry scan is on: the country, timezone and internet provider of your IP address
• Vercel, our host: the approximate country and time zone of the network a request comes from
• Project Overdrive's game server: the in-game names of the players who are online, for the launcher's player list

Why we process this data, and on what basis

• To provide what you signed up for or asked us for: accounts, sign-in, sessions, account and application email, showing your content, and handling the applications in section 3. We do this because it is needed to give you the service our Terms of Service describe
• To keep the community and the service safe: moderation, the word filter, ban enforcement and ban-evasion prevention, the IP and device records, the entry scan, rate limits, the send button's checks, and the checks on VF Communities applications and on relayed posts. We do this because we have a legitimate interest in protecting the people who use the site and the site itself
• To run VF Communities: looking up the servers that apply and showing the announcements of the ones we list. We do this because the server asked to be listed, and we have a legitimate interest in running the directory it asked to be in
• To answer archive corrections and send status updates: because you sent the correction or subscribed, and confirmed your address
• Notification email, which you switch on yourself in your profile: because you agreed to it, and you can switch it off at any time
• To understand and improve the site: the aggregate analytics and usage log described above, and the nightly backup in section 6. We have a legitimate interest in knowing how the site is used and in not losing the community's work
• To comply with legal obligations, should any apply

Where we rely on a legitimate interest, you can object, as section 8 explains

Aetherion, our Discord bot

Aetherion is a bot that lives only in the Rocket Racing Revive Discord server. It is separate from these websites, and staff configure it from the admin console. It welcomes new members, runs support tickets, and has an AI chat: when you talk to that chat, the message you send is passed to our AI provider, Anthropic, so it can write the reply. Anything Aetherion keeps stays with the bot, not in the website's database. To have something you said to it removed, write to contact@visionforceofficial.com

3. Applications you send us

Some things on the site are asked for rather than used: a place in the creator programme, access to Project Overdrive, and a listing in VF Communities. Each one needs a signed-in account with an email address and a username, and each one keeps what you wrote until you ask us to remove it, as section 7 explains

The creator programme

• What we keep. What you want to build, which is the only required answer, and anything else you add: a link to your work, your Discord handle, your Epic creator code, the codes of UEFN islands you have published, what you have built before, where you are, and roughly how many hours a week you expect to give. We also keep the decision with any note attached to it, who made it and when, how many times you have applied, and the date a rejected application can be sent again
• Your links are only ever links. Our server never opens, previews or fetches the address you give. A person reviewing your application opens it in their own browser
• Who sees it. Staff at moderator level or above, in the admin console. When you send it, a copy of everything you wrote, with your username, is also emailed to our team inbox. Unless we set another address, that inbox is a Gmail mailbox we operate, so Google receives a copy
• The Creator programme terms cover the rest

Project Overdrive access

• What we keep when you ask. What you wrote on the request 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, who made it and when, and how many times you have asked. New requests are closed while the project is in development; requests already sent keep their place
• If you are let in. The key you generate to sign in to the launcher is stored only as a hash. A second key, which lets your computer past the game server's front door, is stored encrypted rather than hashed, because the game server has to be handed the actual value to check it, together with your in-game account number and the name you go by in the game. While the launcher is open and signed in it also tells us, about once a minute, which version it is and whether the game is running, and we keep only the latest of those
• Staff at supermod level or above decide requests and manage players. The Project Overdrive access terms explain the launcher, the keys and the game server in full

VF Communities

When you apply for a Discord server, we keep:

• What you send: the invite link from the server's Announcement channel, an optional separate join link, your role in the server as you describe it, your answers about how the server is Rocket Racing related and about the server itself, the optional line for the directory, and when you ticked the box confirming you read the guide
• What Discord says about the server through that invite: its name, icon, banner and splash images, description, creation date, member and online counts, features, verification and NSFW levels, boosts, vanity link if any, and the channel the invite was made from. Discord also tells us who created the invite: their Discord ID, username, display name and when their account was made
• About you: the Discord ID of the account linked to your Vision Force account, and, looked up by our bot, that account's public profile: username, display name, avatar and when it was made. We also note when you joined Vision Force and how many other servers you have applied for. Every automatic check we ran and its result is kept with the application
• Once our bot is in the server: the owner's Discord ID and public profile, whether you are a member there, whether you are the owner or hold Administrator or Manage Server, the names of your roles in that server and when you joined it. That is how we know you run it
• If we switch on the optional Discord proof: you sign in to Discord once and allow us to read your list of servers. We read it to find this server and store only the answer, meaning your Discord ID, whether you own the server or can manage it, and when we checked. The access Discord gives us for this is used for those reads and then dropped, never stored
• If someone else applies for the same server while its application is open, their answers and their linked Discord ID are kept on that application, at most the newest five, so staff can sort out who runs it
• A history of every step and every staff action on the application, with the checks, the post-join reports and whether each email went out. It can name Discord IDs. After a no or a revoked listing we also keep, per server and person, the date you can apply again, together with your linked Discord ID, until that date passes
• Who sees it. Staff at moderator level or above can read the queue and turn applications down; approving, revoking and controlling the relay are for supermods and above. New applications, applications sent again and competing claims are emailed to our team inbox with your username, the server's name, ID, counts and creation date, the checks that need a closer look and your two answers. Unless we set another address, that inbox is a Gmail mailbox we operate, so Google receives a copy

Once a server is listed, VF Relay copies the announcements of its public Announcement channels onto a public page here, with each poster's Discord display name and avatar. We also keep each poster's Discord ID, which is not shown on the page. People who post in those channels are not necessarily Vision Force members at all, so the VF Communities terms explain exactly what is relayed, what is shown, how long it stays, and how a post or a server comes off the site

Sending an application

Our application forms send when you press and hold the button. While it holds, your browser sends our server three things: which form it is, your browser's time zone name and your device's clock time. Our server then checks that you are still signed in, that your account and your current network are not restricted and that your account has an email address. It also compares your clock with ours, compares your time zone with the one our host reports for the network you are connecting from, and looks at whether an earlier entry scan already found your address to belong to a data centre or proxy. It never looks your address up just for this

The last three never stop a send, because plenty of honest people travel, use a VPN or never fixed their clock. When one of them is off, you see a note, and we write one entry to the event log holding your account reference, which form it was and three yes or no answers: clock off, time zone mismatch, data centre. Your time zone names, your clock time and your IP address are not stored

4. 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
• Discord (VF Communities and VF Relay). Our server asks Discord about the invites people paste into the VF Communities form, and our VF Relay bot reads the servers that applied and were listed, as section 3 and the VF Communities terms describe. If we switch on the optional Discord proof, that sign-in goes through Discord with the same app you sign in to Vision Force with
• 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 6
• 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 2, 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, application email, archive mail and status page 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 2
• Google (Gmail). Cloudflare also forwards every message received at that address, in full, to a Gmail mailbox we operate. Our team alerts about creator applications and VF Communities applications go to a Gmail mailbox too, unless we set another address
• 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 and any incident notices we write, and, if you subscribe to updates, the email address or webhook described in section 2
• ipwho.is (IP lookup, while the entry scan is on). As described in section 2, 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
• Fly.io (the game server). Project Overdrive's game server, its player data and its logs run on a machine we rent from Fly.io, a United States company, in London, as the Project Overdrive access terms describe
• 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. The same goes for the avatars of people whose posts are relayed onto a community page and the images in those posts, which we do not copy, and for a few pictures on our documentation pages that are loaded from other websites

5. Where your data is processed

The server code of visionforceofficial.com, including VF Relay, which has no server of its own, is set to run in Vercel's Stockholm region, while Vercel delivers pages from its network around the world. The game server is in London. The providers in section 4 may handle your data in other countries, including the United States, under their own terms. Ask us if you want to know where a particular kind of data goes

6. 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 2 and section 3 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, applications, relayed posts, 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

The status page's store at Upstash is separate from our database and is not part of this backup

7. Data retention and deletion

• Account data is kept for as long as your account exists. So are the IP addresses and device records described in section 2, which go when the account is deleted, apart from banned ones
• 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 Project Overdrive launcher key. Ask us if you want any of those cleared as well
• Applications survive deletion too. Your creator application, your Project Overdrive request with your game key and the launcher's last report, and any VF Communities application with its history stay as they were, linked to the account that sent them. A deleted account can no longer play: its keys stop being accepted. A listed server whose applicant deletes their account or is banned has its relay paused, and the Discord details we looked up about that applicant, including any Discord proof, are cleared. Ask us if you want the rest removed
• 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
• Applications. A rejected application, whether for the creator programme, Project Overdrive access or VF Communities, is deleted six months after the decision, with its history. If the rejection set a wait before you can apply again and that wait is still running, it is kept until the wait is over. Other applications are kept, with their history, until you ask us to remove them
• Relayed posts. When a post is deleted on Discord, it disappears from our pages. Its text and the rest of what we kept about it stay in our database, hidden from everyone. The VF Communities terms have the detail
• The relay's own records. The record of each relay run is deleted after 14 days, and a wait before applying again once it has passed
• Status page subscriptions are kept until you unsubscribe with the link in any mail, and an address that never confirmed stays on the list until it is removed by hand. A webhook is kept until it is removed with its own link, or dropped after 20 failed deliveries in a row
• Rate-limit counters expire between a minute and a day 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, and the password-reset counter's key contains the IP address. The limits on applications and game keys, which are the ones that run for up to a day, are keyed on your account, never on your address
• Backups hold copies of deleted data for up to 90 days, as described in section 6

8. 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, flagged-scan entries in the detection log, which otherwise age out after 90 days, and the applications in section 3
• 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
• Change your mind. Where we rely on your agreement, such as notification email or a status subscription, you can withdraw it at any time, and that does not undo what was done before
• Ask a person. If a decision made automatically, as listed in section 2, affected you, ask and a person will look at it again

These rights are not only for members. If your Discord posts were relayed onto one of our community pages, or you wrote to the archive or subscribed to status updates without an account, you can ask the same of us

Write to contact@visionforceofficial.com. We may ask you to show the request comes from you, for example by writing from the address on your account, so that we never hand your data to someone else. 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, and in the EU is the data protection authority of the country where you live or work

9. Changes and contact

We may update this policy from time to time. When a new version is published, signed-in members are asked to confirm they have read it, as the Terms of Service explain. Confirming that you have read this policy is not consent to anything in it; where we rely on your consent, we ask for it separately. Questions and privacy requests go to contact@visionforceofficial.com, which you can reach from our contact page without signing in and while you are banned