Contact — Pub Casino notes (mirror two)

This contact route serves readers who arrived on our second informational domain. We welcome concise reports about readability, British-English consistency, mobile rendering quirks and suspected factual drift compared with Pub Casino’s official documentation. We cannot reset passwords, refund stakes, alter bonus ledgers or fast-track verification. Those requests belong with the licensed operator’s authenticated support paths; attempting them through us slows everyone down and may expose personal data inappropriately.

Ticket hygiene

One issue per thread where possible. Attach screenshots only when they illustrate a visual defect and redact unrelated tabs. State whether you use Safari, Chrome, Firefox or an in-app browser, plus approximate viewport width. For copy disputes, paste the quoted line from our page and the contrasting official citation. Bulk forwards of marketing newsletters are filtered as noise.

Responsible-gambling escalations

If you are in crisis, contact emergency services or Samaritans for immediate human support; our inbox is not monitored for real-time intervention. For gambling-specific help, BeGambleAware.org and GamCare provide professional routes. We can adjust wording that trivialises harm when you point to a specific paragraph, but we cannot replace clinical or legal advice.

Conflicts between mirrors

Occasionally the two hosts may briefly diverge after a partial deploy. Mention both URLs if you spot mismatched facts; we reconcile intentionally. Do not treat either mirror as a changelog for the operator’s product roadmap.

Security reporting

Responsible disclosure of technical vulnerabilities should include reproduction steps and impact assessment without destructive testing. Do not exfiltrate user data to “prove” a point. We coordinate fixes proportionate to severity; we do not run a public bug-bounty programme on this stack.

Spam and marketing

Unsolicited SEO services, guest-post pitches and affiliate recruitment blasts receive no response. Legitimate accessibility consultants should outline scope and credentials in the first message; vague “we can improve your site” templates are discarded.

Data minimisation reminder

Never send full card numbers, CVV codes or authentication codes. If a template asks for them, assume phishing. Official Pub Casino flows collect payment data inside PCI-scoped forms, not via random email threads.

Timezone and holidays

Replies may cluster around UK working days. Bank holidays extend queues. Repeated “bump” messages within hours do not increase priority; they often bury newer tickets in filters.

Screen-reader and keyboard flows

When reporting accessibility, note whether you navigate by voice control, switch access or keyboard only. Include the exact heading sequence if something skips levels. We prioritise fixes that block task completion over cosmetic polish, but both matter.

Evidence from official chats

If an operator agent contradicted our wording, paste anonymised excerpts or ticket IDs only—never full transcripts with account numbers. We use that signal to align phrasing, not to intervene in the chat outcome.

Duplicate reporting etiquette

Community moderators sometimes batch-send the same typo from a forum thread. One consolidated email with multiple corroborating links beats twenty identical forwards that trigger spam defences.

Plain-text versus HTML email

Either format is fine. If HTML strips in transit, resend as plain text with the same subject prefix so threading stays intact.