Last updated: 15 October 2026 · 한국어로 보기
Summary. RoVuew looks at public Roblox information and a few reputation lists so a community's staff can decide who joins. We only keep something about a person when one of their items was flagged, and then only the flagged items, for 180 days. Staff make every decision. You can see, correct or delete what we keep, or opt out of being checked, free of charge.
The rest of this page is the long version. It is written to meet the EU and UK General Data Protection Regulation (GDPR) and South Korea's Personal Information Protection Act (PIPA). If the Korean version and this one ever differ for someone in Korea, the Korean version applies to them.
RoVuew is a Discord bot and this website (rovuew.xyz), run by the RoVuew team, a small independent group based in South Korea. We are the "controller" (GDPR) and "personal information controller" (PIPA) for the data described here: we decide what is kept and why. We are not part of, or approved by, Roblox Corporation or Discord Inc.
Contact: [email protected], or our Discord (section 14). Data protection officer: we haven't appointed one, as the law doesn't require it for a group our size; the privacy team in section 14 handles everything. EU representative (GDPR Article 27): we haven't appointed one; contact us directly.
/check, members of a server whose staff run /guildcheck. Most of this page is about you.We never ask the person being checked for anything, and never read Discord messages. Everything comes from these sources:
| Source | What we read |
|---|---|
| Roblox (public profile services) | Username, user ID, when the account was made, inventory items (or, if the inventory is private, what the avatar wears and its saved outfits), badges and the dates they were earned, item pictures |
| Server Sweep, TASE | Whether they hold a record for a Discord account |
| XTracker | Whether it holds a cheating record for a Roblox account |
| Bloxlink | Which Roblox account a Discord member linked (only for servers whose owner gave us their Bloxlink key) |
| Discord nicknames | For a server check without a Bloxlink key: the Roblox username in members' nicknames, for example "Name (@username)" |
| Staff using the bot | The username or ID they typed, and the Discord ID of the person running the command |
If you ask, we tell you where any data about you came from, what we use it for, and that you can ask us to stop.
The full result is put together and shown to the staff of the Discord server that ran the check. We keep our copy for 1 hour so the page buttons work, then delete it. The message itself stays in that Discord server's channel until its staff delete it (see section 6).
Only if a check found items on our flag list, we keep a small record so staff can still see it after the inventory is made private or the item is removed:
| What | Example |
|---|---|
| Roblox user ID and username | 1234567, xX_trooper_alt_Xx |
| Each flagged item: name, type, score, short reason | "Skin Shirt", clothing, 2, "painted on abs" |
| When each item was first and last seen | 3 Jun – 9 Oct 2026 |
| When the account was first flagged and last checked | dates |
We do not keep full inventories, badge lists, badge graphs, item or avatar pictures, account age, the AI's overview or suspicion score, reputation results, Discord IDs, or anything at all about accounts where nothing was flagged. Item pictures in a check are fetched from Roblox fresh each time and not stored.
/guildcheck: the server ID and name, who approved it, and when it last ran a server check./guildcheck checks the members of the server where its staff run it. Nothing extra is kept about them: the result works like a single check (section 3.1), and someone who opted out (section 12) is skipped.
The flag list and the AI's notes on catalog items are about items, not people. We keep those as long as they are useful. We also look through Roblox's public catalog for bad items on our own; that looks at items only, never at users or inventories. To find more items from the same uploader, we keep the Roblox ID of the creator of a flagged item for up to 30 days, never their name. One exception: when the AI flags a new item during a check, our review team's copy of that flag notes the Roblox user ID and username it was found on, and which check found it, so the team can look at it in context. Only our review team sees this, and it is deleted after 180 days, or straight away if that person opts out.
A member can look through a Roblox account's public items and report one they think breaks the rules (the /report command, or the browse button on a check). A check and the browser look at every kind of public catalog item the account has, not only clothing and accessories. Items made by Roblox can't be reported. A report adds the item to the flag list for staff to look at, and keeps, with that flag, the item's name, type, the reporter's score and reason, and the Discord user ID of the member who reported it, so staff know who sent it. Only our review team sees who reported an item. It is kept as long as the flag is useful; ask us to remove it (section 11).
The bot writes a technical log on our server. It can contain a Roblox username or ID when something goes wrong. Only we read it, to fix problems, and old logs are cleared automatically, normally within a few weeks.
We don't look for or keep sensitive information such as health, religion, political views or sexual orientation. Some flagged items are sexual or hateful in nature; a record says an item was flagged, it says nothing about the person's own life.
Purpose. RoVuew helps roleplay communities keep out accounts that bring sexual, hateful or harmful content, and repeat troublemakers known to other communities. We use the data for that purpose only: no ads, no selling, no profiles for anyone outside the servers that use RoVuew.
EU and UK (GDPR). Our legal basis is legitimate interests (Article 6(1)(f)): the interest of communities, and of their members, in moderating who joins them. We weighed that against the people being checked. That is why we use only public information, keep almost nothing, delete it on a timer, never let the AI decide anything, and let anyone delete their record or opt out without giving a reason. Bloxlink keys are kept because the server owner chose to give them to us.
Do you have to give us anything? No. No law or contract requires anyone to provide data to RoVuew, and the person being checked is never asked for anything. If you don't want to be checked at all, you can opt out (section 12).
South Korea (PIPA). We process information the person has already made public on Roblox, or that public reputation services hold, only within the scope and purpose for which it is public, as Korean courts have allowed. Where that does not apply, we rely on Article 15(1)(6): our legitimate interest, which is clearly related to the information and stays within a reasonable scope. We do not collect resident registration numbers or any unique identifying information.
RoVuew uses Google's Gemini AI in two places:
This is profiling. In the overview, the AI gives its opinion on whether the account looks like an alt (a second account), and a suspicion score from 0 (clean) to 1000 (most suspicious). The main signals are: flagged items and how they were confirmed, the account's age, the badge pattern (for example very few badges for an old account, or most badges earned in one sudden burst), and records on reputation lists. The score is the AI's rough judgement, it can be wrong, and it is not stored.
Criteria, procedure and method. Criteria: flagged items and whether staff confirmed them, account age, how many badges and when they were earned, and records on reputation lists. Procedure: when staff run a check, RoVuew puts that together, and only in 18+ servers Gemini writes its opinion and score. Only the staff who ran the check see it, and they decide after looking at the evidence. Method: the opinion and score are for reference only; no action is ever taken automatically because of them, and they are not stored.
A person always decides. RoVuew never bans, kicks, blocks or ranks anyone by itself. The overview is a note for staff, and the staff of each server decide what to do after looking at the evidence; our terms require that. Every AI item flag goes to a review channel where our team checks it. So no decision about anyone is made solely by automated means (GDPR Article 22, PIPA Article 37-2). Even so, you can ask us to explain how a result about you came about, ask a person to look at it again, tell us your side, and have a wrong flag taken off (section 12).
How Google uses it. We may use Gemini's free tier. On the free tier Google may use what is sent to improve its products, and trained reviewers may read it after Google disconnects it from our account. On a paid plan Google says it does not. Because of this we send only what is listed above, never Discord IDs, and nothing at all about people who opted out.
We don't sell or rent personal data, and we don't share it for advertising.
| Who gets it | What | Why | How long they keep it |
|---|---|---|---|
| Staff of the Discord server that ran the check | The check result: items, flags, badges and graph, reputation results, the AI overview and score | To decide who joins their community | As long as that server keeps the message. Each server controls its own messages; ask its staff, or us, to have them removed. |
| Company | What they do for us |
|---|---|
| Google LLC (Gemini API) | The AI item check and the check overview (section 5) |
| Discord Inc. | Delivers the bot's messages in the server |
| Cloudflare, Inc. | Carries website and API traffic, and blocks attacks |
To look things up we send an ID to: Roblox (the Roblox ID being checked), Server Sweep and TASE (Discord IDs), XTracker (Roblox IDs), and Bloxlink (Discord or Roblox IDs). Each has its own privacy policy.
Server Sweep in particular. Server Sweep keeps its own database of members of servers it tracks as condo or NSFW servers, with message counts, some message content, join and last-seen dates, and roles, and keeps it indefinitely. We don't store any of that; we only show its answer in a check. For lookups, Server Sweep logs the API key, the request and the time, with the caller's IP address encrypted, for 5 days, and it passes the IDs on to TASE and Rotector. To dispute a Server Sweep record, use its own appeals server (it accepts appeals once someone has been clean for 3 months; an accepted appeal hides the record, and full deletion can then be asked for in its support server). See Server Sweep's privacy policy.
We may also have to give data to authorities if the law truly requires it, and then only what is required.
Our server is in South Korea. Some data goes abroad as part of a check:
| Recipient and contact | Country | What | When and how | Why | Kept by them |
|---|---|---|---|---|---|
| Google LLC, privacy contact | United States | Item pictures and names; in 18+ servers, the check summary and badge graph (section 5) | At each check, over an encrypted connection | AI item check and opinion | Under Google's API terms; on the free tier Google may keep it to improve its products (section 5) |
| Discord Inc., [email protected] | United States | The check result shown in the server | At each check, over an encrypted connection | To show it to staff | Until the message is deleted |
| Cloudflare, Inc., privacy policy | United States and its global network | Website and API traffic, including IP addresses | On each visit or request, over an encrypted connection | Keeping the site up and safe | Briefly, for security |
For people in the EU or UK, these transfers rely on the European Commission's adequacy decision for the EU–US Data Privacy Framework (and the UK extension to it) where the company is certified, or otherwise on the European Commission's Standard Contractual Clauses in those companies' terms. South Korea itself has an EU adequacy decision, so data reaching us in Korea needs no extra safeguard. You can ask us (section 14) for a copy of, or a link to, the safeguards used for any of these transfers. Under PIPA, these transfers are needed to provide the service and are disclosed here (Article 28-8). If you don't want your data to go abroad this way, opt out (section 12): an opted-out account is never checked, so nothing about it is sent anywhere.
| What | How long |
|---|---|
| A full check result | 1 hour, in memory only |
| A person's flagged-item record | Deleted 180 days after the last time a flagged item was seen on them. An item also comes off everyone's record straight away if our team decides it was flagged by mistake. |
| Opt-out list | As long as you stay opted out (only your Roblox ID and the date) |
| Staff actions on flags and review cards | As long as the flag exists |
| Approved servers | Until the approval is taken back |
| Bloxlink keys | Until the owner removes it, or the bot leaves that server |
| Server logs | Cleared automatically, normally within a few weeks |
No law requires us to keep any of this longer.
When data reaches the end of its time above, or someone asks for deletion, it is deleted automatically in a way that can't be recovered. Storage we stop using is wiped before it is reused or thrown away. We don't print personal data.
No system is perfectly safe. If a breach puts people at risk, we will tell the people affected and the authorities as the law requires (within 72 hours where GDPR or PIPA require that), and say what happened and what we are doing about it.
Many Roblox players are under 18, and some are under 14. RoVuew never contacts the people it checks, never asks them for anything, and only reads what Roblox already shows publicly, so it does not rely on anyone's consent, including a parent's. Because children may be checked, we keep the absolute minimum (section 3.2), delete it on a timer, and act on any deletion or opt-out request from a young person or their parent or guardian straight away, without needing more proof than the Roblox account. Staff and server owners using the bot must meet Discord's own minimum age.
Wherever you live, you can ask us to:
While a correction or deletion you asked for is being handled, we don't use or share that data.
To ask, contact us (section 14) with your Roblox username. We may ask you to show the account is yours, for example by putting a short code in your Roblox profile for a minute. A parent, guardian or someone you authorise can ask for you. We answer within 10 days, and always within one month. It's free. If we can't do something you asked, we'll tell you why and how you can challenge that.
If you're in California: we don't sell or share personal information for advertising, and we treat requests from California like everyone else's.
This site has no cookies, no trackers, no analytics and no ads, so there is nothing to accept or turn off. We don't collect browsing behaviour for advertising, we don't process pseudonymised data, and we don't use data for any additional purpose beyond section 4. It doesn't load fonts or scripts from other companies. Pages go through Cloudflare, which may briefly keep your IP address to protect the site from attacks.
Privacy officer (개인정보 보호책임자): the RoVuew privacy team, [email protected]. You can also reach us in our Discord, discord.gg/7tQAyqyHdS (open a ticket or DM a staff member).
If you're not happy with how we handled something, we'd like the chance to fix it first, but you can always go to an authority:
If we ever want to use data for a purpose other than the ones in section 4, we will tell the people concerned about that purpose before we start, together with the information in this policy that changes because of it.
If we change this policy, we'll update the date at the top and post about it in our Discord at least 7 days before it takes effect. If a change means keeping more about people or using it in a new way, we'll announce it at least 30 days before it starts.
Also see the terms of service.