Privacy Policy

Direct and Setapp Editions

Data processed on your Mac

Vibe Island processes data locally on your Mac. Specifically:

• Hook events — Status updates from Claude Code, Codex, Gemini CLI, and other supported AI coding tools are received via a local Unix socket and processed entirely on-device.
• JSONL session files — Read locally to display session titles and conversation context. We do not upload, transmit, or store these files on any server.
• Terminal metadata — Terminal app name, TTY path, and window identifiers are used for precise terminal jump functionality. Only the terminal app name, as a category, is included in the analytics described below.
• License key (direct edition) — Your license key and activation instance ID are stored locally. When you activate or validate your license, they are sent to our license server (see Data Storage & Security), together with your computer name, hardware model, a hashed hardware identifier, and the app version, and are checked with our payment provider.

We do not collect or store your code, prompts, AI responses, or any conversation content, and the app does not transmit them to us. Optional push notifications that you turn on yourself are described under Third-Party Services.

In-app analytics and crash reports

These editions send usage analytics and crash reports so we can fix bugs and decide what to improve. Both are on by default, and you can turn them off at any time.

• Usage analytics (PostHog, United States) — App launches and exits, a periodic heartbeat, and aggregate feature-usage counts (for example how often you expand the panel, approve a request, or jump to a terminal). Which AI tools, models, and terminals you use, as category names and counts. Onboarding progress and macOS permission outcomes. Your app settings. Device details: Mac model, macOS version, display setup (such as whether it has a notch), app version, system language, region, time zone, and currency setting.
• Crash reports (Sentry, United States) — Crashes, app hangs, and abnormal terminations, with stack traces, Mac model, macOS version, and app version. A report can include the location where Vibe Island itself is installed.
• Identifier — Both are tied to a random identifier generated the first time you run the app. It is stored on your Mac and kept when you reinstall the app. It is not your name, email address, or account.
• Direct edition activation — Activation events can additionally include the email address from your purchase and license identifiers, so that we can match activations to orders.
• IP address — As with any internet request, these services receive your IP address and may derive an approximate country from it.
• What is not sent — Analytics and crash reports do not include the contents or paths of your files or projects, project names, session titles, prompts, or AI responses.
• Turn it off — In Settings > About, switch off Help Improve Vibe Island. This turns off both analytics and crash reports. One last event records that you opted out. Analytics stop immediately, and crash reporting is fully off from the next launch.

How we use this data

• License validation — to verify your purchase and manage device activations
• Device management — your Mac's computer name and hardware model are sent during license activation and validation, so you can recognize your devices in the in-app device list and free up seats
• Product analytics — to understand which features are used and to improve the app
• Crash reporting — to identify and fix bugs

Purchases

If you buy Vibe Island on vibeisland.app, your payment is processed by Lemon Squeezy, which acts as our merchant of record, under its own privacy policy. License keys, license activation, and device management apply to the direct edition.

Third-party services

Services the app contacts directly

• AI provider usage APIs — To show your usage and limits, Vibe Island can call the official usage or billing API of the AI services you use (for example Anthropic, Cursor, Grok, Kimi, MiniMax, and Z.ai), with credentials that those tools already store on your Mac. These requests go from your Mac straight to the provider. The credentials and the responses are not sent to us.
• Public price tables — To estimate costs, the app downloads public model price lists (from models.dev and the LiteLLM project on GitHub). These are plain downloads that include no usage or account information.
• Push notifications (Bark) — Off by default. If you turn it on, notifications are sent over HTTPS to the Bark server you configure (api.day.app unless you change it), not to us. A notification names the agent and project and tells you to return to your Mac. If you also turn on detailed content, it can include the session title and a preview of the request, question, or result. You can turn on encryption for the payload.
• Our public content — The app can fetch release notes, community information, and, if you use SSH remote features, a deployment policy from our servers. These requests can include the app version and carry no account information.

Data storage and security

Your session data, hook events, and settings are stored locally on your Mac. We operate a backend on Cloudflare (a Cloudflare Worker and database). For the direct edition it handles license validation, trials, and purchase records, which can include your purchase email, order details, license key, and activation records. It also serves public read-only data to the app, such as Codex usage-reset notices; those requests carry no account information. Requests from the app to our servers use HTTPS.