Privacy for Flywheel

Flywheel processes Slack events, recent conversation context, workspace configuration, and operational metadata to run tasks inside Slack. Flywheel is not a Slack backup and should not be used as one.

• Flywheel collects Slack message and event data needed to respond to mentions, direct messages, Flywheel-owned threads, and configured automations.
• Flywheel uses that data to generate replies, summaries, drafts, scheduling actions, and operational records needed to run the service.
• Slack-derived conversation history stored by Flywheel is capped at 90 days.
• Raw Slack event payloads and job results are retained for shorter operational windows.
• In public and private channels, Flywheel defaults to the message or thread where it was explicitly invoked instead of collecting unrelated channel chatter.
• In DMs and group DMs, Flywheel may use prior conversation in that same DM lane to preserve continuity.
• Flywheel uses AI-generated output. Important summaries, recommendations, and actions should be reviewed by a person before being relied on.
• Flywheel does not use Slack data to train or improve generalized AI models.
• Human access to Slack-derived content is limited to narrow support, security, or legal exceptions.
• Secrets are treated as write-only in the product surface.
• If Flywheel creates summaries or durable learnings from Slack activity, those artifacts are still subject to explicit retention and deletion rules.
• Access, transfer, privacy, and deletion requests can be sent to flywheel@supercharger.studio.