Access requests
The request form collects your work email, GitHub username or organization, team size, primary languages, and any coding-agent details or note you choose to provide. We use these details to assess fit, plan access, and follow up on your request. The form does not subscribe you to a newsletter.
Do not include source code, passwords, tokens, or sensitive personal information in the form.
Local analysis and accounts
Free CLI analysis runs locally without an account or source upload. Supported Pro agent hooks also evaluate code locally. Pro activation involves identity and signed access credentials; signing in does not itself authorize a source-code upload.
Where a paid subscription is enabled, Stripe handles checkout and payment details. Fettl receives the customer, subscription, invoice, tax, and entitlement records needed to operate access. Hard Mode Labs does not receive full payment-card numbers.
Managed repository scanning, hosted finding history, dashboards, and model-provider repair are outside the public MVP. This website does not offer those workflows.
Optional website analytics
When configured, Google Analytics 4 helps us understand visits to public pages, language-example interactions, video engagement, install interest, and successful access requests. The Google tag loads only after you allow analytics, either from the banner or in Cookie preferences. You can deny all optional analytics and still use the website.
Analytics events do not include form fields, email addresses, GitHub names, code, account identifiers, or checkout tokens. We send public page addresses without their query strings or fragments, referring-site origins, and campaign source, medium, or name when supplied as simple campaign labels. Google may derive browser, device, and approximate location information from an allowed request.
Fettl uses its own analytics property and cookie prefix. Advertising, Google signals, and remarketing are disabled. CLI connection and account routes are excluded from website measurement.
Use “Cookie preferences” in the footer to change your choice. Rejecting analytics stops subsequent measurement and removes Fettl analytics cookies accessible to this site. Your choice is stored in this browser. We also honor Global Privacy Control and Do Not Track by keeping analytics off. Previously collected data is not deleted just by changing cookie preferences; contact us for a deletion request.
For information about Google’s processing, see how Google uses information from sites that use its services.
Service providers
The website and control plane use Codex Sites / OpenAI-hosted application infrastructure backed by Cloudflare Workers and D1. GitHub supports enabled account connections. Stripe supports enabled billing. Google provides optional website analytics after consent.
These services can process operational records, logs, backups, and abuse-prevention information. Their infrastructure can process information in countries outside your own, including the United States.
Retention and deletion
We keep access requests while evaluating fit, arranging access, and following up. If you withdraw your request or ask for deletion before onboarding, we delete the request records unless a legal or security reason requires temporary retention.
Account, billing, and operational records follow the retention rules for the enabled service. Provider backups, financial records, and records needed for legal, accounting, fraud-prevention, or security purposes can remain after a product record is deleted.
Questions and requests
Use the access-request form and begin the optional note with “Privacy request” to ask about access, correction, or deletion. Do not include secrets or sensitive source content. A dedicated privacy mailbox will be published when business email is operational.