Skip to content

Legal

LBcat Privacy Policy

What LBcat collects, why, who receives it, how long it is kept, and how to delete it.

Last updated: November 14, 2026

Who runs LBcat

LBcat is our browser extension for userscripts, with local browser control for coding agents. It is a fork of the open source ScriptCat userscript manager, and its source code is public at github.com/latentbyte/lbcat. LBcat is run by Latent Byte LLC. Questions about your privacy in LBcat go to [email protected].

What LBcat collects and shares

  • Latent Byte runs no servers that receive data from LBcat, and LBcat has no analytics, tracking, or ads. Your scripts, settings, and logs are stored in your browser.
  • LBcat needs broad access to web pages, and uses it on your device. Userscripts you install run on the pages they match. Cookies, web requests, downloads, the clipboard, and notifications are used only when a script you installed, or a command you ran, asks for them.
  • If you connect the optional Browser Control tools, a program on your own computer can read and act on tabs in the browser window you set aside for agents, and on another tab only when you grant that exact tab. The tools accept commands only from programs under your user account, over a local connection that does not use the network. Screenshots and page content go only to the program that asked for them.
  • LBcat sends data over the network only when: a script you installed makes requests to the sites it declares (you approve those permissions when you install it; scripts are third-party code, so review them first); it checks the update address of each installed script; it fetches icons from the sites your scripts match, or the matched domain names go to Google, DuckDuckGo, or Icon Horse if you pick that icon service; you turn on cloud sync or backup, which sends your scripts to the storage provider you set up with your credentials; or you set up the built-in AI agent, which sends your prompts and the page content it works on to the model provider you chose, with your own API key.
  • LBcat does not contact the ScriptCat project's servers on its own. Two things reach servers run by that project, not by Latent Byte, and only when you use them: the sign-in relay for connecting a cloud drive such as OneDrive for sync, and links you open to the ScriptCat script store and documentation.
  • Everything LBcat stores lives in your browser profile, and removing the extension deletes it. Data you sent to a sync or model provider is covered by that provider's policy.

Security

LBcat sends nothing to Latent Byte servers, and its Browser Control connection stays on your computer. How we protect stored data, and the limits of that protection, are described under Data Security in the Latent Byte Privacy Policy.

Latent Byte Privacy Policy

This notice supplements the Latent Byte Privacy Policy, which covers your rights, cookies, international transfers, children's privacy, and how we announce changes. Where the two differ, this notice applies to LBcat. Your use of LBcat is governed by the Terms of Service.