Concepts
Public data and brand rules
PokerWorks publishes useful public-safe output for result pages, widgets, verifier flows, recipes, and support evidence. Public-safe does not mean unrestricted reuse.
Use documented API routes and approved recipes for the outcome they describe. Do not scrape first-party pages, resell hand histories, train models on private room data, expose support-only evidence, copy PokerWorks/PokerDeck trade dress, or imply partnership, certification, regulated status, or real-money support that PokerWorks has not granted.
Visibility tiers
| Tier | Meaning | Typical access |
|---|---|---|
| Public | Safe for anonymous or browser-visible reads. | Explicit public tournament result permalink, schedule widget, public result page. |
| Participant | Visible because a player took part. | Player/session-gated export or own standing. |
| Operator | Visible to the owning organization, room, or project. | Server-side Management API reads and exports. |
| Support-only | Used for support, dispute, or integrity workflows. | Redacted support-safe summaries only. |
| Internal | Source-of-truth implementation data. | Not exposed in public docs, widgets, SDKs, CLI, MCP, or examples. |
Default to the narrower tier when a result, export, widget, or recipe is ambiguous.
Practical rules
- Use API responses only for the documented route, token, room, project, environment, visibility tier, and recipe outcome.
- Keep management tokens, product keys, support evidence, private ids, and private room data out of browser widget code.
- Use public tournament result verification and public exports for result display, verifier, announcement, and support workflows only.
- Do not publish public hand-history datasets or player scouting products from PokerWorks data.
- Use brand names only for factual attribution allowed by the docs or an approved partner agreement.
- Report suspected data leakage, impersonation, scraping, model-training abuse, or support-evidence exposure through support channels rather than public accusations.
This guide summarizes the canonical architecture policy in
docs/architecture/public-data-use-and-brand-rules.md.