Memory and your privacy
What Dropstone memory stores, what it never stores, who can see it, and how to keep something out of it. Memory is private to your account and you can see and remove all of it.
Memory is useful precisely because it persists, which is also why it deserves a clear answer about what is in it and who can see it.
What memory stores
Three things, all in plain text you can read:
- Lessons: the rules and facts Dropstone has learned from working with you. Each is a short sentence or two, stated generally, sometimes with a note on why it was recorded.
- Studied knowledge: what Dropstone kept, in its own words, from sources you asked it to study, with the source attached.
- Conversation summaries: brief descriptions of what you worked on together, so it can pick up context later.
That is the full list. You can see every entry at any time by asking. See See what Dropstone has learned.
What memory does not store
Your conversations. Chat history is kept separately so you can search and revisit it, but it is not memory. Memory holds what was learned, not the transcript.
Your files. Documents you upload to a project stay in that project. What Dropstone learns from working with them can become a lesson; the file contents do not.
Your code. The CLI reads your codebase to do its work. It does not copy your code into memory. A lesson might say "this project keeps config in a single typed file"; it will not contain the file.
Anything from incognito. An incognito chat neither reads memory nor writes to it.
Who can see it
You. Memory belongs to your account.
Nobody else, by default. On a personal account, no one else can see your memory. In an organization, other members can see only memories you have chosen to share, and only at the level you shared them. Sharing is always your decision. See Memory in teams and organizations.
Not other customers. Memory is isolated per account and per organization. There is no path by which one customer's memory reaches another.
Keeping something out
If there is a conversation you do not want Dropstone to learn from, use an incognito chat.
If it has already learned something you want gone, ask it to forget. It is removed from use on every surface.
If you want everything gone, delete your account. Memory is deleted with it.
Secrets
Dropstone is designed not to record credentials, tokens, or keys as lessons. If you are in an organization, any memory is additionally scanned before it can be shared, and a memory containing something that looks like a secret cannot be shared until that is removed.
If you see something in your memory list that should not be there, ask Dropstone to forget it, and let us know through How to get support.
Where memory lives
Memory is stored on Dropstone's servers, associated with your account, so that it can follow you across chat, the CLI, and the SDK. For where requests are processed and how data is handled more broadly, see How Dropstone handles your data and Where your requests run.
Related articles
- See what Dropstone has learnedAsk Dropstone what it remembers and it lists everything, standing rules separately from facts. You can also ask what memory it used on a specific reply. Nothing is hidden from you.
- Change or forget a memoryTell Dropstone to forget something and it stops applying it. Tell it a fact should be a rule, or a rule is too broad, and it adjusts. Only you can remove a memory. It never forgets on its own.
- Incognito chatsAn incognito chat writes nothing to your memory: nothing you say or correct is kept, and no summary is made. What Dropstone already knows about you is still available to it, so the work gets the same assistant without leaving a trace.
- How Dropstone handles your dataWhat Dropstone stores, for how long, who can see it, whether it is used to improve the models, and the commitments that apply to every account. A plain-language summary of Dropstone's data practices.
- Memory in teams and organizationsIn a Dropstone organization, memory has three levels. Private is yours alone. Team is shared with one team. Organization is shared with everyone. Nothing is shared unless its author decides to share it.