# Privacy

> The public website documents an open-source project. The software itself runs where you install it.

Canonical URL: https://openbrowse.co/privacy
Markdown URL: https://openbrowse.co/privacy.md

## Privacy

OpenBrowse does not provide a hosted browser-agent account or a managed customer workspace. When you install the runtime, its configuration, database and browser profiles live on the machine you operate. Your chosen model provider receives the prompts and browser-derived context needed to answer a task, subject to that provider’s own terms and privacy controls. Lucas Johnston Kurilov maintains this public website and is its contact for privacy questions at help@lujstn.com.

Browser profiles are especially sensitive: they can contain cookies and web-storage data that grant access to third-party accounts. Keep profile exports out of source control, restrict access to the host and API token, and avoid exposing an instance directly to the public internet. The safe exposure guide and profile documentation explain the operational boundaries in more detail.

## This website

This website is a public, static documentation and marketing site. It does not ask visitors to create an OpenBrowse account or submit browser-agent credentials. If you follow links to GitHub, PyPI, a model provider, or another external service, that service handles your information under its own policy. GitHub issues are public unless the repository provides a private security-reporting route.

Like most web hosting, delivery may produce technical request records such as IP address, user agent, requested path and time. Do not send secrets through public pages, issue comments or URLs. If you need to operate the runtime for other people, set your own retention, access and incident-handling policies: you are the operator of that instance and its data.

## Changes and questions

This page describes the project’s public site and documented self-hosted architecture, not the privacy policy of every deployment. Material changes will be reflected here. For project questions, use the contact routes and never include credentials or unredacted session data.