HYPERPICK
// Privacy

Know what travels. Choose what stays.

Local controls and provider processing have different boundaries. This is how HyperPick treats them.

Messages travel to a model provider.

When you send a request, HyperPick relays its content to OpenRouter and the selected model provider so they can generate a response. Their privacy, retention, and acceptable-use terms apply. This is not end-to-end encrypted inference or a guarantee of zero provider logging.

Local history is opt-in.

Conversation persistence starts off. If you enable it, the browser stores your chat history locally. Anyone with access to that browser profile may be able to read it. Clearing local history removes that copy, not data already processed by a provider.

Burner keeps the conversation temporary.

Burner does not add a conversation to persistent history. Clearing the session removes its local conversation state. Temporary browser storage does not hide your IP address, cancel provider charges, or make public blockchain activity private.

Usage metadata has a separate local record.

Completed non-Burner requests can add model, token counts, reported cost, and time to this browser's usage record even when chat history is off. Burner does not add those local usage entries. This record contains no conversation text and is not a signed billing receipt.

Your authorization is sensitive.

Connecting OpenRouter produces access tied to your account. Requests to the HyperPick proxy include the credential needed to contact that provider. Do not share it or enter it into a chat. Disconnect locally and revoke it at OpenRouter when it is no longer needed.

A wallet address is public information.

A connected Solana address can be sent to the configured RPC service to read supported balances and chain state. HyperPick does not ask for seed phrases or private keys. Loading Jupiter also connects to its third-party services. Approved launch or swap transactions are public on the chosen network.

Service requests leave operational records.

Hosting and upstream services may process request metadata such as time, network address, errors, and usage. Provider billing records are managed by the provider. HyperPick does not describe this workspace as log-free or anonymous.

Use the controls at each layer.

Clear browser history in HyperPick, disconnect an account, and use OpenRouter's own settings for provider access and records. Local deletion does not revoke a provider credential automatically or erase a public transaction.

OpenRouter privacy policy