Commercial intent is allowed. Manufactured certainty is not.
Independence and commercial relationships
Broker.codes may earn compensation when a code or partner route attributes an eligible customer. That relationship is disclosed on the relevant record. Compensation does not determine a verification label and is not evidence that an offer is suitable or best.
Publication standard
A public offer must have an exact provider, an exact code or attribution route, a source record, a check date and a conservative market fallback. Benefits are omitted when they cannot be supported.
We do not publish development fixtures as deals. We do not turn a representative statement into provider-published terms, and we do not silently merge separate promotions.
Language
Copy should be sharp, concise and understandable to a newer trader without becoming patronising. We avoid get-rich language, casino framing, false urgency and claims that a promotion changes the risk of a trading product.
Authorship and review
Launch content is attributed to the Broker.codes editorial desk. The site does not invent staff biographies, qualifications or regulatory credentials. The data model can record a named author, reviewer and verifier when real people take those roles.
Conflicts, updates and removals
A materially wrong code, expired campaign or newly restricted market should be corrected or paused even if doing so reduces conversion. Useful expired pages may remain with a clear state and history; thin expired pages can be removed or redirected when that better serves the original intent.
AI-assisted work
Automation may help structure facts, flag duplication or run QA. It does not make final regulatory calls, invent missing offer terms or approve publication. Every public commercial sentence remains accountable to the source record.