Editorial Guidelines

Sourcing & Verification

• Track official developer announcements, Discord servers, livestreams, and in-game notices daily.
• Redeem every working code in-game or confirm screenshots from trusted community testers.
• Label uncertain reports as “Needs Check” until a staff member verifies them.

Update Cadence

Codes pages refresh every time a new drop is confirmed or an old reward expires. Routine scans are logged as the page's “Last checked” date, while the structured data only changes when real content updates occur.

Corrections

Mistakes happen. When readers flag an issue via the contact page, we investigate within one business day. Confirmed corrections include a timestamped note and, when relevant, credit for the tip.

Attribution & Ethics

We link to the original developer channels when they share codes first and clearly mark sponsored placements. Contributors must disclose any developer relationships before publishing coverage.

Reviewer Expertise

Each writer maintains expertise in their assigned genres and keeps an active Roblox account to validate rewards. You can check author credentials on the author listing.

Staying Transparent

These guidelines evolve alongside Roblox and community expectations. Significant adjustments will be noted here with a revision date so you always know how the team operates.