Privacy Policy

• Your email address: when you buy something, sign in, or request our free worksheet. We use it to link your purchase to your account and send you your receipt, your download link, and setup instructions. If you join our list, we occasionally send product news; every email has an unsubscribe link and one click means we stop.
• Payment details: handled entirely by Stripe, our payment processor. We receive your email and what you bought; we never see or store your card number.
• Your setup and Pro conversations: messages and screenshots you send to Virgil on the website, during guided setup or in a Pro project, plus the project specs and plans those conversations produce. We store them so you can close the tab and pick up where you left off. They are processed by Anthropic's Claude API to generate Virgil's replies.
• Basic usage events: things like "a checkout was opened" or "a step was completed," so we can see where people get stuck and improve the product. This is our own simple logging, not third-party ad tracking.
• Error reports: when something in our software breaks, a technical error report may be sent to Sentry, our error monitoring service, so we can fix it. These are about the failure, not about your files.

Virgil works differently from the website, and the difference is the point. Your projects, their workspaces, and every file in them live on your own computer. We do not have a copy. There is no Virgil server holding your project files.

• Files you drag into a project are copied into that project's workspace folder on your machine.
• Folders you grant access to stay where they are; the grant is scoped to that one project and you can revoke it at any time.
• Virgil can only see what you added or granted. There is no pathway to the rest of your computer.

When the app does AI work, the material you shared with that project is sent to an AI model to do the work. Where it goes depends on which engine you run, and that is the next section.

On your own key (the default), Virgil connects directly to your own account with your AI provider, such as Anthropic or OpenAI. Your content travels from your computer to your provider under your agreement with them. It does not pass through our servers. We are not in the path, so there is nothing for us to store, log, or lose.

On Virgil Engine, requests are routed through our account with OpenRouter to the model best suited to the task. That is a different posture, and here is exactly what it means: our routing configuration does not log your prompts or outputs, we have opted out of any option that would grant usage rights over your content, routing is restricted to providers that do not train on your data, and we route to zero-data-retention endpoints where the provider supports them. Some providers may retain content briefly for abuse monitoring under their own policies. If privacy is your top priority, use your own key; it is also cheaper.

Either way, we never train AI models on your content, and neither arrangement allows anyone to train on it.

You can connect outside accounts, such as Google Workspace or Microsoft 365, to a single project inside the Virgil desktop app. Connections are scoped to that one project, and you can disconnect at any time from the project's Integrations panel or from your account settings with that provider.

When you connect a Google account, Virgil may, with your consent, read your calendar events to prepare schedule-aware work, save files the app creates to your Drive and reopen files you opened through the app, and read your email to summarize correspondence and prepare draft replies for your review. Drafts are never sent by Virgil; sending is always your action. Sign-in tokens are stored encrypted on your device, the data Virgil reads is processed on your device and by the AI engine you configured, and none of it is stored on our servers.

Virgil's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We never transfer Google user data to third parties except as needed to provide the features you asked for, never use it for advertising, and never allow humans to read it unless you ask us to for support, it is required for security or legal reasons, or it is aggregated and anonymized.

• We never sell or rent your data to anyone.
• We don't run third-party advertising trackers.
• We never browse your computer. Virgil sees only what you drag into a project or explicitly grant it access to.
• We never train AI models on your content.
• We never spam you. Beyond emails about your purchase and setup, we occasionally send product news and offers we think are genuinely useful. Every one of those has an unsubscribe link, and one click means we stop.

During setup, Virgil may ask you to paste a screenshot of your screen so it can see what went wrong. Screenshots you share are stored with your conversation and sent to the AI provider for processing. Avoid including anything sensitive in them. Crop out passwords or personal information before sharing.

Only the services that make the product work: Stripe (payments), Supabase (our database and sign-in), Anthropic (the AI that powers Virgil's chat on the website), OpenRouter (model routing, only if you use Virgil Engine), Resend (email), Sentry (error monitoring), and Vercel (our hosting). Each receives only what it needs to do its job.

We use cookies and browser local storage for sign-in and to remember your setup progress on your own device. No advertising cookies.

Want a copy of your data, or want it deleted? Email hello@hirevirgil.com from the address you purchased with and we will take care of it. Deleting your account data does not affect any pack files you have already downloaded or projects on your own machine. Those are yours.

If we change this policy, we will update the date at the top. If a change meaningfully affects how we handle your data, we will tell you by email.