Corrections
Found something we got wrong?
An old download link. A Club ID that does not match. A time that looks wrong. Send us the page and the detail—we will check the source before changing it.
Send us the page and the problem
Send a correction
Tell us which DPH page needs a correction, what looks wrong and what the current source says.
Five useful details. No essay needed.
Paste the DPH page link.
Point to the exact detail: the app or club name, link, Club ID, contact, game, schedule, restriction or status.
Say what is wrong, missing or out of date.
Add the current public source when you have one.
For a changing detail, include when you saw it. Add the timezone for a schedule or table-status mismatch.
For a Club ID mismatch: “This page and the club’s current public post give different IDs. Here is the post.” Send the source, not a private invitation.
For a changed screen: “The guide says Table Settings, but I cannot find it in this app version on my phone.” Add the version and device. For a schedule: “This start time has no timezone.” Include the event and date.
You do not need to prove the whole case before reporting a possible mistake. The page link and a clear description are enough to start; the source decides whether the factual correction is supported.
What happens next?
An acknowledgement means the report arrived; it is not confirmation that the detail was checked or fixed. Look at the affected page and any dated correction note for the published change.
We compare your report with the source responsible for the detail: the app, club, operator, agent, public contact, policy or dated observation. A report points us to a possible error; it does not prove the correction on its own.
If the page is wrong, we fix the affected information. If sources disagree, we explain that disagreement or stop giving a settled answer. A correction may require removing a value or replacing or redirecting a page, but it is not a reason to discard unrelated useful information.
We cannot promise a response time or a particular outcome. A factual change needs support from the relevant sources, not just a request to change the page.
Small fixes count too
Anything factual on a DPH page that is wrong or outdated: app and club identities, official links, devices, account requirements, public Club IDs and contacts, games, schedules, live-status checks, agent roles, integrity policies, restrictions, dispute processes, source dates or commercial disclosures. Copy mistakes count too.
We do not run a public player-review archive. But a reader report can still help us find a wrong ID, stale contact, inaccurate restriction or outdated table status.
Need app or account help instead?
This inbox is for corrections to DPH. It does not arrange deposits, chip purchases, withdrawals or cashouts, and it cannot verify a club's ability to pay.
Our guides can explain supported troubleshooting steps. The app operator handles account recovery and product support; sending a correction here does not open a ticket with the app or contact the club for you.
Where will I see the change?
On the affected page. A meaningful correction may include a short dated note explaining what changed.
Daily Pick corrections, withdrawals and replacements keep their earlier version in the change history. That history does not make an old Club ID, contact, join link or table-status claim current again.
A wording or formatting edit is not a new check of the underlying facts. Rebuilding a page or opening a link does not refresh all its source dates.
Editorial updates
Follow the work behind the pages.
Get important corrections, methodology changes and updates to our reader-safety guidance.