Terms

How the hosted service is meant to be used.

These terms are a plain-language baseline for the Slack app and related web surfaces. They explain the basic service relationship without pretending the product has guarantees or enterprise promises it does not currently support.

Plain-language trust surface. Slack gameplay and browser administration remain separate.

Field note

Workspace installation responsibility

The Slack app should only be installed by someone who has permission to do so for that workspace. Workspace admins are responsible for how the product is introduced, configured, and used in their Slack environment.

Field note

Acceptable use

  • Do not use the service to harass, threaten, or abuse players.
  • Do not attempt to access another workspace's data or hidden game state.
  • Do not use the service in a way that breaks law, policy, or Slack platform rules.
  • Do not treat internal/debug paths as public customer tools.

Field note

Slack dependency and service changes

The product depends on Slack and other third-party services such as Stripe and hosting infrastructure. Features may change over time, and the service may be paused, limited, or adjusted to protect security, comply with platform rules, or keep the product working reliably.

Field note

Billing and subscriptions

Free and paid options are described on the pricing page. Billing is handled through Stripe. Paid access is tied to the workspace/customer path rather than browser gameplay.

Field note

Availability and limits

We do not promise uninterrupted uptime, perfect availability, or feature permanence. The service is provided on an as-available basis and may evolve as the product hardens.

Field note

Support and contact

Questions about terms, support, billing, or workspace access should go through the contact route. Enterprise or event-specific commitments may require a separate written agreement.