Last updated · July 2026
kerf.box is an early-stage (beta) product. This page describes what we collect, why, and what we deliberately never hold. It is written to be read, not to be hidden behind. If anything here is unclear, ask via the issue tracker.
Almost nothing. kerf.box is account-free — there is no login, no password, no user database, and no API key to issue. We hold no record that you used the product.
localStorage — they never reach our servers. They live on the device that created them; clearing your browser storage removes them. To move a kerf elsewhere, export it as JSON and import it on another device.X-Provider / X-Api-Key headers or the legacy X-Anthropic-Key header — it is used for that single request and never persisted, logged, or proxied anywhere we can read it. In the web app it lives only in your own browser's storage; clearing the field removes it for good.We rely on a deliberately small set of infrastructure providers: Vercel (hosting) and the AI provider you choose (model inference — Anthropic, OpenAI, Google, Moonshot, Alibaba, DeepSeek, Groq, OpenRouter, or your own endpoint). Your inputs are sent to that provider only to generate the response you requested — billed to your own key. There is no authentication provider and no database, because there are no accounts and we store nothing server-side.
Your saved kerfs are yours to manage directly: delete any entry — or clear the whole archive — from the archive page, or just clear your browser's site data. Because there is no account and we hold nothing server-side, there is no profile to request the deletion of. Questions go to the issue tracker.
This notice may change as the product matures. Material changes will be reflected in the “last updated” date above. This is a beta service provided as-is and is not a substitute for formal legal advice about your own obligations.