BeckettBeta access

Privacy and trust

Beckett should be clear before it asks for context.

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

Last updated: June 22, 2026

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 and may search relevant Slack history across authorized channels, DMs, group DMs, and private channels when you ask for coaching.

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

What Beckett collects and stores

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

This can include personal information such as your name and email address, authentication and connection information, user-provided communication preferences, and workplace communication context you choose to send for coaching.

Beckett does not store full Gmail or Slack message history by default, including raw Slack search results used for a coaching response. 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.

How Beckett uses your data

Beckett uses user data to provide and improve its single purpose: workplace and workplace-adjacent communication coaching in Gmail, Slack, the Chrome extension, practice sessions, and skill modules.

That includes authenticating your account, enforcing beta access and usage limits, generating coaching responses, remembering your preferences, connecting Gmail or Slack when you ask, troubleshooting bugs, responding to support requests, and improving coaching quality.

Beckett does not use or transfer user data for purposes unrelated to workplace or workplace-adjacent communication coaching.

Who Beckett shares data with

Beckett shares user data only with service providers and systems needed to run, secure, support, and improve Beckett.

These may include authentication and database providers such as Supabase, AI providers such as Anthropic for generating coaching responses, Google and Slack APIs when you connect those services, hosting and infrastructure providers, analytics and debugging tools, email delivery tools, and beta/customer-support tools such as HubSpot and Loops.

Service providers receive only the information needed for their role. Beckett does not sell personal data or transfer user data to advertising platforms, data brokers, or other information resellers.

What Beckett does not do

Beckett does not sell your personal data.

Beckett does not use Gmail or Slack content for advertising.

Beckett does not use or transfer user data to determine creditworthiness or for lending purposes.

Beckett does not collect payment card information through the Chrome extension during beta.

Beckett does not collect health information, precise location, or general web browsing history for its Chrome extension.

Beckett does not connect to LinkedIn, Google Calendar, Zoom, or Google Meet during beta.

Beckett does not ask for or store your personal Anthropic API key.

Chrome Web Store and Google API Limited Use

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

Beckett uses Google API data only to provide or improve user-facing workplace and workplace-adjacent communication coaching features requested by the user.

Beckett does not use Google API data for advertising, does not sell Google API data, and does not transfer Google API data except as needed to provide or improve Beckett, comply with applicable law, protect against abuse or security threats, or complete a merger, acquisition, or sale of assets with user consent where required.

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 help users pressure, convince, pursue, monitor, or retaliate against someone who has said no, hesitated, not responded, or shown discomfort.
  • Beckett does not encourage romantic pursuit where there is a manager/direct-report relationship, meaningful workplace power imbalance, or likely policy or safety concern.
  • Beckett does not help create sexualized workplace messages or anything likely to make the workplace unsafe.
  • 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.