Manage your data

How 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.

What Dropstone keeps from an image or document attached to a conversation, which formats keep the original file and which keep only their text, what happens in a temporary chat, in a shared conversation, and in an export.

The 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.

How an owner turns on full content logging for an organization, what the confirmation means, how to tell members, and how to turn it off again.

Who can read an organization's recorded conversations, how to search and filter them, what the archive never holds, and how to export it as JSONL.

Every request records the model, the tokens, the cache hits, the cost and the timing, on every account and whatever your training settings are. What that record holds, who can see it, and what it never holds.

On an organization account, never. On a personal account, only if you leave the setting on. What is collected, what is never collected, and what deletion can and cannot undo.

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 an organization teaches Dropstone stays, belongs to the organization, and is recalled by everyone it is shared with. It survives model changes, it can be exported in full, and it is never used to train Dropstone's models.

In a shared conversation the person who owns it can open the activity log and see who joined, who viewed, who sent what, who commented, what changed, and when. What it records, and what it does not.