[ extension privacy policy ]updated · august 6, 2026

browser control, your rules.

This Privacy Policy describes how Donkit.AI ("Donkit", "Company", "we", "us") collects, uses, and protects information in connection with the Donkit Browser Control browser extension for Google Chrome and Chromium-based browsers (the "Extension"), version 2.1 and later.

It is a standalone policy for the Extension and supplements the general Donkit.AI Privacy Policy, which governs the Donkit platform, websites, and services as a whole. Where you use the Extension together with the Donkit platform, both documents apply; in case of conflict regarding the Extension’s behavior, this policy prevails.

Company details: Donkit.AI, Registration No. 516981651 · Derech Menachem Begin 158, Tel Aviv-Yafo, 6492109, Israel · info@donkit.ai · +972 (77) 360-9468

01

What the Extension Does

The Extension connects your browser to an AI agent that you have created or use on the Donkit platform, so that the agent can browse the web on your behalf. After you explicitly pair the Extension with your Donkit workspace, the agent can — in dedicated browser windows created by the Extension, separate from your own browsing — open pages, click, type, scroll, take screenshots, and read page content, and receive the results of those actions.

Each agent conversation gets its own controlled tab, so separate tasks never share a page. While an agent is acting, the controlled page displays an on-screen “agent is active” indicator, which disappears automatically once the agent has been idle for 30 seconds.

The Extension acts only on your instructions: it does nothing until you pair it, and the agent only controls the browser while executing tasks you have asked it to perform on the Donkit platform.

02

Information the Extension Collects and Transmits

2.1 Data from agent-controlled windows

When (and only when) an agent is executing a task, the Extension collects from the dedicated controlled tab and transmits to your Donkit platform environment:

  • Screenshots of the controlled tab (JPEG images of the rendered page);
  • Page text and HTML content of the controlled tab, including content inside frames embedded in that page;
  • Accessibility-tree data (a structured description of page elements — buttons, links, form fields — used so the agent can interact with the page);
  • Page URL and page title of the controlled tab;
  • Results of interactions (e.g., which element was clicked, whether an action succeeded or failed, and a short report on the currently focused form field so the agent can confirm that its typing arrived).

This data is sent over an encrypted connection (WSS/HTTPS) to the Donkit platform environment you paired with, where it is used by your AI agent to complete the task you assigned. Processing of this data on the platform — including processing by the large-language-model providers that power your agent — is governed by the general Donkit.AI Privacy Policy.

Sensitive form fields are masked before anything leaves your browser. Where a field is a password field, or is marked by the website as a credit-card field (autocomplete="cc-…") or a one-time code (autocomplete="one-time-code"), the Extension reports only the length of what is in the field, never its contents. This applies both to the accessibility tree and to the focused-field reports, so passwords, card numbers and SMS/authenticator codes are never transmitted to the platform or placed in your agent’s context. Values of other form fields are reported and are truncated to the first 500 characters.

Important: apart from the masked categories above, if you log in to websites or display personal information inside an agent-controlled window, that content may appear in screenshots and page text transmitted to the platform. Controlled windows are separate from your own and are marked while the agent is active, so you can always tell them apart from your personal browsing.

2.2 Data from your normal browsing — not collected

The Extension does not collect, read, record, or transmit:

  • your browsing history;
  • the content, screenshots, cookies, or credentials of any tab outside the dedicated agent-controlled windows;
  • keystrokes or form input in your normal tabs;
  • bookmarks, downloads, or other browser profile data.

There is one narrow exception, and it is entirely under your control: when you open the Extension popup to pair your browser, the Extension reads the address of the tab you are currently on and offers it as a suggestion for the Donkit server address, shown as a button you may click. If you do not click it, the address is not used, and it is never transmitted anywhere.

2.3 Pairing and connection data

To establish and maintain the connection, the Extension processes:

  • a single-use pairing code that you generate in the Donkit platform and type into the Extension popup; it is consumed by the first successful pairing;
  • a device token issued by the platform once pairing succeeds — the credential that lets this browser reconnect without re-pairing;
  • a device identifier and a device name. The device name is proposed by the Extension from your browser and operating system (for example, “Chrome on Windows”) and can be edited by you before pairing; it exists so you can recognise this browser in the Donkit interface;
  • the address (URL) of the Donkit platform environment you paired with;
  • the version number of the Extension, reported when the connection is established, so the platform can tell you when a newer version is available.

These values are stored locally in your browser’s extension storage (chrome.storage.local). They identify the paired browser; the Extension itself does not store your name, email, or Donkit account password.

2.4 Data the Extension does not collect at all

The Extension contains no analytics, telemetry, advertising, or tracking code. It does not use cookies. It does not collect health, financial, payment, location, or biometric information as a category of its own (though, as noted in 2.1, content you choose to display in a controlled window is captured as part of screenshots and page text, save for the masked field categories).

03

How Information Is Used

Data described in Section 2 is used solely to:

  • establish and maintain the pairing between your browser and your Donkit environment;
  • let your AI agent perform the browsing tasks you assign (navigate, click, type, scroll, read pages);
  • return the results of those tasks (screenshots, page content, action outcomes) to you through the Donkit platform;
  • display connection status, the on-page “agent is active” indicator, and a notice when a newer version of the Extension is available.

We do not use Extension data for advertising, profiling, or creditworthiness determination, and we do not sell or rent it to anyone.

04

