Transparent rules and readable game states
These principles guide product decisions, community conduct, privacy choices, and the way we communicate changes.
04
ROUND 04 / PRODUCT AND COMMUNITY PRINCIPLES
House Rules
Our product and community principles: clear systems, thoughtful design, and responsible entertainment.
Privacy-minded product decisions
Prompts and reminders support play without manufacturing urgency or disguising limits.
Responsible entertainment principles
Core actions, errors, and recovery paths remain visible and usable across supported devices.
TRUST BY DESIGN / 02
Fairness must be visible, not assumed.
Trust grows when the interface explains outcomes, policies use plain language, and support paths are easy to find. We treat these as product requirements rather than legal decoration.
03
PLAYER EXPERIENCE / 03
What players should expect from the table.
Every session should preserve agency, comprehension, and the ability to step away without unnecessary friction.
- 01
Clear outcomes
Results identify the rule, action, or chance event that produced them.
- 02
Respectful pacing
Prompts and reminders support play without manufacturing urgency or disguising limits.
- 03
Accessible controls
Core actions, errors, and recovery paths remain visible and usable across supported devices.
04
COMMUNITY STANDARD / 04
Competition never removes responsibility.
A lively table can still be respectful. Community expectations protect the shared space without flattening personality or friendly rivalry.
- A
Play the person, not the profile
Challenge decisions and strategy without targeting identity, background, or personal circumstances.
- B
Keep the table honest
Do not exploit defects, coordinate unfairly, impersonate others, or misrepresent outcomes.
- C
Use the support path
Report harmful conduct or unclear results with enough context for a meaningful review.
WHEN SOMETHING FEELS WRONG / 05
Pause, document, and use the right channel.
A clear response path helps us separate a rule question from a technical issue or conduct concern.
Pause the session
Do not repeat an action that appears unintended or harmful.
Capture context
Note the table, round, time, visible result, and any relevant message.
Choose a topic
Identify whether the issue concerns rules, access, privacy, conduct, or technology.
Send the signal
Use Open Table so the request reaches the appropriate review path.
NEED CLARITY?
Ask about a rule before it becomes friction.
Send us the table, the moment, and the part that did not feel clear.