Privacy

Knosy is built to know as little as possible. What you and your team choose to share syncs through Knosy Cloud, because that's what makes it shared. Everything else stays on your machine.

What syncs to Knosy Cloud

• Shared context you publish. Context files you've explicitly added to Knosy and published, so your teammates see the same thing you do.
• Memories. The useful facts Knosy learns from your sessions. The learning itself happens on your machine; only the resulting memories and their details reach the cloud, never the conversation they came from.
• Your account and team. Who you are, which team you belong to, and the roles and permissions that govern access.

This data belongs to you and your team. Access to it follows your team's roles and permissions, and the Knosy team operates the infrastructure without access to your content.

What never leaves your machine

• Your conversations. Raw prompts and responses are processed locally when Knosy learns a memory, and full transcripts never reach the server.
• Files you haven't added. Anything on your machine that you didn't explicitly add to Knosy is invisible to it, and is never read or uploaded.
• Your local notes. A local companion file beside a scope's instructions stays local, always.
• Provider credentials. Your host logins stay in their own credential storage. Knosy never copies, displays, or uploads them.
• Diagnostics. They exist only locally, and anything you copy from them is scrubbed of prompt excerpts, file contents, and identifying details first.

Secrets are scrubbed before anything is stored

Before a memory is saved anywhere, it's checked for secrets on your machine. Clear secrets are removed; anything uncertain or sensitive goes to review instead of being published automatically.

Private stays private

Your Private scope and personal memories belong to you alone, even though the cloud synchronizes them for you across your work. No teammate, Admin, or Owner can see or manage them.

While Knosy is running

Session cards, their states, and the short prompt excerpts that identify them live only in memory. Close Knosy and they're gone.

What Knosy remembers between runs

• Your preferences: appearance, language, monitor, shortcut, startup, and notification choices.
• The capsule's position on each monitor.
• The last scope you confirmed for each host and folder, so it can be suggested next time.
• Which scope each known session uses, as identifiers only, so resuming a conversation keeps its context. No prompt or content is stored with it.
• What it needs to safely repair or remove its own host integrations, including your configuration backups.

Your host configurations

Connecting an integration changes only Knosy's own entries in the host's configuration, after backing the file up. Everything else you've configured in Claude Code or Codex is preserved, through connect, repair, and remove alike.