Privacy Policy

We collect only what the Service needs to function:

• Workspace data: a hashed API key, your on-chain deposit address, verified withdrawal addresses, trusted sign-in wallet addresses, and your policy settings.
• On-chain activity: deposits, trades, activations, staking, and withdrawals. These happen on a public blockchain and are inherently public; we record them to keep your books.
• Usage metadata: per-request model, token counts, cost, and timing, used for billing and your savings receipts. We do not need or retain your prompts or completions beyond what is required to route a request (see sharing below).
• Operational data: IP address for rate limiting and abuse prevention, and any contact detail you optionally provide on the Support page.

We do not ask for your name, email, password, government ID, or payment card by default. We do not sell personal information. We do not build advertising profiles. Your raw private keys are never transmitted to us when you sign in or verify a wallet; you sign a message with your own wallet and we only see the signature.

To fulfill an inference request, its contents are transmitted to the upstream model provider (for example Orbio, and any fallback provider) that serves the model you called. Those providers process the request under their own terms and privacy policies. Perigee does not store request or response bodies as part of normal operation and does not log them.

We share data only as needed to run the Service: with model providers to fulfill requests, with blockchain and infrastructure providers to settle transactions and host the Service, and where required by law or to protect against fraud, disputes, or security threats. Blockchain transactions are public by nature and visible to anyone.

Ledger and audit records are retained as long as needed for accounting, dispute resolution, and legal obligations. Operational diagnostics and price history are downsampled or deleted on a rolling schedule. Hashed API keys are retained while a workspace is active. On-chain data cannot be deleted from the blockchain.

Secrets are encrypted at rest; signing authority is guarded by an allowlist, spending caps, and (as it rolls out) hardware-backed custody. No system is perfectly secure, and you are responsible for protecting your API key and your wallets. See the Risk page for the security model and its current limits.

We use a single session cookie to keep you signed in and, for the demo, an unsigned marker cookie. We do not use third-party advertising or tracking cookies.

You can stop using the Service and withdraw your withdrawable balance at any time, subject to the withdrawal terms. Requests about your data, including access or deletion where applicable, can be made through the Support page. Specific statutory rights (for residents of jurisdictions with privacy statutes) are to be completed by counsel.