Privacy

Joining the waitlist gives Kappa Engine permission to email you about access to the engine.

We store your email address, signup time, and the version of this notice in a private Cloudflare database. The waitlist is not publicly accessible, and we do not sell it.

Cloudflare hosts this website and provides Turnstile to prevent automated abuse. Security checks process technical information, including your IP address and browser information. We do not store your IP address in the waitlist database. See Cloudflare’s privacy policy for details.

Kappa accounts

You can sign in to Kappa with Google or GitHub. Kappa never sees or stores your Google or GitHub password. When you sign in, we store your name, your email address (only when Google or GitHub confirms it is verified), a link to your profile picture, the account ID Google or GitHub uses for you, which of them you signed in with, and when you signed in. We use this to sign you in to this website and the Kappa editor and, when enabled for your account, to authorize and limit hosted AI usage.

Signing in sets a cookie that keeps you signed in on this website for up to 30 days. Signing in the Kappa editor creates a separate editor session for up to 180 days. We store only a one-way hash of these session tokens, not the tokens themselves, and signing out ends the session. We do not store your IP address with your account.

This site does not use advertising trackers or analytics cookies. The only cookies it sets keep you signed in and protect the sign-in process.

Hosted AI

If hosted AI is enabled for your Kappa account, sending a chat submits your message, relevant conversation history, editor context, and requested project file excerpts to Kappa's service and the selected model provider, OpenAI or Anthropic. Your project is saved on your iPad, and editor changes and their reviews run there.

Kappa stores request messages and model results in its private Cloudflare database to support interrupted requests and prevent duplicate model calls. Cached results are available for seven days. A daily cleanup removes expired message and result content on its next successful run. Request identifiers, content hashes, account and project scope, and usage records support duplicate prevention and allowance enforcement; identifiers and hashes remain until the account is deleted. The request content and raw provider errors are not written to application logs by this service.

Your iPad stores its Kappa session in the device Keychain and keeps chat history and drafts locally, separated by Kappa account and project. Signing out ends the session and hides that account's conversation; it does not delete its local history or your project.

AI plans and purchases

When purchases are enabled, Apple handles the payment details. Kappa verifies Apple's signed purchase information and stores transaction and product identifiers, the Kappa account associated with the purchase, subscription periods, credit grants, refunds, and usage amounts. Kappa does not receive your card number. These records support your balance, restoring purchases, preventing duplicate credit, and resolving refunds.

Purchase and credit records do not contain chat messages or raw Apple purchase tokens. Transaction ownership and duplicate-prevention records can be retained after account deletion so the same purchase cannot be claimed again. Your available balance, pending usage, and recent credit usage are shown in the editor. Additional credit purchases require your action; automatic top-ups are off.

Updated October 5, 2026.