Privacy Policy

Effective date and last updated: 8 September 2026. Privacy contact: support@vibecommand.eu.

This policy covers VibeCommand for iPhone, iPad and Mac, its companion service on your Mac, and this support website.

Your Mac and your work

VibeCommand connects your Apple device to a Mac that you choose and control. Operational traffic goes to that Mac. There is no VibeCommand-operated cloud relay for your projects, chat or LIVE stream, and you do not create a VibeCommand account to use the app.

Coding agents run on the Mac, using the agent's installed account and configuration. Project tasks work in the original selected folder. Mac Assistant can work from your Mac home folder and access other locations according to the installed agent's permissions and your instructions.

Information used by the app

• Connection details, a random client identifier, device name and pairing information are used to connect and authorize your devices.
• Project names, paths, commands, status, process information and diagnostics are used to operate your Mac projects.
• Your prompts, answers, approvals, agent output, terminal history and selected file previews are used to carry out and display your work.
• Images you explicitly select can be used as attachments or project icons. The app does not automatically read your photo library or clipboard.
• LIVE uses traffic from your development server, or Simulator frames and your touch, gesture and keyboard input.
• Skill searches and agent discovery can use search terms, source metadata and installation records.
• If enabled, notifications use a device push token and run status to notify you about an agent's progress or an approval request.

The camera is used to read a pairing QR code. The pairing information is used to contact your Mac; it is not sent to the developer as a camera image. Clipboard content is written through explicit Copy actions.

Where information goes

The paired client and Mac exchange information directly. Tailscale can provide the private connection when you install and configure it separately. Tailscale processes information under its own terms; VibeCommand does not receive your Tailscale password.

Actions on your Mac may send prompts, files, images and other context to the coding agent or services you choose, including OpenAI/Codex, Anthropic/Claude Code, other installed agents, GitHub, Git remotes, package registries and services used by your projects. These services have their own accounts, privacy policies and retention settings. Review the selected provider before sending confidential or personal information.

Optional push notifications travel from your Mac through Apple Push Notification service when configured. Apple receives the device push token and notification payload. The payload can include a project name, project/chat/run identifiers, selected agent metadata and a brief status, but does not include the prompt, agent reply, source files or file paths. You can turn notifications off in system settings.

A web project opened in LIVE can load its own external content and run its own scripts. Its data practices are controlled by that project. VibeCommand does not add advertising or analytics to your preview.

Storage and retention

The app keeps its Mac credential in the device Keychain without synchronizing it through iCloud Keychain. Connection preferences remain in the app container. Bounded chat and active-run records use protected local files. File previews and LIVE exports use temporary storage excluded from backup. App-created web previews use a nonpersistent WebKit data store.

The Mac companion can retain project configuration, chat and run history, logs, uploads, icons, skill records, recovery copies and process information in its support directories. The paired-device registry stores credential digests rather than the original device secrets. Push registration information is stored separately on the Mac. Project files stay in your chosen workspaces. Installed agents retain their own records under their own settings.

Simulator frames and input are used for the live session rather than recorded as a video archive by VibeCommand. Explicit screenshots, exported files, build outputs, system logs or separate tools may create their own copies.

There is no single automatic deletion period for all content on your Mac. Some histories are bounded, while other records remain until you use the relevant removal control. Your device or Mac backups may also retain earlier copies under your backup settings.

Archive, deletion and access choices

Archive keeps a chat in the restorable Archived list. Delete requires confirmation and permanently removes the selected chat and its VibeCommand conversation and terminal history. This does not delete project files or the agent CLI's separate history. Other clients reconcile with the Mac when they reconnect; an offline client may retain cached content until then.

Privacy & Security offers separate confirmed controls for eligible device conversations, completed Mac run content, attachment uploads, backend logs, reviewed skill recovery copies and prior-session LIVE temporary files. Each control explains its scope. Stop and Stop All end owned runtime activity; they are not data-deletion controls.

You can disconnect, change your endpoint, revoke a paired device on the Mac or pair again. You can withdraw camera, local-network or notification permission in system settings. Provider-held data must be managed with that provider. Uninstalling the client does not delete projects or provider history on your Mac, and operating-system-managed Keychain records may survive uninstalling.

Support requests and this website

If you contact support, the developer receives the sender details, message and attachments you choose to send. These are used to answer the request, investigate the reported issue and keep necessary correspondence. They remain in the support mailbox while needed for that purpose or applicable record-keeping obligations. Do not include credentials or private source code. You can request access, correction or deletion through support@vibecommand.eu.

This website does not offer an account, upload form, advertising or an analytics integration added by VibeCommand. The website is hosted by Vercel. Vercel and network providers process connection data, such as IP address and request information, to deliver and protect the pages under their own service records and retention rules. Support email is handled through Apple iCloud Mail. Website hosting does not carry your app's Mac connection, agent conversation or LIVE stream.

Cookies and website traffic

The public website does not set analytics or advertising cookies, request GPS access, or use a separate visitor-tracking script. When you close the cookie information panel, we save one local preference in your browser so it stays closed across pages, reloads and future visits in that browser. This preference contains no visitor identifier or browsing history and is not sent to our server. It remains until you clear this website’s browser data. You can reopen the panel at any time using Cookie information in the footer. If browser storage is unavailable, the information remains available from the footer.

We may review aggregate request totals and approximate countries in the hosting provider’s traffic dashboard. These are server request statistics, not a count of uniquely identified people, and may include bots and requests for page assets. Approximate country information comes from the network connection, not your device’s precise location. Vercel still processes technical connection records to operate and secure its hosting, as described above; this is not a promise that the hosting provider stores no data.

Security, tracking and your rights

Requests to your Mac require authentication. Public or unknown cleartext endpoints are blocked. The optional direct private-LAN compatibility mode requires explicit consent because that mode does not add VibeCommand transport encryption. Protect your devices, accounts and pairing codes. No system can guarantee complete security.

VibeCommand has no advertising SDK or cross-app tracking SDK and does not sell your personal information. It does not automatically upload your project history or diagnostic logs to the developer. The developer may receive information that you deliberately send for support and platform-provided reports under your Apple sharing settings.

Where applicable law grants these rights, you may request access, correction, deletion, restriction or portability of personal data held by the developer, object to processing, withdraw consent, or complain to your local data protection authority. Processing of support correspondence serves the legitimate interest of responding to your request and maintaining the app; legal obligations may require limited retention. Services you choose may process information outside your country under their own privacy and transfer arrangements.

The developer cannot remotely access or erase data held only on your devices, Mac, backups or third-party accounts. Contact support@vibecommand.eu for help locating the relevant controls or for requests concerning information you supplied to the developer.

Children and policy changes

VibeCommand is a developer tool and is not directed to children. If you believe a child has supplied personal information to the developer, contact support@vibecommand.eu.

Changes to this policy will be published here with an updated effective date. See Support for contact and troubleshooting information.