Your work stays on your computer.
That is not a feature. It is the architecture.

Your projects, workspaces, and every file in them live on your own computer. There is no Virgil server holding your project files. There is no cloud sync you have to trust. When you close the app, your data is right where you left it: in a folder on your machine.

This is not an opt-in privacy mode. It is how the product works. There is no toggle because there is nothing to turn off.

Virgil connects directly to your own account with your AI provider. Your content travels from your computer to your provider under your agreement with them. It does not pass through our servers.

We never see your API keys. They are stored locally on your machine in your key vault, scoped to each project. If you switch providers or revoke a key, that is between you and your provider. We are not in the path.

Every project is a walled workspace. Virgil can only see what you added or granted access to inside that project. There is no pathway to the rest of your computer, your other projects, or anyone else's work.

Integrations attach to a project, not to your account. If you connect a service to one project, your other projects cannot see it. We call this custody: Virgil can only touch what you handed this project.

Every project logs whether an edit was made by you or by AI. This is not optional and cannot be turned off. When you hand a finished deliverable to a client, a boss, or a regulator, the record is there: who did what, and when.

Guest collaborators get the same treatment. If someone joins your project on a Guest Pass, their edits and their AI usage are logged separately from yours. Full attribution, no ambiguity.

We never train AI models on your content. When you use your own key, your provider's data policy applies and most major providers do not train on API traffic. When you use Virgil Engine, we route through zero-data-retention endpoints and have opted out of any option that would grant usage rights over your content.

Every tool in Virgil stores its state as a plain file in your workspace: board.json, doc.md, table.json, deck.json. There is no proprietary database. If you stop using Virgil tomorrow, your files are still yours, in standard formats, on your machine. Export to .docx, .xlsx, .pptx, or just open the raw files.