Privacy Mode, explained
Octavo Team · 4 min read

Octavo works by sending code to language models. The agent needs your code to plan and edit it. Tab needs the lines around your cursor to predict the next edit. Inline edit needs the selection you want changed. Any team that adopts Octavo should know where that code goes and who keeps it.
Privacy Mode sets the rule. With Privacy Mode on, Octavo never stores your code, and neither Octavo nor model providers train on it. Every organization has it on by default, and admins control it for all members.
This post explains what the setting covers, what Octavo still stores, how the codebase index works without keeping your code, and how admins enforce Privacy Mode across an organization.
What happens to a request
Take a single agent request. The editor collects the context the agent needs: your prompt, the files it reads and the output of the commands it runs. It sends that context to Octavo over TLS 1.2 or later. Octavo passes it to the model you chose, or the one Auto picked, and streams the response back to you.
With Privacy Mode on, Octavo holds that code only while the request runs. It is not written to a database, a log or a training set. The same rule applies to Tab and inline edit requests, and to requests served by Octavo’s own models.
Zero data retention with model providers
Frontier models run on their providers’ infrastructure, so Octavo’s own policy covers only part of the path. The rest is covered by contract. Octavo has zero-data-retention agreements with the model providers it works with.
Under those agreements, a provider processes a Privacy Mode request, returns the response and keeps neither the request nor the response. The provider does not train on the code it receives. The guarantee therefore holds for the whole path, from your editor to the model and back.
What Octavo stores
Privacy Mode covers your code. To run your organization’s account, Octavo still keeps these records:
- member accounts and the organization’s billing details
- usage data, which powers usage analytics and spend limits
- your settings, and the team rules an admin syncs from the dashboard
- audit logs, on Enterprise
- embeddings and obfuscated file paths for the codebase index
Octavo encrypts all of it at rest with AES-256.
How the codebase index works
The index lets the agent and search find code by meaning across the whole repository, monorepos included. Ask where failed webhooks are retried, and the index finds the function that schedules the next attempt, even if that function never uses the word “retry.”
To build the index, Octavo splits each file into chunks and computes an embedding for each chunk. An embedding is a list of numbers that places code with similar meaning close together. Octavo stores the embedding with an obfuscated path for its file and discards the chunk. The index never holds plain-text code, and the obfuscated paths keep file and folder names unreadable in storage.
When the agent searches, Octavo compares the embedding of the query with the stored ones and returns the closest matches as locations. The editor resolves each location to a file in your local copy of the repository and reads the lines from disk.
You decide what enters the index. Files matched by .gitignore or .octavoignore are left out. Add a path to .octavoignore to exclude a file you track in git, such as test fixtures that hold sample customer records.
Enforcing Privacy Mode across a team
Privacy Mode is on for the whole organization by default. The admin dashboard shows it as enforced, and it applies to the requests of every member.
Enterprise adds controls over where code can go and who can send it:
- Model and MCP allowlists limit members to the models and MCP servers your organization approves.
- Data residency keeps your data in the US or the EU.
- Self-hosted cloud agents run in your own VPC, so the VMs that hold your repository stay inside your network.
- SCIM provisioning adds and removes members as your identity provider changes. Single sign-on with SAML or OIDC comes with both plans. The rollout page covers setting up both.
- Audit logs record who changed which setting and when.
The security section of the Enterprise page lists the full set of controls.
Questions
Write to privacy@octavo.me with questions about how Octavo handles your data, or to security@octavo.me to report a security issue. The Privacy Policy covers the legal detail.


