Data we collect
Coyoti may collect wallet public keys, email addresses, session records, strategy settings, selected markets, paper and live authorization records, billing metadata, chat messages, support messages, audit events, and device or request logs.
Why we use it
Data is used to authenticate sessions, load wallet context, evaluate strategies, show evidence, enforce customer limits, verify billing, provide isolated chat, prevent abuse, investigate incidents, resolve support issues, improve the product, and maintain audit records.
Chat review
Authorized Coyoti staff may review customer conversations for support, safety, abuse investigation, and product improvement. Administrative access is restricted, audited, and server-redacted. Product insight reports aggregate recurring themes and require human review; customer chat is not automatically shared with other customers or used to change strategy settings.
On-chain data
Wallet addresses, token balances, and transactions can be public on-chain data. Coyoti may read that data through RPC, indexers, or wallet-connected services to provide the product.
Payments
Billing records can include plan, billing period, amount, wallet address, provider invoice or payment ID, payment status, and transaction ID. This evidence is used to activate access, reconcile exceptions, prevent fraud, and resolve disputes.
Service providers
Coyoti uses providers for cloud hosting and monitoring, Solana RPC and indexing, market data, wallet routing, hosted crypto checkout, and isolated AI assistance. These can include AWS, NOWPayments, Helius, Pyth, Jupiter, market-data venues, Hermes, and model providers. Each should receive only the data needed for its role.
Retention
Account, strategy, billing, support, security, and audit records are kept while the account is active and afterward only as needed to reconcile payments, resolve disputes, prevent abuse, protect the service, or meet legal obligations. Operational logs and sessions use bounded operational windows; backups age out through their normal lifecycle.
Access and deletion
Request access or deletion through the verified Coyoti Discord. Include the public wallet address and request type. Coyoti may ask for a signed wallet message to verify ownership, but never a seed phrase or private key. Deletion can exclude public-chain data and records retained for security, disputes, audit integrity, or legal duties.
Your controls
You can disconnect the browser wallet, stop renewing paid access, revoke wallet authorizations where supported, and stop using Coyoti. Public-chain data remains available independently of Coyoti.
Security and incident support
Report suspicious sessions, unexpected wallet requests, or privacy concerns through the verified Coyoti Discord. Coyoti will preserve relevant evidence, contain affected access, investigate the incident, and notify affected customers when required. Never send wallet recovery material.