Where Data Goes (Disclosure and Sharing)

  • Your Donkit platform environment. All data collected by the Extension is transmitted only to the Donkit platform host you explicitly paired with (shown in the Extension popup while connected). No data is sent anywhere else by the Extension.
  • Service providers of the platform. Once on the platform, agent-task data (including page content and screenshots) may be processed by the infrastructure and AI-model providers described in the general Donkit.AI Privacy Policy.
  • Websites you direct the agent to visit. When the agent browses a website in a controlled window, that website receives the same information any browser visit conveys (IP address, user agent, and any input the agent submits on your instructions).
  • No third-party sharing by the Extension. The Extension itself shares data with no advertisers, data brokers, or analytics providers.

We may disclose information where required by law, as described in the general Privacy Policy.

05

Browser Permissions Explained

The Extension requests the minimum permissions needed for its function:

permissionwhy it is needed
debuggerThree uses, all confined to agent-controlled tabs. (1) Sending trusted mouse and keyboard events through the Chrome DevTools Protocol, so the agent’s clicks and typing behave like real user input — events synthesized any other way are marked untrusted and are ignored by many websites. (2) Capturing screenshots of the controlled tab’s own surface, which means the agent can see the page without activating the tab or stealing focus from what you are doing. (3) Asking Chrome not to freeze the hidden controlled tab, which would otherwise stall the agent silently. Never attached to your own tabs; detached when the session ends or the tab closes.
tabsTo create and manage the dedicated controlled windows, navigate them, detect when pages finish loading, read the controlled tab’s URL and title, relay commands to the injected script, exempt the controlled tab from Chrome’s Memory Saver so it is not discarded mid-task, and clean up when it is closed.
scriptingTo inject the Extension’s own packaged scripts into the controlled tab in order to read page text, HTML and the accessibility tree, resolve which element an action should target, and render the “agent is active” indicator.
storageTo store the platform address, device token, device identifier and name, and which tab belongs to which agent session, so the connection survives Chrome restarting the Extension’s background worker.
alarmsTo run timers that survive Chrome suspending the Extension’s background worker: reconnecting after a dropped connection, and the sweep that hides the “agent is active” indicator once the agent goes idle. No user data is involved.
notificationsTo confirm successful pairing, to tell you when a pairing has been revoked or is no longer authorized, and to mention once per version that a newer Extension build exists. No marketing notifications.
activeTabTo read the current tab’s address in the popup so it can be offered as a suggestion for the server field during pairing, and to capture screenshots on the fallback path used for pages the debugger cannot attach to.
host access (<all_urls>)The agent must be able to browse whichever website you direct it to, and that set cannot be known in advance, so it cannot be limited to a fixed list. The Extension still only ever reads content from tabs it created for agent sessions.
06

Data Storage, Security, and Retention

  • Locally: the Extension stores the platform address, the device token, the device identifier and name, reconnection bookkeeping, and which tab belongs to which agent session. It stores no page content, screenshots, form input, or credentials for third-party websites. Local data is deleted when you disconnect, when the platform revokes the pairing, or when you uninstall the Extension.
  • In transit: all communication with the platform uses encrypted WebSocket/HTTPS connections. Pairing codes are single-use and are spent by the first successful pairing.
  • On the platform: screenshots and page content transmitted during agent tasks are retained and protected as described in the general Donkit.AI Privacy Policy (see its Data Retention and Security sections).

No method of transmission or storage is 100% secure; we apply commercially reasonable technical and organizational measures appropriate to the risk.

07

Your Controls and Rights

You are always in control:

  • Pair/unpair at will. Click Disconnect in the Extension popup to end the session immediately; the stored device token is erased.
  • Revoke from the platform. Revoking this browser in your Donkit workspace ends its access; the Extension is notified, releases the controlled tabs, and tells you what happened.
  • Close a controlled window at any time to interrupt agent browsing.
  • Take back control of a tab by dismissing Chrome’s own “is being debugged” banner on it.
  • Uninstall the Extension to remove it and all locally stored data.

For data already transmitted to the Donkit platform, you may exercise the rights described in the general Privacy Policy — including access, rectification, deletion, restriction, objection, portability, and withdrawal of consent under GDPR, UK GDPR, applicable US state privacy laws, and the Israeli Privacy Protection Law — by contacting info@donkit.ai.

08

Children’s Privacy

The Extension is not directed at children under 16, and we do not knowingly collect personal information from them. If you believe a child has used the Extension, contact info@donkit.ai and we will delete the associated data.

09

International Data Transfers

Data transmitted by the Extension is processed where the Donkit platform is hosted and may be transferred internationally as described in the general Donkit.AI Privacy Policy, subject to appropriate safeguards (such as Standard Contractual Clauses where required).

10

Chrome Web Store Limited Use Disclosure

The Extension’s use of information received from browser APIs adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements:

  • data is used only to provide and improve the Extension’s single, user-facing purpose (letting your Donkit agent browse for you);
  • data is not used for personalized advertising;
  • data is not sold to third parties;
  • humans do not read the collected data except with your consent, for security purposes, to comply with applicable law, or as part of aggregated/anonymized internal operations.
11

Changes to This Policy

We may update this policy from time to time. Material changes will be reflected by a new effective date and, where appropriate, announced through the Donkit platform or the Chrome Web Store listing. Continued use of the Extension after changes take effect constitutes acceptance of the revised policy.

12

Contact Us

Questions or requests regarding this policy or the Extension: