The product boundaries that protect the game.

Workspace installation happens through Slack OAuth. The install flow verifies authorization state and hands the installer browser session into the customer console path after Slack returns successfully.

Hidden roles, private votes, night actions, and similar game state are needed to run the game correctly. Those details should not appear in ordinary player-facing web surfaces. Slack gameplay and browser administration remain intentionally separate.

Slack is the gameplay surface. The webapp is for install, workspace configuration, billing, support, logs, and history. That separation reduces confusion and helps keep private game actions out of browser gameplay surfaces.

• Slack requests are signature-verified and replay-protected before they reach gameplay handlers.
• Workspace and tenant boundaries are enforced in server-side data access and Supabase policies.
• Gameplay side effects use durable, retryable jobs so a transient Slack failure does not silently lose a phase transition or announcement.
• Hidden roles, private actions, and private game state are kept out of public marketing, player web surfaces, and operator summaries.

This page does not claim certifications, compliance programs, SOC 2, GDPR readiness, DPA support, or guaranteed uptime unless those capabilities are separately implemented and documented.

Security concerns, suspicious installs, or data-boundary questions should go through the contact route so they can be handled through the support/admin process.