Product security overview
Security and Privacy
Vera is built as a local-first AI project workspace. This page explains the practical security model behind Vera: where project files live, when data can leave your machine, and how user-controlled actions work.
Local-first project workspace
Vera is designed for desktop work on macOS and Windows. Your project files, generated artifacts, conversations, and task history live in the local Vera workspace unless you explicitly use a feature that needs a cloud model, browser service, payment service, or other integration.
User-directed file and command access
Vera can read files, edit files, and run commands so AI work can land directly in your project instead of staying in a chat box. Sensitive operations are tied to user intent and confirmation boundaries, so you stay in control of what the agents are allowed to touch.
Cloud and model-provider boundaries
When you ask Vera to use an AI model or cloud-backed capability, only the content needed for that request is sent to Vera-operated services or the relevant model/provider integration. Vera's privacy policy explains these processing paths in legal detail.
Browser control is explicit
The Vera Chrome extension connects Chrome to the desktop app through native messaging. Browser page access is used for workflows you ask Vera to perform, not as a background browsing-history collector.
Account and billing protection
Website accounts, subscription status, and checkout records are handled separately from your local project workspace. Vera does not store full payment card numbers.
Questions or reports
For security, privacy, or account questions, contact help@veracat.work.