Privacy Policy

Last updated: July 17, 2026

Data Processed

LuckyMe processes the data needed to display pool state, build unsigned transactions, simulate transaction results, and support backend reliability.

• Connected public wallet addresses submitted to API endpoints.
• Request timestamps, endpoint paths, and operational logs.
• IP-derived rate-limit metadata handled by the hosting layer.
• Transaction build and simulation payloads needed for wallet review.
• For the Solana dApp Store APK, a randomly generated installation identifier is sent on activation and launch. LuckyMe stores only a keyed, non-reversible hash of that identifier together with app version, release channel, platform, and timestamps. This provides an estimated count of unique app activations; it is not a store-certified download count.
• For NFT promotions, the signed public wallet address, verified NFT asset identifier, tree and leaf reference, entry time, and campaign result are stored to prevent duplicate entries and make the draw auditable. The authentication signature is not a Solana transaction and cannot transfer assets or funds.

Push Notifications

If you allow notifications, LuckyMe stores the device's push token, platform, app project identifier, and, when available, the connected public wallet address. This information is used only to deliver LuckyMe round alerts and maintain notification delivery. Push alerts are delivered through Expo and Firebase Cloud Messaging. You can disable notification permission at any time in Android settings and contact us to request removal of the stored push registration.

Private Keys

LuckyMe does not collect seed phrases or private keys. Transactions are signed by the user's wallet.

On-Chain Data

Public Solana addresses and transactions may be visible on Solana mainnet and third-party explorers.

Contact

Privacy questions and data-removal requests can be sent to 2022vyktorrio@gmail.com.