Privacy Notice

In force from 29 October 2026

This notice explains what personal data Switch collects, why, who receives it, how long we keep it, and your rights under the EU General Data Protection Regulation (GDPR).

1. Who is responsible

The controller is Fallon Ough, trading as "Switch", Julius-Raab-Straße 10, 4040 Linz, Austria.
E-mail: support@getswitch.net · Phone: +43 660 2945061
We don't have a data protection officer. Write to the e-mail address above with any privacy question.

2. The short version

We collect what we need to sell you a licence, deliver it, enforce it, run your account if you create one, and meet tax and consumer law.
We don't sell your data, and we don't use it for advertising.
We don't collect your Roblox username or your Roblox account details. We collect gameplay data only if you turn on play statistics on your account page (section 3). Max also sends the ID of the Boxing Beta server you're in, which our server turns into a one-way code at once, so other Max users can find you (section 3).
Stripe handles your payment. We never see your full card number. If you pay with a wallet such as PayPal, that provider handles it too.
If you pay with crypto, the payment goes through our own payment server, without a payment provider. Payments on a blockchain are public and can't be deleted.

3. What we collect, and why

Data	What we use it for	Legal basis (GDPR)
E-mail address	Sending your key, order confirmation, receipts and notices about your order or subscription. Answering you.	Art. 6(1)(b) contract; Art. 6(1)(c) legal obligation (receipts)
Country; in the US also state and ZIP code	Checking we can sell to you. Showing the right currency. Tax records (VAT and US sales tax).	Art. 6(1)(b); Art. 6(1)(c)
Date of birth	Checking you're 13 or over, and 18 or over for a subscription.	Art. 6(1)(b) (which contract we can make with you); Art. 6(1)(f) (protecting minors; avoiding contracts that aren't valid)
IP address and browser details at checkout, and when you buy an extra PC reset on your account page	Proving when and how you gave your consents. Preventing fraud. Location evidence for tax, where the law requires it. Limiting repeated attempts on our order, sign-in, cancellation, withdrawal and creator pages: for that we keep only keyed hashes of your IP address and, on the sign-in, cancellation and withdrawal pages, of the e-mail address you give, for at most two days.	Art. 6(1)(f); Art. 6(1)(c)
Consent records: the boxes you ticked, their exact wording, the time, your IP address, the terms version	Proving your consent to immediate delivery of your key and to automatic renewal, and, when you buy an extra PC reset, your request that we do it right away.	Art. 6(1)(c) where a law requires us to keep them; otherwise Art. 6(1)(f)
Order and subscription records: plan, price, currency, dates, status, renewals, cancellations, withdrawals and how we handled them, receipt numbers, and the extra PC resets you buy	Performing the contract. Keeping the books.	Art. 6(1)(b); Art. 6(1)(c)
Payment data	Stripe processes your payment. We receive the payment's status and amount. For cards, also through Apple Pay or Google Pay, we receive card details such as the brand, the issuing country and the last four digits; for other methods, only the method's name.	Art. 6(1)(b)
Card fingerprint (card payments only): a code Stripe derives from your card number. It doesn't reveal the number.	Making sure creators don't earn a commission on their own orders.	Art. 6(1)(f)
Crypto payments, if you pay with crypto: the invoice, the coin and amount, the payment address, the transaction ID, and when the payment was confirmed	Performing the contract. Keeping the books.	Art. 6(1)(b); Art. 6(1)(c)
Licence key. We also keep it encrypted, so your account page can show it.	Giving you access and recognising your licence. Showing it to you on your account page.	Art. 6(1)(b)
An identifier of your PC: the hardware ID (HWID) your executor provides or, if it has none, Roblox's device ID. We store only a hash of it, never the ID itself.	Locking your licence to one PC, as the licence requires. Handling HWID resets. Spotting shared keys.	Art. 6(1)(b); Art. 6(1)(f) (preventing key sharing)
Creator link, if you come to our website through one and order within 24 hours: whose link it was, and the hour you arrived. The link is carried only in the address of the pages you open; we store nothing in your browser for it.	Paying that creator a commission. Counting the clicks on each creator's link per day, without recording who clicked: we leave out bots, recognised by the browser's name, and repeated clicks, recognised by a keyed hash of your IP address that we keep for at most a day. The creator sees only totals per month, never who you are.	Art. 6(1)(f) (running our creator program)
Creator invite, if you join our Discord through a creator's invite: your Discord user ID, which invite you joined through, and when. If you order within 24 hours after joining, and your key is linked to that Discord account: whose invite it was, and the hour you joined, kept with the order.	Paying that creator a commission. Counting, per creator and day, how many people joined through their invite. The creator sees only totals per month, never who you are.	Art. 6(1)(f) (running our creator program)
Discord user ID, if you link your key in our Discord or connect Discord on your account page	Giving you your Discord roles, among them your plan's role (Basic, Pro or Max), from which our support bot marks Pro and Max tickets as Priority, and, for 7 days after your last paid key runs out, the role that lets you post in #reviews; letting you reset your HWID; showing your licence there. Also, if you joined through a creator's invite, matching your order to it (the row above).	Art. 6(1)(b), at your request; Art. 6(1)(f) for a creator's invite and for posting in #reviews after your key runs out
Ping roles, if you pick them in our Discord: your Discord user ID and the ping roles you have	Pinging you about the updates you chose.	Art. 6(1)(b), at your request
Your data in our Discord server, if you join it: your Discord user ID, username, avatar, when you joined, and your messages there, as the bots others run in our server process them (section 8)	Keeping the server safe from spam and raids.	Art. 6(1)(f) (a safe server)
Member backup, if you verify in our Discord server: your Discord user ID, our server, and your authorization for our verification app to add you to a Discord server (Discord shows it as "Join servers for you"). RestoreCord keeps them (section 8).	Bringing you back to our community if we ever lose our Discord server. We'd use the authorization only to add you to the server that replaces ours, never to any other. New members verify to see most of our server (section 6).	Art. 6(1)(f) (being able to bring our community back)
Bug reports and ideas, if you post them in our Discord: in #bug-reports and #ideas, open to everyone with a live key, or in #testers, for testers. What you post there, files included, with your Discord name	Fixing problems and improving Switch.	Art. 6(1)(f) (making Switch better)
Reviews, if you post one in our Discord: in #reviews, where everyone with a live key, or with a paid key that ran out in the last 7 days, can post and everyone in our server can read. What you post there, with your Discord name, and whether we gave you your key free or you're a tester, creator or one of our staff, as things were when you posted	Letting buyers tell others what they think of Switch; making sure a review says so when we gave the key free, and that testers, creators and staff don't post reviews.	Art. 6(1)(f) (sharing buyers' reviews and keeping them honest)
Usage records: when the agent was first delivered to your key, when it was last used, the dates it was used, and how many different PCs your key has been used on	Evidence if a payment is disputed, for example as "not received". Checking, if you withdraw, whether the licence was already used. Spotting shared keys.	Art. 6(1)(f)
The code in each model we send: each copy of an agent's model carries a code derived from your licence key (section 14). We record which model versions each key received, and the first and last day we sent each one; that record holds no IP address, no PC identifier and no copy of the model.	Tracing copies shared without permission to the key they were sent to, and acting on that under our Terms (sections 17 and 18).	Art. 6(1)(f) (protecting our models from being shared without permission)
Connection data on the licence server: in its web server's request logs, your PC's IP address and the time of each request, with technical details: the address requested, the type of request, the result, the size of the answer and how long it took. The address requested can include an internal licence ID or your Discord user ID, but never your licence key.	Delivering the model. Protecting our server.	Art. 6(1)(b); Art. 6(1)(f)
Withdrawal and cancellation declarations	Acting on them, confirming them and being able to prove them.	Art. 6(1)(c); Art. 6(1)(f)
Support messages and anything you send us, by e-mail or in a support ticket in our Discord. For a ticket, our support bot keeps a record: the messages as they stand when the ticket closes (the newest 5,000), the files attached (for text files, files in forwarded messages and files past 50 or 100 MB a ticket, only their name, size and type), the ticket's reason and form answers, who opened, claimed and closed it and when, and the Discord user ID, username and display name of everyone taking part. It removes anything that looks like a licence key first.	Answering you, fixing problems, handling warranty claims, and keeping a record in case of a dispute.	Art. 6(1)(b); Art. 6(1)(f)
Account, if you create one: your e-mail address; your Discord user ID if you sign in with Discord or connect it; when you created the account and last signed in; your sign-in sessions, without your IP address or browser details; and a record of when your key was shown, when its PC lock was reset, when you connected or disconnected Discord, and when you turned play statistics on or off	Showing you your orders, your key and, if you're a creator, your stats. Letting you reset your key's PC lock, cancel a subscription and connect Discord for your buyer role. Keeping your account secure.	Art. 6(1)(b); Art. 6(1)(f) (the security record)
Play statistics, only if you turn them on in your account: for each session your AI plays, which AI it was, when it started and how long it ran, and, where your AI reports them, how many games it played and how many it won; and whether your AI is running now	Showing them to you on your account page, and nothing else: we don't use them as evidence in payment disputes, add them up across buyers or use them in advertising.	Art. 6(1)(b), at your request
Your Boxing Beta server, as a one-way code, if you use Max (a partner's free trial key too): while you're in a Boxing Beta matchmaking server, the script sends the licence server that server's ID together with your session's reference (no Roblox name and no Roblox user ID). The server turns the ID into a one-way code at once and doesn't store or log the ID. It keeps the code and your session's reference in memory for two minutes, never on disk.	Telling a Max user who asks about that server whether another Max user is there, so that the Avoid Switch option works. We send it whether or not you turned the option on, because that's how other Max users find you.	Art. 6(1)(b) where you turned the option on; otherwise Art. 6(1)(f) (making Avoid Switch work between Max users)
Free keys, if we give you a key free of charge: your e-mail address, the plan, its dates, and our own note on why we gave it	Giving you the key, e-mailing it to you, and showing it on your account page.	Art. 6(1)(b)
Trial keys from a partner, if another script hub gave you one of our free trial keys: the plan, its dates, and which of our partners and batches it came from. Its other records are as for any key (above). The partner tells us nothing about you, and we tell the partner nothing about you, except how many of its keys were used.	Giving you the trial, ending it, and running and ending the promotion.	Art. 6(1)(b); Art. 6(1)(f) (running promotions with other script hubs)
Our record of support actions: what we did on your order, key or account through our admin panel, when, why, and which of us did it (by an internal code, not a name)	Being able to show what support did and why, and keeping our admin access secure.	Art. 6(1)(f)
Website visits: IP address, browser, pages, time (server logs at our host). The same when your e-mail app loads the logo and fonts in our e-mails from our website; we don't use that to tell whether you read them.	Delivering the website and keeping it secure.	Art. 6(1)(f)

Our legitimate interests (Art. 6(1)(f)) are: proving what was agreed or discussed, preventing fraud and key sharing, tracing copies of our models shared without permission, defending disputed payments, protecting our server, improving Switch with the bug reports and ideas you post, sharing the reviews buyers post and keeping them honest, running promotions with other script hubs, making Avoid Switch work between Max users, and keeping minors out of contracts they can't make.

4. What we don't collect

Your Roblox username or Roblox account details.
Gameplay data from your matches, unless you turn on play statistics (section 3). Even then, nothing about other players (no names, no opponents, no chat), and never your in-game rating.
Your full card number or bank details. If you post something that looks like a card number or IBAN in a support ticket, our support bot removes it as soon as it sees it and never stores it.

5. Where the data comes from

From you: at checkout, on the withdrawal and cancellation pages, and in support messages, by e-mail or in our Discord.
From Stripe: about your payment.
From the Switch script on your PC: your key, an identifier of your PC (section 3), which AI to load, and when the agent is delivered. While the agent runs, the script also checks in every few minutes. If you turn on play statistics, we also keep which AI ran in each session, and the script sends the games your AI reports it played and won. With Max, also the ID of the Boxing Beta server you're in (section 3).
From another script hub, if it gave you one of our trial keys: nothing about you. It only hands you the key; the Switch script then sends what it sends for any key.
From Discord, if you sign in to your account with Discord or connect it there: only your Discord user ID.
From Discord, if you link your key or open a support ticket there: your Discord user ID and username, and for a ticket also your display name. If you join our Discord server, Discord also sends your details and messages there to the bots others run in our server (section 8).
From Discord, if you verify in our Discord server: RestoreCord receives your Discord profile, such as your user ID, username and avatar, and the authorization you give our verification app on Discord's screen (section 8).

6. Which data you have to give

To buy, you must give your e-mail address, your country (in the US also state and ZIP code) and your date of birth, and tick the required boxes. Without them we can't sell to you.
To use the licence, the script must send your key and an identifier of your PC. Without them the licence can't work.
Linking Discord is optional.
In our Discord server, new members verify with RestoreCord (section 8) to see more than #start-here, #rules, #verify, #contact and #licence, so support tickets and our bot's licence panel work without it. Members who were in the server before verification started don't have to verify, but can.
An account is optional. You don't need one to buy.
Play statistics are optional and off unless you turn them on.

7. Automated decisions

At checkout, automatic checks decide:
- whether you can buy (your age and your country);
- whether you can subscribe (18 or over).
These checks are necessary to make the contract (Art. 22(2)(a) GDPR).
You can ask for a person to review a decision, give your point of view, and contest it. Write to support@getswitch.net.

8. Who receives your data

Stripe, our payment provider. Stripe processes payment data for us. It also uses it as an independent controller for its own purposes, such as preventing fraud and meeting its legal duties. Our Stripe contracting entities: Stripe Payments Europe, Limited and Stripe Technology Europe, Limited, both in Ireland. Stripe's privacy policy: https://stripe.com/privacy
The wallet or payment service you choose at checkout (Apple Pay, Google Pay, PayPal, Revolut Pay or Amazon Pay), if you pay with one. It processes your payment as an independent controller, under its own privacy policy, which also explains where it processes data.
Vercel Inc., 440 N Barranca Avenue #4133, Covina, CA 91723, USA. It hosts our website and our payments backend.
The hosting provider of our crypto payment server, if you pay with crypto once checkout offers it. It runs the server for our own crypto payment page (BTCPay Server), which we operate ourselves. The payment itself is public on the blockchain: anyone can see a transaction and its addresses, and nobody can delete them. We don't publish which transaction belongs to which order.
Resend (Plus Five Five, Inc., USA), which sends our e-mails from its servers in Ireland.
Our e-mail provider, which hosts our support mailbox, where your e-mails to us arrive.
Neon (Databricks, Inc., USA), which stores our order, consent, subscription and account records on its servers in Frankfurt, Germany.
A hosting provider in the EU, which runs our licence server and our Discord bots in Finland. It holds keys, hashed PC identifiers, usage records, the record of which model versions each key received, play statistics if you turn them on, support ticket records and server logs, and delivers the models.
Discord, if you sign in with Discord, use our Discord bots or a support ticket there. If you sign in with Discord, Discord confirms who you are and tells us only your Discord user ID. Discord is responsible for its own platform and processes your messages under its own privacy policy; in the EEA that's Discord Netherlands BV. Our bots receive your Discord user ID. Our support bot also receives what you post in your ticket, and when we read a closed ticket's record, it shows it to us through Discord.
Our support team in Discord: besides us, a contractor and moderators answer support tickets. They see your Discord name and what you post in your ticket while it's open, and they're bound to confidentiality. Seconds after it closes, our support bot deletes the ticket from Discord. After that, only we and that contractor can read the ticket's record. They also read #bug-reports, #ideas, #reviews and #testers.
Other members of our Discord server see the roles our bot gives you there, on your profile and in the colour of your name: that you're a buyer, which plan you have (Basic, Pro or Max), whether you're a tester, and, for 7 days after your last paid key runs out, that you bought Switch before. Everyone with a live key can read what you post in #bug-reports and #ideas, and the testers what you post in #testers. Everyone in our server can read what you post in #reviews, where only members with a live key, or with a paid key that ran out in the last 7 days, can post, and our staff answer there.
Other Max users: a Max user in the same Boxing Beta server can learn that another Max user is there. In a two-player match that means their opponent. They learn nothing else about you.
Bots others run in our Discord server, under their own terms and privacy policies. Discord sends them data about everyone in the server:
- Wick (its operator isn't named; team@wickbot.com): protects the server against raids and spam. It analyses messages and keeps moderation records and logs of edited and deleted messages. It publishes lists of accounts caught in raids. https://wickbot.com/legal/privacy
- Beemo (California, USA): protects the server against raids. It keeps your Discord user ID, username, avatar, when you joined and your messages, and it can publish a list of the accounts it banned in a raid. https://beemo.gg/privacy
- Honeypot (an individual developer; its terms follow Australian law): catches spam accounts. It keeps the user ID and the time of each account it catches. https://github.com/RiskyMH/honeypot
RestoreCord (Axvant UG (haftungsbeschränkt), Berlin, Germany) runs our verification app, Switch Verify, in our Discord server, under its own privacy policy: https://restorecord.com/privacy. Like the bots above, its bot receives data from Discord about everyone in the server. It gives each new member the "unverified" role when they join, and anyone who verifies the "verified" role, which other members can see on their profile. When you verify on RestoreCord's website, it receives your Discord profile and keeps your Discord user ID, our server and your authorization. With our settings it keeps no IP address or e-mail address and runs no captcha or VPN check; RestoreCord says it may also keep your country and an anonymous identifier for its security checks. Cloudflare, which runs in front of RestoreCord's website, sees your IP address and browser details on the way.
Card issuers, card networks and the payment service you used, through Stripe, if a payment is disputed. We send evidence such as order, consent and usage records.
Our tax adviser and public authorities, where the law requires it.
Courts and lawyers, if we need to establish, exercise or defend legal claims.
Your bank, PayPal or Wise, if you're a creator in our affiliate program and we pay you that way (section 17).

9. Transfers outside the EU

Stripe, Vercel and Discord process data in the US. Resend and Neon keep our data in the EU, in Ireland and Frankfurt, but as US companies they and their sub-processors may access it from the US.
- Their US companies are certified under the EU-U.S. Data Privacy Framework. The European Commission has decided that it ensures an adequate level of protection (Commission Implementing Decision (EU) 2023/1795).
- Where that doesn't cover a transfer, the EU Standard Contractual Clauses apply (Commission Implementing Decision (EU) 2021/914).
Members of our support team (section 8) work from outside the EU, most of them from the USA. They access from there the data they can see in our support tickets and our Discord server, and the contractor also what our admin panel shows. If one of them is in a country the European Commission has found to protect personal data adequately, its decision covers the transfer. For everyone else, the USA included, we're putting the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914) in place with them.
The bots others run in our Discord server (section 8) are outside the EU: Beemo is in the USA, Honeypot's terms follow Australian law, and Wick doesn't say where it is. None of them offers the EU Standard Contractual Clauses or another EU transfer safeguard.
RestoreCord keeps its database in Germany. Depending on where you are, its application servers may also run in the USA or Singapore, and Cloudflare (USA) handles every request to its website. RestoreCord says it uses the EU Standard Contractual Clauses for these transfers.
You can ask us for a copy of these safeguards.

10. How long we keep your data

Receipts and accounting records, including the order details on them: 7 years from the end of the calendar year.
EU One-Stop Shop (OSS) records, only if we ever use the OSS: 10 years from the end of the year of the sale.
Checkout and consent records (your consents, date of birth, IP address and browser details): at least 3 years, or 1 year after your last pass or subscription ends, whichever is longer.
- Your order confirmation also repeats your consent. It's part of the receipt, so it's kept for 7 years.
Licence key, hashed PC identifier, usage records and Discord user ID: deleted 550 days (about 18 months) after your licence ends, because card disputes can arrive months after a payment. Your licence ends when it expires, or earlier if it's revoked. A pass you haven't used yet hasn't started, so it hasn't ended either, and its data stays until 550 days after it ends. If we replaced a lost key, the old key is deleted together with its replacement.
The record of which model versions your key received: deleted with your licence data above, 550 days after your licence ends.
The licence server's record of changes to your licence (such as renewals, resets, status changes and turning play statistics on or off; it can include your Discord user ID, never your key or PC identifier): each entry until it's 550 days old or your licence data above is deleted, whichever is later.
Play statistics, if you turn them on: each session for up to 90 days, after which it counts only in your totals; all of it until you turn statistics off, or until 30 days after your licence ends. Turning them off, or deleting your account, deletes them at once.
Server code (Max): two minutes, in memory only.
Support messages (by e-mail or in a Discord ticket), withdrawal and cancellation declarations: 3 years after the case is closed.
Our record of support actions: 3 years.
A free key we gave you: its record until 550 days after its licence ends, like the licence data above; the encrypted copy of the key for your account page until 30 days after its licence ends.
A trial key from a partner: its record until 550 days after it ends, like the licence data above, because copies of our models shared without permission can surface months later. It ends when its days run out, or earlier if we end the promotion.
Logs on the licence server, its web server's request logs included: 7 days. Your IP address appears only in the request logs, and no log holds your licence key.
Backups of our server in Finland are encrypted. Data we delete leaves every backup within 30 days.
Website server logs: as long as our host, Vercel, keeps them.
Creator invites: the record that you joined our Discord through a creator's invite, 32 days after you joined. An order it counted for keeps whose invite it was and the hour you joined, for as long as the order is kept.
Your account: until you delete it on your account page, or until 24 months after you last signed in. Sign-in links work once, for 15 minutes. A sign-in session ends 30 days after you last used it, and 90 days after you signed in at the latest. The record of key views, PC-lock resets, Discord changes and play-statistics changes: 1 year.
The encrypted copy of your key for your account page: until 30 days after your licence ends.
Our Discord bot for buyer roles keeps your Discord user ID, and when it next checks your roles, only while you're owed buyer roles (for 7 days after your last paid key runs out, the role that lets you post in #reviews), also before you join our server if you connected Discord on your account page. It drops them once you're owed none. To limit how often its buttons can be used, it keeps the times you used them in memory only, until they no longer count or the bot restarts. Its logs, on our server and in a staff-only channel of our Discord, are gone within 7 days, and it never stores keys or messages. Every 10 minutes it also checks new posts in #reviews: from each, it uses only who posted it, when, and what kind of message it is (a reply, for example), never what you wrote. It looks up the keys the author had when they posted, and their roles, in memory only during that check. If all their keys were free ones from us, or they're a tester or a creator, or they're one of our staff posting other than a reply, it tells our staff in that staff-only channel, never with the key, and that message is gone within 7 days. Of the check itself, it keeps only the ID of the last post it checked. To credit creators, it also receives Discord's notices when members join, leave or change, and reads our server's invites and how often each has been used. It uses only the joins: it holds a new member's Discord user ID and join time in memory only, until it is sure which invite they used, or that it can't tell (at most about ten minutes), and keeps no list of them. Only for a join through a creator's invite does it send us your Discord user ID, the invite and the time. It keeps those three in its state file until we have them (usually seconds), and if it can't deliver them, tries again for at most 32 days.
Ping roles you pick in our Discord: the same bot gives you the role or takes it away there, and stores nothing about it. To limit presses, it keeps the times you pressed in memory only, until you press again or the bot restarts. Discord's audit log of our server shows the bot's role changes (buyer, creator and ping roles) to us, the contractor in our support team and our admins and moderators, for 45 days.
Our support bot deletes a ticket's record, its files included, 3 years after the ticket closes. It deletes the ticket itself from Discord seconds after it closes. The bot's logs, on our server and in a staff-only channel of our Discord, are gone within 7 days and never hold your messages.
Your posts in #bug-reports, #ideas, #reviews and #testers stay in Discord until you or our staff delete them, even after your key ends. Once it has ended, you can't see #bug-reports, #ideas or #testers any more: ask us in a ticket, and we delete your posts there.
Data held by the bots others run in our Discord server (section 8), as their own terms say:
- Wick keeps moderation cases for 1 month and doesn't say how long it keeps the rest.
- Beemo doesn't say.
- Honeypot keeps what it caught until it leaves our server.
Member backup (RestoreCord): RestoreCord keeps your verification for as long as our server is on RestoreCord. You can withdraw the authorization at any time: remove Switch Verify in Discord (User Settings, Authorized Apps), or use RestoreCord's My Data page (https://restorecord.com/mydata). We then can't bring you back, but you keep your access to our server. Withdrawing doesn't delete what RestoreCord keeps: for that, ask us, or RestoreCord at contact@restorecord.com. Leaving our server doesn't end your verification either, so if you leave and don't want to be brought back, withdraw the authorization.
If you're under 13 and try to buy, we stop the checkout and don't store what you entered.
We keep data longer only while it's needed for a legal dispute that has already started.

11. Your rights

You have the right to:

get a copy of your data (Art. 15 GDPR);
have wrong data corrected (Art. 16);
have data deleted (Art. 17);
have processing restricted (Art. 18);
get your data in a portable format (Art. 20);
object to processing based on our legitimate interests (Art. 21);
withdraw any consent you gave us, for the future (Art. 7(3)).

How it works:

Write to support@getswitch.net from the e-mail address you ordered with or, if you use a partner's free trial key, say which key it is. We may ask you to confirm who you are.
You can delete your account yourself, on your account page.
You can turn play statistics off on your account page. We then delete them.
We answer within one month.
We can't delete data that the law requires us to keep, such as receipts. We'll tell you if that applies.

12. Complaints

You can complain to a data protection authority.
In Austria: Datenschutzbehörde, Barichgasse 40–42, 1030 Wien, Austria. E-mail dsb@dsb.gv.at, phone +43 1 52 152-0, https://dsb.gv.at.
You can also complain in the EU country where you live or work.

13. Children

Switch isn't for anyone under 13. We don't knowingly collect data from children under 13.
If we learn that we have, we delete it, except what the law requires us to keep.
13- to 17-year-olds can buy passes. A subscription needs a parent or guardian aged 18 or over as the customer.
Trial keys from a partner follow the same ages: 13 or older, and under 18 only with a parent's or guardian's permission.
If a child under 13 uses Switch anyway, we collect only what the licence needs and, with a Max key (a partner's free trial key too), what Avoid Switch needs: an identifier of the PC, the IP address, usage records, which model versions the key received and, with Max, the ID of the Boxing Beta server they're in (section 3). We use them only to run and protect the licence and to make Avoid Switch work, never to contact anyone or build a profile, and delete them as section 10 says.
Parents and guardians can contact us at support@getswitch.net.

14. Cookies, device data and the script

Our website itself sets no cookies and runs no analytics or ads.
Stripe's payment page is run by Stripe and uses Stripe's own cookies, for payments and fraud prevention.
If you sign in to your account, our payments server sets one cookie that keeps you signed in; during a Discord sign-in a second one for 10 minutes; and when you ask for a sign-in link, a third one for 15 minutes, which ties the link to that browser. All three are strictly necessary for the sign-in you asked for. Nothing else is stored in your browser for your account.
The Switch script reads an identifier of your PC (the hardware ID from your executor or, if it has none, Roblox's device ID) to lock your licence to one PC. We read it only because it's strictly necessary to provide the licence you ordered.
The Switch script keeps four small files in a folder named "switch" in your executor's workspace on your PC: your key, so you don't have to paste it every time; the last session's lease, so a reload after a teleport isn't counted as another game window; while play statistics are on, the game counts since the last load, so a teleport doesn't lose them; and, if you use a trial key from a partner, a short fingerprint of the last one you started, so the screen before a trial doesn't show again for it.
The Switch panel keeps its settings (such as its toggle key, its size and streamer mode) and the Switch logo, for your executor to show, in the same workspace. For each game, it also keeps the choices you made in the panel and the page you left it on, so they stay when you change servers.
The Boxing Beta agent keeps a log there for each server you play on: how it queued, the matches and their statistics, and for a ranked match your own rating change. It holds no names, user IDs or chat, and the panel's Record page shows it. The panel deletes each log once its newest entry is 30 days old, the next time it runs in Boxing Beta. Another file notes when the agent last changed servers, so it waits at least 15 minutes before the next change.
We never receive these files. They stay on your PC until you delete them, which you can do at any time. Two kinds go by themselves: the game counts, when play statistics are off, and Boxing Beta's logs, as above. After deleting them you'll paste your key again, the panel starts with its usual settings, and its Record page starts empty.
If you turn on play statistics, the Switch script also sends the games your AI reports it played and won. That's needed for the statistics you asked for. While they're off, it sends nothing for them.
With Max, including a free trial key from a partner, the script also reads the ID of the Boxing Beta server you're in and sends it to our licence server, as section 3 says, whether or not you use the Avoid Switch option, so that other Max users can find you. Your own licence doesn't need this. You can object to it (section 11).
The script, the panel and the agents send us nothing beyond what this notice lists, and nothing to anyone else, except that the panel asks Roblox for your own avatar picture, as games do. When the script starts, it downloads its code from our licence server, which logs the request like any other (section 10). Options that change how names look on your screen keep those names only in memory and change nothing that anyone else sees.
Each copy of an agent's model that we send carries a code derived from your licence key. We do this so that copies shared without permission can be traced to the key they were sent to. We also record which model versions each key received; that record is deleted with the key's other records.

15. Security

We protect your data with technical and organisational measures suited to the risk, such as access controls.
We don't publish the details of our security measures.

16. Changes to this notice

We update this notice when our processing changes. The date at the top shows the version in force.
If a change matters for current customers, we tell them by e-mail.

17. Creators in our affiliate program

This section is for creators who ask to join our affiliate program or take part in it.

What we collect:
- our conversation in Discord about joining, in a support ticket: what you tell us there, such as your channels (section 10 says how long our support bot keeps a ticket's record);
- your sign-up on our website: legal name, e-mail address, date of birth, country, how you'd like to be paid, and your acceptance of the Affiliate Terms with its time and version;
- if we approve you: your creator link and your Discord invite, your payout details (IBAN and account name, or PayPal or Wise e-mail address), your VAT number if you have one, your Discord user ID if you link it, the number of clicks on your link and of joins through your invite per day, and the orders that count for you, with their commissions, payouts and statements;
- our notes on your invitation, such as your Discord name;
- our e-mails with you.
Why, and on what legal basis:
- deciding whether to work with you, and running the program, including paying you (Art. 6(1)(b));
- keeping accounting and tax records, and making reports that tax law requires (Art. 6(1)(c));
- checking your age, and preventing orders through your own link and other abuse (Art. 6(1)(f)).
Who receives it: your bank, PayPal or Wise, to pay you, under their own privacy policies; our tax adviser and the tax authorities, where the law requires it. In Discord, our bot shows your totals only to you, in a private reply.
Buyers stay private: you see only totals per month, never who bought or joined.
How long we keep it:
- a sign-up link you never use: it stops working after 7 days, and we then delete it;
- our conversation in Discord: as section 10 says for support tickets;
- statements and payout records: 7 years from the end of the calendar year;
- everything else: 3 years after you leave the program.
Your rights in section 11 apply to this data too.

18. Testers

This section is for people we invite to test Switch.

What we collect:
- our invitation: when we made it and when it was used, the key it gives, and our own note on it, such as your Discord name, which we keep in our record of support actions (section 3);
- the account you join with: your Discord user ID, and your e-mail address only if you add one (section 3);
- that you're a tester: since when, and whether you still are;
- your tester key and its records, as for any licence (section 3). It's marked as a tester key, so our Discord bot gives you the Tester role.
Why, and on what legal basis: to give you your tester key and the Tester role, and to run the tester program (Art. 6(1)(b), at your request); our record of support actions (Art. 6(1)(f), section 3).
Who sees it: as section 8 says. Other members of our Discord server can see that you're a tester.
How long we keep it:
- an invitation: until it's used, runs out after 7 days, or we withdraw it; then we delete it within a day;
- that you're a tester: until 550 days after you stop being one, like your tester key's records (section 10);
- your account: as section 10 says.
Leaving: delete your account on your account page. Your tester status and your tester key end with it. We can also end them at any time.
Your rights in section 11 apply to this data too.

19. Partners who hand out our trial keys

This section is for people who run another script hub and hand out our trial keys.

What we collect:
- the name of your hub, which we use as your label in our records, and how to reach you, such as your Discord name;
- the batches of keys we make for you: number, count, dates and our notes, and how many of their keys were used;
- your acceptance of our partner conditions, with its time and version;
- our messages with you.
Why, and on what legal basis: running the promotion with you under our partner conditions (Art. 6(1)(b)); keeping a record of what was agreed and done (Art. 6(1)(f)).
Who receives it: no one outside our team. Our messages with you are also on the platform we use for them, such as Discord, under its own privacy policy.
How long we keep it:
- the batches: as long as their keys' records (section 10);
- everything else: 3 years after the promotion with you ends.
Your rights in section 11 apply to this data too.