No advertising SDKs, analytics trackers, remote fonts, or third-party JavaScript.
Processed only when needed for browser-control features you enable and actions you request.
You choose which AI client/service, if any, receives task-relevant information.
This website intentionally uses no advertising SDKs, analytics trackers, remote fonts, or third-party JavaScript.
Scope and operator
This policy covers the Equinox Browser Chrome extension, the Equinox Local runtime installed on your computer, and this website. The project is operated by Samet Başbuğ. Privacy questions can be sent to iletisim@sametbasbug.dev.
What Equinox Browser may process
Equinox Browser only processes browser data when it is needed for the browser-control feature you enabled. Depending on the action you request, this may include:
| Category | Examples | Why it is used |
|---|---|---|
| Website content | Visible text, accessibility-derived page structure, dialog text, screenshots | Understand the current page and carry out the action you requested. |
| Browsing activity | Tab URL/title, navigation state, bounded request/response URL and status metadata | Choose the correct tab, navigate safely, and observe requested browser activity. |
| User activity | Text you instruct an agent to type, selected form values, click/scroll targets | Perform the interaction you explicitly requested. |
| Agent Browser bookmarks | Bounded bookmark/folder titles, HTTP(S) URLs and readable folder paths from the isolated Agent Browser profile | Save, find, organize and revisit sites in the agent's dedicated browser workspace. |
| Extension settings | Automation on/off, cursor preference, local agent display name, consent state | Remember your local browser-control preferences. |
The extension does not expose a cookie API, and bounded network observation does not collect request/response bodies or HTTP headers. The required Chrome bookmarks permission is used by the product only for the isolated Agent Browser workspace; Equinox Local rejects bookmark automation for the user's personal Your Browser context, and the extension independently rejects bookmark commands outside Agent Browser.
Where browser data goes
Equinox Browser sends the information needed for an action through Chrome Native Messaging to the Equinox Local runtime installed on your own computer. Equinox does not send that browser data to an Equinox-operated advertising or analytics service.
If you connect Equinox Local to an AI client or AI service, information required to fulfill your requested task may then be provided to that client or service. That provider's own privacy terms apply. Equinox Local does not silently choose an AI provider for you.
Storage and retention
The extension stores local preferences in chrome.storage.local, including control state, cursor preference, display name and consent. Agent Browser and Your Browser have independent profile state. Agent Browser bookmarks remain in that Chrome profile’s bookmark store; Equinox does not maintain a cloud browsing-history or bookmark database.
Equinox Local stores configuration, credentials, task artifacts and bounded runtime diagnostics on your computer. Requested screenshots or downloaded files may be made available to your connected agent. Runtime events are bounded and rotated, with credential-like values redacted before persistence; task files are not all automatically deleted at the end of a session.
Root-aware structured capabilities follow Full or Selected access mode. Terminal is a separate, broad operating-system-user shell and is not confined to Selected roots once started. Disable Terminal if you require strict selected-root containment.
Local tools and connected services
File and Terminal actions can return project contents, command output and process logs to your AI client. On macOS, optional Desktop control can provide requested screenshots and interaction results; Screen Recording and Accessibility permissions are granted to Equinox Local.app. Windows Local v1 does not expose Desktop automation.
For ChatGPT, OpenAI Secure MCP Tunnel makes an outbound HTTPS connection to OpenAI. The runtime key is stored privately on this computer and used to authenticate that connection. Task-relevant data goes to the connected provider under that provider’s privacy terms. Local-first does not mean offline-only processing.
Optional Telegram delivery sends agent-supplied message text to Telegram’s Bot API and the single private account configured in Control Center. The bot token and recipient ID are held in private local files and are not returned to agents. Agents cannot choose another recipient, read an inbox, or send to groups/channels through this integration. Telegram’s own terms apply to delivered messages.
How data is used
Browser and local-project data is used only to provide, secure, troubleshoot, and improve the user-requested Equinox Local / Equinox Browser functionality. It is not sold, rented, used for personalized advertising, or used to build advertising profiles.
Chrome Web Store Limited Use
The use of information received from Chrome and related browser APIs by Equinox Browser adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Information is used only for the prominent user-facing browser-control purpose and permitted security or reliability work directly related to that purpose.
Your controls
- Review Agent Access in Control Center. New managed installs start in Full mode; you can select configured roots for root-aware structured capabilities.
- Disable Terminal/process, Desktop or Browser capabilities separately. Removing a configured root is not a substitute for disabling broad Terminal access.
- Accept browser-data disclosure and enable browser automation separately in each Chrome profile. Turning control off rejects browser actions.
- Use isolated Agent Browser by default; personal Your Browser is an explicit choice. Personal bookmark automation is not exposed.
- Choose which AI or service providers to connect and disconnect optional integrations when no longer needed.
- Uninstall the extension or Local. Local’s normal uninstall preserves workspace/configuration; full local-data removal is a separate confirmed option.
Security model
Control Center binds to loopback only and requires same-origin/CSRF protections for management mutations. Root-aware structured operations have path and protected-area checks; these are not a filesystem sandbox for Terminal. Equinox Browser has no broad host_permissions and uses Chrome’s debugger API and Native Messaging. See the Security page for the scope and limits of these boundaries.
Changes to this policy
If Equinox Local's data handling materially changes, this page will be updated before the changed behavior is relied on for public distribution. The effective date above identifies the current policy version.