Privacy Policy
Updated 15 November 2026
This policy explains what personal data RoScripts collects, why, who we share it with, how long we keep it, and what you can do about it. It covers roscripts.io and every RoScripts service, including the script loader and the API.
1. Who we are
RoScripts is run by Sirius. We are the controller of the personal data described in this policy.
RoScripts shares one account system with other Sirius products. Your Sirius account (username, email, password, Discord link, role, Pro status and bans) is the same record in each of them, and Sirius is the controller for all of it.
2. Information we collect
Information you give us
- Account details. Your username, email address, password (stored securely, never in plain text), profile picture and settings.
- What you publish. Listings, script source and versions, thumbnails, tags, comments, votes, saves and reports. Listings and comments are public.
- Verification applications. If you apply for the verified badge, your application and the social links you give us.
- Sponsors. If you send the form on our advertising page or buy a sponsored card: your name or your company's, a contact email, what you'd advertise, your budget, the booking and the emails you send to [email protected]. The form is emailed to that inbox and not kept on the site. A script sponsor whose code is obfuscated also gives us its readable source, which we keep privately.
Information we collect when you use RoScripts
- Sign-in and security data. The IP address and browser user agent for each sign-in session, the IP that asked for a password reset, and an audit log of security events on your account (sign-ins, email and password changes, staff actions) with IP and user agent.
- Short-lived counters. Counters keyed on IP address that rate-limit sign-in and other actions, and count a listing view or run once per IP per hour.
- Loader and API requests. When a script is fetched through our loader or our API, we record the listing, the country the request came from and basic request details. For the loader this includes which executor fetched it, worked out from which headers it sends and how it connects. We don't record your IP address, your user agent, the values of those headers or any id your executor sends. A script's creator can see these counts for their own scripts, as totals by day, by country and by executor, never for a single request. When a new version of an executor comes out, the loader adds a short compatibility check to scripts it serves to that executor, until enough reports have come in. The check runs a few seconds after the script starts, shows nothing on screen or in the console, and sends us a probe report.
- Search terms. Counted in aggregate, with no account or IP address attached.
- Account records we create. Your sign-up and last-seen dates, whether you are verified, staff, upload-blocked or banned, and your past usernames.
- Moderation records. Reports about you or your content, strikes, sanctions (upload blocks, suspensions, bans), and notes and flags that staff add to your account.
Information from other services
- Discord. If you sign in with or link Discord, we keep your Discord user ID, username and avatar. Before you upload, we check that you're a member of the RoScripts Discord server, and staff roles come from that server.
- ScriptBlox. If you import your scripts from ScriptBlox, we keep your ScriptBlox username and account ID, when you linked it, and which of your scripts became which listing. To check the account is yours, we read your public ScriptBlox profile for a code we give you; the code is kept for 24 hours.
- Stripe. If you subscribe to RoScripts Pro, we keep a reference to your subscription and your Pro dates. We never see or store your card details.
3. How we use it
UK GDPR requires a legal basis for each way we use personal data. These are ours:
| Purpose | Legal basis |
|---|---|
| Giving you an account and letting you publish, comment, vote and save | Contract |
| Checking Discord membership before you upload, and syncing staff roles | Contract; legitimate interests in limiting uploads to accountable members |
| Keeping accounts secure and stopping bots and abuse | Legitimate interests |
| Counting views and runs, ranking listings and showing counts | Legitimate interests in running and improving discovery |
| Counting where visits come from (the kind of site only, such as a search engine or Discord), how fast pages load and which kind of site a link leads to, with no IP address and no identifier | Legitimate interests in running and improving RoScripts |
| Scanning uploaded scripts for malware | Legitimate interests in keeping malicious scripts off the site |
| Moderation, strikes, sanctions and ban-evasion checks | Legitimate interests in protecting users and enforcing our rules |
| Reviewing verification applications | Contract; legitimate interests |
| Keeping old usernames so nobody can take them and impersonate you | Legitimate interests |
| Billing for RoScripts Pro | Contract; legal obligation for financial records |
| Showing ads from Google on some pages, personalised where you allow it | Consent in the UK, the EEA and Switzerland; legitimate interests in funding RoScripts elsewhere |
| Showing sponsored cards and counting how often they're seen and clicked, with no cookie and no IP address | Legitimate interests in funding RoScripts |
| Answering advertising enquiries, and booking and billing sponsors | Contract; legal obligation for financial records |
| Running an obfuscated sponsored script's shared source beside its build, to check they match | Contract |
| Linking your ScriptBlox account and importing your scripts from it, when you ask | Contract |
| Sending email about your account and your scripts | Contract; legitimate interests for creator updates, which you can turn off |
| Counting how many of each kind of email are delivered, opened and clicked, with no address or identifier kept by us | Legitimate interests in sending email that works |
Malware scanning
We scan every uploaded script for malware. Parts of the source, the title and the description are sent to AI model providers to help judge whether a script is harmful. We also run scripts in a sandbox on Cloudflare's servers to see what they do. The sandbox uses made-up account details, never yours. We don't send your account details.
If your script has a key system, you can give us a key so the sandbox can run it past its key screen. We store the key encrypted and only our checks use it. We keep it until you remove it, or until you delete the script or your account.
Some new scripts and updates are held for review before they go public. We keep a record of each one, linked to the uploader's account: when it was held and how the review ended.
Reports and comment checks
New comments, and content that has been reported, are checked automatically against our rules by AI models that run on Cloudflare. The models get the text of the comment, or a listing's title and description, and nothing about who wrote or reported it. Scriptsight's scan can also see what reports said about a script. Reports you file are used to work out how much your later reports count. We look at how many of them were upheld.
Each moderation decision is recorded with the rule it relied on, a short summary, whether it was automatic, and the model's score. These records contain no copied text, apart from the note you add to an appeal, which is deleted after 180 days.
Ban evasion
To stop banned people coming straight back, we keep a few identifiers from banned accounts, and from accounts deleted while a ban was on its way, such as a Discord ID, and fingerprints of scripts confirmed as malicious. We use them only for moderation. You can object to them using the contact details below.
Staff view-as
To investigate a problem, a moderator can view the site as you, read-only. They can't change anything or open your account settings, and every use is logged.
Personalised recommendations
The For you list and similar lists learn from which scripts you're shown and which you open. Your browser makes a random id for this and sends it with those two things only. Our model keeps 16 numbers for that id, nothing about who you are. You can switch it off at the foot of any page. Your browser then forgets the id and we delete its numbers. If you do, you see the same lists as everyone else, built from everyone's picks.
We send email about your account: verification, password resets, security notices (such as an email change), verification decisions, ban notices, and notices about your scripts, such as a removal after a legal notice or after reports. If you publish scripts, we may also send an occasional update on how they're doing. Every update has an unsubscribe link, and we never send marketing for anyone else.
Ads
Some pages may show a sponsored card: a paid placement for a script listed on RoScripts or for a website, marked Sponsored. We check every one before it shows. A card is part of our own page. It uses no cookies and sends nothing to the sponsor. Its link goes through RoScripts first, and we count how often each card is seen and clicked, with no IP address and no identifier. A website card opens the sponsor's site, which has its own privacy policy.
Some pages may also show ads from Google, marked Advertisements. Google may personalise them from what it knows of your browsing on other sites, using cookies or similar storage. In the UK, the EEA and Switzerland, and when we can't tell which country a visit comes from, a consent screen from InMobi Choice asks you first, and if you decline, Google picks ads from what's on the page instead. In US states whose privacy laws count personalised ads as selling or sharing personal data, you can turn that off. On any page with an ad, you can change your answer with Privacy choices at the bottom of the page. Google also uses cookies or similar storage to limit how often an ad shows, count ads and stop fraud, and it receives your IP address and browser details when it sends an ad. Google's use of that data is covered by Google's privacy policy and how Google uses information from sites that use its services. For each page with a Google ad, we count whether the ad loaded, filled and was on screen, and which consent answer was given, with no IP address and no identifier.
People with RoScripts Pro see neither kind of ad. Nobody sees them on scripts with a warning, or on account, upload, staff, legal and Pro pages. We never sell personal data for money.
Cookies and storage
This is everything RoScripts keeps in your browser:
| Name | What it's for | How long |
|---|---|---|
sid (cookie) | Keeps you signed in. | 7 days. |
tsp (cookie) | A two-step sign-in in progress. | 10 minutes. |
rs_wall (cookie) | That the picture beside the sign-in form has been shown, so the next sign-in page doesn't play its arrival again. No id. | 30 minutes. |
discord_oauth_state (cookie) | A Discord sign-in in progress. | 10 minutes. |
rs_viewas (cookie) | Staff only: a read-only view of another account. | 15 minutes at most. |
rs:theme, rs:recent, rs:verify-nudge-dismissed, rs:staff-drawer (local storage) | Your theme, the scripts you viewed recently, a reminder you dismissed, and the staff drawer's state. | Until you clear them. |
rs:vid, rs:perso (local storage) | A random id for personalised recommendations, made by your browser and never tied to your account, email or address, and whether you switched them off. | Until you switch personalised recommendations off (the id is deleted) or clear site data. |
rs_src (cookie) | Where this visit came from, as a kind of site such as "google" or "discord", so we can count which sources bring sign-ups, uploads and Pro. No id. | Until you close the browser. |
rs:last, rs:first (local storage) | The day numbers of your last and first visits, so we can count visits as new or returning. No id. Neither day number is sent. Only "new", "again today" or "another day" is sent, with the weeks since your first visit. | Until you clear site data. |
rs:pv, rs:vig, viewed:…, ss:ack:…, rs:import, rs:house (session storage) | Counts the pages in a visit without an id, notes for a few minutes that Google showed a full-page ad so the next page can count that it was reached through one, stops a view counting twice, remembers you saw a warning before copying, keeps a link you're importing while you sign in, and takes turns between our own two cards when Google leaves an ad space empty. | Until you close the tab. |
Google's ad cookies (such as __gads, __gpi and __eoi) and its fraud-detection storage | Set by Google on pages that show its ads. In the UK, the EEA and Switzerland, only once you agree. Google lists them at business.safety.google/adscookies. | Set by Google. |
InMobi Choice's consent record (euconsent-v2 and its own storage) | Remembers what you chose about ads, in the UK, the EEA and Switzerland. | 13 months. |
5. International transfers
Several of our providers are based in, or process data in, the United States and other countries outside the UK and EEA. For those transfers we rely on the provider's data processing terms, which include the UK International Data Transfer Addendum and the EU Standard Contractual Clauses, or on the UK-US Data Bridge where the provider is certified under it.
6. How long we keep it
| Data | Kept for |
|---|---|
| Account (username, email, password hash, profile, Pro status) | Until you delete your account. An email address that is never confirmed is removed from the account after 7 days. |
| Sign-in sessions, with IP address and browser user agent | 7 days from sign-in, then deleted. |
| Two-step sign-in: the authenticator key (encrypted) and recovery codes (stored only as hashes) | Until you turn two-step sign-in off or delete your account. |
| A key you give for your script's key system (encrypted) | Until you remove it, or delete the script or your account. |
| Password-reset and email-verification requests (reset requests include the requesting IP) | Deleted 7 days after the link expires (links last 1 to 24 hours). |
| Account audit log (sign-ins, security changes) and staff action log | Events are kept while the account exists. The IP address and user agent on them are erased after 90 days. |
| Personalised recommendations: the scripts shown and picked with your browser's random id, and the 16 numbers our model learned from them | Shown scripts wait at most 10 minutes before the model learns from them and are then dropped. The 16 numbers are deleted 30 days after your last visit, or as soon as you switch personalised recommendations off. |
| Scripts copied in the same tab, counted per pair of scripts (no id) | 90 days after the pair was last seen. |
| Short-lived counters keyed on IP address (rate limits, view and run counting) | Between 1 minute and 24 hours, then they expire automatically. |
| Request statistics and page counts (the country a request came from, the kind of page, phone or computer, which page of a visit it was, what the page's ad slot showed, and for the loader which executor fetched the script, with no IP address, cookie, user agent or executor id) | Up to about 3 months. |
| Sponsored card counts (views and clicks per card per day, with no IP address, cookie or id) | Kept with the booking they belong to. |
| Sponsor details (the sponsor's name, a contact email and staff notes) | Contact email and notes are deleted 12 months after the sponsor's last card ends. Invoices and booking records are kept 6 years, as UK tax law requires. |
| Emails to [email protected], including the advertising form | 12 months from the last message. |
| The Scriptsight licensing form (your name, work email, platform and what you'd need), emailed to [email protected] | 12 months from the last message. |
| Readable source a script sponsor shares with us | Deleted 30 days after their card ends. |
| Executor probe reports, from roscripts.io/probe or the loader's compatibility check (the executor's name and version, the functions it has and how they behave, and the request's header names, with no IP address, account, player name, user id or hardware id) | 90 days. |
| Server logs (a sample of requests, plus errors) | Up to 7 days. |
| Search terms (aggregated, with no account or IP attached) | Daily counts 14 days. Running totals are deleted 90 days after a term was last searched. |
| Listings, versions, source code, comments | Until you or staff delete them. When you delete your account, you choose to delete them or leave them attributed to [deleted]. |
| Votes, saves, comment votes | Until you remove them or delete your account. |
| A linked ScriptBlox account (username, account ID, when you linked it) and your import queue | Until you unlink it on /import or delete your account. The code you put in your bio is kept 24 hours. |
| Which ScriptBlox script became which listing | As long as the listing exists. |
| Username history | While the account exists (used to reserve old names and stop impersonation). |
| Verification applications | While the account exists. |
| Moderation records: reports, strikes, sanctions, staff notes and flags | While the account exists. Strikes stop counting after 180 days but stay on record. Reports you filed are kept without your account ID after deletion. |
| An upload block, suspension or strikes still running when you delete your account or unlink Discord, kept against your Discord ID (stored as a hash) | Until each one ends. If a new account gets that Discord before then, it takes them on. |
| Moderation decision records (the rule, a short summary, whether it was automatic) | While the content they're about exists. Notes you add to an appeal are deleted after 180 days. |
| Review records for uploads held before they go public (when, and how the review ended) | While the account exists. |
| Ban-evasion records | Until staff revoke them or they expire. |
| Links between accounts, made when a script taken down for harm loads code from or sends data to the same place as another account's script | 180 days. The places each script reaches are kept 90 days after it last reached them. |
| Staff view-as entries | Kept in the staff action log. The IP on the entry is erased after 90 days. |
When you delete your account, everything tied to it in the table is deleted at that point, apart from the exceptions the table lists: reports you filed, staff action logs, ban-evasion signatures, sanctions still running, and any content you chose to leave up as [deleted]. Deleted data can stay in our database backups for up to 60 days. After that it's gone. Backups are encrypted.
7. Your rights and choices
Under UK GDPR you can ask us for a copy of your data and ask us to correct it, delete it, or move it to another service. You can also ask us to restrict how we use it, or object to how we use it, including anything we do on the basis of legitimate interests. Contact us at the address below and we'll reply within one month.
Download your data
In account settings you can download a file of your account data, including your sign-in history, your listings and their source, your comments, votes and saves, and your moderation history. Passwords and security tokens are left out. Ask us if you want anything that isn't in the file.
Delete your account
You can also do this in account settings. If you have RoScripts Pro, we cancel it first. Deleting your account removes it along with your sessions, Discord link, profile picture, votes, saves and moderation records, and revokes your API keys.
You choose whether your listings and comments are deleted or stay up attributed to [deleted]. Listings that staff removed, or that are under an open malware or theft report, are kept as [deleted] for moderation. Deleting your account is permanent.
An upload block, suspension or strikes that are still running don't end when you delete your account. They stay with your Discord ID until their own end date, and a new account that signs up with or links that Discord takes them on.
Other settings
You can change your username, email, profile picture and connected accounts in settings.
Complaints
If you're unhappy with how we handle your data, you can complain to the Information Commissioner's Office at ico.org.uk. We'd appreciate the chance to sort it out first.
8. Children
You must be at least 13 to make a RoScripts account. Many people interested in Roblox scripts are young, so we collect only what the site needs, we don't profile anyone, and we don't show email addresses publicly. We block ad categories that aren't suitable for young people, such as dating and gambling. If you believe a child under 13 has an account, contact us and we'll delete it.
9. Changes to this policy
We'll update this policy when what we do changes, and change the date at the top. We'll announce significant changes on the site or by email.
10. Contact
Email privacy questions and requests to [email protected]. You can also reach staff through our Discord, but use email for anything about your personal data.