Legal
Privacy Policy
Early-access version. The operating entity's details will be added before billing opens; the content describes how the system works today.
This page describes the data Browlix processes when you use the website, dashboard, API, MCP, CLI, SDK and the Browlix worker — as the system works today.
1. Data we process
| Kind | Examples | Why |
|---|---|---|
| Account | Email, display name, language/theme settings, two-factor factors | Sign-in and personalization |
| Workspace | Workspace name, members, roles, groups, tags | Permissions and collaboration |
| Profiles and proxies | Profile names, browser settings, proxy host/port | Opening browsers with the right settings |
| Credentials | Proxy passwords, connector credentials, data keys | Kept in a secret vault, released only to the command that needs them |
| Workers | Machine name, operating system, worker version, status, exit IP during proxy checks | Pairing, placement, diagnostics |
| Logs | Who did what and when, through the web, API or MCP; command receipts | Audit and safety |
| Synced browser data | Cookies, site storage, extensions (only when sync is on) | Opening a profile on another machine |
| AI agent | Observed page content, plans, token usage | Running the tasks you assign |
| Feedback and contact | Ticket content, contact messages, contact email | Answering you |
Browlix does not sell data, uses no advertising cookies and runs no third-party tracking on the website.
2. Where data lives and how it is protected
- Browser data stays on your worker machines. When sync is on, data is chunked, compressed and encrypted with authenticated encryption bound to the workspace, profile and key version before it leaves the machine. The workspace key is managed by Browlix in a secret vault — this is not end-to-end encryption.
- Proxy passwords and other secrets live in a secret vault and are hidden from members without access.
- Every access decision goes through the same server-side permission check.
3. Processors acting for Browlix
- Supabase — database, authentication, file storage and the secret vault.
- Lovable — website and application hosting (running on Cloudflare infrastructure), and the Lovable AI Gateway used to call AI models for the AI agent.
- An infrastructure provider for the remote-view relay (TURN) — it only relays encrypted streams between your worker and your browser.
A detailed list of processors will be published with the data processing terms before billing opens.
4. AI agent
When you run the AI agent, Browlix servers send the necessary page content to a model through the Lovable AI Gateway. Cookies, passwords and secret values are never sent to the model. Page content is treated as untrusted data.
5. Retention
- Account and workspace data is kept while the workspace is active.
- Sync revisions are kept according to the workspace's retention policy; when no policy is set, all revisions are kept.
- When you permanently delete a profile, its stored copy on Browlix is queued for deletion and every machine that ran it deletes its own copy.
6. Your rights
You can view and edit most data directly in the dashboard. To request a copy, a correction or deletion, use the Contact page.
7. Cookies and browser storage
See the Cookie Policy.
8. Contact
Send privacy questions through the Contact page. The operating entity's legal details will be added before billing opens.