Contact us
Use this page for factual corrections, broken-route reports, media questions, commercial or disclosure questions, accessibility issues, and other site-level feedback. It is not an operator support desk.
What we can help with
Correction requests
Use this page to report a wrong fact, stale term, broken route, or misleading wording on a live TPU page.
Policy or disclosure questions
Use this page when your question is really about methodology, editorial standards, privacy, or affiliate disclosure.
Media or commercial questions
Use the dedicated inbox that matches media, partnership, or legal-policy context rather than sending everything to one address.
Accessibility and UX issues
Broken navigation, anchor mismatches, rendering issues, and accessibility problems are appropriate contact reasons here.
What we cannot do
Open state guidesNo operator account recovery
We cannot unlock, verify, or recover your account at a casino or sportsbook.
No withdrawal processing
We cannot resolve a payout with an operator directly or guarantee an operator response.
No legal or tax advice
State-law and tax questions belong on support routes and independent professional channels, not this inbox.
No future-offer guarantee
We cannot confirm that an operator will honor a future bonus, payout path, or account condition outside the live destination.
Pick the right inbox
General editorial and route issues
Use for factual corrections, broken links, route mismatches, and general page feedback.
InboxCommercial and partner questions
Use when the question is about commercial relationships, business outreach, or partner-side clarifications.
InboxPress and media requests
Use for interviews, quotes, media requests, and publication-related outreach.
InboxLegal and policy questions
Use for terms, privacy, disclosure, or policy questions that need the legal-policy inbox instead of general support.
Before you email us
- If your question is about one operator, open the relevant review page first.
- If your question is about bonus categories or wording, open the bonuses hub first.
- If your question is about legality, age, or local access, start with state guides.
- If your question is about methodology or disclosure, the process pages below may answer faster than email.
- Include the exact URL and claim if you are reporting an error.
What to include in a correction report
| Problem | What to send us |
|---|---|
| Wrong bonus wording | URL plus the quoted text and what changed |
| Broken route or anchor | Source URL plus the target URL that fails or misroutes |
| State or legal issue | Page URL, state, and the exact statement that looks wrong |
| Payout-note issue | Page URL, payment method, and why the note looks misleading |
| Accessibility issue | Device or browser, screenshot if available, and the page URL |
Expected routing by issue type
| Issue | Best inbox | Best fallback route |
|---|---|---|
| Stale bonus wording | Editorial | Bonuses hub |
| Payout-note issue | Editorial | Payout page or relevant review |
| Legal or state issue | Legal/policy | State guides |
| Accessibility issue | General editorial | Contact |
| Commercial question | Commercial | Affiliate disclosure |
What happens after you email us
Report received
The report enters the right inbox first instead of disappearing into a generic support promise.
Issue triaged
We look at the route, the exact claim, and whether the question belongs with editorial, policy, commercial, or another owner.
Owner review or correction
Actionable issues should be corrected or answered according to the route family that owns them, not treated as a marketing ticket.
Urgent help and related process routes
How we test
Use this route if your question is really about testing standards or page evidence.
Support routeEditorial policy
Use this route for governance, sourcing, corrections, and commercial separation rules.
Support routeAffiliate disclosure
Use this route if your question is really about monetization or commercial context.
Support routeResponsible gambling
Use this route for urgent gambling-related help instead of waiting for a site reply.
Recent contact-page updates
Need a faster answer than email?
Use the route that matches the actual question first. Most trust, policy, and routing issues are answered faster on the page family that owns them.