On every reviewed version:
Trust and safety on Rodex
Every asset is opened in Studio by a person before it goes live. Here is exactly what that covers, what it does not, and what we promise when something goes wrong.
On this page
What "Staff reviewed" means
Every listing on Rodex is reviewed by a person before it goes live, and every new version is reviewed again. When a version passes, it gets this badge:
Staff reviewed · version · date: a Rodex staff member opened this version in Studio and checked it against our published checklist.
We usually review within 3 working days.
What it checks
- The files open in Studio and match the listing: what you see in the images is what you download.
- Every script, including disabled scripts and scripts inside packages and models, against the checklist below.
- The files are hosted on Rodex. A listing that only delivers an outside link fails review.
- Roblox technical rules: meshes and images set so they load in your game, animations included in the file, audio included as files.
- A playable demo place where we ask for one (scripted systems, game templates and GUI), opened and tried by the reviewer.
- The seller states how AI was used: none, AI-assisted or mostly AI.
What it does not mean
- It is not a promise that an asset is "safe" or "virus-free". We never use those words. A reviewer can miss something, so the checklist is public and anyone can report a problem.
- It covers one version. A new version shows "In review" until it passes, and any change to the files resets the badge.
- It is not a quality rating. Ratings come from verified buyers' reviews.
- It does not check that the seller owns the work beyond what we can see. Sellers must own what they sell; stolen or leaked work is removed and the seller banned.
The review checklist
Reviewers open each file in an empty baseplate with HTTP requests and loadstring turned off, list every script with its path, length and longest line, and search the whole tree for these patterns.
| Check | What the reviewer looks for |
|---|---|
| Remote code loading | require with a number, a built-up or hex ID, or a model inserted at runtime instead of a module inside the file. |
| Dynamic execution | loadstring, getfenv and setfenv used to hide what runs. |
| Hidden strings | Text assembled from character codes, escaped bytes, reversed strings or a home-made decoder that feeds code. |
| Hidden placement | Scripts buried 10 or more levels deep, named like Roblox's own scripts, or with look-alike characters and trailing spaces in the name. |
| Off-screen code | Code pushed hundreds of spaces to the right or hidden after many blank lines. |
| Data sent out | HTTP calls to webhooks or paste sites. Allowed only when documented, set by you, off by default and disclosed on the listing. |
| Purchase prompts | Prompts for the seller's own items or passes, prompts when a player joins, or product IDs hard-coded outside the settings. |
| Admin backdoors | Remotes that run code, admin given to a hard-coded user or group, hidden remotes. |
| Destructive code | Scripts that rewrite other scripts, copy themselves around or teleport players somewhere unknown. |
| Plugin infections | Plugins that edit other scripts, insert into the server when unloading or watch everything added to the game. |
The reviewer then runs a play test while watching outgoing requests, and records the result with their name, the date and a fingerprint of the file.
Other signals you will see
| Signal | What it means |
|---|---|
| Playable demo | Try it in Roblox before you buy. A reviewer checked the demo link. |
| Files hosted on Rodex | You download the files here, with no outside links needed. |
| Roblox linked | This developer has linked a Roblox account. |
| Verified seller | Identity and payouts verified by our payment provider. |
| Verified developer | Staff confirmed this developer owns or helps build a live Roblox game. |
| Verified purchase | The reviewer bought the item. Only buyers can review, sellers can reply but cannot remove reviews, and staff remove reviews only for breaking the rules. |
Every listing also shows the seller's history: when they joined, a sales band, how quickly they reply and their refund rate band.
Refunds and disputes
- First reply within 2 working days, a decision within 5. A person reads every request.
- Refunds are decided case by case, by staff, using the refund policy. Open a request from your library or the help page.
- If a refund happens within the 7-day hold, the seller's share is simply cancelled. After the hold, the payout is reversed.
- If you open a card dispute with your bank, Rodex pays the dispute fee. Please talk to us first: it is faster for you.
- For commissions, the buyer has 7 days to approve the delivery, ask for changes or open a dispute.
How to report a problem
- Every listing, profile, request, job, showcase post and comment has a Report button. Reports go straight to staff.
- Two reports of malicious code or stolen work from verified buyers hide a listing and pause its payouts until staff decide.
- For anything else, use the contact form. Choose "Report a safety problem" and we look at it first.
Staff never DM you first
Rodex staff will never DM you first asking for payment or your Roblox login. We will never ask for your password, your Roblox cookie or a payment outside Rodex.
If someone does, it is a scam: do not click their links, report the account, and check the official links page for the only real Rodex addresses.