Contact

Contact the Clutch desk

Press, corrections, and general desk mail. Include URLs and primary sources when requesting a correction.

Corrections

Email pattern for implementers: editorial at clutch11.com (replace with live inbox when provisioned). Include page URL, quote the line, and attach a primary source.

Press

Event access and methodology questions welcome.

Privacy

Data requests via /privacy/ process notes.

How to use this page

Read the answer-first sections, then the checklists and tables. If a field is empty, treat emptiness as a signal to verify on official channels rather than a missing decoration. Cross-link into competition desks when your question turns into schedule, roster, patch, or viewing work.

Editorial first

Explainers and standards before any commercial route.

No credential asks

Clutch articles never collect passwords or OTPs.

18+ boundary

Adult audience; see responsible play for guardrails.

Practical reader workflow

Start with the hero promise and the first checklist. If you arrived from search looking for a binary yes/no, slow down: jurisdiction, product terms, and source dates change answers. When you need match context, jump to the matches or tournaments desks instead of forcing this page to impersonate a live data feed.

If you continue into a disclosed first-party route from mobile sticky or an in-body panel, notice the disclosure. Editorial rankings and methodology do not depend on that path. Responsible play rules still apply after you leave the article surface.

Corrections belong on the record. If something here drifts from a primary source you trust more, send the URL, the quoted line, and the better source via contact. We timestamp material fixes rather than silent-editing history into a highlight reel.

Internal links to keep handy

Tournaments for stage machines, matches for windows, teams and players for verification, games for patch boards, guides for watch plans, news for dated notes.

Out of scope here

Invented live brackets, fake bonus guarantees, unrelated sports modules, gambling table lobbies, and credential harvesting forms.

Mail that helps us help you

Useful correction mail includes the URL, the exact line, the better primary source, and your timezone if timing matters. Screenshots help when the live DOM may change.

Press requests for access should say which event, which day, and whether you need methodology conversation or operational logistics.

URL + quote + source

Correction trinity.

Timestamps welcome

Especially on schedules.

Press specificity

Event and day.

No credential mail

Never send passwords.

FAQs

What does the contact desk refuse to invent?

Live scores, unverified rosters, prize pools, and patch numbers without a dated primary source.

How often are pages updated?

When primary sources move. Evergreen methodology stays stable; dated fields change with as-of stamps.

Can I trust social screenshots?

Not as standings. Social can trigger reporting, but confirmation needs publisher, TO, or team primary channels.

Where do viewing rights fit?

In the viewing matrix. We describe platform types and accessibility checks without guaranteeing your local rights.

Is there a mobile app requirement to read Clutch?

No. The site is the editorial surface. App and download pages explain official channels only.

How do affiliate routes appear?

As disclosed first-party paths separate from rankings. Editorial does not sell outcomes.

What age is this for?

18+. Competitive coverage is not underage wagering content.

How do I send a correction?

Use the contact page with the URL, the claim, and a primary source link.

Does contact coverage drift into unrelated sports or casino modules?

No. Clutch stays on esports competition literacy.

Why are some tables partly empty?

Empty is honest. We show field labels so you know what to verify rather than filling fiction.