Bonus code

How promo claims should be verified before they become a habit

The headshot desk does not run a paid contest, does not publish a bonus code and does not guarantee any return. This page documents how a reader can verify a promo claim before deciding to act on it, and what the desk does if a third-party "headshot bonus code" surface is reported.

Bonus code verification illustration

Why no code

The desk does not publish a bonus code

The headshot desk is an editorial newsroom. The desk does not run a paid contest, does not host a wallet and does not publish a bonus code. The only commercial surface on the site is a single first-party play entry route with disclosure, reached via the header CTA or the mobile sticky bar.

If a third-party surface claims to publish a "headshot bonus code", the desk's standard advice is to verify the surface on the official organizer feed before acting. Promo claims that cannot be verified on a canonical source are a high-risk signal, and the desk's editorial standard is to never endorse a promo claim without verification.

The desk's editorial boundary on wagering context is published on the responsible play page. The boundary has three rules: no guaranteed return, no payout language, no winner language. Any surface that violates the boundary is acting outside the desk's editorial standard.

Verify before you act

Four steps for any promo claim

1

Find the canonical source

Every legitimate promo claim has a canonical source — the organizer's official page, the team channel, the regulator's public notice. The desk asks readers to start there.

2

Read the small print

Real promo claims always carry eligibility, expiry and jurisdictional framing. The desk never endorses a claim that hides any of these in the small print.

3

Check the 18+ marker

If a promo claim does not show an 18+ marker, it is acting outside the desk's editorial standard. The desk treats this as a hard fail.

4

Use the desk's review

The desk publishes a stand-alone note on the newsroom if a credible promo surface is identified. The desk never republishes a phishing URL.

No claim by the desk

What the desk does and does not promise

The desk does

Publish a play entry route with disclosure. Show 18+ marker. Show jurisdiction framing. Link to the responsible play page. Update the entry on every site refresh.

The desk does not

Publish a bonus code. Publish a payout rate. Publish a "lock" or "sure win" tip. Promote a third-party promo surface. Verify a promo claim on the reader's behalf.

Why

The desk is an editorial newsroom. Verifying a promo claim requires access to the organizer's internal data, which the desk does not have. The desk's standard practice is to publish the boundary and let the reader verify on a canonical source.

Language

What promo language the desk refuses to publish

The desk's editorial boundary on promo language is plain. The desk never publishes a "sure win", a "lock", a "guaranteed payout", a "free bonus", a "risk-free bet", or any other variant of language that promises a result. The desk publishes reads, not predictions. The desk publishes context, not outcomes. The boundary holds on every desk, every guide, every newsroom brief.

Where promo language appears in a third-party surface, the desk's editorial standard asks the reader to verify the surface on a canonical source. The four red flags are listed on the referral page. The same four red flags apply to any promo claim. If a surface hides any of the four, the desk's recommendation is to close the surface and verify on the organizer feed.

The desk's standard practice is to publish the boundary and let the reader verify. The desk does not chase promo claims across the network. The desk does not endorse a promo claim. The desk does not promote a promo claim. The desk's editorial role ends at the URL; the verification step is the reader's.

Third-party

What a third-party "headshot bonus code" usually is

The phrase "headshot bonus code" is a high-risk search term for a brand with no app and no platform. The top results are usually affiliate networks, tracking surfaces, and SEO landing pages that route the reader to a third-party wallet. The reader enters their details on the third-party surface, the affiliate network earns a commission, and the desk has no editorial control over the surface.

The desk's editorial boundary on the affiliate surface is the same as for any promo claim. The surface must be verifiable on a canonical source, must show an 18+ marker, must show jurisdiction framing, and must link to the responsible play page. The desk treats the absence of any of these items as a hard fail. The desk does not endorse a third-party surface that does not meet the standard, and the desk does not promote a third-party surface via the bonus-code page.

Red-flag checklist

The four red flags a reader should check before acting on any promo claim

The first red flag is the absence of a canonical source. A real promo claim always has a canonical source — the organizer's official page, the team channel, the regulator's public notice. The reader should find the canonical source before acting on the claim. If the claim cannot be verified on a canonical source, the desk's recommendation is to close the surface.

The second red flag is the absence of eligibility framing. A real promo claim always has eligibility rules. The eligibility rules are the conditions that the reader must meet to qualify for the claim. The eligibility rules are documented in plain language, not hidden in a small-print block. The reader should read the eligibility rules before acting on the claim.

The third red flag is the absence of jurisdiction framing. A real promo claim always has jurisdiction framing. The jurisdiction framing is the set of jurisdictions in which the claim is valid. The jurisdiction framing is documented in plain language, not hidden in a small-print block. The reader should read the jurisdiction framing and verify the local rule before acting on the claim.

The fourth red flag is the absence of an 18+ marker. A real promo claim always has an 18+ marker. The 18+ marker is shown in plain language, not hidden in a small-print block. The reader should check for the 18+ marker before acting on the claim. If the marker is missing, the desk's recommendation is to close the surface and verify on the organizer feed.

The four red flags are not a legal compliance tool; the four red flags are an editorial discipline. The desk applies the four red flags to itself. The desk asks the reader to apply the four red flags to any third-party surface. The desk's editorial role is to publish the four red flags; the reader's role is to apply the four red flags.

What the desk does

How the desk responds to a credible promo surface

If a reader identifies a third-party promo surface that uses the headshot brand name or logo without authorisation, the desk routes the report to the security contact listed on the contact page. The standard report should include the URL of the third-party surface, the date the reader first saw the surface, the device and browser used, and a screenshot if possible.

The desk's standard practice is to read security reports in the order they arrive and to publish a public note on the newsroom if a credible surface is identified. The desk does not republish a phishing URL in public copy. The desk does not name a phishing surface without verifying the report with a security partner. The desk treats the public note as a stand-alone correction that respects the reader who reported the issue.

How promo claims spread

Why a promo claim outlives the original surface

A promo claim typically outlives the original surface because third-party surfaces republish the claim. The republishing is often automated; the original surface is the canonical source, and the republishers are tracking surfaces that route the reader to the original surface for a commission. The republishers are not the desk's editorial surface, and the republishers are not under the desk's editorial control.

The desk's standard practice is to surface the verification step on the bonus-code page and the contact page. The reader should verify the claim on the canonical source, not on a republisher. The reader should check the URL bar, the certificate, and the canonical list on the official-website page. The reader should not enter a password on a republisher surface. The reader should not grant unusual device permissions on a republisher surface.

For readers who want to know whether a promo claim is still valid, the desk's standard practice is to check the original surface. The original surface typically maintains a current list of valid claims. The original surface typically maintains an expiry date for each claim. The reader's role is to check the original surface; the desk's role is to surface the verification step.