The written rules match the product posture.
PokerMeet is built around private-home coordination, host approvals, and address privacy. The documents here explain the operating rules that support that posture during beta.
County visibility first, private-home details later.
The legal documents reinforce the same address protection you see inside the product.
PokerMeet coordinates trusted tables rather than operating games.
The written policies keep the line clear around approvals, address privacy, and private-home responsibility.
Start with the documents that define the beta.
These are the first pages to read if you want the product boundaries, data posture, and escalation model in one place.
The rules for using PokerMeet and participating in the beta.
Read termsHow PokerMeet handles waitlist data, account information, and privacy requests.
Read privacy policyHow to report problems, classify severity, and escalate safety issues.
Review incident policyThe community rules are part of the product system too.
Hosts, players, and support all operate from the same standards so the county rollout stays intentional rather than chaotic.
Expectations for hosts protecting private homes and controlling approvals.
Review host rulesHow approved guests should handle private-home details and table conduct.
Review player codeThe product guardrails that keep PokerMeet focused on private-home coordination.
Read safety posture
Read the policies, then contact support if the line still feels unclear.
The legal center explains the operating rules, but support is still the right place to ask about edge cases, privacy requests, or safety concerns.