Privacy notice

AblitAI is in private beta. Bitcoin checkout is open in beta; card checkout is closed. Operator, service-address, and jurisdiction disclosures continue to mature. This page is not currently an offer to purchase credits.

No-email accounts

Creating an AblitAI account does not require a name, email address, telephone number, or password. We retain a random pseudonymous account number, a cryptographic hash of each API key, token balance, payment references, and credit-ledger entries. We cannot recover a lost plaintext API key.

Inference requests

AblitAI's application does not intentionally retain API prompts or generated responses. They are handled transiently in memory to provide the service. Application access logging is disabled, and the account database contains no prompt, response, or request-IP fields. Infrastructure providers may still process network and operational metadata under their own terms.

Payments

Bitcoin checkout is open in beta via self-hosted BTCPay Server. Card (Dodo) checkout remains closed. If Dodo card checkout is later enabled, Dodo Payments will act as merchant of record and may collect identity, billing, tax, fraud-prevention, and receipt information under their own terms. Bitcoin transactions remain public on the Bitcoin network. Current Bitcoin checkout does not require a customer-facing location attestation.

Bitcoin invoices are created by BTCPay Server on infrastructure operated for AblitAI. The payment provider never receives your API key.

Any future card checkout may introduce separate eligibility rules; none apply to the current Bitcoin beta.

Infrastructure

Cloudflare provides authoritative DNS and serves the static website. Hetzner hosts the API control plane and payment services. Specialized third-party GPU infrastructure processes model inference. These providers may process network and operational metadata under their own terms even though AblitAI does not retain application request-IP logs.

Local browser storage

The website stores your account number and plaintext API key in this browser’s local storage. Anyone with access to the browser profile may be able to use the key. Export an offline backup and protect it.

Contact

A verified privacy and DPO contact channel will be published before paid checkout opens. Because accounts are pseudonymous, we may be unable to identify or recover an account without a valid key or provider payment reference.

Transient prefix state

The current model runtime can reuse transient in-memory prefix state across requests. This state is distinct from persistent prompt or response logs and databases. Disabling prefix caching is prepared but has not yet been deployed; content should not be assumed to clear from GPU memory immediately after a request.

Runtime telemetry opt-outs are prepared but not yet applied. Request, output, statistics, and HTTP access logging are disabled. Operational telemetry is a separate boundary from prompt and response logs; no claim is made here that every runtime telemetry mechanism is disabled.