This policy explains how Shannon Labs, Inc. (“we” or “us”) handles information when you use Codewhale, a Shannon Labs product.
Information we collect
We collect the identity information needed to create and protect your account, including your GitHub identity, display name, and a primary verified email when GitHub makes one available. We also store product information you create, such as preferences, projects, conversations, Work runs, approvals, usage totals, purchased-balance and payment receipts, and security or operational receipts. Codewhale does not store full payment-card details.
How we use it
We use this information to authenticate you, operate and secure Codewhale, preserve your requested product state, provide support, and—only when you have enabled the relevant communication—send product or waitlist updates. We do not sell personal information.
Storage and processing
Codewhale is one global product. There is no residency selector, no region-specific account, and no promise that your account data stays in a particular jurisdiction. Account authentication and session state is stored in Cloudflare Durable Objects, today configured in Cloudflare’s US jurisdiction; that placement is an operational choice we may change, and we will update this policy when we do. Durable product state is owned by Codewhale’s private product runtime. Cloudflare may perform TLS, request routing, and cryptographic processing on its global edge, so we do not describe edge processing as US-only. Hosted compute is a separate system from account storage and, when enabled, identifies its placement before launch.
Service providers
We use these service providers to run Codewhale. Each processes information only as needed to provide its service to us.
Stripe processes payments, calculates sales tax, and handles receipts, refunds and payment disputes when you make a purchase.
Vercel AI Gateway routes the Codewhale-managed AI requests paid for from your AI balance, and DeepInfra, the model provider it uses today, serves the model and processes each request. Any other managed route uses the provider or gateway the product identifies, as described below.
Cloudflare hosts the Codewhale web app and API, routes and secures requests, and stores account authentication and session state.
Supabase provides sign-in and the database that holds your account and product records.
PostHog may receive the anonymous usage totals described under Settings, Usage data, and only while that setting is on: whole-number counts and a random install identifier that is not tied to your account, never your content.
Resend delivers email we send you.
Services you connect yourself, such as GitHub or your own model provider, handle information under their own terms.
Payments
When you buy a pack, you pay on a checkout page hosted by Stripe. Your card details go to Stripe and never reach Codewhale’s servers. To open checkout we give Stripe your account identifier and, when we have it, your email address; Stripe collects the billing details it needs to take the payment and calculate tax. We keep a record of each purchase: Stripe’s identifiers for you and for the payment, what you bought, the amounts charged (price, Platform fee and tax), the payment’s status, and any refund or dispute. We use these records to grant and account for your balance, answer your questions, prevent fraud, and meet tax and accounting duties, and we keep them as long as those duties require, including after account deletion. Stripe also uses payment information under its own privacy policy, including to prevent fraud.
Model providers and repositories
When you use bring-your-own-key inference, Codewhale sends the content needed for the request to the provider you connect, under your provider agreement. When you use managed inference, Codewhale sends the required prompt, context, tool results, and response data through the model provider or gateway identified by the product. Managed operator credentials remain inside Codewhale's trusted broker and are not exposed to you or to a provider sandbox. Provider retention, training, and regional processing are governed by the selected provider's terms and disclosed controls. Repository access is limited to the grants you approve with the source provider.
On-demand execution providers
When a managed run starts a cloud sandbox, Codewhale sends the repository content, instructions, environment values, and session data needed for that work to the execution provider and region identified before launch. The sandbox is ephemeral capacity acquired for that run and released afterward. Computer Use, when available, provides interactive control inside the live sandbox. Durable account, Agent, task, repository binding, artifact, and explicitly retained workspace state is stored separately. Provider-backed resources are not treated as deleted until the provider confirms deletion.
Retention and deletion
You can review export and deletion controls after signing in under Account, Data & privacy. Content is deleted according to the displayed retention and deletion process. Privacy-minimal security, audit, deletion, and financial receipts may be retained when necessary to prove an action, prevent abuse, or meet legal obligations. Provider-backed resources are not treated as deleted until the provider confirms deletion.
Questions and requests
Use Account, Data & privacy after signing in to request an export or deletion. For anything else, or if you cannot sign in, email help@codewhale.net.
Changes
This version replaces the policy effective August 21, 2026. It adds who we are, the service providers we use, how payments are handled, and how to contact us. We may update this policy as the product and its processors change. The effective date above identifies the version that applies.
Usage counting
Codewhale counts product usage by default, on this website and in the program. On this website that means page views, documentation views, install-command copies, sign-in link clicks and error pages shown, visits to the home, install, quickstart and contribution pages, clicks on links to Codewhale’s GitHub stars, issues, help-wanted work and contributing guide, documentation searches, searches with no result, selected search results, and your own confirmations that you installed Codewhale or checked a quickstart answer. Counts are added up in this browser and sent to Codewhale’s own counting service in one batch after a short delay or when you leave the page. Each batch is keyed on a random install id that the site stores in this browser and replaces every 90 days; it is not derived from you or your device, but it does tie together the counts sent from this browser while it lasts, so they are not anonymous totals. A batch also carries the site’s version number and the time it was sent. No page address, search text, referrer, account or work content is stored, and website batches are not forwarded to PostHog or any other analytics processor. The counting service stores no IP address, although the site’s host receives each request as it does for every page. When your browser sends Global Privacy Control or Do Not Track, the site counts nothing, creates and reads no install id, sends nothing, and clears counts and an install id saved by an earlier visit. You can also turn counting off for this browser on this page. In the Codewhale program, usage reporting is on by default and sends a closed set of counts, such as version, platform, session length and outcome, and feature, error, model and tool counts, and never conversations, code, prompts, files, repository or branch names, model content or credentials; codewhale config set telemetry false turns it off, and CODEWHALE_TELEMETRY=0 turns it off for a single run. The installer sends no usage report. An explicit opt-out is never silently reversed, and presenting this notice does not record acceptance on your behalf.
Usage counting on this site
This site counts page views, documentation views, install-command copies, sign-in link clicks and error pages shown, along with visits to the home, install, quickstart and contribution pages, clicks on links to Codewhale’s GitHub stars, issues, help-wanted work and contributing guide, documentation searches, searches with no result, selected search results, and your own confirmations that you installed Codewhale or checked a quickstart answer. Each batch of counts is keyed on a random install id that this site stores in this browser and replaces every 90 days. The id is not derived from you or your device, but it does tie together the counts sent from this browser while it lasts, so these are not anonymous totals. A batch also carries the site’s version number and the time it was sent. No page address, search text, referrer, account or content is stored, and the batch goes only to Codewhale’s own counting service. Counts are not unique visitors, and your confirmations are self-reports, not proof that an installation or a task succeeded.
This site counts nothing, and creates and reads no install id, while your browser sends Global Privacy Control or Do Not Track; it also clears any counts and install id that an earlier visit saved. You can turn counting off for this browser below. That choice is kept in this browser, clears any queued counts and the install id, and is never silently reversed. Nothing here records that you accepted anything.
In the Codewhale program, usage reporting is on by default. In the app, use Settings → Usage data. In the terminal, run codewhale config set telemetry false to turn it off, or set CODEWHALE_TELEMETRY=0 to turn it off for a single run. The installer itself sends no usage report.