Who we are
Beepflow is a trading name of Overflow Labs Ltd (company no. 13324827), Suite 201, 16 Pepper Street, London, E14 9RP, United Kingdom. We are the controller of the personal data described here. Contact us at [email protected].
What we collect
- Account data. Your email address, name and sign-in tokens.
- Workspace data. The spaces, tabs, blueprints, pages and settings you create.
- Data from accounts you connect. What your connections read from services such as Google, Meta or Shopify, and the credentials they use.
- Request logs. For every request: method, path, status, duration and IP address. Error reports go to Sentry.
- MCP tool call records. Described in AI assistants and the MCP server.
- Website visits. Pages on www.beepflow.com load the Google tag for Google Ads, which records the pages you visit, the ad that brought you, your IP address and browser details.
The app sets no cookies and keeps workspace state in your browser's storage. Our website uses Google Ads cookies outside the EEA, the UK and Switzerland. The Cookies Policy explains both.
Why, and on what lawful basis
- Providing the service, including running the workflows you set up and sending service and support emails: performance of our contract with you.
- Security, abuse investigation, debugging and improving the service, which is what request logs and MCP tool call records are for: our legitimate interest in keeping the service safe and working.
- Measuring and showing our ads, with the Google tag on www.beepflow.com: our legitimate interest in knowing which ads bring us customers. In the EEA, the UK and Switzerland the tag sets no advertising cookies.
- Meeting legal obligations, such as tax records or lawful requests: legal obligation.
AI assistants and the MCP server
- 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, with the same access as your Beepflow session.
- What we receive. Each tool call's arguments, and we return its results. We use them only to perform the call and keep only the workspace changes it makes. We never receive your conversations, except what the client puts into a tool call.
- What we record. When a client connects, its name and version with your user id. For each tool call, the tool name, whether it succeeded, how long it took, your user id and your client's user agent, never its arguments or results. Error reports sent to Sentry don't include the contents of MCP requests.
- Stopping access. Remove the Beepflow server in your client's settings.
Google user data
When you connect a Google account, Beepflow reads, sends or changes the Gmail, Google Drive, Google Sheets, Google Docs, Google Slides, Google Forms and Google Ads data the workflows you set up ask for, only to run them. In Google Drive, Beepflow reaches only the files you choose for it with the Google Picker and the files your workflows create; it opens the spreadsheets, documents, presentations and forms your workflows name by their ID, reads form responses, and reads or applies Drive labels only when your workflows ask for them. For Google Ads, that means the accounts, campaigns, ads, budgets and reports your workflows query or change. We don't sell it, use it for advertising (including our own Google Ads campaigns), or use it to train AI models, and nobody at Beepflow reads it unless you ask us to, for security, or when the law requires it. Beepflow's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
How we protect your data
- Encryption in transit. Beepflow is served only over HTTPS (TLS), and plain HTTP requests are redirected to HTTPS. Beepflow calls Google and every other provider over HTTPS.
- Encrypted credentials. OAuth access and refresh tokens, API keys and the other credentials of your connections, Google included, are encrypted with AES-256-GCM before they are stored, under a key kept apart from the database. Each encrypted value is tied to its own connection, so it cannot be opened on any other record. Credentials are never sent to your browser or to AI clients; only our servers decrypt them, to call the provider for your workflows.
- Access control. Every request is authenticated with a signed session token. Workspace data and connections are available only to the people the space they belong to grants access to, or the people they are shared with.
- Infrastructure. Beepflow runs on Amazon Web Services in the EU (Ireland). Our databases have no public network address and can be reached only from inside our private network. Backups are encrypted at rest in Amazon S3.
- Staff access. Only the Beepflow staff who operate the service can access production systems, and only to run, secure and support it, as Google user data describes.
- Incidents. If a security breach affects your personal data, we will tell you and the UK Information Commissioner's Office as the law requires.
Sharing
We never sell data. We share it only with the providers that run the service for us, for hosting, email, sign-in and error monitoring (Sentry), with Google for the website visits its tag records, and when the law requires it.
International transfers
Our providers may process data outside the UK. Those transfers are covered by the EU Standard Contractual Clauses with the UK Addendum.
Retention
- Account, workspace and connection data until you delete it or your account is deleted.
- Request logs for 90 days.
- MCP tool call records are kept, also after your account is deleted, for security and abuse investigation. They hold your user id, not your email or anything you sent.
Your rights and deleting your data
- Your rights. You can ask us to access, correct, delete, restrict or export your personal data, or object to how we use it, by emailing [email protected].
- 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. You can also remove Beepflow's access in the provider's own settings, such as Integrations > Connected apps in your Meta Business Settings or Third-party apps in your Google 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. 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 when it is done. MCP tool call records are kept, as Retention describes.
- Complaints. You can complain to the UK Information Commissioner's Office at ico.org.uk.
Changes
We post updates to this policy on this page.