Security and privacy
How Vörr handles access to your systems, and the boundaries around the data it reads.
Read-only access
Vörr requests read-only credentials and does not change your infrastructure, code or CI system. Scanning discovers and maps supported resources; it does not modify them.
Credential storage and scoping
Connection credentials are stored for the organization and masked in the interface once saved. Connections are scoped to workspaces, and results are shown in the account and workspace context they came from.
Repository indexing covers committed code only. Local, uncommitted work on a developer's machine is never read.
Consent and revocation
Adding Vörr to Claude or ChatGPT requires an explicit consent step tied to your user and organization. The authorization does not expose Vörr's stored cloud, Git or observability credentials to the AI assistant.
Removing the connector from the assistant revokes that access and changes nothing inside Vörr.
Training policy
The published training-policy statement is pending security-owner approval and is not reproduced here. Contact hello@frigga.cloud for the current wording.