[Repeater22746]

Fair question.

ContextVault stores data at the workspace/org level, not only the individual user level. That is intentional. If someone leaves a team, their useful shared context should not disappear by default.

So deletion needs two paths: a user can remove their account/access without destroying shared workspace memories, while a workspace owner/admin can delete the workspace and its associated data through a clearly confirmed destructive flow.

Those account/data deletion controls are on the roadmap. I’m being careful with the design because the wrong version either preserves too much or lets one user accidentally delete knowledge other team members depend on.

I’m a solo founder in the US. I’m not interested in reading customer data; the product needs to earn trust through org scoping, minimal access, and clear deletion/privacy controls.