Privacy and data
What CULP sends, what it stores, and the one thing it deliberately does not log.
The short version: CULP does not log your usage. There is no record of what you decoded, what you searched for, or what you edited.
What leaves your machine
On a compact write. The compact content, the tool name, the target file path, and the kind of mutation. That is what the decoder needs to pick a language and expand the notation. The result is returned and not retained.
On a status or plan check. A signed request carrying this device's id and nothing about you.
On a search. Nothing leaves your machine to CULP. The delegated session runs locally against your files.
On a patch. Nothing. The tool is a local process; there is no network call, no decoder and no language detection.
What is stored
| Where | What |
|---|---|
| Your machine | The device key, the device identity, the access token, the cached manifest and message of the day. All under ~/.culp. |
| The API | Your email, your Stripe customer relationship, and one row per authorized device: its public key, platform, architecture and timestamps. |
| The mail gateway | Delivery metadata for messages we sent you: time, recipient, subject, provider id, result. No bodies. |
The device credential deliberately excludes your email, your password, your MAC address and any refresh token.
Deleting it
Write to privacy@claudeusagelimits.com from the address on the account. See the privacy policy for the full statement.