Privacy

Privacy notice

How clutch11.com approaches personal data on an editorial esports site: minimal collection, cookie caution, and request paths.

We aim to collect as little personal data as needed to operate the site. Analytics, if enabled by the host, should remain aggregated.

Do not send passwords or government IDs to editorial inboxes unless a verified support process requires them inside an official product flow.

For deletion of product accounts, see delete account.

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.

Minimal data posture

Editorial sites should not pretend to be banks. We aim for minimal collection. Hosting analytics, if present, should stay aggregated. Do not email sensitive IDs to editorial aliases.

Product account data lives under product processes, not necessarily under the newsroom inbox. Use delete-account guidance for product exits.

Minimize collection

Editorial default.

No ID to newsroom

Wrong channel.

Product vs editorial

Different processes.

Host analytics caution

Aggregated if any.

FAQs

What does the privacy 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 privacy 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.