What the service needs to know to run the game.

• Slack workspace, team, channel, and installation identifiers.
• Slack user identifiers and display names where needed to run the game.
• Game/session metadata such as phases, actions, votes, missions, shields, and event history.
• Billing and subscription metadata from Stripe.
• Contact/support submissions and operational logs used to run and debug the service.

• Install and operate the Slack app.
• Run the game, assign roles, process actions, and announce outcomes in Slack.
• Provide console/admin, billing, history, recap, and support surfaces.
• Protect hidden game state, investigate failures, and maintain service reliability.

The service uses hidden role and game-state data to run the game correctly. That data should not be exposed to ordinary players through browser surfaces. The browser exists for install, billing, configuration, logs, history, and support rather than player gameplay.

We rely on providers such as Slack, Stripe, Supabase, Vercel, and other infrastructure or monitoring tools needed to operate the service. We do not claim unsupported certifications or guarantees on this page.

We aim to keep detailed operational and gameplay data only as long as needed to run the product, provide recent game history, resolve disputes, debug failures, and meet legal/accounting obligations. If you need deletion or uninstall-related help, use the contact route.

This page is informational and should be reviewed before a broad production launch with final entity details, contact channels, and any customer-specific contractual commitments.