Privacy Policy

What we collect

• Account details. Your name, email address and profile picture, how you sign in (for example email, Google or GitHub), and the organizations you belong to or are invited to.
• Workspace content. The documents, epics, tasks, comments, decisions, progress updates, test results and branch or pull request links that you or your agents add.
• What connected agents send. The MCP server sends the content of each tool call, plus a session ID, the git remote URL and the current branch of the project it runs in. The plugin looks up which workspace that remote belongs to.
• API tokens and AI keys. We store a hash of each API token, not the token itself. If you add your own OpenAI or Anthropic key, we store it encrypted and use it only to call that provider for you.
• Billing details. Your plan, seats, subscription status and AI credit use. Stripe handles card details; we never see your full card number.
• Usage and device data. Pages you visit, actions such as creating a workspace or recording a plan, errors, browser and device type, and IP address (used for approximate location). When you are signed in, this is linked to your account ID, name and email.
• Messages to us. What you send when you email us.

How we use it

• to run Beck: sign you in, store and show your workspaces, and connect your agents;
• to run the AI features you use;
• to bill you and manage your plan;
• to answer support requests and send messages about your account, billing or changes to Beck;
• to keep Beck secure and prevent abuse;
• to understand how Beck is used and improve it.

We don’t sell your personal information, share it for advertising, or use your content to train AI models.

AI features

When you use an AI feature, the content it needs (for example the document you ask Plan it to break down) is sent to an AI model provider. With Beck’s AI credits, it goes through Vercel AI Gateway to providers such as OpenAI and Anthropic. With your own key, it goes straight to that provider. They process it to return a result under their API terms.

Coding agents you connect, such as Claude Code or Cursor, are run by you under their makers’ terms. What they read from Beck is then handled under those terms.

Who we share it with

Members of your organization can see the workspaces you share with them. Beyond that, we share personal information only with the service providers below, who process it for us; when the law requires it; to protect Beck, our users or the public; or with a buyer if Beck Labs LLC or Beck is sold or merged, under this policy.

Cookies and local storage

We use cookies that sign-in needs (from Clerk), analytics identifiers from PostHog, and local storage for preferences such as your theme. Analytics requests go through beck.bot. We don’t use advertising cookies.

How long we keep it

We keep your account and workspace content while your account is open. When you delete a workspace, its content is removed. When you ask us to close your account, we delete your content and account details within 30 days, apart from backup copies, which expire on their normal schedule, and records we must keep by law, such as billing records. We delete analytics linked to you at the same time.

Your choices and rights

You can edit your profile, delete workspaces, revoke API tokens and remove your AI keys yourself. To get a copy of your data, correct it, delete it or close your account, email hello@beck.bot. We answer within 30 days.

Depending on where you live, for example in the EU, the UK or California, you may have more rights over your personal information, including to object to or restrict some processing. We honor those requests and won’t treat you differently for making one. Where the GDPR applies, we rely on our contract with you to run Beck, our legitimate interests for security, analytics and improving Beck, and your consent where the law requires it. You can also complain to your local data protection authority.

Where it is processed

Beck Labs LLC is based in Utah, in the United States, and our providers process data mainly in the United States. If you use Beck from elsewhere, your information is transferred there.

Security

Connections to Beck are encrypted, API tokens are stored as hashes, your AI keys are encrypted, and workspace data is scoped to your organization. No system is perfectly secure. If a breach affects your information, we will tell you as the law requires.

Children

Beck is not for anyone under 18, and we don’t knowingly collect their information.

Changes

We will post any update here with a new effective date. If a change is significant, we will also tell you by email or in the app before it takes effect. See also our Terms of Service.

Contact

Beck Labs LLC, hello@beck.bot.