KazoCode DocsAccount

Legal

Security

How KazoCode protects your account and data, and how to report a security vulnerability under our safe harbor.

On this page

Updated November 20, 2026

How we protect you

  • Your code stays local. Projects, chats, memory and terminal sessions live on your computer, so they aren't exposed by a breach of our servers.
  • Keys stay in your OS key store. API keys for your own providers are kept in Windows Credential Manager, macOS Keychain or the Linux secret service, and aren't synced.
  • Hashed secrets. Passwords are stored as salted hashes. Device access and refresh tokens are stored only as hashes and rotate on use.
  • Encryption in transit. Every connection to kazocode.app and api.kazocode.app uses TLS. Session cookies are HTTP-only and secure.
  • Signed updates. App updates are cryptographically signed, and the app refuses an update whose signature doesn't match.
  • The agent asks first. Writes, commands and network access go through the permission system unless you allow them.
  • Least access. Only the people who need it can reach production systems.

Report a vulnerability

Email [email protected] with:

  • what you found and where;
  • steps to reproduce it, and a proof of concept if you have one;
  • what an attacker could do with it.

We'll confirm we received it within 3 business days, keep you updated, and tell you when it's fixed. With your permission, we'll credit you.

Safe harbor

If you research in good faith under this policy, we won't pursue legal action against you or report you to the authorities, and we'll consider your research authorized. In return:

  • test only against your own accounts and data, and stop as soon as you reach anyone else's;
  • don't degrade the Services for others, run denial-of-service tests, spam or social-engineer our staff or users;
  • don't access, change or keep more data than you need to show the problem, and delete what you've accessed when you're done;
  • give us reasonable time to fix the issue before telling anyone else, and don't demand payment in exchange for not disclosing it.

Out of scope

  • vulnerabilities in third-party services, add-ons or model providers, which should go to their owners;
  • reports from automated scanners without a demonstrated impact;
  • missing security headers or best practices with no exploitable impact;
  • attacks that need physical access to a user's unlocked device;
  • the agent doing something a user explicitly approved.

Updated November 20, 2026