Your data and privacy
This page explains where Otto keeps your data, what leaves your computer and to whom, and how to delete it.
The short version: in the desktop app and a source install, everything Otto stores stays on your computer. Requests go to the model provider and apps you choose. The Otto team at n8n receives none of your data unless you send feedback or opt in to usage analytics.
Where your data lives
Section titled “Where your data lives”| Desktop app | From source | Hosted | |
|---|---|---|---|
| Otto server | Your computer | Your computer | The operator's infrastructure |
| Database, workspace, browser | A private virtual machine on your computer | Docker containers on your computer | A separate runtime and storage per user |
| Data folder | ~/Library/Application Support/Otto/ and ~/.otto-desktop/ on a Mac. %APPDATA%\Otto\ and the Otto- WSL distribution on Windows |
.local/ (OTTO_DATA_ROOT) and Docker volumes |
The operator's database and storage |
| Who can read it | You | You | You, and the operator, who holds the keys |
For what Otto stores and how long it keeps it, see the Security review guide.
What leaves your computer
Section titled “What leaves your computer”flowchart LR otto[Otto on your computer]:::accent otto -- prompts and results --> model[Model provider] otto -- app actions --> apps[Composio and<br/>your apps] otto -- your chats --> chat[Telegram, WhatsApp] otto -- browsing --> web[Websites] otto -. only if you choose .-> n8n[n8n]:::muted
| Goes to | What |
|---|---|
| The model provider you choose | Your conversation, tool results and screenshots. With Gmail connected, also recent email Otto reads to suggest first tasks and learn your writing style |
| Apps and services you connect | The actions Otto runs in them |
| Composio, if you connect apps through it | Those app connections and the actions Otto sends |
| Telegram and WhatsApp, if you set them up | The messages in those chats |
| Websites Otto visits | Whatever Otto browses, fills in or submits there |
| n8n | Feedback you send, and masked usage analytics if you opt in |
Provider keys, such as your model and Composio keys, stay in the Otto server. They never enter a prompt, Otto's workspace or its browser.
Usage analytics
Section titled “Usage analytics”Usage analytics are off until you turn on Share usage data in onboarding or in Settings. They record which screens you open, how you move through them, and product events such as a task starting or a setting changing.
Analytics never include your messages, anything you type, Vault values, sign-in or model-key forms, the remote browser view, images, real page addresses, names or email addresses. See Analytics for the full list and the switch that turns them off for a whole installation.
Feedback
Section titled “Feedback”Feedback you send goes to the Otto team at n8n. By default it includes a diagnostic report of your recent chat, actions and their results. Select Review to read the report first, or untick Include diagnostic report to leave it out. Otto removes known secret values from the report before you see it.
What memory learns from
Section titled “What memory learns from”Otto learns only from your own short messages, never from its replies, tool results or web pages. When you connect Gmail, your model also reads your recent sent email and writes one short note on your writing style. The model is told to leave out facts, names and quotes, and Otto drops a note with an email address or link. See Memory.
Delete your data
Section titled “Delete your data”- Memories. Open Settings → Memory, select a note and choose Forget. This deletes the note and its earlier versions. You can also ask Otto to forget something.
- Vault items. Open the item in Vault → Saved and delete it. For a saved browser session, select Sign out.
- Apps. Disconnect an app in Apps.
- Everything. Quit Otto and delete its data folders from the table above. Uninstalling the app alone keeps your data. In hosted mode, ask your operator.
Where this is enforced
Section titled “Where this is enforced”src/server/memory-learning.ts (memory sources) · src/server/analytics.ts (analytics opt-in and events) · src/web/lib/analytics-privacy.ts (recording masks) · src/server/bug-report.ts (report redaction)