History, export and privacy
What agents may do, how you undo changes and where your data lives.
Every change is a version
Whether you type or an agent writes: every change creates a new version of the note. In the history you see who (you or which agent), when and what changed, as a comparison with the previous version.
- Undo: Restoring an earlier version creates a new version. Nothing is ever lost.
- Agents are visible: Anything an agent wrote is marked in purple and carries the name of the connection.
- Roll back everything from one agent: In the history you can reset all changes from one connection since a point in time in one go.
What agents may do
- Permissions per connection: read only, or read and write. You can change or revoke them at any time.
- Targeted, not wholesale: Agents append text or replace single sections. Replacing a whole note only works if the agent knows the current version.
- No deleting: Nothing can be deleted via MCP. You can only delete in the app, and even then the note goes to the trash.
- Brake on mass changes: If a connection writes an unusual amount in a short time, it is stopped and you get an email.
Export
Your vault is plain Markdown with folders, frontmatter and [[wikilinks]]. The export is a zip you can open directly as an Obsidian vault. Reading and exporting always stay possible, even without a paid plan.
Where your data lives
- Database, sign-in and files: Supabase, Frankfurt data center
- Website and server functions: Vercel, Frankfurt region
- Emails: Plunk
What an agent reads, its provider sees too
When you connect an agent, its provider (for example Anthropic or OpenAI) processes the content the agent retrieves. Only connect agents you want to trust with that content, and if in doubt, give read access only.