Privacy Policy

1. Information handled

• Browser session and conversation identifiers stored in signed cookies.
• Wallet address, chain ID, SIWE login message and signature, and the Terms/Privacy versions accepted.
• Chat messages and assistant responses.
• Transaction instructions, token and amount details, order identifiers, transaction hashes, status and error information.
• Hashed browser and wallet identifiers, country code, visit time, wallet activity and aggregate transaction metrics.
• Privacy-minimized acquisition data: referring domain, recognized UTM source/medium/campaign, landing path without its query string, coarse device category and automated-browser signal.
• Technical request and security information needed to operate and protect the Service.

The Service does not request or store your wallet private key or recovery phrase.

2. How information is used

Information is used to authenticate wallet ownership, maintain conversations, prepare and restore transaction flows, show order history, monitor transaction status, secure and troubleshoot the Service, measure aggregate usage, comply with law and maintain evidence of policy acceptance.

3. Cookies and local state

A browser-session cookie is used for conversation continuity, and a wallet-session cookie is used after SIWE authentication. A short-lived cookie records pending legal acceptance while wallet connection and signature are completed. These cookies are necessary for the requested Service flow. The Service does not enable Reown analytics and does not currently load advertising cookies.

4. Analytics and location

Service analytics use HMAC-pseudonymized browser and wallet identifiers. Raw IP addresses and full referring URLs are not stored in analytics tables; an IP may be processed transiently to derive a country code, and the browser User-Agent may be processed transiently into a coarse device or automated-browser category. Query strings are removed from stored landing paths, except recognized UTM campaign fields supplied for attribution. Aggregate dashboards do not expose wallet addresses or pseudonymous identifiers. Operational transaction records still contain the wallet address required to restore and display wallet-specific history.

5. Service providers and blockchain disclosure

Information may be processed by infrastructure necessary to provide the Service, including Reown/WalletConnect, AI and agent infrastructure, RPC providers, Orbs/Spot and liquidity infrastructure, bridge providers such as LI.FI, hosting and security providers. A signed or submitted blockchain transaction, wallet address, token transfer and transaction hash become publicly visible and may be permanently replicated by blockchain networks and explorers.

6. International processing

Service providers and blockchain infrastructure may operate in multiple countries. Information may therefore be processed outside your country, subject to applicable safeguards and the providers’ own terms and policies.

7. Retention

Browser sessions normally last up to 30 days and wallet sessions up to 7 days. Pending legal acceptance normally expires after 15 minutes. Clear Chat removes the prior conversation from the active browser session and starts a new conversation, but it does not by itself erase the former messages from server storage. Chat records may be retained where reasonably necessary to improve transaction-intent interpretation and the trading environment, diagnose execution and user-interface errors, evaluate reliability, prevent abuse, support transaction-status inquiries and resolve disputes. Transaction, order-history, security and legal-acceptance records may also be retained while needed to operate and improve the Service and meet legal obligations. Access should be limited and records should not be kept longer than reasonably necessary for those purposes; however, the current beta does not yet apply one automated deletion period to all operational records.

8. Your choices and rights

You may decline the Terms and avoid connecting a wallet, disconnect your wallet, use Clear Chat to reset the visible conversation, and request access, correction or deletion of server-held information where applicable. Blockchain records cannot generally be altered or deleted by the Service. Requests may require proof that you control the relevant wallet.

9. Security

The Service uses signed, HttpOnly session cookies, wallet-signature verification, access controls and pseudonymization for analytics. No system is completely secure, and you remain responsible for wallet and device security.

10. Updates and contact

Material Policy changes will use a new version and may require renewed acknowledgement. Questions or rights requests may be directed through the operator contact channel published at kryp.xyz.