Privacy Policy

1. Non-Custodial & Zero-KYC Architecture

Cryptonim AI ("we", "us", or "our") operates under a foundational zero-knowledge and self-custodial architecture. We do not require identity verification, passport submission, phone numbers, or standard Know-Your-Customer (KYC) documentation to access our token deployment, bundle bundling, or automated liquidity tools.

Your interaction with the software occurs through client-side interfaces and direct RPC broadcasts to decentralized blockchain protocols, primarily the Solana mainnet-beta network.

2. Data We Strictly Do Not Collect

3. Information We Collect or Process

To provide stable operations, delivery of digital license access, and maintain the affiliate system, we process minimal technical data:

4. Public Blockchain Transparency

Please note that the Solana blockchain is a public, immutable, distributed ledger. When you deploy tokens, create liquidity pools on Raydium or Pump.fun, distribute sub-wallets, or execute atomic bundle transactions via Jito Block Engine relayers, those transactions, wallet addresses, and token amounts are permanently recorded on public ledgers accessible via Solscan, SolanaFM, and Birdeye.

Cryptonim AI cannot alter, delete, or obscure transactions recorded on public blockchains.

5. Third-Party Service Providers

In operating our website and deployment cockpit, we interact with select third-party service providers:

6. Cookies & Browser Storage

We use essential functional cookies and HTML5 local storage strictly necessary for the application to function:

You can delete or disable cookies at any time via your browser settings; doing so will not prevent you from using the platform.

7. Data Retention & Rights

Because Cryptonim AI maintains no custodial account database, we do not store personal profiles. Any operational server logs retained for security are routinely purged every 30 days. To request the deletion of an email provided during checkout, contact our support team.

8. Security Practices

We implement industry-standard cryptographic practices, including strict HTTPS enforcement (TLS 1.3), Content Security Policy (CSP) headers, and origin verification. However, users are exclusively responsible for securing their private keys, safeguarding backup seeds, and ensuring local computing environments are free of malware or malicious browser extensions.

9. Contact Us

For inquiries regarding this Privacy Policy, our data handling architecture, or to request removal of operational contact records, please contact us via: