Privacy policy

Effective November 4, 2026

Crabigator connects your phone, tablet, and browser to coding assistants running on your computers. When you stream a session, its terminal content and project details pass through our service so your paired devices can display them. Only stream content you intend to make available to your account.

This policy covers the official Crabigator service at drinkcrabigator.com and the Crabigator iOS, Android, and desktop apps. Crabigator is operated by Samuel Clay. A self-hosted server is controlled by its operator and may have a different privacy policy.

Information we handle

• Account and device information. Pairing identifiers, device names, authentication tokens, and connected computers let us authorize access. If you connect Google or GitHub, we receive account identifiers and profile information such as your name and email address. We do not receive your Google or GitHub password.
• Session content. Streaming can include terminal screens, conversation history, prompts and replies, session titles, recaps, repository names, file paths, code changes, commit and pull request details, and activity statistics. This content can include private information that appears in your terminal. We store session information and history to provide live viewing, reconnection, search, and the PR board.
• Voice input. When you choose to transcribe a recording, audio goes through our server to OpenAI's transcription API. The transcription returns to the app and is sent to your session when you choose Send. We save each transcription in your account's voice transcript history so you can copy it later, and you can delete entries there. We do not keep the audio: the apps delete a recording once it is transcribed or cancelled. The transcription may also remain in your session history. OpenAI processes the audio under its own service terms and retention practices.
• Notifications. We store push tokens and notification preferences. Apple's Push Notification service and Google's Firebase Cloud Messaging deliver notifications. Delivery records help diagnose failures. Notifications can identify a session; the app fetches its current question or permission request using your paired credentials.
• Purchases and support. If you buy a service plan, payment providers such as Stripe or PayPal process payment information. We receive subscription and transaction records to manage access and billing. We also receive information you send in support requests or mailing-list signups.
• Website and service activity. We use website visitor and session identifiers, page visits, referral and campaign information, interactions, browser and device information, and approximate location derived from a network request. Infrastructure providers also process IP addresses and technical logs to deliver and protect the service.

How we use and share information

We use this information to operate and secure Crabigator, synchronize your paired devices, deliver notifications, process your requests, manage subscriptions, respond to support requests, and understand usage and reliability.

Cloudflare hosts the official service and its storage. Other providers process the information needed for the features described above. Your chosen coding assistant and any integrations you connect also receive the prompts or actions you send to them. Their policies govern that processing. Optional desktop recaps send relevant transcript excerpts to the configured recap provider.

The marketing website uses first-party analytics and a Meta pixel for advertising measurement. Meta may receive page visits, browser information, identifiers, and interactions and associate them with information it holds. This website tracking is separate from the native mobile apps, which do not embed the Meta pixel. Browser privacy controls and content blockers can limit website tracking.

We may disclose information when required by law, to address fraud or security incidents, or to protect the service and its users. If ownership of the service changes, information may transfer as part of that change.

Your choices and deletion requests

You choose which desktop sessions to stream. You can stop a session, unpair a device, disable notifications, deny microphone access, or use a compatible self-hosted server. Unpairing ends that device's access; it does not by itself delete account records or session history. The local sample-session demo requires no pairing and does not send demo messages to a server.

For access, correction, or deletion of your Crabigator account and associated information, email crabigator@conesus.com with the subject “Crabigator privacy request.” Tell us which account or paired device is involved, but do not send passwords or pairing tokens. We may ask you to verify ownership. Deletion requests cover account identities, device associations, and associated session content; records needed for legal obligations, billing, security, or resolving disputes may be retained. Deleting Crabigator data does not delete copies held by your coding-assistant provider, other integrations, or your own computers.

Retention and security

Retention depends on the type of data and feature. Account and device records support ongoing access; session history supports viewing and search; usage, payment, and security records support operations and legal obligations. We do not promise that all records disappear when a session ends. Contact us to request deletion of information you no longer want us to retain.

Connections to the official service use HTTPS. Mobile pairing credentials use iOS Keychain or Android Keystore-backed storage. Cloud streaming is not end-to-end encrypted: the service processes session content to provide its features. Protect your devices and pairing codes, since access to a paired account can allow input to your desktop sessions.

International processing and children

Crabigator and its providers may process information in the United States and other countries. Crabigator is a developer tool and is not directed to children under 13. Contact us if you believe a child has provided personal information.

Changes and contact

We will update this page when our practices change and revise the effective date. For privacy questions or app support, contact crabigator@conesus.com.