API privacy notice
Published 25 October 2026.
Account and billing data
Customer sign-in is handled by Privy using email or an external wallet. Privy processes login identifiers and authentication data under its privacy policy. DeepHat verifies the signed Privy identity on its server and maps it to your API account. Customer accounts use Privy identities; DeepHat does not merge accounts by email. Operator authentication is separate. Account identifiers associate API keys, credit balances, invoices and usage. API keys are stored as hashes; a newly issued key is shown once. Billing records include token counts, charges, reservations, payment references, status and timestamps.
Inference and payment processors
Prompts and generated responses pass through DeepHat to Yeta to serve inference requests. The gateway does not intentionally save prompt or response text in the billing database. Avoid sending secrets or unnecessary personal data. Yeta and the hosting infrastructure process request data under their own applicable terms and privacy policies.
NOWPayments processes crypto invoices, including addresses, assets, amounts and transaction metadata. Public blockchains can expose payment transactions. DeepHat stores invoice references and settlement status; it does not need your wallet seed phrase or private key.
Optional holder verification
When you check a holder discount, DeepHat verifies your Privy-signed linked wallet and sends its public address and the configured mint to the configured Solana RPC provider (currently Helius) to read token balances. DeepHat stores the wallet address, mint, raw balance, verification expiry and check timestamps with your account. It does not store the identity token, wallet private key or seed phrase, and cannot transfer tokens. Holder verification becomes available when the token-holder program is enabled.
Retention and requests
Billing and usage records are kept for account operation, dispute resolution and applicable recordkeeping obligations. No automatic deletion period is configured in this initial release. Contact the merchant through invoice support for access, deletion, billing and incident requests. Required billing records may need to be retained.