Prokop Browser Privacy Policy

Last updated: September 2, 2026

Applies to: Prokop Browser Chrome Extension (the “Extension”), published by CapekAI (“we”, “us”, “our”).

The Extension connects your browser to a Prokop server you configure. It does not collect or send your data to CapekAI.

1. Overview

Prokop Browser is a client-side browser extension that gives Prokop’s built-in browser tools access to web pages. When requested by your Prokop server, the Extension can read visible page content, discover and interact with page elements, navigate, manage tabs, and capture screenshots.

The Extension sends browser data only to the Prokop server URL you configure. It does not send that data directly to CapekAI, Google, analytics providers, advertising services, or other third parties.

2. Data handled by the Extension

2.1 Data stored locally in your browser

The Extension uses Chrome’s chrome.storage.local API to store its configuration on your device.

Data	Purpose	Retention
Server URL	Connects the Extension to your Prokop server.	Until you change it or clear extension data.
API token	Optional authentication for your Prokop server.	Until you change it or clear extension data.
Client ID	Identifies the Extension to your Prokop server.	Until you clear extension data.

This configuration leaves your browser only when the Extension connects to the Prokop server you selected.

2.2 Data processed while browser tools run

Depending on the browser action requested by your Prokop server, the Extension may temporarily process:

Page content: visible text read from a web page.
Page structure: selectors, attributes, text, and metadata for interactive elements.
Screenshots: PNG images of the visible area of a browser tab.
Navigation data: URLs and page titles.
Tab information: tab IDs, titles, URLs, active state, and window information.
Interaction data: browser actions requested by your Prokop server and their results.

This runtime data is returned to the Prokop server you configured. The Extension does not retain page content, screenshots, or browser-action results in local storage after processing them.

3. Data we do not collect

We do not collect personal information through the Extension.
We do not collect or sell browsing history.
We do not track the websites you visit.
We do not use analytics, telemetry, advertising cookies, or tracking pixels.
We do not use Extension data for advertising, profiling, or credit decisions.
We do not have access to your Prokop server or the data stored on it.

4. Third-party services

The Extension does not integrate directly with analytics, advertising, or external browser-automation services. Its network connection is limited to the Prokop server URL you configure.

Your Prokop server may use model providers, tools, or other services that you configure. Data handled by those services is governed by their own privacy policies and by your Prokop setup. CapekAI does not choose or control those services for you.

5. Chrome permissions

Permission	Why it is needed
`storage`	Saves the server URL, optional API token, and client ID in `chrome.storage.local`.
`tabs`	Reads tab details, captures the visible tab, and lets browser tools create, close, navigate, or switch tabs.
`activeTab`	Allows browser tools to work with the active tab.
`alarms`	Keeps the Extension’s connection to your configured Prokop server available after Chrome suspends its background service worker.
Host access	Allows the content script to read and interact with web pages when a browser tool is used.

The Extension does not use remote code. Its executable logic is included in the extension package and is not downloaded at runtime.

6. Data flow

Your browser tab
  ↕
Prokop Browser extension
  ↕ WebSocket connection
Your configured Prokop server

The WebSocket connection uses the protocol supported by the server URL you configure. Use HTTPS and secure WebSockets when connecting across an untrusted network.

7. Your Prokop server

You control which Prokop server the Extension connects to. Data sent to that server is subject to the server operator’s configuration and privacy practices. If you operate the server yourself, you control its storage, providers, tools, and data retention.

8. Security

You are responsible for protecting access to your Prokop server and API token. Only connect the Extension to a server you trust. You can remove stored configuration by clearing the Extension’s data or uninstalling it.

9. Open source

Prokop Browser is open-source software. You can inspect its source code and verify the behavior described in this policy at github.com/capek-dev/prokop/tree/main/packages/browser.

10. Changes to this policy

We may update this policy when the Extension or its data practices change. The date at the top of this page will show the latest revision.

11. Contact

For questions or concerns about this policy, contact CapekAI through github.com/capek-dev/prokop/issues.