Privacy Policy

Repositories, working trees, terminals, local agent processes, workspace state, and most product configuration are intended to remain on the user's computer.

Remote access features, tunnels, messaging channels, model providers, and shared preview links can move data outside the machine when the user configures them. Those surfaces should be treated as privileged integrations.

The public website provides documentation, release links, static assets, redirects, and machine-readable release metadata. Downloads are distributed through GitHub Releases.

Hosting providers, GitHub, browsers, and network intermediaries may process standard request metadata such as IP address, user agent, URL, referrer, and timestamps according to their own systems and policies.

When an agent sends prompts, tool results, files, images, or code context to a configured model provider, that traffic is governed by the selected agent, provider, API endpoint, and account settings.

Provider profiles and API Bridge routes make routing explicit, but they do not remove the need to review each provider's privacy policy, retention behavior, regional routing, and acceptable use terms.

Messaging channels, browser pairing, Web Terminal, handover links, tunnel-backed access, and preview shares can expose local sessions or outputs to other devices or services.

Use private channels first, scope preview links, rotate exposed tokens, and disable integrations that are no longer needed.

For privacy questions about VibeAround, open an issue in the public GitHub repository and avoid posting secrets, tokens, private repository content, or personal data in the issue body.