Who can see and change your memory
What Dropstone remembers belongs to your account. You can read all of it and delete any of it, the agent records and never forgets on its own, and nobody at Dropstone can read it.
What Dropstone remembers belongs to your account. You can read all of it, and delete any of it. This page is about who else can touch it, because that is the part people ask about.
What is kept
Two kinds of entry, kept differently on purpose:
- Rules. How you want things done. A rule is applied to every task, which is why a wrong one matters.
- Facts. Something true about you or your work, recalled only when it is relevant to what you are doing.
Studied knowledge sits alongside them: when you ask Dropstone to read a page, a paper, or a reference and keep what it learned, it is stored the same way. See How Dropstone remembers you.
You
See it. Ask Dropstone "what do you remember about me?" and it lists everything, or open /memory in the CLI, which shows the rules first, labelled as applying to every task, then the facts.
Delete it. In that CLI list, press x on the entry. Or ask Dropstone to forget something and it will find the entry and remove it. If the server refuses, the CLI says so rather than pretending: "Could not forget that one. It is still being applied." See Change or forget a memory.
Share it. A memory starts private to you. Only its author can share it with a team or with the whole organization, from the session where it was written. Nobody can share yours on your behalf.
Dropstone
The agent records as it works: when you correct it, reject an approach, or state a preference, it saves that. When it meets the same thing again it merges the repeat rather than storing a second copy.
It never forgets anything on its own. Its instruction is explicit: forget only when the person asks, never on its own judgement. Deletion is yours to ask for.
Your organization
If you shared a memory with your team or your organization, an administrator can withdraw it from the shared list. Withdrawing is not deleting: the entry returns to you privately, and you can share it again. A memory you kept private cannot be withdrawn, read, or listed by anyone else in the organization.
Dropstone staff
There is no route into your memory from Dropstone's side. It is not part of support access, and it is not part of the organization's data controls: content logging covers conversations, not memory. See How an organization manages its data.
How it is found again
Rules are applied to every task, without being searched for. Facts are found by meaning rather than by keyword, so "the client with the Tuesday deadline" can recall a fact you wrote as "Acme ships on Tuesdays".
Related articles
- How Dropstone remembers youDropstone keeps a persistent memory that follows your account across chat, the CLI, and the SDK. Correct it once and it should not need correcting again, anywhere you use it.
- 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.
- 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.
- How an organization manages its dataThe three settings an owner controls for an organization, what each one stores, who can read it, and the limits of the strongest setting. Content logging, product telemetry, and retention, in one place.
- Export and delete your dataHow to get a copy of everything Dropstone holds for you, and how to remove it. Conversation export, memory, project files, CLI history, and account deletion, in one place.