Legal
Privacy Policy
Last updated 20 November 2026 · Versión en español · Versione italiana
NoSlop keeps as little about you as it can. Your games, code and prompts don’t reach our servers unless you choose to share them (a project with NoSlop sharing, or an asset in the library): your AI agents send what they need to the AI company you picked. Your AI keys stay on your computer. Our servers keep your account, your purchases and add-ons, the computers you use NoSlop on, the projects and assets you choose to share and the wikis you publish, and, if you turn on Live events or Analytics, your game’s events. If you join NoSlop’s Discord server, they also keep what its bot needs. We don’t sell your data, show ads, track you or train AI on your work.
The short version
- NoSlop is run by one person, Giacomo Del Bianco, a self-employed developer in Gran Canaria, Spain. He decides what happens to your data (“we” on this page).
- We keep what we need to run your account, your purchase, the community library, NoSlop sharing and the add-ons: your email address, a name, what you bought, the computers you use NoSlop on, the projects and assets you choose to share and the wikis you publish.
- Your AI agents run on your computer with your own AI accounts. Your prompts, code, game files and the pictures of Studio they take go from your computer to the AI company you picked, not to us.
- If you share a project with NoSlop sharing, we store a copy of its files and history for the people you share it with, and they can see your email address. Projects you don’t share stay on your computer.
- We don’t sell your data, show ads, track you, or use your work to train AI. We don’t send marketing emails.
- You must be 13 or older. Under 14, or under the age your country sets, a parent or guardian must agree. Under 18, a parent or guardian must agree to a purchase.
- You can see, correct, download or delete your data. Delete your account at any time, or write to hello@noslop.gg.
Basic information
| Controller | Giacomo Del Bianco (NoSlop), NIF Y1962584P, hello@noslop.gg |
| Purposes | Your account and sign-in, selling and unlocking NoSlop and its add-ons, keeping each licence to one person, the community library, sharing the projects you choose to share, Analytics, Community wikis and Discord set-up, NoSlop’s Discord server, connecting Roblox, security, anonymous website visit counts, answering you |
| Legal basis | Our contract with you; legal duties (tax records, the EU Digital Services Act); our legitimate interest in security, in preventing licence sharing, in counting website visits and in keeping NoSlop’s Discord server safe. For your players’ data in Live events and Analytics, we act for you (you’re the controller) |
| Recipients | Service providers that run our servers and email; Cloudflare, when sign-up shows a captcha; Stripe and Link for payments; Google, Discord and Roblox only if you use them. We sell data to no one |
| Transfers | Some providers are in the US: covered by the EU–US Data Privacy Framework or Standard Contractual Clauses |
| Your rights | Access, correction, deletion, restriction, portability, objection; complaint to the AEPD |
| More information | The rest of this page |
Who is responsible for your data
The controller of your personal data is Giacomo Del Bianco, a self-employed developer (autónomo) in Gran Canaria, Spain, trading as NoSlop. NIF: Y1962584P. Email: hello@noslop.gg. Write there about anything on this page, including to use your rights. A person reads every message. Our other details are in the legal notice.
We haven’t appointed a Data Protection Officer: the law doesn’t require one for what NoSlop does. Write to hello@noslop.gg instead.
This policy covers the website at noslop.gg (including the public game wikis at noslop.gg/wiki/), the NoSlop desktop app, its Roblox Studio plugin, its account service, NoSlop sharing, its add-ons, the NoSlop Discord bot and NoSlop’s own Discord server. It is written in English and Spanish and both say the same; if they ever differ, the Spanish version applies to consumers in Spain.
What we handle, why, and for how long
Here is each thing we do with personal data: what data, why, the legal basis under the EU General Data Protection Regulation (GDPR) and how long we keep it. Where the data doesn’t come from you, we say where it comes from.
You don’t have to give us any data. But without an email address we can’t create an account, and without an account NoSlop’s agents don’t run. To buy, you need to give Stripe and Link your payment details.
Your account
- What we handle
Your email address; your password, stored only as a secure hash that we can’t read; the name you give at sign-up (or that Google or Discord sends); when the account was created, confirmed and last signed in; which sign-in methods it uses; and its plan and until when it runs.
- Why
To create your account, sign you in on the website and in the app, show your name and know what your account may use.
- Legal basis
Our contract with you (GDPR art. 6(1)(b)).
- How long
Until you delete your account. A sign-up whose email was never confirmed, that never signed in and never bought anything is deleted after 7 days. We don’t delete inactive accounts on our own, because your account holds the NoSlop you bought.
Signing in with Google or Discord
NoSlop’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
- What we handle
From Google or Discord, if you choose them: your account id with them, your email address, your name or username, a link to your profile picture and the other basic profile details they send with it. Never your password, contacts, files, messages or servers.
- Why
To create your NoSlop account, sign you in and show who is signed in. When you’re signed in, the website loads your profile picture straight from Google’s or Discord’s servers, so they see your IP address.
- Legal basis
Our contract with you (art. 6(1)(b)): you chose this way to sign in.
- How long
Until you delete your account.
Buying NoSlop, add-ons and your licence
Purchases and add-on subscriptions are sold through Link (Sold through Link, LLC, a Stripe company), Stripe’s merchant-of-record service: Link takes the payment, handles tax, sends the receipt and deals with refunds and disputes. Stripe and Link collect your payment details, billing address, country and tax details themselves and use them as an independent controller under Link’s privacy policy and Stripe’s privacy policy, including their own automatic fraud checks. We never see your card number. We remain the seller responsible for NoSlop itself. To have Stripe or Link delete your payment data, ask them through the Stripe Privacy Center or write to us and we’ll pass your request on.
- What we handle
- What we send Stripe when you press Buy or Subscribe: your account id, your email address (to fill in the checkout the first time), what you’re buying (for Analytics, which tier), and that you ticked the checkout box, with the time.
- Seats and gifts: if you buy team seats or a gift, we store the email addresses you give us, and a gift’s address also goes to Stripe. They stay with the purchase record, even after account deletion.
- What we get back and keep: Stripe’s payment and customer numbers, what you bought, when, the amount and currency including tax, the time you ticked the checkout box, and whether the payment was refunded or disputed.
- Your order confirmation: after each purchase we email you a confirmation of it, to your account’s email address (or the one you gave Link), and note that it was sent.
- Before Pro yearly renews: about 30 days ahead we email your account’s address the date, the price and how to cancel, and note that it was sent, so you get it once for each renewal.
- If you withdraw with “Withdraw from contract here”: what you send (your name, the purchase, the email address for the confirmation and any note), the date and time, your account id and whether the confirmation was sent. A copy goes to our mailbox.
- For each add-on (Analytics or Community): which add-on and tier, its status, the date the paid month ends, when a payment first failed, and Stripe’s subscription and customer numbers. Each monthly payment itself is recorded by Stripe and Link, not in our database.
- Your licence token: each time the app checks your plan, our server gives it a signed token with your account id, your plan, which games it covers, the computer it was signed for (see Your computers), and when it was issued and runs out (48 hours later). The app keeps it on your computer so NoSlop keeps working offline for up to 48 hours. It works only on that computer.
- Why
To sell you NoSlop and its add-ons through Link, unlock them for your account, handle refunds and disputes, and keep the sales records the law requires.
- Legal basis
Our contract with you (art. 6(1)(b)). Keeping sales records is a legal duty (art. 6(1)(c); Spanish Commercial Code art. 30 and General Tax Law). Keeping proof of what was sold and agreed, in case of a claim, is our legitimate interest (art. 6(1)(f)).
- How long
Purchase records: 6 years from the end of the year of the sale. When you delete your account we remove the link to your account and your Stripe customer number; what stays is Stripe’s payment number, the product, date, amount and status, which Link can still match to its own record of the payment. The plan and add-on details are deleted with your account. Withdrawal statements are kept with the purchase records, as proof of what you asked and when; deleting your account removes their link to it. The licence token runs out after 48 hours and is removed from your computer when you sign out.
Your computers
- Only you see your list of computers. We don’t store your IP address for this; our account service’s logs see it on every request, as described in Security.
- The limits apply by themselves. Spotting shared accounts is done by hand: we look at accounts with many take-overs or removals, and act only as the Terms describe.
- Versions of NoSlop released after 0.7.0 send this from the day they are installed, and list your computers. The limits apply from 14 November 2026. Versions up to 0.7.0 send none of it.
- What we handle
- An id for each computer: a code (SHA-256) the app makes on your computer from your account id and your system’s own machine id (on Windows the MachineGuid, on macOS the IOPlatformUUID, on Linux
/etc/machine-id). The machine id itself never leaves your computer, and the same computer has a different id on another account. Where no machine id can be read, the app makes a random one and keeps it in.noslop/device.json. - The computer’s name as your system has it (for example “ANA-PC”), so you recognise it in the list, and its system: Windows, macOS or Linux.
- When each computer was added and last seen, and which one NoSlop is in use on now.
- A history of computers added, removed and taken over, with the computer’s id and name at that time.
- An id for each computer: a code (SHA-256) the app makes on your computer from your account id and your system’s own machine id (on Windows the MachineGuid, on macOS the IOPlatformUUID, on Linux
- Why
A licence is for one person, so NoSlop works on up to 3 of your computers and on one at a time (see the Terms). The app sends the id, name and system when it checks your licence, and while NoSlop is open and signed in it says “still here” every 5 minutes, with the id only. This lets NoSlop tell you where it’s in use, move to the computer you’re on, and show your computers in the app and on your account page so you can remove one. We use the history for the limits (take-overs per day, removals per 30 days) and to spot accounts that are shared.
- Legal basis
Our contract with you (art. 6(1)(b)): the licence is for one person, and this is how NoSlop keeps to it. The history: our legitimate interest in preventing licence sharing (art. 6(1)(f)). You can object; see Your rights.
- How long
A computer’s entry: until you remove it (in the app, or under Computers on your account page) or delete your account. Which computer is in use is replaced each time it changes. The history: until you delete your account.
Emails we send
We don’t send marketing emails or newsletters. If we ever want to, we’ll ask first with a separate box that is unticked, we won’t offer it to anyone under 16, and every such email will have a link to stop them.
- What we handle
Your email address and the message: a 6-digit code or a link (valid for 15 minutes) to confirm your email or sign in, password resets and notices about your account or important changes to our terms. Our email provider Resend keeps a record of each email (address, subject, whether it was delivered). Receipts and payment emails come from Link, under Link’s policy.
- Why
To sign you in and keep your account working, and to tell you about things that affect your account.
- Legal basis
Our contract with you (art. 6(1)(b)); for notices the law requires, a legal duty (art. 6(1)(c)).
- How long
Resend keeps its record for a short time set by our plan. We don’t keep copies of these emails.
Security, abuse prevention and fixing faults
- What we handle
- Sign-in records in our account service’s logs: time, IP address, browser or app version, your account id and email, and what happened (signed in, signed out, password changed).
- Request logs: our website host logs each request (IP address, page, time, browser). Our account service logs requests too; some lines include your account id or a Stripe event number (for example “licence issued for <account>”).
- Rate-limit counters: your account id, which action (buying, the billing page, licence checks, deleting an account, connecting Roblox, adding Analytics games, Discord codes, Community actions, NoSlop sharing), a time window and how many times; for Discord connect and /link tries, the server’s id instead; for the website’s visit counts, a fingerprint of your IP address (see Website visit counts). No name or email.
- Human check: when sign-up or sign-in shows a captcha (Cloudflare Turnstile), Cloudflare checks your IP address and signals from your browser and device to tell people from bots, and our account service checks Cloudflare’s answer before it goes ahead.
- Payment events we couldn’t match to an account: Stripe’s event number, customer number and the account id the payment named.
- Why
To keep accounts and NoSlop secure, stop attacks, abuse and fraud (for example, too many attempts), find and fix faults, and make sure every payment reaches the right account.
- Legal basis
Our legitimate interest in protecting NoSlop, its users and their payments from attacks, abuse and errors (art. 6(1)(f); GDPR recital 49). You can object; see Your rights.
- How long
Website request logs: up to 30 days. Account service logs, including sign-in records: up to 7 days. Rate-limit counters: deleted by a daily clean-up once they’re over a day old. Unmatched payment events: today there is no automatic time limit, and they are not removed when you delete your account. Ask us and we’ll delete yours, unless we need them for a security case or a claim. The human check’s answer is used once and not stored by us.
When you write to us
- What we handle
Your email address, what you write and attach (for example a screenshot or the text from “Copy debug info”) and our replies. For requests about your rights or complaints: what you asked and when we answered. Emails to hello@noslop.gg are forwarded by our domain provider to our mailbox.
- Why
To answer you, handle refunds and complaints, deal with reports, and let you use your rights.
- Legal basis
Our contract with you, for questions about your account or purchase (art. 6(1)(b)); legal duties, for rights requests and consumer complaints (art. 6(1)(c)); our legitimate interest in answering other messages and defending claims (art. 6(1)(f)).
- How long
Up to 3 years after the conversation ends; records of rights requests for 3 years. Longer only while a claim is open.
The community library
Nothing goes to the library unless you choose it: per asset (“Share…” in the Library tab) or with the switch “Share the models my agents make in Blender”, which is off until you turn it on. Sounds and images are never shared automatically.
Who sees it:
- People signed in to a NoSlop account with access to NoSlop see your shared asset with its title, description, tags, prompt, preview and, if you chose it, your display name. Never your email address or account id.
- The library isn’t public on the web. Answers are only shown as totals. Only we see reports and who sent them.
- When other people’s agents look through the library, those agents send the asset’s picture and details to their own AI company, just as yours do.
- Don’t put anyone’s personal data in an asset, its prompt or its description.
Moderation: anyone can report an asset in the app or by email to hello@noslop.gg. When three different people report an asset, it is hidden automatically until a person (us) looks at it and decides to bring it back or remove it. We remove assets that are illegal or break our Terms, and a removed file can’t be shared again. We don’t scan assets with any other automated tool. If we hide or remove your asset, we email you why and how to ask us to look again.
- What we handle
- When you share an asset: the file and, for models, a preview picture; its title, description and tags; the prompt (how it was made or what was asked for, up to 1,000 characters); the tool it came from; its type, size, triangle count, picture size or length; a fingerprint of the file (SHA-256); its licence; your display name, only if you tick the box to show it; how often it was used, turned down or reported; and which account shared it.
- When you use the library: what you search for is sent to our server to find matches and isn’t stored. Each time an agent asks “Use this asset?”, we store your answer with your account so one person can’t count twice.
- When you report an asset: the asset, your account, your reason and the time.
- Why
To run the library, show the most useful assets first, keep it safe and lawful, and meet our duties under the EU Digital Services Act.
- Legal basis
Sharing: our contract with you, because you ask us to share the asset (art. 6(1)(b)). Ranking with your answers: our legitimate interest in showing useful assets first (art. 6(1)(f)). Reports and moderation: our legitimate interest in a safe library (art. 6(1)(f)) and our legal duties under the Digital Services Act, Regulation (EU) 2022/2065 (art. 6(1)(c)).
- How long
A shared asset stays listed until you stop sharing it. When you stop, it leaves the library at once, but its file and details stay stored on our server until you delete your account. A file uploaded but never listed is removed when we run our clean-up, at the earliest 2 days later. Answers and reports: until the asset or your account is deleted.
Sharing a project inside NoSlop (NoSlop sharing)
Nothing is uploaded until you press Share for a project. After that, NoSlop sends that project’s changes by itself while you work on it. Projects you don’t share aren’t stored with us. Your prompts, your agents’ conversations and the task board aren’t part of what is uploaded.
Before each upload, NoSlop looks through the text files about to be sent, on your computer, for things that look like keys or passwords. If it finds any, nothing is uploaded until you remove them or choose Upload anyway. This check doesn’t tell us what it found, and it can’t catch everything.
Who sees it:
- Everyone in the project can download all its files and its whole history, and can send changes to it.
- The people in a project see each other’s email addresses and who owns it; the app also receives each person’s account id, to tell them apart. Checkpoints a person makes carry the part of their email address before the @ as the author’s name, which everyone in the project sees, and it stays in the history even after that person leaves.
- Someone you invite by email sees the project’s name and your email address. Only the owner sees invitations that haven’t been answered. Anyone who has an invite link can use it to join, until it has been used or runs out.
- When the agents of the people in a project read it, those agents send what they read to their own AI company, just as yours do.
- A person who leaves or is removed loses access to the stored copy. We can’t reach the copy on their computer.
- We don’t browse shared projects. We can reach them when we have to: to keep the service running (for example, to fix a fault or check a report of illegal content) or when the law requires it. They travel encrypted (HTTPS), but they aren’t encrypted in a way that locks us out.
Invite links: the page at noslop.gg/join/ only shows the code that comes after the # in the link. Browsers don’t send that part to websites, the page doesn’t send it anywhere, and it isn’t counted in our website visit counts.
The rules for what you may upload are in our Terms.
- What we handle
- The project: when you press Share, its files and its whole version history, including earlier versions of files and files you have since deleted, and after that every change that is synced. We also keep its name, its branches and release labels, and a list of the stored files (fingerprint, size and which account uploaded each). Don’t put anyone’s personal data in a project you share.
- Who is in it: which accounts are in the project and who owns it.
- Invitations: the email address you invite, the project and when the invitation runs out. That person may not have a NoSlop account yet: in that case their address comes from you, the person inviting. We send that address an email about the invitation, with your email address and usually the project’s name. Invite links hold no address, and we keep only a one-way fingerprint (hash) of the link.
- Connection details: Supabase, which stores the files, handles the IP address of each computer that uploads or downloads them, like any server.
- Why
To keep a copy of the project that everyone in it can reach, pass each person’s changes to the others, show who is in the project, deliver invitations and apply the limits.
- Legal basis
Storing and syncing the project, who is in it and the invitations you send or answer: our contract with you, because you ask us to share the project or to let you join it (art. 6(1)(b)). Keeping the address of someone you invited until they answer or the invitation runs out, and emailing them about it: our legitimate interest, and yours, in letting the invitation reach them (art. 6(1)(f)). The email tells them where we got their address, and they can object by writing to hello@noslop.gg. Looking into a report or answering a legal order: our legitimate interest in a safe service (art. 6(1)(f)) and, where the law requires it, a legal duty (art. 6(1)(c)).
- How long
The project’s files, history and details: for as long as the project exists. When its owner deletes it, or deletes their account, its records are deleted at once and its files are removed from storage shortly after. An upload that was started but never finished is cleared after at least 24 hours, the next time someone uploads to that project. Membership: until you leave or are removed, the project is deleted, or you delete your account; what someone already added stays in the project’s history. An email invitation stops working after 30 days and an invite link after 14 days or its first use; the owner can cancel either one sooner. An invitation is deleted when it’s answered or cancelled, and with the project at the latest.
Connecting your Roblox account
- Our server holds NoSlop’s Roblox app secret. When you connect, and when the connection is refreshed, it swaps the one-time code from Roblox for the tokens and passes them, with your Roblox profile, to the app.
- Our server keeps no copy. If an exchange fails, its log may hold Roblox’s error message for the log period.
- The app keeps the refresh token and your Roblox profile in your computer’s credential store and the access token only in memory. Your agents never see the tokens.
- If we ever lose access to Roblox’s APIs, we delete anything we received from them.
- Instead of connecting, advanced users can add an Open Cloud API key they created for their own Roblox account or group. It stays on your computer and never reaches our servers.
- Roblox handles your Roblox data under its own privacy policy.
- What we handle
From Roblox, when you connect: your Roblox user id, username, display name, a link to your profile picture, your account’s creation date, the permissions and the games and groups you chose on Roblox’s page, and tokens that let NoSlop act within those permissions: a refresh token (valid 90 days) and an access token (valid 15 minutes). Never your Roblox password.
- Why
So your agents can, from your computer and straight to Roblox, upload models, sounds and images and read and change game passes and developer products (names, prices, icons, whether they’re for sale) in the games you picked. We use it only to do what you ask in NoSlop. We don’t sell it, share it with other creators, use it to track anyone or use it to train AI.
- Legal basis
Our contract with you (art. 6(1)(b)): you asked for this feature.
- How long
Nothing on our servers. On your computer until you press Disconnect (Settings → Roblox account), which also ends the connection on Roblox, or until Roblox ends it. Signing out of NoSlop, or deleting your account in the app, also disconnects it. If you delete your account on the website, disconnect in the app first.
Free access and library curators
- What we handle
If we give you free access to NoSlop (for example as a creator in our creator program), or let you add packs to the library, your email address and a short note on a list.
- Why
To give your account that access.
- Legal basis
Our agreement with you (art. 6(1)(b)).
- How long
Until we take you off the list. Deleting your account doesn’t remove you from it today; ask us and we will.
Update checks
- What we handle
Your IP address and the request, like any website you visit. No account id.
- Why
The app asks our server whether a new version exists 10 seconds after it starts, then every 30 minutes and when you come back to its window, and downloads a new version in the background so it’s ready when you press Restart to update. Versions after 0.8.0 also keep a connection to that server while the app is open, so it can tell them the moment a new version is out; your sign-in is not sent over it. The website asks the same server which installers exist.
- Legal basis
Our contract with you, and our legitimate interest in getting fixes and security updates to you (art. 6(1)(b) and (f)).
- How long
In our account service’s logs, up to 7 days.
Website visit counts
- What we handle
- As you move through our website, your browser sends our account service an anonymous count for each of these steps: a page viewed, the demo seen, the prices seen, Buy pressed, sign-up started, a new account’s first sign-in, checkout started, and coming back from a payment. Only the step’s name is sent: no cookie, no id, no account. The game wikis and the page that opens invite links (/join/) aren’t counted.
- We store only how many times each step happened each day. Nothing in those numbers can tell one visitor from another.
- So that one visitor or script can’t inflate the numbers, our server turns your IP address into a fingerprint (a keyed hash) that changes every day and counts it against a short limit (120 in 10 minutes). The address itself is never stored with the counts. Like any request, it is also in our account service’s logs.
- If your browser sends Do Not Track or Global Privacy Control, it sends no counts at all.
- Why
To see, in total, where visitors stop between the first visit and buying, so we can make the website better. Not to follow or profile anyone.
- Legal basis
Our legitimate interest in knowing how well our website works (art. 6(1)(f)). You can object at any time: turn on Do Not Track or Global Privacy Control in your browser, or write to hello@noslop.gg.
- How long
The daily counts are kept; they say nothing about anyone. The day’s fingerprint is used for 10 minutes at a time and deleted by a daily clean-up once it’s over a day old. Log lines: up to 7 days.
Affiliate links and the affiliate program
- What we handle
- If you arrive through an affiliate’s link (an address ending in
?ref=and a code): your browser keeps that code and the day in its local storage, and sends our account service one anonymous count for that link. Nothing about you is kept or sent. So that one visitor can’t inflate the count, our server turns your IP address into a fingerprint (a keyed hash) that changes every day, as for the visit counts; the address itself is never stored. - When you then create an account or sign in on the account page, the code is sent to our account service once and removed from your browser. We store which affiliate your account came through. If you buy NoSlop within 60 days, that affiliate earns a commission on it, and on your other NoSlop payments in the 12 months after (for example each month of a monthly plan). They see that a sale was made, when, and what they earn from it. They never see who you are.
- If you are an affiliate: what you wrote when joining (your name or channel name, age, country, your channels and why you joined), your code, the clicks on your link, your sales and what we paid you. Before your first payout we also ask for your payment details (whether you invoice as a freelancer or a company, your legal name, tax ID, address and IBAN) and keep your invoices, as the law requires for our books. Each time we open your full IBAN or tax ID (only to pay you), we record who opened it and when.
- Checks against self-referral: for a sale through an affiliate’s link, we compare the buyer’s email address, Stripe customer number and Stripe’s fingerprint of the card (not the card number) with the affiliate’s and with their other buyers’. A sale that matches earns nothing. One that only looks alike is checked by hand before it is paid.
- If your browser sends Do Not Track or Global Privacy Control, it keeps no code and sends no count.
- If you arrive through an affiliate’s link (an address ending in
- Why
To pay the people who send us buyers what we owe them, to stop commissions on their own purchases, and to keep our books.
- Legal basis
Visitors and buyers: our legitimate interest in crediting the person whose link you chose to follow (art. 6(1)(f)). You can object: turn on Do Not Track or Global Privacy Control, clear this site’s data in your browser before you sign in, or write to hello@noslop.gg. The checks against self-referral: our legitimate interest in preventing fraud (art. 6(1)(f)).
Affiliates: the affiliate agreement (art. 6(1)(b)), and our legal duty to keep accounting records (art. 6(1)(c)).
- How long
The code in your browser: until you sign in on the account page, or 60 days. Which affiliate an account came through: until the account is deleted. Click counts: kept as totals per day. An affiliate’s application and payment details: while they are in the program. Commissions and payments: 6 years from the end of the year they were made (tax and commercial law). The card fingerprint: with the purchase record. Who opened an affiliate’s payment details: as long as those details.
The NoSlop Discord bot, Live events and Analytics
Our providers for this are Supabase (Frankfurt, EU), where the data is stored, and Discord, which shows the bot’s posts. Players can ask the game’s creator to delete their data for that game, or write to us at hello@noslop.gg: we pass the request to the creator and act on their instructions, for example by deleting it. NoSlop’s bot is not made or endorsed by Discord.
- What we handle
- About your Discord server and game: when someone links a game with
/linkor Connect Discord, we store the server’s id, the channel for each kind of post, the Discord user id of the person who linked it, the game’s name and Roblox experience id, a one-way fingerprint (hash) of the game’s key, and which NoSlop account it belongs to. With Connect Discord, Discord tells us the server and your Discord user id; we don’t keep the sign-in token it gives us. The bot doesn’t read messages and doesn’t collect anything about the server’s members. - Codes for
/link: when you press “Get a Discord code” on your account page, a one-way fingerprint (hash) of the code, your account and when the code runs out (30 minutes). - About your games in Analytics: when you turn on Analytics for a game in the app, the game’s name, which NoSlop account it belongs to, when it was added and a fingerprint (hash) of its key. A game linked with
/linkand your code is on your account from the start; one linked before/linkneeded a code joins your account when you add it with its key, or when you connect its Discord server to Community. - Live events from the game, for that game only: players’ Roblox user ids; when each player joins and leaves, how long they stay, and when they first and last played; the steps each player reached (moments the game’s creator names, such as “tutorial_done”) and when they first reached each; purchases (item, Robux price and Roblox’s receipt id); error messages from the game’s servers, with player names and long numbers removed in the game and again on our server; and the game servers’ ids, version and player counts. No usernames, display names or account ages are sent or stored.
- About your Discord server and game: when someone links a game with
- Why
To post the game’s updates in the channels you chose: lines without player names or ids (“A player joined · first visit · 7 playing now”, “A player left after 23m 49s”), purchases without the buyer, cleaned-up errors and hourly totals. Discord never gets player names or ids. And to show the game’s owner, and no one else, its numbers on the app’s Analytics page: players per day, who comes back, steps reached, play time, what sells and errors. Event data never goes to AI agents, is never combined with other games or other data, is never sold and is never used to train AI.
- Legal basis
Server details and the games on your account: our agreement with you, or with whoever adds the bot (art. 6(1)(b)). Live events: we handle them on behalf of the game’s creator, who is responsible for their players’ data (the controller); we are their processor under the data processing terms in our Terms.
- How long
Live events: 35 days, or 90 days for the games of an account that subscribes to Analytics, then deleted nightly; when the subscription ends, the next nightly run takes the games back to 35 days.
/unlinkdeletes everything for a game at once, unless the game belongs to a NoSlop account (as every game linked with a code does); then it only leaves the server. Turning Analytics off for a game you added in the app deletes it with all its data; a game in a Discord server instead leaves your account and stays with the bot, and/unlinkthen deletes it. Server details: until/unlink, or until we notice the bot was removed from the server (its posts start failing), when that server’s games and their data are deleted (games that belong to a NoSlop account only leave the server)./linkcodes: until used, until you get a new one, or a day at most once expired; and with your account.
Community: wikis, Discord set-up and announcements
Wikis are public. Anyone can read them, and search engines may list and copy them. When a wiki is hidden or deleted, it leaves our site straight away, but copies others already made (such as a search engine’s) are outside our control. Your agent writes the pages on your computer, with your AI company (see below). Don’t put anyone’s personal data in a wiki or an announcement, including players’ names or ids. Anyone can report a page with “Report this page” or by email to hello@noslop.gg; we handle reports as described in our Terms.
- What we handle
- Your wikis: for each game (up to 5), its wiki address, name and short description, whether it’s published, and each page’s address, title, text (Markdown), order and when it changed. If we take a wiki down, when and why.
- Your Discord server, once you connect it with
/connect: the server’s id and name, the ids of the channels and roles/setupmade or found, when it ran, and the title, channel and time of the last announcement. The text of announcements goes to Discord; we keep only that last title. - Connect codes: only a one-way fingerprint (hash) of each code, valid for 30 minutes.
- Nothing about players is stored for Community, and the bot stores nothing about your server’s members: when someone presses Update pings, it uses their Discord user id only to give or take the role.
- When someone reads a wiki: like any page of our website, their IP address and the request are in our website host’s logs (up to 30 days) and our account service’s logs (up to 7 days). Wikis need no account, set no cookies and store nothing in the browser.
- Why
To host your public wikis, set up your Discord server and post the announcements you approve; to keep the wikis safe and lawful and handle reports; and to keep the website secure.
- Legal basis
Hosting, set-up and announcements: our contract with you (art. 6(1)(b)). Reports and taking wikis down: our legitimate interest in safe wikis (art. 6(1)(f)) and our legal duties under the Digital Services Act (art. 6(1)(c)). Readers’ log lines: our legitimate interest in security (art. 6(1)(f)).
- How long
Wikis: shown while published and Community runs, and for 30 days after it ends; then hidden but kept, so they come back if you subscribe again. Deleted with your account, or earlier if you ask us. Discord server details: until you disconnect the server in the app or delete your account. Connect codes: they stop working after 30 minutes and are cleared the next time a code is made, and with your account.
NoSlop’s Discord server
NoSlop has its own Discord server, only for people who have NoSlop, run by a private bot of ours. It is not the bot you can add to your own server (see above). Joining is optional: if you don’t join, nothing in this section is collected.
To join, press Join the Discord on your account page (Community), sign in to Discord and allow NoSlop to know who you are on Discord and to add you to the server. Only accounts that have NoSlop can do this. We then link that Discord account to your NoSlop account and add it to the server with a Customer role. One Discord account can be linked to one NoSlop account. Every few minutes the bot checks which linked accounts still have NoSlop. When an account stops having it (a refund, a removed team seat, a deleted account, or you disconnect Discord on your account page), the Customer role is removed and you no longer see the server’s channels.
Supabase (Frankfurt, EU) stores this data. The bot runs on Railway, the same host as this website, which handles what Discord sends the bot in memory; only the bot’s error log is kept there (it can name a Discord id, never message text). Discord holds the server, its messages and the staff channels. NoSlop’s bot is not made or endorsed by Discord.
Your choices:
- Disconnect Discord on your account page removes the link, your XP, your message counts and your giveaway entries at once, and your access to the server. Moderation cases and closed tickets stay for the times below.
- What you write in the server is in Discord: you can delete your messages there, and Discord’s own privacy policy applies to them.
- Everything else (access, erasure, a complaint) works as for the rest of this page: see Your rights.
- What we handle
- The link: your Discord user id, your Discord account’s language at the time (English, Spanish or Italian), used to speak to you in your language, and when you joined.
- A join attempt: a one-way fingerprint (hash) of a one-time value, and your account.
- For each member of the server (by Discord user id): XP and level progress, a total message count, and when they joined, left, were welcomed and accepted the rules.
- Daily numbers: how many messages each member wrote each day, and how many were written in each channel each day. A number, never the text. And daily totals with nobody in them: members, joins, leaves and messages.
- Moderation cases: the Discord ids of the member and of the staff member, the kind (warning, timeout, kick, ban or note), the reason staff wrote, and the dates. A ban also keeps which NoSlop account the banned Discord account was linked to, so the ban holds whatever Discord account is used.
- Support tickets: who opened it (Discord id), the topic (purchase or licence, a bug, help with my game, or other), the language, when it was opened, first answered and closed, who handled it, and how many messages it had. The conversation itself is not stored on our side: it stays in Discord, and when a ticket closes, the bot posts a text file of it in a private staff channel in Discord.
- Giveaways: the Discord id of each entry and when it was made, and the winners’ Discord ids. Announcements that staff schedule hold no personal data about members.
- What the bot reads in the server: the messages posted there, to count them (levels and the daily numbers), to show staff edited and deleted messages in a private staff channel in Discord, and to build a ticket’s text file. It also sees who joins and leaves, role and nickname changes, and bans. Message text is not stored on our systems.
- NoSlop’s free community server: the same bot also runs our free, public Discord server. There it stores nothing about members on our systems: it posts joins, leaves and bans in a private staff channel in Discord. Only if you press the Premium badge button does it check whether your Discord account is a customer in the private server, to show the Premium role; it takes the role away when you stop being one.
- Why
To let in only people who have NoSlop, and take the Customer role away when they stop having it; to speak to members in their language; to run levels and giveaways; to answer support tickets; to keep the server safe with moderation and the staff log; and to count, in total, how busy the server is.
- Legal basis
The link, the access check and running the community you asked to join, tickets included: our contract with you, at your request (art. 6(1)(b)). Levels, giveaways and the numbers per member: part of the community service you chose to join (art. 6(1)(b)). The daily totals are statistics with nobody in them. Moderation cases, the staff log and keeping cases for 24 months: our legitimate interest in keeping the server safe (art. 6(1)(f)).
- How long
The link: until you disconnect Discord or delete your NoSlop account. A join attempt: valid 15 minutes, deleted once expired. A member’s XP, message count and dates: deleted at once when the Discord link is removed or the NoSlop account is deleted; otherwise 30 days after they leave the server. Daily counts per member and per channel: 90 days (a member’s own go at once with their link). Daily totals: kept, as totals that say nothing about anyone. Moderation cases: 24 months, also after the link or the account is gone, so that a ban or a warning can’t be escaped with a new account. Tickets: 12 months after they close. Giveaway entries: 30 days after the giveaway ended, and at once when the link is removed; the giveaway and its winners’ Discord ids: 12 months after it ended.
What stays on your computer
NoSlop runs on your computer, and most of what it handles never leaves it. NoSlop doesn’t send these to us:
- Your projects, their files and version history, and the rules NoSlop writes into them, unless you share a project with NoSlop sharing.
- Your prompts, your agents’ conversations, the task board and its notes.
- Your own asset library, including prompts, unless you share an asset.
- Pictures of Roblox Studio your agents take (the newest 30 are kept) and Blender previews (kept for a day).
- Videos your agents make of your game (on Windows): recordings of the Roblox Studio window and of Studio’s own sound, never of the rest of your screen, the voice clips and the finished video, in your Videos folder, under NoSlop. They stay until you delete them.
- Which notes folder your agents may use, if you turn on Obsidian notes.
- Which Analytics game goes with which of your projects.
- The app’s logs, your settings, open tabs and recent projects.
- In your system’s credential store (Windows Credential Manager, macOS Keychain or the Linux secret service): your NoSlop sign-in, your AI, Roblox, ElevenLabs and Meshy API keys and your Roblox connection.
- Your licence token, and the tools NoSlop downloads for you (Python, Rojo, Blender, FFmpeg).
- Your system’s machine id. NoSlop only uses it to make your computer’s id, which is sent instead (see Your computers).
The app collects no usage statistics, no crash reports and no telemetry. “Copy debug info” (Settings → Troubleshooting) only copies text to your clipboard; you decide whether to send it to anyone.
Signing out removes your NoSlop sign-in and licence token from the computer. Remove API keys in Settings and disconnect Roblox in Settings → Roblox account. The rest lives in the .noslop folder in your user folder and in your projects; you can delete them.
What your computer sends straight to other companies
Some things go from your computer directly to another company, without passing through our servers. That company handles them as its own controller, under its own terms and privacy policy, and we don’t receive them.
- Your AI agents. Claude Code (Anthropic), Codex (OpenAI), GitHub Copilot (GitHub), Gemini CLI (Google), Cursor CLI (Anysphere) and Grok Build (xAI) run on your computer, signed in with your own account or API key. They send their company what you type and what they read while they work: your code and project files, what NoSlop’s tools tell them about your game (Studio’s objects, properties, scripts and output, or UEFN’s on accounts that use Fortnite), pictures of the Roblox Studio window (on Windows, taken when an agent needs one, without asking you each time), Blender previews, pictures of library assets, your Obsidian notes if you turned that on, and the task board’s notes. If you choose “Use my API key”, NoSlop gives your key to that one program. These programs may also send their makers their own usage data. Each company has its own age limits: for example, Claude Code and Cursor are for adults, and Google’s Gemini API terms don’t allow anyone under 18. Following them is between you and that company.
- Roblox, when your agents upload models, sounds or images or change game passes and developer products, with your Roblox connection or your own Roblox key: the files, names, descriptions, prices and icons. The app shows your Roblox picture from Roblox’s servers.
- ElevenLabs, when an agent makes a sound with your ElevenLabs key: the sound’s description and length. When an agent makes the voice for a video of your game: the words the voice says (the prompts shown in the video).
- Meshy, when an agent makes a 3D model with your Meshy key: the model’s description, or the picture from your project that the agent makes it from.
- Obsidian involves no network at all: agents read and write Markdown notes in the folder you chose, and NoSlop can open it in Obsidian.
- Downloads. When needed, NoSlop downloads these by itself: Python 3.13 from GitHub (the python-build-standalone project) if your computer has no Python 3.9 or newer; Rojo from GitHub when a project needs it; Blender from download.blender.org if you don’t have Blender 4.2 or newer; and FFmpeg from GitHub (the gyan.dev build) the first time an agent makes a video of your game. Every file is checked against a fixed fingerprint before use. Like any download, those sites see your IP address, the time and which file you asked for, under their own policies. NoSlop sends them nothing about you or your account.
- Free assets. Searches for free assets go to Openverse and Poly Haven, and the files you import come from where they’re hosted (such as Freesound or Wikimedia Commons). Those services see your IP address, the time and what you asked for, under their own policies.
NoSlop’s Studio plugin talks only to NoSlop on your own computer.
AI and your content
NoSlop doesn’t train AI on your content, and doesn’t sell or give it to anyone for training. NoSlop itself never sends your content to an AI company: your agents do, from your computer, under your own account with that company (see above). When other people’s agents use an asset you shared, its picture and details go to their AI company, under that company’s terms. The same goes for a project you share: when the agents of the people in it read it, it goes to their AI companies. NoSlop doesn’t make decisions about you with AI.
Who receives data
These companies receive personal data from our servers. Processors handle it only on our instructions, under data processing agreements. Independent controllers decide for themselves how to use it, under their own policies.
| Who | Role | What for | Where | Transfer safeguard |
|---|---|---|---|---|
| SupabaseSupabase Pte. Ltd. (Singapore), with Supabase, Inc. (US) | Processor | Our account service: accounts, sign-in, purchase records, add-ons, licence tokens, the computers each account uses NoSlop on, connecting Roblox accounts, the community library, game analytics, Community wikis, shared projects (their files and history, details, members and invitations), app updates and NoSlop’s Discord server (links, levels, counts, moderation cases, tickets and giveaways) | Hosted in Frankfurt, Germany (EU). Supabase staff outside the EU may access it for support and operations | Standard Contractual Clauses |
| ResendPlus Five Five, Inc. | Processor | Sending sign-in codes, links, account emails, order confirmations, withdrawal confirmations and invitations to shared projects | Emails are sent from Ireland (EU); Resend is a US company | EU–US Data Privacy Framework; Standard Contractual Clauses as a fallback |
| RailwayRailway Corporation | Processor | Hosting this website and its request logs; running the bot of NoSlop’s Discord server, which handles what Discord sends the bot in memory. The bot’s error log can name a Discord id or a channel (never message text) and is kept by Railway for up to 30 days | United States | EU–US Data Privacy Framework; Standard Contractual Clauses as a fallback |
| PorkbunPorkbun LLC | Processor | The noslop.gg domain, and forwarding emails sent to hello@noslop.gg to our mailbox | United States | Standard Contractual Clauses |
| GmailGoogle LLC | Processor | The mailbox where emails you send us, and our replies, are kept | United States | EU–US Data Privacy Framework; Standard Contractual Clauses as a fallback |
| CloudflareCloudflare, Inc. | Processor | When sign-up or sign-in shows a captcha (Turnstile): checking that you’re a person, not a bot, from your IP address and signals from your browser and device | United States and worldwide | EU–US Data Privacy Framework; Standard Contractual Clauses as a fallback |
| Stripe and LinkSold through Link, LLC and other Stripe companies | Independent controller | Checkout, payment, tax, receipts, refunds, disputes and fraud checks for purchases | United States and worldwide | Stripe, LLC is certified under the EU–US Data Privacy Framework; Stripe’s data processing agreement adds Standard Contractual Clauses |
| Google, DiscordGoogle LLC, Discord Inc. | Independent controllers | Only if you choose to sign in with them | United States | EU–US Data Privacy Framework |
| RobloxRoblox Corporation | Independent controller | Only if you connect your Roblox account | United States | You deal with Roblox directly. Roblox isn’t certified under the Data Privacy Framework; our server sends Roblox only the codes and tokens Roblox itself issued for your connection |
| DiscordDiscord Inc. | Independent controller | Only if you join NoSlop’s Discord server: Discord holds the server, its messages and the private staff channels; our bot gives and takes the Customer role, carries out staff’s moderation actions and posts the staff log of edited and deleted messages and ticket text files there | United States | EU–US Data Privacy Framework |
| DiscordDiscord Inc. | Recipient of the bot’s posts (sub-processor for Live events) | Showing the bot’s posts in your Discord server: lines and totals without player names or ids, and the Community announcements you approve; making the channels and roles Community’s setup adds | United States | EU–US Data Privacy Framework |
We also give data to courts, tax and other public authorities when the law requires it. If NoSlop is ever sold or passed to someone else, your data would go to the new owner, who would have to keep this policy; we would tell you first. We don’t sell your personal data or share it for advertising.
Data outside the European Economic Area
Some of our providers are outside the European Economic Area (EEA) or can reach data from outside it:
- United States: Stripe, Railway, Resend, Google, Discord and Cloudflare are certified under the EU–US Data Privacy Framework, which the European Commission found adequate (Decision (EU) 2023/1795). As a fallback, and for any provider that isn’t certified, we use the European Commission’s Standard Contractual Clauses (Decision (EU) 2021/914).
- Supabase: our database and the files of shared projects are in Frankfurt, Germany. Supabase Pte. Ltd. (Singapore) and Supabase, Inc. (US) may reach them for support and operations, under the Standard Contractual Clauses. Downloads of those files pass through Supabase’s content delivery network, which may serve them from a location near you.
You can read these safeguards in the providers’ data processing agreements (Supabase, Stripe, Resend, Railway, Cloudflare) and check certifications on the Data Privacy Framework list, or ask us for a copy at hello@noslop.gg.
How long we keep it
| What | How long |
|---|---|
| Your account, profile and plan | Until you delete your account |
| A sign-up whose email was never confirmed (never signed in, nothing bought) | 7 days, then deleted automatically |
| Purchase records | 6 years from the end of the year of the sale (tax and commercial law). Unlinked from you when you delete your account |
| Affiliates: your application and payment details; commissions and payments | Until you leave the program or delete your account; commissions and payments 6 years from the end of the year they were made |
| Licence token (on your computer) | Runs out after 48 hours; removed when you sign out |
| Your computers (id, name, system, when added and last seen) and which one is in use | Until you remove the computer or delete your account |
| The history of computers added, removed and taken over | Until you delete your account |
| Resend’s record of emails we sent | A short time set by Resend for our plan; we keep no copies |
| Website request logs (Railway) | Up to 30 days |
| Account service logs (Supabase), including sign-ins | Up to 7 days |
| Rate-limit counters (including the website’s daily visitor fingerprint) | Deleted by a daily clean-up once they’re over a day old |
| Payment events we couldn’t match to an account | Today no automatic limit; not removed when you delete your account |
| Website visit counts (per day, per step; nothing about the visitor) | Kept, as totals that say nothing about anyone |
| Emails you send us and our replies | Up to 3 years after the conversation ends; records of rights requests 3 years |
| Assets you shared | Listed until you stop sharing; the file and its details stay stored until you delete your account |
| Your library answers and reports | Until the asset or your account is deleted |
| Projects shared with NoSlop sharing (files, history and details) | For as long as the project exists. Deleted when its owner deletes it or their account; the files leave storage shortly after |
| Who is in a shared project | Until you leave or are removed, the project is deleted, or you delete your account |
| Invitations to a shared project (the email address; for a link, only a fingerprint) | Email invitations work for 30 days, links for 14 days and one use. Deleted when answered or cancelled, and with the project at the latest |
| Your Roblox connection | Nothing on our servers. On your computer until you disconnect |
| Free-access and curator lists | Until we take you off the list (ask us) |
| Your add-on subscriptions (add-on, tier, status, paid-until date, Stripe numbers) | Until you delete your account |
| Your Community wikis | Shown while published and Community runs, and for 30 days after it ends; then hidden but kept, so they come back if you subscribe again. Deleted with your account |
| Community’s Discord server details (server id and name, channel and role ids, last announcement) | Until you disconnect the server or delete your account |
| Discord connect codes (kept only as a fingerprint) | Valid 30 minutes; cleared the next time a code is made, and with your account |
| Your link to NoSlop’s Discord server (Discord user id, its language, when linked) | Until you disconnect Discord or delete your account |
| A Join the Discord attempt (a fingerprint of a one-time value, the account) | Valid 15 minutes; deleted once expired, and with your account |
| A member of NoSlop’s Discord server: XP and level, total messages, when they joined, left, were welcomed and accepted the rules | Deleted at once when the Discord link is removed or the account is deleted; otherwise 30 days after the member leaves the server |
| Daily message counts in NoSlop’s Discord server, per member and per channel (numbers, never the text) | 90 days. A member’s own counts go at once when their Discord link is removed |
| Daily totals for NoSlop’s Discord server (members, joins, leaves, messages; nobody in them) | Kept, as totals that say nothing about anyone |
| Moderation cases in NoSlop’s Discord server | 24 months, also after the Discord link or the account is gone |
| Support tickets in NoSlop’s Discord server (not the conversation, which stays in Discord) | 12 months after the ticket closes |
| Giveaway entries in NoSlop’s Discord server | 30 days after the giveaway ended, and at once when the Discord link is removed. The giveaway and its winners’ Discord ids: 12 months after it ended |
| Live events from a game (Discord or Analytics) | 35 days, or 90 days while the game’s owner subscribes to Analytics, then deleted nightly; everything for a game at once by turning Analytics off (a game added in the app) or with /unlink (a game on no NoSlop account) |
| Discord bot settings (server, channels, who linked) | Until /unlink, or until we notice the bot was removed from the server |
| Games on your account, added in the app or linked with your /link code (name, key fingerprint) | Until you turn Analytics off for the game (a game in a Discord server then stays with the bot until /unlink). If you delete your account, they stay on no account: see Deleting your account |
| Discord /link codes (kept only as a fingerprint, with the account that asked for it) | Valid 30 minutes and once; deleted when used, when you get a new one, in a daily clean-up once expired, and with your account |
| A Connect Discord attempt (a fingerprint of a one-time value, the account and game, how it ended, the server’s name) | Valid 15 minutes; replaced by your next attempt, deleted once expired the next time anyone connects, and with your account |
When we must delete data but the law requires us to keep it for possible claims, we block it (Spanish data protection law, LOPDGDD art. 32): we keep it apart, don’t use it, and make it available only to courts and authorities until the time limits for claims end, and then delete it.
Deleting your account
Use Delete my account on your account page at noslop.gg or in the app (Settings → Account & plan), or write to hello@noslop.gg. If you have add-ons, cancel them first (under Billing): deletion is refused while one is running or a payment is overdue, and works once it is set to end.
- Deleted straight away: your sign-in and sign-in methods, your profile, your plan and add-on details, your computers and their history, the assets you shared (files and details) with their answers and reports, your own answers and reports, your Community wikis and Community’s Discord server details.
- Projects in NoSlop sharing: every project you own is deleted for everyone in it: its records straight away and its files from storage shortly after. The other people keep the copies on their own computers. You are also taken out of projects other people own. What you already added to those stays in their history, no longer linked to your account but with the name your checkpoints carry.
- Games you added to Analytics or linked to the Discord bot stop belonging to your account. To delete their data straight away, turn Analytics off for them first (Settings → Analytics), and use
/unlinkfor the ones in a Discord server; otherwise their events run out after 35 days, like any game’s. - Kept, and why: purchase records, for 6 years for tax and commercial law, with the link to your account and your Stripe customer number removed; what Stripe and Link hold, under their own policies; logs, until they run out (see the table); support emails, as above; rate-limit counters, until the daily clean-up removes them; and, today, unmatched payment events and the free-access list (ask us to delete these).
- NoSlop’s Discord server: your link, XP, message counts and giveaway entries are deleted straight away, and you lose access to the server. Moderation cases and closed tickets stay for the times in the table.
- Our provider keeps daily backups of the account service. Deleted data disappears from them as they roll over, within 10 days.
- You lose the NoSlop you bought: it belongs to your account and can’t be brought back. The refund rules are in the Terms.
- Not touched: anything on your computer (see above), including your keys: remove them first if you want them gone. Deleting in the app also disconnects Roblox; if you delete on the website, disconnect in the app first. Data you sent to AI companies or Roblox is deleted with them.
Your rights
You can ask us to:
- see the personal data we hold about you and get a copy (access);
- correct it if it is wrong or incomplete (rectification);
- delete it (erasure), unless the law requires us to keep it;
- limit how we use it while something is checked (restriction);
- get it in a common, machine-readable format to take elsewhere (portability);
- stop using it where we rely on our legitimate interest (objection);
- withdraw consent at any time, where we rely on it, without affecting what was done before.
Write to hello@noslop.gg, ideally from your account’s email address, so we know it’s you; otherwise we may ask you to confirm. Some things you can do yourself: delete your account, remove a computer, stop sharing an asset, leave or delete a shared project, disconnect Roblox, disconnect Discord from NoSlop’s Discord server. It’s free. We answer within one month; for complex or many requests we can take two more months, and we’d tell you within the first month.
If you think we’ve handled your data wrongly, you can complain to the Spanish data protection authority, the Agencia Española de Protección de Datos (AEPD), C/ Jorge Juan 6, 28001 Madrid, online at sedeagpd.gob.es, or to the authority where you live or work. You don’t have to write to us first, but we’d like the chance to fix it.
Children and teens
- You must be 13 or older to have a NoSlop account. If you are under 14 (Spain’s age for agreeing to data use online), or under the age your country sets, a parent or guardian must agree to it.
- Under 18, a parent or guardian must buy NoSlop for you or agree to the purchase.
- We don’t check ages: you confirm yours when you create an account. If we learn that an account belongs to someone under 13, we delete it and refund anything it bought.
- We send no marketing to children, show no ads and build no profiles. In the library, a name is shown only if its owner chooses.
- In a project shared with NoSlop sharing, the people in it can see your email address, and the part before the @ appears in the project’s history. Only share with, or join, people you trust.
- Parents and guardians can ask us to see or delete a child’s data: write to hello@noslop.gg with the email address of the child’s account. We may ask you to confirm you’re their parent or guardian.
How we protect it
- Everything sent to and from our servers travels encrypted (HTTPS), and the website uses a strict content security policy: the only outside script it allows is Cloudflare’s human check.
- Passwords are stored only as hashes. Sign-in codes expire after 15 minutes and sign-in tokens are replaced as they’re used.
- Our database only lets each account read its own rows; plans and payments are written only by our server, and its keys never leave it. Library files are kept in private storage, readable only by accounts with access. Shared projects are in private storage too: only the project’s members get links to them, which last an hour to download and 2 hours to upload.
- Buying, the billing page, licence checks, account deletion, connecting Roblox, adding Analytics games, Community’s actions, NoSlop sharing, Discord connect and
/linkcodes, what each game sends and the website’s visit counts are rate-limited. Codes, invite links and game keys are kept only as fingerprints. When it’s switched on, sign-up and sign-in check that you’re a person, not a bot. - On your computer, sign-ins and keys are kept in your system’s credential store, not in plain files. Agents never see your Roblox tokens, and the Studio plugin only talks to NoSlop on your computer, with a random key.
- Licence tokens and app updates are signed and checked before use, and a licence token works only on the computer it was signed for; downloaded tools are checked against fixed fingerprints.
No system is perfectly safe. If a breach puts your data at risk, we tell the AEPD within 72 hours, and tell you without delay if the risk to you is high.
Automated decisions
We don’t make decisions about you based only on automated processing that have legal or similarly significant effects, and we don’t profile you. A few things happen automatically as part of the service: the app checks whether your account owns NoSlop, so a refund or a payment dispute stops the agents; NoSlop stops on a computer when you use it on another one or remove that computer, and a fourth computer is refused; add-ons stop when their subscription ends, and a wiki is hidden 30 days after Community ends; the Customer role in NoSlop’s Discord server is removed when an account stops having NoSlop; an asset reported by three people is hidden until a person looks at it; and Stripe screens payments for fraud as its own controller. If you think something went wrong, write to hello@noslop.gg and a person will look at it.
If you live outside the EU
We give everyone the rights above, wherever they live. In addition:
- United Kingdom: the UK GDPR gives you the same rights. You can complain to the Information Commissioner’s Office (ICO). Transfers to the US use the UK Extension to the Data Privacy Framework or the UK addendum to the Standard Contractual Clauses.
- United States: we don’t sell or share personal information, and we don’t use it for targeted advertising. NoSlop isn’t meant for children under 13, and if we learn we have data from a child under 13, we delete it.
- Brazil: under the LGPD you can confirm whether we process your data and use the rights above by writing to hello@noslop.gg, and complain to the ANPD.
Changes to this policy
If this policy changes, we update the date at the top. If a change is important, we tell account holders by email or in the app before it applies. Ask us at hello@noslop.gg for an earlier version.