Contact the team without exposing private-home details.
PokerMeet support is built for safety-first escalation, product questions, and rollout coordination. Keep addresses redacted in screenshots and use the guided flows for anything urgent.
support@pokermeet.org
Hours: 09:00-21:00 PT. Include event time and issue context, not private-home details.
Safety first, local authorities first.
For immediate danger, contact local authorities first, then notify PokerMeet for follow-up.
Bring time, IDs, and redacted screenshots.
Include the event ID, timestamp, user or post reference, and what you expected to happen.
Short answers to the questions that matter most.
The support posture stays aligned with the product guardrails: privacy-first coordination, host approvals, 21+ access, and no platform payments.
How do I contact support?
Email support@pokermeet.org. For safety or data/privacy issues, include the event name and time - do not share full addresses in email.
What does PokerMeet do?
PokerMeet is a private-home coordination and safety platform for adults 21+. It helps people browse county momentum, request seats, and manage host approvals without exposing exact addresses upfront.
Why is my request pending or waitlisted?
Hosts approve every request manually. If seats are full, you may be waitlisted and promoted if a spot opens.
What if a table feels misrepresented or unsafe?
Report it immediately with the event time and county. Keep private-home details out of the ticket unless support asks for follow-up context.
How does age gating work?
PokerMeet is 21+ only. Beta access uses account-level confirmation and trust controls, and any verification changes would be communicated clearly before they affect access.
Response expectations stay clear and practical.
Severities below are operating targets for support triage, not guarantees. The goal is to keep safety and trust issues from sitting in a generic queue.
Safety threat, address leak, major outage. Target response: 15 minutes.
Login/SMS outage, approvals failing for many. Target response: 1 hour.
Single-user functional issue (verification stuck, one event bug). Target: 4 hours.
Copy/UX confusion, minor bug. Target: next business day or backlog.
Join the waitlist, then reach out when your county or table needs context.
Support is there to help the rollout stay trustworthy. The waitlist is still the main path for players and hosts who want county updates or launch access.