BeepflowBeepflow Sign in

Privacy Policy

Last updated: Oct 1, 2026

Overview

This policy explains how Beepflow (Overflow Labs Ltd) collects, uses, and protects information.

Information we collect

We collect information you provide and information needed to run service:

  • Account data like email address and authentication tokens.
  • Workspace data like tabs, dashboards, and configuration.
  • Integration data you connect, such as Shopify events or external API data.
  • Technical data like browser type, IP address, and error logs for reliability.

How we use information

  • Provide, secure, and operate service.
  • Process data streams and run workflows you configure.
  • Maintain reliability, prevent abuse, and debug issues.
  • Communicate service updates and support responses.

Claude and other AI clients (MCP connector)

  • What it accesses: when you connect Claude or another MCP client, it reads and changes your Beepflow workspace only through the tool calls it makes, acting as you. It has the same access as your Beepflow session: the spaces, tabs, blueprints, pages, integrations and connections you can access. Integration endpoint calls can reach the external service behind a connection, using the credentials you stored in it.
  • What we receive: each tool call's arguments, and we return its results. We use them only to perform the call, and we keep only the workspace changes the call makes. We never receive your Claude conversations, memory, chat history or files, except what the client puts into a tool call.
  • What we log: when a client connects, we record its name and version with your email. As with every request, we log the method, path, status, duration and IP address. Error reports sent to Sentry don't include the contents of connector requests. Logs are kept for 90 days.
  • Anthropic handles your conversations and the tool results Claude receives under Anthropic's own privacy policy.
  • Stopping access: remove the connector in your client's settings.

Storage and retention

  • Browser storage: localStorage and IndexedDB cache workspace state and sessions on your device.
  • Service storage: data you send or connect may be processed and stored to provide features.
  • Retention varies by feature; we delete data when you delete workspace or disconnect integration, unless required by law.

Deleting your data

  • Connections: delete a connection from the Connections menu to remove its stored credentials and access tokens from Beepflow immediately. This covers connections to Meta (Facebook and Instagram), Google, Shopify and every other integration.
  • Revoking access at the provider: you can also remove Beepflow's access from the provider's own settings, such as Integrations > Connected apps in your Meta Business Settings or Third-party apps in your Google Account. Beepflow then can no longer read or change data in that account.
  • Workspace data: deleting a tab, blueprint result or space deletes the data stored in it, including anything a blueprint copied from a connected account.
  • Your account and all its data: email [email protected] from your account's email address with the subject "Delete my data". We delete your account, spaces, connections and stored data within 30 days and reply to confirm when it is done.
  • Request logs are deleted automatically after 90 days.

Sharing and subprocessors

We use trusted subprocessors to run service (hosting, email, auth, and error monitoring through Sentry). We do not sell data. We share data only as needed to provide service or comply with law.

Cookies and tracking

We do not use cookies or advertising trackers. Service uses browser localStorage and IndexedDB only.

Your rights

International transfers

Data may be processed in countries where our providers operate. We use safeguards where required.

Changes

We may update this policy. We will post updates on this page.

Contact

Email: [email protected]