Privacy and safety

What Ducter never does by itself, what runs where, how it uses your AI plans, memory with Nowledge Mem, and who can reach your Ducter.

Ducter is meant to be a partner you can leave alone with real work. That only works if you know exactly what it will and won’t do. This page lists it.

What Ducter never does by itself

What runs where

Your AI plans stay yours

Ducter works through each AI agent’s own official app, signed in with your own account. It doesn’t proxy your login, share it, or pretend to be anything else. That’s also why Ducter is something you run yourself rather than a hosted service.

Tasks use your plan’s limits like any other session would. Your agent’s own settings, skills and tools apply to tasks too, so a Ducter task in your project behaves the way your own session there does.

Memory, with Nowledge Mem

Memory is optional. Without it, Ducter works fine and remembers your conversation.

If you use Nowledge Mem, your partner starts out knowing who you are and what you’re working on, from the same memory your other AI tools share. When it saves something worth keeping, you see one quiet line under its reply: Noted · . Every memory records that it came from Ducter and which conversation it came from, so you can always trace it back. If you edit a memory in Nowledge Mem, your edit wins.

Tasks run as you

Tasks don’t stop to ask before every command; that would make Ducter one more thing to babysit. Instead, a task on your Mac runs with the same access your own AI agent session would have: it can do what you can do there. That’s the trade, and it’s why merging and sending things out wait for you.

Running Ducter’s tasks on a separate server keeps them away from your personal files. Sandboxed places that can’t touch your files at all are coming later.

Who can reach your Ducter

Found a security problem? Please report it privately, as described in SECURITY.md.