Contact the dreamcatcher editorial desk.
This page lists the ways to contact the dreamcatcher editorial desk: editorial email, regulatory clarification email and a physical address for written correspondence.
Editorial email
Corrections
Email the desk if you spot a factual error on any page. Include the page URL, the paragraph in question and the public source for the correction.
Regulatory updates
Email the desk if you spot a regulatory change the desk should reflect. Include the public source for the change.
Platform updates
Email the desk if a platform has changed its published terms, KYC method or withdrawal window. Include the URL of the platform page.
Response window
Corrections response
The desk responds to editorial corrections within five business days.
Regulatory response
The desk responds to regulatory updates within ten business days.
No commercial
The desk does not respond to commercial enquiries, partnership pitches or SEO solicitations.
Physical correspondence
Written reply
The desk accepts written correspondence at the address published on the contact page. Allow ten business days for a written reply.
Three channels the desk reads, three channels the desk does not.
The desk reads editorial corrections, regulatory clarifications and platform updates. The desk does not read commercial pitches, partnership offers or SEO solicitations. The list below names the channels the desk reads and the channels the desk does not, so a reader knows where to send each type of message.
Editorial corrections
Send a correction when you spot a factual error on a desk page. Include the page URL, the paragraph in question and a link to the public source that supports the correction. The desk reads editorial corrections within five business days and revises the page where the source confirms the correction.
Regulatory clarifications
Send a regulatory clarification when you spot a regulatory change the desk has not yet reflected. Include the public source — a Gazette notification, a state government press release, a parliamentary bulletin or a regulator's website. The desk reads regulatory clarifications within ten business days.
Platform updates
Send a platform update when a platform has changed its published terms, KYC method, withdrawal window or responsible-play controls. Include the URL of the platform page so the desk can verify the change. The desk reads platform updates within ten business days and revises the relevant comparison shelf.
What the desk does not read
The desk does not read commercial enquiries, partnership pitches, SEO solicitations, link-exchange requests, guest-post offers or influencer-marketing pitches. Messages in these categories are deleted without acknowledgement. The desk is a read-first editorial publication; the desk does not accept advertising or sponsored content.
What the desk does not publish
The desk does not publish customer-care phone numbers, ownership data, payout rates, sign-up bonuses or app-store ratings not already published on the platform itself. Where a reader asks for these, the desk responds with the URL of the platform's own page where the data is published.
How quickly the desk responds.
| Message type | Response window | What the response contains |
|---|---|---|
| Editorial correction | Five business days | Confirmation of receipt, plan to revise or a written explanation of why the desk is not revising. |
| Regulatory clarification | Ten business days | Confirmation of receipt, plan to revise or a written explanation of why the desk is not revising. |
| Platform update | Ten business days | Confirmation of receipt, plan to revise the relevant comparison shelf. |
| Reader rights request | Five business days | Confirmation of the action taken on the request. |
| Commercial enquiry | No response | Message deleted without acknowledgement. |
The standards the desk holds itself to.
Sourced facts
Every factual claim about licences, security, payments or responsible-play controls on any desk page is sourced to a public source: a platform's own published page, a regulator's register, a state gaming notice or a parliamentary bulletin. The reader can verify any claim against the named source.
Marked uncertainty
Where a fact cannot be verified at the time of writing, the desk marks the cell as verification-needed. The reader is responsible for the final verification on the platform's own page or the relevant regulator's register. The desk does not omit a fact silently; it marks the gap and explains what to verify.
No promotion
The desk does not publish promotional language, guaranteed-win language, fabricated payouts or sign-up bonuses. The desk does not publish customer-care phone numbers, ownership data, app-store ratings or app-download links not already published on the platform itself.
No advertising
The desk does not run advertising, sponsored content or affiliate links that pass reader identifiers to a third-party advertising network. The desk's only first-party link is the responsible-play page, which sits on the same first-party domain.
Quarterly revision
The desk revises tier 1 routes every quarter. The desk revises tier 2 routes when a named source changes. The desk revises tier 3 routes on demand. The desk revises tier 4 routes only when the underlying policy changes.
The languages the desk reads and the languages the desk publishes in.
What the desk reads
The desk reads English, Hindi and Tamil. The desk can read a message in any Indian language if the message includes an English translation. The desk does not auto-translate messages; the desk reads the message in the language the reader sends and reads the English translation as a reference.
What the desk publishes in
The desk publishes every route in English. The desk does not publish routes in Hindi, Tamil, Bengali, Marathi, Telugu or any other Indian language. Where a reader wants a translation, the reader can request one via the editorial inbox; the desk translates the route on a published timeline.
How the desk handles a translation request
The reader emails the editorial inbox with the route URL and the target language. The desk replies within ten business days with the translated route. The desk publishes the translation on the originating route as a side-by-side link so the reader can verify the translation against the original.
What the desk recommends
The desk recommends the reader write the editorial message in English because the desk reads English fastest. Where the reader prefers to write in Hindi or Tamil, the desk reads the message in the reader's chosen language. The desk does not delay the response for the language choice.
How the desk processes an editorial correction.
Step 1: receipt
The desk reads editorial corrections within five business days. The desk confirms receipt in writing with the date the desk will respond and the date the desk will revise the affected route.
Step 2: source verification
The desk verifies the correction against the underlying public source. Where the public source confirms the correction, the desk revises the affected route. Where the public source does not confirm the correction, the desk declines to revise and explains the reasoning in writing.
Step 3: route revision
The desk revises the affected route within ten business days of the verification. The desk updates the dateline at the top of the route. The desk publishes a change note at the bottom of the route explaining what was changed and why.
Step 4: confirmation
The desk confirms the revision in writing with the date the revision was published. The desk sends the confirmation to the reader's return address. The desk does not publish the reader's name in the change note; the desk publishes the correction anonymously.
How to read the contact desk.
The contact desk above is the inbox the desk reads, the channels the desk reads, and the response windows the desk honours. Read the contact desk before you send a message so you know which channel to use and what response window to expect.
How the desk triages a message
The desk triages every message into one of three buckets: editorial corrections, regulatory clarifications and platform updates. Each bucket has a named response window. The desk does not triage commercial pitches or SEO solicitations; messages in those categories are deleted without acknowledgement.
How the desk escalates a reader concern
Where a reader raises a concern that the desk cannot resolve through the editorial process — for example, a personal complaint about a specific platform's withdrawal delay — the desk directs the reader to the platform's own customer-care pathway and to the responsible gambling helpline if appropriate. The desk does not act as an intermediary.
How the desk handles a regulatory tip
Where a reader sends a regulatory tip, the desk verifies the tip against the underlying public source. If the source confirms the tip, the desk revises the relevant editorial route. If the source does not confirm the tip, the desk declines to revise and explains why.
How the desk handles a platform complaint
The desk does not accept platform complaints. A platform complaint is a personal dispute between a reader and a platform; the desk is not a regulator or a dispute-resolution body. Where a reader raises a platform complaint, the desk directs the reader to the platform's complaint pathway, the consumer forum and the responsible gambling helpline.
How the desk handles anonymous messages
The desk accepts anonymous messages but cannot respond to an anonymous message because the desk cannot address a response without an address. Where a reader wants a response, the reader must include a return email address. The desk does not publish the address; the desk uses the address only to send the response.
Three pages that complete the picture.
The rules ledger, the safety explainer and the responsible-play framework.