Private by
default.

01 · Receipt content

Your prompt stays with you.

The current receipt studio creates and verifies receipts in your browser. Kernave does not operate an application database that receives your prompt, model output, notes, seed, or imported receipt. That content remains in the active page unless you choose to download, copy, import, publish, or otherwise transmit it.

02 · Browser storage

Local state is limited.

Kernave may use browser storage for a local points activation state, interface preferences, or an in-progress local workflow. This state is stored on your device, is not a transferable asset, and may disappear when you clear site data or use another browser.

You can clear local state through your browser controls. Closing the page does not delete files that you already downloaded or records that you independently submitted to a public network.

03 · Wallet data

Minimum wallet access.

Kernave requests wallet access only after you select “Connect Wallet.” The interface may then read the currently selected public address and active network identifier so it can display connection status and check compatibility.

• Connecting does not automatically request a signature.
• Connecting does not automatically send a transaction or payment.
• Connecting does not automatically activate points.
• Your wallet provider may process data under its own privacy terms.

If you later choose a signing or transaction action, the wallet and public network may expose the public address, payload or digest, transaction value, fee, timestamp, and transaction status.

04 · Hosting and network logs

Basic delivery metadata may exist.

The website is delivered through Vercel. Like most hosting and security infrastructure, the provider may process standard request metadata such as IP address, user-agent information, requested URL, timestamps, error details, and abuse-prevention signals. Such processing may be used for delivery, security, reliability, and diagnostics under the provider’s own terms.

Kernave’s current interface does not intentionally place third-party advertising trackers in the receipt workflow. External font or library requests, wallet providers, RPC providers, and explorer links may receive normal connection metadata when your browser contacts them.

05 · Public records

On-chain data cannot be made private.

If you explicitly submit a transaction, the resulting public record may be replicated, indexed, and retained indefinitely. Kernave cannot delete or alter a confirmed public transaction. Never put a prompt, output, private key, seed phrase, personal information, or confidential material in a public transaction field.

06 · Control and changes

Your practical choices.

• Use the receipt studio without connecting a wallet.
• Review an exported receipt before sharing it.
• Reject any wallet request you do not understand.
• Clear browser storage using your browser settings.
• Avoid optional network actions when local verification is sufficient.

This notice may change as the product evolves. The date at the top identifies the current public version. Material changes should be explained before new data-handling behavior is introduced.