Beckett for Slack

Privacy

Last updated: August 11, 2026

What Beckett processes

Beckett processes a message you select, text you send to Beckett, or the exact private Beckett thread only when you request coaching. It may send that transient content to Beckett's AI provider to generate the response you requested.

What Beckett stores

Slack remains the transcript system of record. Beckett does not persist Slack messages, prompts, generated responses, transcripts, workspace search results, participant names, channel names, or content-derived titles and summaries. Beckett stores encrypted installation credentials, opaque Slack routing identifiers, flow status, optional Beckett account links, and content-free credit and operational usage events.

Access and scope

The zero-copy launch uses bot-only access for commands, private Beckett messages, the exact Beckett DM thread, App Home, and Slack user identity. It does not request user tokens, search the workspace, or request public-channel, private-channel, or group-DM history scopes.

Credits and account linking

A Beckett account is not required to install or start using the app. Unlinked users receive a limited daily allowance. Linking is optional and lets Slack usage share the daily credits included with the user's Beckett subscription.

Sharing and training

Beckett shares transient request content only with processors needed to provide and secure the requested coaching. Beckett does not sell Slack data, use it for advertising, or use it to train general-purpose models.

Control and deletion

Workspace administrators can uninstall Beckett from Slack. Uninstall and token-revocation events invalidate stored credentials. Users can unlink their Beckett account or request deletion by emailing hello@meetbeckett.co.

Questions: hello@meetbeckett.co