Contact this PlayOJO guide
Use the email published in the footer to reach the people who maintain this independent PlayOJO guide. Good reasons to write include ambiguous sentences about safer gambling, suspected factual drift in general library descriptions, broken responsive layouts on our pages, or missing alt text on images we control. Poor reasons include requests to manually add OJO rewards, reverse self-exclusion decisions, or upload passport photos for verification—those belong exclusively to PlayOJO’s regulated support and security teams who can access the right systems. Misrouting sensitive documents to an editorial inbox risks identity exposure without unlocking your account. Please pause, classify your issue, then choose the proper channel.
Crafting a high-signal message
Start with the exact URL, then summarise in one sentence. For visual bugs, specify device, OS, browser, and orientation. For wording disputes, quote the line and link to official PlayOJO help if you have it. Avoid attaching twenty-megabyte log dumps for a typo. Redact account numbers from screenshots. Threads stay saner when one issue per email is observed unless issues are truly entangled.
Promotion and reward disputes
If a campaign did not credit as you expected, only operator tools can trace eligibility and timestamps. We cannot see your promotion history. If our prose mis-described how a class of offers generally works, we want to know—but separate factual article fixes from individual settlement grievances.
Privacy and attachments
Minimise personal data. Malware filters run on inbound mail. Executable attachments are unwelcome. Encrypted archives with passwords pasted beside them frustrate scanning—avoid that pattern. If you overshare by mistake, ask for deletion promptly.
Timelines and expectations
This is not live chat. Editors batch responses around UK business hours. Complex multi-page reviews take longer than single-word typos. Duplicate mails and aggressive follow-ups within hours rarely help. One polite reminder after a reasonable gap is enough.
Accessibility
Describe barriers concretely: keyboard trap location, screen reader announcement failures, colour contrast failures with approximate hex if you know it. We attempt fixes within template limits. Native app issues must go to PlayOJO.
Commercial spam
Link-selling outreach and unsolicited SEO retainers are filtered. Genuine business proposals should identify a legal entity and purpose succinctly.
Security research
Reports about obvious misconfigurations on our host may earn thanks without a bounty programme. Do not disrupt readers with reckless testing. Phishing PlayOJO users via our mentions is out of scope and unwelcome.
Tone and conduct
Criticise sentences, not people. Harassment ends cooperation. If gambling harm fuels anger, contact BeGambleAware.org or GamCare—staff there train for those conversations.
Language locale
We target British English. Mixed dialect slips happen; point to the line. Full localisation requests exceed casual email capacity.
Successful outcomes
Ideal threads end with deployed fixes, transparent deferrals pending verification, or a clear redirect to PlayOJO support. We value readers who sharpen accuracy without treating guides like call centres.
Operator incidents and rumour control
When social networks amplify rumours about downtime, payment partners, or bonus outages, we cannot confirm or deny operator internals. Pointing you to official status pages or in-app notices is the honest limit of our knowledge. If our static text accidentally states an always-on guarantee that reality contradicts, tell us—but expect fixes to soften absolutes rather than to narrate live incidents minute by minute.