Browserflow policy · Version 2026-11-10.3
Who we are and our role
Browserflow B.V., registered with the Dutch Chamber of Commerce (KvK) under number 42176045, based in Zeist, the Netherlands, operates Browserflow. For privacy questions or requests, contact [email protected].
Browserflow is the controller for personal data it processes for its own account administration, billing, service communications, security, legal compliance and the product-improvement and optional measurement purposes described below. When we process workflow data solely on a customer’s documented instructions, the customer determines the purposes and we act as its processor under the separate DPA at /dpa, or as subprocessor if the customer itself acts for another controller. Roles follow the actual processing, not a label in a contract.
This notice covers visitors, account users, customer contacts, contributors and people whose information is handled by the service. We receive data directly from users, from websites and files they instruct the service to access, from authorised integrations and sign-in providers, from payment and service providers, and through use of the service. If your data is processed in a customer’s workflow, that customer is responsible for its own privacy information and legal basis. You may contact us to help route a request; we do not promise to disclose another customer’s confidential information.
Data we process and security boundaries
Your account details, onboarding choices, saved flows, login profiles, settings and run results are stored on the server hosting Browserflow. Execution history may include page content, screenshots and technical logs. Passwords are stored as salted hashes. Login profiles, API keys and queued inputs are encrypted. Flow definitions, history and completed results may contain readable data in the workspace database. Do not include data you are not entitled to process. Construction drafts, including unfinished setup and editor fields and intermediate recorder steps, are saved automatically. Construction history snapshots are encrypted in the workspace.
How your data is used
Browserflow uses this data to authenticate you, operate your workspace, execute your requested workflows, provide support and protect the service. Workspace data is separated by account; the server operator has access to the host and stored data. Shared listing names, descriptions, creator profiles and other public listing information can be viewed by visitors. Shared template definitions may also be displayed publicly on the Browserflow website, including to visitors who are not signed in. Signed-in users can obtain and copy shared templates. Review all content before publication.
Workflow processing on your behalf is governed by the separate DPA at /dpa where applicable. That agreement does not authorise unrelated use, advertising or general-purpose model training with Customer Personal Data. Our own controller purposes are identified below and require their own legal basis. Accepting the Terms or DPA is not blanket consent for processing.
Browserflow’s authorised operator can review construction activity per account, including entered non-secret values, drafts, saved flows, published versions, timestamps, sampled recorder screenshots, click positions and selection highlights, to understand how the builder is used and improve the platform. AI construction history includes task descriptions and tool outcomes received by Browserflow, not the full conversation in an external AI chat. Recorder screenshots mask input fields, editable areas, embedded frames, canvases and known declared secret values; ordinary visible page content may still include personal data. Profile-only login sessions are not captured for construction replay. Password fields, declared secret defaults, API credentials and saved login cookies are excluded from the structured review data. Do not place credentials in ordinary text fields. This internal review does not send workflow content to advertising or analytics providers.
Review for our own product improvement is a separate controller purpose, rather than part of your workflow instruction. It is limited to necessary, proportionate use under an applicable legal basis, with access restricted to the authorised operator. Browserflow currently has a single operator who performs this review for analysis and service improvement. That authorisation does not by itself establish a legal basis or permit broader collection or unrestricted access. Accepting the DPA does not authorise unrestricted review of workflow content.
Purposes and legal bases
Account creation, authentication, delivery of a subscription and responding to a user’s service request: we rely on performance of our contract with that individual, or steps at their request before entering it. Where the contract is with an organisation, necessary processing of its representatives’ contact and account information is based on our legitimate interests in administering and providing that organisation’s service. Required account and billing information is needed to provide the relevant feature; declining it may prevent registration, service delivery or payment.
Billing records, tax administration and compliance with binding legal obligations: we rely on the applicable legal obligation; payment administration also supports performance of the contract. We retain only the data necessary for the relevant obligation.
Security, fraud and abuse prevention, operational reliability, support and establishing or defending legal claims: we rely on our legitimate interests in protecting users and the service, resolving problems and protecting legal rights, where those interests are not overridden by individuals’ interests or fundamental rights. Particular disclosures may also be required by law. Necessary technical cookies support authentication and service operation; optional measurement and advertising choices are described separately.
Product improvement: our legitimate interest is understanding and correcting usability and reliability problems. We rely on this interest only where the processing is necessary and does not override the rights and interests of the people involved, using limited data and appropriate safeguards. A customer’s acceptance does not supply consent on behalf of people appearing in its workflows. Sensitive data requires an additional applicable condition. This does not permit unrelated use of workflow content.
Optional analytics, advertising measurement and retargeting: we rely on the relevant, separate consent described under “Cookies & third-party websites”. Refusing or withdrawing it does not prevent use of the core paid service. Withdrawal does not affect processing lawfully carried out before withdrawal. For workflow data processed as processor, the customer establishes the legal basis and we process under its instructions and the DPA; our contract with the customer is not a universal legal basis for collecting third parties’ data.
Retention & data requests
Saved workflows and login profiles remain available until removed through the applicable feature or an account-level request. Ordinary completed run history is eligible for periodic cleanup after seven days; runs retained as workflow references and evidence still needed for repairs may remain longer. Temporary files have their own expiry. Retention remains limited by the relevant purpose, customer instructions and applicable law. For Customer Personal Data, the DPA’s return and deletion requirements apply when the processing service ends or a valid deletion instruction is given. You can remove flows, login profiles and your marketplace listings. Removing a flow or profile does not automatically erase prior results, independent marketplace copies or backups. Any continued retention remains subject to applicable data protection requirements.
Contact [email protected] for access, correction or deletion requests, or to exercise applicable rights to restriction, objection or portability. You may also complain to the competent data protection authority. Information may need to be retained for legal obligations, security or resolving disputes, within applicable limits.
Additional construction history is retained for up to 30 days, with a rolling ceiling of 2,000 changes or 64 MB per workspace; older entries may therefore expire earlier. Workspace storage limits can shorten this history further, and an individual snapshot that cannot fit within the record or workspace limit is omitted so ordinary workspace use can continue. Unfinished setup and editor drafts expire after 30 days without updates. Cleanup runs periodically. Deleting a flow does not immediately erase its recent construction history. Current saved flows and published versions are not subject to this additional history window. Backups follow their separate retention schedule.
Account and contact information is retained while needed to administer the relationship and resolve outstanding service, security or legal matters. Financial records are retained for the applicable statutory tax and accounting periods, generally seven years for Dutch core accounting records, and longer only where a specific obligation applies. Support correspondence and security evidence are retained for as long as necessary to resolve the issue, investigate a documented risk or establish or defend relevant claims; necessity and access must be reviewed rather than retaining every record indefinitely. Transactional email queue records are pruned after 30 days; providers’ own retention may differ. Cookie and advertising-event periods stated above apply to those records.
The DPA sets end-of-service return and deletion deadlines for Customer Personal Data, including a maximum residual-backup period of 120 days after deletion from active systems. Backups are not ordinary working copies; deletion instructions must be reapplied if a backup is restored. These are contractual requirements and do not mean that clicking Delete removes every copy immediately. Data retained for a specific legal obligation must be restricted to that purpose. Ask [email protected] for the retention information applicable to your data or service.
Your rights and requests
Subject to the conditions in the GDPR, you may request access, correction, erasure, restriction or portability of your personal data. You may object to processing based on legitimate interests on grounds relating to your particular situation, and object at any time to processing for direct marketing. Where we rely on consent, you may withdraw it at any time, including through Cookie settings for optional tracking. Not every right applies to every processing activity; we will explain any lawful limitation.
Send requests to [email protected]. We may ask for proportionate information needed to verify identity and locate the data, without collecting more than necessary. We will respond without undue delay and normally within one month; where the GDPR permits an extension, we will explain the reason and extension within that first month. Requests concerning a customer’s workflow will be referred to that customer where it is the controller, and we will assist under the DPA. A service subscription is not required to exercise applicable privacy rights.
You can complain to the Dutch Autoriteit Persoonsgegevens or another competent supervisory authority, including in the EEA country where you habitually live or work or where an alleged infringement occurred. Automated service checks may restrict access, enforce limits or validate payments. If a decision based solely on automated processing produces legal or similarly significant effects and Article 22 GDPR applies, the applicable legal basis and safeguards, including human intervention and contesting the decision where required, must be provided. This notice does not authorise customers to make otherwise prohibited automated decisions about individuals.
Third-party service providers
Browserflow uses third-party providers to operate and support the service, including when you use Browserflow default for browser connectivity or AI. These default connections are selected and managed by Browserflow and use external network, VPN or proxy services and an external large language model (LLM) provider, respectively. Depending on the features and services used, these may include hosting and cloud infrastructure, storage and backups, network connectivity, VPN, proxy and routing services, payment processing, authentication, service communications and customer support, security and operational monitoring, and AI services. Providers receive or process only the account, billing, technical or workflow data needed for their relevant function; use of a provider does not mean that every provider receives all your data.
Network, VPN, proxy and routing providers carry browser traffic and may process connection information, such as network addresses, destinations, timestamps and traffic volumes. Their access to traffic content depends on the connection, protocol and encryption in use. Third-party websites receive the requests and data sent by your workflows and apply their own privacy practices. This also applies when you configure your own supported proxy or VPN gateway. Using your own connection does not stop Browserflow from processing the workflow data needed to operate the browser session. Connections, integrations or AI providers you configure are also subject to the relevant provider’s terms and data practices.
When you authorise an external application or AI assistant through an API, MCP or another supported integration, it can receive workflow information, run status and results within its granted access. For MCP, this includes enabled workflows and the output fields selected for sharing. The external application processes the information you submit to it and the data it receives under its own privacy practices; disconnecting it does not delete copies it already holds. Review the access and data you make available before connecting.
Browserflow default uses a third-party large language model (LLM) provider selected and configured by Browserflow. When AI-assisted features are used, relevant workflow instructions, page context, technical errors and screenshots may be sent to that provider, or to your own AI provider if you have selected one. Masking and filtering do not guarantee that all sensitive information is removed. Only use these features with data you are entitled to send to that provider and review the provider settings for your intended use.
Browserflow remains responsible for its applicable obligations when selecting and using its own providers, including appropriate processing agreements, security safeguards and requirements for international data transfers. These provider categories are not permission to disclose data for unrelated purposes. Material changes to the described processing will be reflected in this privacy notice, with any additional information, notice or consent required by law.
The service-provider inventory in Schedule C of the DPA identifies Hetzner infrastructure, the default Mistral AI connection, Browserflow-managed network routing and Mailgun transactional email. Provider processing roles depend on the service and data involved. The Subprocessor Schedule identifies the entities, locations and safeguards for processing on customers’ behalf. Payment, identity and advertising providers may act as independent controllers for some activities under their own terms; they are not thereby authorised to receive private workflow content. We may also disclose necessary information to professional advisers or competent authorities for legal obligations or the establishment, exercise or defence of legal claims, subject to applicable confidentiality and disclosure requirements.
International processing and notice changes
Processing may involve providers, recipients or support access outside the EEA, depending on the chosen features and destinations. Restricted transfers require a relevant adequacy decision or other valid safeguards, such as executed standard contractual clauses and any necessary supplementary measures. The DPA governs transfers made on customers’ behalf. Contact [email protected] for information about applicable safeguards and how to obtain a copy, subject to lawful redaction of confidential information.
A browser’s EU or US routing selection controls its network exit, not every storage or processing location. Custom websites, endpoints and connected applications can receive information outside the EEA. Selecting a connection does not waive data protection rights or transfer requirements. In particular, screenshots and page context sent to an AI provider may contain personal data despite filtering; provider retention and training treatment depend on the applicable contract and settings, subject to our obligations under the DPA.
We will update this notice when the described processing changes and give appropriate notice of material changes. Where a new purpose requires consent or other legal steps, updating this notice does not replace them. A revised notice does not retrospectively authorise earlier processing or change a recorded consent choice.