Privacy Policy & Non-Custodial Data Framework
Cryptographic transparency standards, non-custodial architecture guarantees, and minimal metadata collection policies for KvantBot operations.
Non-Custodial & Web3 Data Handling
At KvantBot, our architecture is engineered from the ground up to uphold the core principles of Web3: decentralization, user sovereignty, and minimal data footprint.
We firmly reject predatory tracking, surveillance advertising, and unnecessary personal data harvesting. Accordingly, KvantBot does not collect, process, or store:
- Personally Identifiable Information (PII) such as legal real names, physical addresses, or phone numbers.
- Government-issued identification documents, passports, or KYC (Know Your Customer) identity dossiers.
- Private cryptographic keys, secret seed phrases, or password hashes.
- Credit card numbers, bank account routing details, or fiat payment processing credentials.
Your funds remain permanently non-custodial inside your own Solana wallet. Our smart routing algorithms only execute transactions when explicitly authorized via cryptographic message or transaction signatures through your Web3 wallet provider.
Collected On-Chain Identifiers & Database Storage
To authenticate active software licenses, manage node allocations, and prevent Denial of Service (DoS) attacks on our private RPC pipelines, we store a strictly bounded set of technical metadata in our secure backend database (Supabase):
| Field | Purpose | Storage Scope |
|---|---|---|
| wallet_address | Solana public address verifying active node license. | Public blockchain key |
| username | User-defined pseudonymous trader handle. | Self-selected string |
| selected_plan | Node execution tier (Starter, Advanced, Whale). | Tier designation |
| allocated_capital | Trading balance limit for simulation and scaling telemetry. | Numeric telemetry limit |
| payment_status | Cryptographic authorization state for terminal access. | State flag (completed) |
| email (optional) | Optional contact handle for technical node alerts if provided. | Optional user input |
All database records are protected by strict server-side Row Level Security (RLS) policies, preventing unauthorized read or write access from external clients.
Local Storage & Client Telemetry
We utilize standard HTML5 localStorage in your browser exclusively to ensure a seamless trading experience between page reloads. We do not use third-party tracking cookies, fingerprinting scripts, or marketing pixels.
Local storage keys store only essential UI state:
- kvant_user_wallet: Caches your active connected public key to preserve terminal session continuity.
- kvant_auth_status: Remembers your verified authorization token so you do not have to re-sign on every page visit.
- kvant_selected_plan: Stores your UI layout preferences and active engine configurations.
- kvantbot_settings: Preserves custom user preferences, such as slippage tolerance, gas tip overrides, and chart intervals.
You can instantly wipe all local data by clicking "Disconnect" in the terminal header or clearing your browser's application storage at any time.
Public Blockchain Data & Third-Party RPC Protocols
Transactions executed through KvantBot are broadcast to the public Solana mainnet. Please be aware that all transactions, token swaps, liquidity pool interactions, wallet balances, and timestamped contract calls become publicly visible and permanent on the Solana distributed ledger, accessible via explorers such as Solscan and Solana Beach.
To broadcast transactions at sub-millisecond speeds, the Protocol interfaces with institutional RPC providers (such as Helius and Triton) and the Jito block engine validator relay. These third-party nodes receive raw transaction payloads necessary to validate and include blocks in the Solana state machine.
Data Security & Retention Standards
We implement industry-standard cryptographic practices to secure all data transmissions. All communication between your client and our API endpoints is encrypted via Transport Layer Security (TLS 1.3).
License data is retained as long as your node allocation remains active. If you wish to unlink your pseudonymous trader handle from your public wallet address, you may submit a request to our technical team, and your profile metadata will be anonymized from our database.
Inquiries & Responsible Disclosure
For privacy inquiries, technical audits, or responsible security disclosures regarding our telemetry pipeline, please contact our engineering team directly at: