Effective July 28, 2026

Privacy starts local.

VibeSpace is designed as a local-first desktop workspace. Local-first does not mean that every optional connected feature stays on your device.

What stays local by default

Workspace content such as chats, settings, tasks, and project context is designed to live primarily on your device. Local providers can process supported workflows without sending prompts to a hosted AI provider.

You are responsible for device security, operating-system access, backups, and anyone else who can use your local account.

Data used for accounts and Access

Account data

A verified account identifier and service records may be used to start the access trial, prevent resets, scope entitlement, and protect account isolation.

Billing data

A payment processor handles checkout and payment details. VibeSpace may receive customer, subscription, payment-status, and event identifiers needed to reconcile Access. The public site does not collect card details.

Optional providers and cloud features

When you deliberately use a hosted AI, voice, calling, messaging, sync, or cloud feature, the content needed for that request may be sent to the selected provider. That provider processes it under its own terms and privacy policy. Bring-your-own-key providers may also bill you directly.

Review the selected provider, destination, and content before sending sensitive material. Do not assume that a local workspace makes an explicitly cloud-routed request local.

Your controls

For public bug reports, use the GitHub issue tracker, but do not post secrets or personal information. Public issues are not an account-support channel.

Scope of this summary

This page describes the intended public privacy boundary without claiming that no data ever leaves your device, that third parties retain nothing, or that a particular legal right applies in every location. Provider policies and the exact in-product disclosure at the time of use remain important.