BeckettBeta access

Privacy and trust

Beckett should be clear before it asks for context.

Beckett is a workplace communication coach for beta users. It works best with real communication context, so the rules below explain what Beckett reads, what it stores, what feedback can include, and where the coaching boundaries are.

What Beckett reads

During beta, Beckett can use Gmail, Slack, and Chrome extension context only when you connect those tools and ask Beckett for coaching, or when you turn on an analysis setting yourself.

For Gmail, Beckett uses read-only access so it can understand email threads and help draft replies. For Slack, Beckett uses connected workspace context so it can understand recent DMs, channels, or threads you ask it to analyze.

Beckett is not meant to read your work communication in the background without your action.

What Beckett stores

Beckett stores account details, beta access status, onboarding answers, connection status, usage counts, timestamps, contacts you choose to add, and coaching settings.

Beckett does not store full Gmail or Slack message history by default. For product analytics and CRM, Beckett uses counts, timestamps, connection status, and safe event names, not raw message content.

Beckett may store short summaries or metadata when needed to make the product work, debug beta issues, or remember your preferences.

Feedback and debugging

If you submit beta feedback, that feedback may include the page, rating, your comment, and relevant debug context.

Extension feedback may include message context from the analysis you are reporting, because that helps us understand what went wrong. Only send feedback when you are comfortable sharing that context with the Beckett team.

We use beta feedback to fix bugs, improve coaching quality, and decide what needs to change before inviting more users.

Deletion during beta

You can request account deletion from Settings. During beta, deletion is handled manually so we can remove data across Beckett, Supabase, HubSpot, email tools, and related systems.

Beckett currently targets completion within 30 days. If you need help, email hello@meetbeckett.co.

Beckett's coaching boundaries

Beckett notices patterns, offers interpretations, suggests options, and leaves the user in control.

  • Beckett does not diagnose the user or other people.
  • Beckett does not use clinical or shaming labels such as manic, crazy, toxic, narcissistic, or unstable.
  • Beckett does not present guesses as facts; it frames interpretations as possibilities based on available context.
  • Beckett does not tell users what they must do; it offers options and tradeoffs.
  • Beckett does not send, schedule, cancel, decline, or change anything without explicit user action.
  • Beckett does not encourage manipulation, surveillance, coercion, or retaliation.
  • Beckett does not shame users for struggling or assume neurodivergence means incapability.
  • Beckett does not pressure users to disclose a diagnosis unless they explicitly ask for help with disclosure or accommodations.
  • Beckett does not replace legal, medical, HR, or therapeutic advice.