Support
Single operatorGetting a straight answer
Clutchhall is run by one operator. That shapes what you can expect: careful answers about locks, scoring, and corrections, prioritised around the moments a round is actually at stake — and no promise of a response time that a single person cannot keep.
How to reach Clutchhall
Contact not yet published- Support email
- support addressrequired before launch
- Legal notices
- legal notice addressrequired before launchA postal address for formal notices. It has to be a real one, so it is not written here until it is.
- Rights requests
- Export, correction, and deletion requests go through your account: privacy and your data. The privacy notice explains what happens to each kind of request.
- Service incidents
- Service status reports which services are configured and what each one affects.
Clutchhall has no support telephone number and no chat queue. Anyone contacting you by phone claiming to be Clutchhall support is not Clutchhall, and Clutchhall will never ask you for a password or a sign-in link.
What to expect
- No service level is promised
- There is no published response time, because one operator cannot guarantee one and a number nobody can keep is worse than no number.
- Lock windows come first
- Availability and support effort are prioritised around lock windows and scoring runs. A question that affects whether a round can be submitted is handled ahead of one that does not.
- An answer names the evidence
- A reply about a lock or a score states what the server recorded and when, not an opinion about what probably happened.
- No retroactive selections
- If Clutchhall is unavailable during a lock window, the response states what will happen to the affected round. Clutchhall does not accept, reconstruct, or invent a selection after its lock.
What to include in a lock or scoring question
05 details| # | Send this | Because |
|---|---|---|
| 01 | The community and the competition | Both by name. A community may be running more than one competition of the same game type. |
| 02 | The round | Its number as shown in the competition, so the right lock and the right scoring run are examined. |
| 03 | The event | Which matchup, by team names. For Confidence, say which value you assigned to it. |
| 04 | The time you submitted, and your timezone | Server time decides acceptance. Your submission time and zone are what make it possible to line your account of events up against the server’s receipt. |
| 05 | What you expected, and what you saw | In your own words. A screenshot helps as context, but a screenshot alone is not evidence a selection was accepted. |
A selection exists only when the server issues a receipt for it before the lock. Comparing your submission time against the receipt log is how a genuine defect gets separated from a submission that arrived late — and it is the difference between a correction that is owed and one that is not.
Reporting an integrity issue
Handled separatelyAn integrity issue is different from a support question. It is a claim that the record itself is wrong: a lock that did not hold, a selection that was accepted or rejected incorrectly, a score that does not follow the published rules, or an action by a commissioner that a member believes changed an outcome.
What happens after you report one
- It is acknowledged as received. You are told what is being examined and what the possible outcomes are, including that the outcome may be no change.
- A commissioner is never judge of their own disputed action. If the report concerns something a commissioner did, that commissioner does not decide it. Clutchhall handles it, and the reporter receives the status directly rather than through the person being questioned.
- Evidence is weighed against a fixed list. Only four kinds of evidence can support a correction: a versioned change from the designated sports-data source, an internal processing defect reproducible from logged inputs, immutable server evidence that a valid selection was accepted before the lock, or a documented eligibility or configuration defect.
- A statement, a screenshot, or a preference is not enough. Neither is a commissioner’s wish for a different outcome. This cuts both ways, and it is the reason the record is worth anything.
- A correction is appended, never edited in silence. If a correction is warranted, the original is preserved; actor, time, reason, evidence, and scope are recorded; the same deterministic scorer reruns over the whole affected scope; the entry appears in the competition’s correction log; and materially affected participants are notified.
- You are told the outcome either way — including when the answer is that the record stands.
The flagging window
Members can flag an apparent issue until 48 hours after a round is finalized. That window is a service target, not a shield: Clutchhall still fixes an objectively verified error found after it closes. Nobody, including Clutchhall staff, can silently edit a locked selection or a standings total.
What this service is, plainly
Clutchhall is built and run by one person. During the 2026 season the number of active communities is deliberately capped at what one operator can support directly, and the cap exists so that a round that matters to your community is not competing for attention with a queue.
What that means for you: answers come from someone who knows the scoring code, and they may not come immediately. If you need a contractual response commitment before trusting a season to Clutchhall, say so before you subscribe rather than after — that is a fair thing to ask for, and it is not something this launch offers.