privacy
Mumbl is built for thoughts that need a safer place to become useful. Private dumps stay private. Team reads are published only when someone chooses to publish them.
Mumbl stores the private dumps, field-note drafts, room posts, reactions, and account details needed to make the product work. For Slack, Mumbl stores installation records, connected Slack user ids, and only the Slack message text someone explicitly saves.
Mumbl does not read Slack channel history, monitor Slack presence, collect member lists for analytics, or track who quietly opens a room. Anonymous posts do not store display names.
The core Slack app uses slash commands and basic user profile/email scopes to connect explicit user actions to Mumbl. Optional team-read posting asks for write/private-channel permissions only when a room creator chooses to create a Slack reads channel.
the line
You choose what becomes a team read. You choose whether a team read is anonymous or published with a handle. You choose whether a Mumbl room mirrors published reads into Slack.
If you want data removed or have a privacy question, email mumbl.wtf@gmail.com.
This page is a practical beta privacy note, not legal theater. It will become a fuller policy before broad public distribution.