What stays on your machine when a browser agent reads a page
The page stays in the browser profile on your computer. The website sees the visit, and the AI client you connected keeps the tool results it asked for.
Drafted with AI tools (Claude Code and Codex) and published by Rattana Devs. How we write
What stays on your machine when a browser agent reads a page is the local profile record: the visit, cookies for that profile, and the score and evidence Kitsuvo stored for the page. The app has no telemetry. The website still receives the request, and the AI client you connected receives the tool results it asked for and keeps them under its own policy.
We make Kitsuvo. The details below match the privacy policy and the agent section of the security page. They describe the current Mac release. The published Windows 0.2.4 installer predates browser_status and cannot complete the current MCP connection check, so it is not a verified agent setup. See the Windows MCP compatibility limit. If browser_status is missing, do not guess the profile mode.
What remains on the computer?
kitsuvo mcp uses your normal signed-in browser profile by default. Add --separate-profile for a separate persistent profile with its own sign-ins. Separate profiles need macOS 14 or later. Direct agent mode uses a separate profile. Hiding the window with --headless also uses an isolated profile.
In whichever profile the agent used, the visit can leave history, cookies, site data and downloads on the computer. Scores, evidence and verdict corrections are stored on the computer too. The browser has no telemetry: the app does not send Kitsuvo usage statistics, crash reports, or an identifier for you. Local detection does not upload the page to Kitsuvo.
You can export or clear saved browsing data from Settings, then Privacy. The confirmation lists what that action retains. Downloaded files are separate from the browsing-data clear. The agent profile keeps its own cookies, history and downloads until you clear that profile or delete the files. There is no fixed timer that wipes it.
What does the website receive?
A read is a real page load. Kitsuvo uses the system web engine, WKWebView on Mac and WebView2 on Windows. The site receives what a browser normally sends, including your IP address, under that site's own policy. Kitsuvo turns off the engine features that would send the addresses you visit to Microsoft, Google or Apple for those engines' browsing reports.
A few signals stay with the operating system. On Windows, WebView2 diagnostic data follows your Windows diagnostic setting, and the engine updates through Microsoft. On Mac, crash reports follow Share Mac Analytics. Those are operating-system controls, not a Kitsuvo analytics feed.
If update checks are on, Kitsuvo asks kitsuvo.com once a day whether a new version exists. That request shows an IP address and a time to the host. It does not include the page the agent read, and it is not an identifier for the device. You can turn update checks off in Settings, then Advanced, then Updates.
What leaves for the AI client?
The local MCP connection does not add a Kitsuvo analytics upload. It does return tool results to the client you configured. Those results can include URLs, page text, accessibility snapshots, detection reports, and screenshots when the installed build reports that the capture mode is supported. Do not infer screenshot support from the operating system alone. Ask browser_status on a build that has it.
The client stores and retains those results under its own policy. That copy is not removed when you clear Kitsuvo. If the page contains personal data, the result can contain it too. Review a page before you let an agent read it: review an unfamiliar site before an agent clicks.
Sign-in pages are not read or scripted, and password fields do not take typed text, unless you start Kitsuvo with --allow-sensitive. Sensitive categories listed on the security page are refused in the same way. The agent can still be told to hand that step to you.
What about the optional cloud relay?
The cloud connector is off unless you start it. It asks for consent in your local terminal and uses an isolated agent profile. It forwards selected tool arguments and results, including snapshots, supported screenshots and detection reports, through a Kitsuvo relay hosted by Fly.io to the client you authorize. It does not upload your normal browsing history. Tool payloads are handled in transit and are not saved as a Kitsuvo page archive. Disconnecting the connector stops further forwarding. It cannot pull back a copy the client already accepted.
Remote access from another device reaches only that separate agent profile. It cannot list or open your normal signed-in profile. Setup is on the integrations page.
Where each copy lives
| Copy | Where it stays | Who else can already have it |
|---|---|---|
| History, cookies, score, evidence | The profile on this computer | Nobody at Kitsuvo from local detection |
| The page request | Not only local; the site handled the visit | The website, under its policy |
| Tool results | Returned to the connected client | That client, and the relay only while a cloud session is forwarding |
| Update check | Not a page copy | The host sees IP address and time, not the page |
Optional cross-device continuation is a different switch, off by default. It is described in the privacy policy and is not what a local page read does.
Questions people ask
Does Kitsuvo upload the page when an agent reads it?
Local detection does not upload the page to Kitsuvo. The app has no telemetry. The connected AI client still receives the tool results it requested, and the website receives the visit.
Does the default MCP profile share my signed-in sites?
Yes. kitsuvo mcp uses your normal signed-in browser profile by default, so existing cookies for that profile are available. Add --separate-profile for a separate persistent profile. Check browser_status on a build that provides it.
If I clear browsing data, is the agent's copy gone?
Clearing Kitsuvo removes the local profile data that the clear says it removes. It does not remove copies the website already received, or copies the connected AI client already stored.
Is the published Windows installer a verified agent setup?
No. The published Windows 0.2.4 installer predates browser_status and cannot complete the current MCP connection check. Windows 0.2.4 remains available for ordinary browsing and local filtering. Use the current Mac release for a verified agent setup, or wait for a qualified Windows release. See the Windows MCP compatibility limit.
Comments
Read the discussion or sign in to add a plain-text comment.
Loading comments…