Public read freshness
Public reads are browser-safe only for their documented purpose. A public result link, schedule widget, standings card, or stream overlay must say what it is allowed to show, how fresh it is, and what happens when the underlying result or visibility changes.
What public reads must declare
Before PokerWorks documents a public read or widget as beta-ready, it must define:
- the visibility tier: public, participant, operator, support-only, or internal;
- the projection authority and generated time;
- the freshness class and stale ceiling;
- cache headers such as
ETag,Last-Modified,Cache-Control, and304 Not Modifiedwhere supported; - CORS or origin behavior;
- rate-limit and client-identification expectations;
- invalidation, correction, and revocation behavior.
Current beta posture
Use public tournament result verification reads only for explicitly public outcomes. Use host-server
proxying for widgets that need Management data. Do not put pw_mgmt_, pw_test_, or pw_live_
credentials in browser, mobile, stream overlay, or embedded code.
Public reads are still governed by Public Data Use And Brand Rules. Cacheable or browser-callable data is not permission to scrape first-party pages, create public hand-history datasets, train models on private room data, or reuse PokerWorks brand assets outside the documented policy.