Privacy and data handling

Local-first where practical. Network access only where the selected feature needs it.

Local tools and inputs

Docbench processes local documents and PDFs in the browser; Codebench processes code payloads and scans locally. Papagenerator keeps imported images on the device. Streambench keeps local playlists, XMLTV data, edits, favorites and history in browser storage or memory. Exported files are saved to the device.

Camera access requires browser permission. Browser data can be cleared in site settings. Clearing it may remove saved preferences or local history.

Network requests

The hub and tools use network services for hosting, public feeds, weather, provider catalogs, stream playback, fonts, icons or external media. Requested third-party URLs may receive connection metadata such as IP address and request headers. Streambench's Worker fetches public provider catalogs; loading a remote stream or document contacts its source where supported.

Hosting and external services may process request data according to their own policies. Local-first does not mean that every feature works offline or that no network requests occur.

Optional agent access

WebMCP tools reuse the current visible app state on supported browser hosts. Requested tool results may include editor text, code payloads or playlist information. Once returned to an agent or host, data is handled under that host's policy. Do not pass sensitive files, codes or credentials to an agent unless you intend to share them.

Scope and contact

This shared policy describes the public TRAVNY hub and browser tools, not account-connected bots or plugins. Service-specific access boundaries are documented by the individual applications when needed.

Report a hub issue · Report a Bench issue. Never include confidential input or credentials in a public report.

Back to the workshop