League Lock is a season-long fantasy sports application that settles prize pools in the SKR token on Solana. We are an independent product and are not affiliated with Solana Mobile, Inc., the NBA, or any team.
| Category | Examples |
|---|---|
| Account / wallet | Public Solana wallet address; optional display name / .skr |
| Waitlist | Email, optional social handle, country/region you provide |
| Device / app | Device type, OS version, app version, crash logs |
| Usage | Screens viewed, draft actions, approximate region for geo-gating |
| On-chain | Transactions you sign are public on Solana |
| Support | Messages you send to support |
We do not ask for seed phrases or private keys. We cannot spend funds without your wallet signature.
Where GDPR/UK GDPR applies: contract performance, legitimate interests (security, product improvement), consent (marketing emails), and legal obligation. Some regions (including the UK) may be waitlist-blocked or limited via our geo deny-list.
We may share data with infrastructure vendors, stats/data vendors under contract, on-ramp/KYC providers when you choose them, and advisors or authorities when required. We do not sell your personal information.
League Lock interactions you sign are recorded on Solana and may be publicly visible forever. Off-chain lineup blobs are stored as described in-product; on-chain we store commitments/hashes as designed.
Waitlist and account data: until you request deletion or we no longer need it for leagues, disputes, or law. On-chain data cannot be deleted by us.
Not directed to anyone under 18 (or higher age required in your region). Do not use the app if underage.
We may block or limit access by region (including attested country/region on the waitlist and IP/header signals such as Cloudflare cf-ipcountry) to manage risk. Providing a region on the waitlist does not guarantee eligibility. Default Season 1 waitlist deny includes the United Kingdom (GB); other regions may be flagged or added over time.
We may update this policy. Material changes will be posted with a new effective date. Continued use after the effective date means you accept the update.
privacy@[domain]