Legal
KEK.PRO is non-custodial and minimises the data it processes. This policy explains what we do, and what we do not see, when you connect a wallet and use the Service.
Last updated: 2026-08-14
KEK.PRO is a non-custodial launchpad and trading interface. The Service is designed to function with the minimum amount of personal data necessary to render the interface and route transactions to the underlying blockchain.
We do not require accounts, emails, names, or KYC submissions to use the Service. Wallet addresses you connect, and transactions you sign, are publicly observable on-chain by design.
We do not collect: real names, email addresses, phone numbers, government IDs, biometric data, or financial-account information. The Service has no signup form because no signup is required.
We do not sell, rent, or trade any data we do receive. We do not run third-party advertising trackers or behavioural ad pixels.
Wallet addresses: when you connect a wallet, the Service reads your public address to query balances and public chain history needed for the interface. A public wallet address is pseudonymous, not anonymous.
Transaction payloads: when you sign a swap, launch, or claim, the Service constructs the transaction in your browser and forwards it to a public RPC endpoint. The transaction is then publicly observable on-chain.
Operational telemetry: like most web services, our hosting infrastructure may temporarily log IP addresses, user agents, request paths, and timestamps for rate-limiting, debugging, security, and abuse prevention.
The Service uses local storage to persist your selected language, dismissed notices, and similar UI preferences. These values stay on your device and are not transmitted to KEK.PRO servers.
No third-party advertising or cross-site tracking cookies are set by KEK.PRO.
We use Vercel Web Analytics, a privacy-friendly, cookieless analytics service provided by Vercel Inc., 340 S Lemon Ave #4133, Walnut, CA 91789, USA ("Vercel"), to understand aggregate traffic to the Service (page views, referrers, country, browser, operating system, device type).
Vercel Web Analytics does not use cookies, does not write to local storage, and does not assign a persistent identifier to your device. To produce de-duplicated visit counts, Vercel derives a short-lived, salted hash from your IP address, user agent, and the requested domain; this hash rotates daily and cannot be reversed to identify you. Your full IP address is not stored.
Legal basis under Art. 6(1)(f) GDPR: our legitimate interest in measuring, securing, and improving the Service. Because no information is stored on or read from your terminal device, no consent under § 25 TDDDG (the German implementation of the ePrivacy Directive) is required.
Vercel acts as our processor under Art. 28 GDPR. Data may be processed on Vercel infrastructure outside the European Economic Area, including in the United States; international transfers are covered by the EU Standard Contractual Clauses. Vercel’s privacy notice is available at https://vercel.com/legal/privacy-policy.
You may object to this processing at any time by enabling "Do Not Track" in your browser, by blocking the Vercel Analytics endpoint (e.g. va.vercel-scripts.com) with a content blocker, or by contacting us via the channels listed below. Objecting does not affect your ability to use the Service.
When you load the Service, your browser contacts a number of third-party providers that the Service does not control. These include: public Solana RPC endpoints (e.g. Solana Foundation, Helius, QuickNode, or similar) used to read on-chain state and broadcast transactions; blockchain indexers and metadata providers; IPFS and Arweave gateways used to fetch token images and metadata; and the wallet provider you choose to connect (e.g. Phantom, Solflare, or Backpack).
These providers may receive your IP address, user agent, the public wallet address you connect, and the requests you make. Their handling of that data is governed by their own privacy policies. KEK.PRO does not control these providers and is not responsible for their practices.
KEK.PRO does not share wallet-level activity with advertisers or data brokers.
Blockchains are public by design. Any transaction you sign — including launches, swaps, and claims — is permanently visible to anyone querying the chain.
KEK.PRO cannot delete, redact, or otherwise unwind on-chain activity. If you want to maintain pseudonymity, use a fresh wallet and avoid linking it to off-chain identifiers.
Where KEK.PRO does process operational data (server-side request logs, infrastructure telemetry, the analytics described in section 5), it does so for the purposes of providing the Service, maintaining platform security, preventing fraud and market abuse, complying with applicable law, enforcing the Terms of Service, resolving disputes, and satisfying recordkeeping obligations.
KEK.PRO otherwise retains data for as long as reasonably necessary to fulfil the purposes above, including any period required by applicable law or legitimate business needs. Operational logs are kept for short, rolling windows; aggregate analytics counts persist longer because they are not intended to identify an individual visitor.
The Service is not directed at children under the age of 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect data from children.
We follow industry-standard practices to protect the Service from abuse, including transport encryption (HTTPS) and minimal logging. No system is perfectly secure; you remain responsible for the security of your wallet and the device you use to access the Service.
A "Security Breach" includes any actual or suspected unauthorised access to your wallet, recovery credentials, connected social login, device, or session, and any impersonation, social engineering, or deceptive communication that may affect your access to the Service. If you suspect a Security Breach, please notify KEK.PRO promptly via the public support channels listed in the footer. This duty is also reflected in section 10 of the Terms of Service.
We may update this policy from time to time. Material changes will be reflected in the "Last updated" date below. Continued use of the Service after a change constitutes acceptance of the updated policy.
Questions about this Privacy Policy can be sent to the project’s public channels listed in the footer of the Service.
