Privacy Policy
Effective date: May 27, 2026
This policy describes the kinds of data claimly ("the Service") collects and how it is handled. The Service is non-custodial — we never collect your private key, seed phrase (12 or 24 words), or keystore files, and we do not hold your assets.
1. Data we collect
The data claimly stores in its own database — all entered directly by you — is listed below.
- 🔓 Registered wallet addresses — public addresses on EVM (0x…), TON, Solana, or XRPL. You enter them yourself in the app.
- 📛 Wallet label — free-text label you attach to a registered wallet (e.g. "My main wallet"). Optional.
- 🔔 Telegram chat_id — the Telegram user identifier you enter to receive alerts. Optional.
- ⚙️ Alert and search thresholds — the alert trigger amount and the search-result visibility threshold (USD) that you configure.
2. What we do not collect
We never ask for your private key, seed phrase (12 or 24 words), or keystore files — on any screen, in any form. We also do not collect personal identity information such as name, email, phone number, or date of birth.
3. How we use the data
- Use your registered wallet addresses to search assets, unclaimed rewards, and yields across multiple blockchains and display them to you
- Send Telegram alerts for unclaimed rewards that reach the threshold you optionally configured
- Respond to bot commands you explicitly send (e.g. /check)
4. Third-party processors — where your data is sent
To provide asset search and alerts, the Service sends data to the third-party services listed below. Each service is governed by its own privacy policy.
- Zerion — EVM and Solana wallet addresses for DeFi position lookup
- Alchemy — EVM wallet addresses for supplementary token balance lookup
- Helius — Solana wallet addresses for SPL token and SOL balance lookup
- Tonapi — TON wallet addresses for TON and Jetton balance lookup
- XRPL public nodes (s1, s2.ripple.com) — XRPL addresses for AMM LP and DEX offer lookup
- Merkl — EVM wallet addresses for unclaimed incentive lookup
- Telegram — your Telegram chat_id (only after you opt in to alerts and complete OTP verification) for delivering messages
When the Service queries price or yield information (CoinGecko, DefiLlama, Beefy, Curve, STON.fi, etc.), it does not send your wallet address.
5. Where your data is stored
The database that stores your data is located in Korea (Seoul region, Supabase). However, the application server runs in the United States (Vercel US East region), so your data passes through US servers during processing. In addition, when data is sent to the third-party processors listed in § 4 (Zerion, Alchemy, Helius, Tonapi, XRPL, Merkl, Telegram), it may be transferred across borders depending on the location of those services.
6. Retention and deletion
Data is handled differently depending on type:
- 🕐 Auto-expires after 5 minutes — Telegram OTP codes, TON wallet-ownership proof tokens
- 🗑️ You can delete it yourself — registered wallet addresses (in the app's "Wallet management" view, per-wallet delete)
- 📩 Full deletion on request — for all other data (Telegram chat_id, verification record, threshold settings, LST reward accumulation records), email ginet304@gmail.com and we will process the deletion.
- 📜 Auto-retained logs — verification attempt records and server logs are kept for a limited period for security and debugging. The exact retention follows the hosting provider's (Vercel) policy. User identifiers in server logs (such as wallet addresses) are stored in a masked form that shows only partial characters.
7. Browser storage
For a smooth user experience, the Service stores the following in your browser's localStorage. You can delete it at any time from your browser settings.
- 📌 Telegram chat_id — to recognize you on return visits after you link alerts
- 📌 Registered-wallet selection state — multi-wallet chip toggle state
- 📌 Volatility alert toggle state and last-alerted timestamp
The Service does not set any other cookies directly. Only the language cookie (NEXT_LOCALE) that the Next.js framework uses for multilingual routing is set automatically.
8. Analytics and tracking tools
The Service uses Vercel Analytics (provided by the hosting provider) to collect anonymous usage statistics such as page views and access times. Vercel Analytics uses no cookies and does not collect personal identifiers (full IP address, account name, etc.). We do not use other analytics or tracking tools such as Google Analytics, Sentry, Mixpanel, or PostHog.
9. Non-custodial principle
The Service never collects, stores, or asks for your private key, seed phrase, or keystore files. Reward claims, swaps, and other transactions always happen on the DeFi protocol's official external page, signed by you with your own wallet. claimly has no authority to move or claim your assets.
10. Changes to this policy
If this policy changes, we will update the "Effective date" on this page.
11. Inquiries and deletion requests
Send inquiries about data processing, access, or deletion to: ginet304@gmail.com