Privacy policy
Last updated 4 November 2026
The short version: we collect what we need to sell you a script and support it, and the only tracking is the Whop Pixel, which shows us which ads bring buyers. Each point has a reference, like 2(c), and our Terms use the same format.
1.Who we are
2.What we collect
- 2(a)Purchase details, received from Whop when you buy: your name, email address, Whop user ID, the product you bought, the date and the amount. We never see or store your card or bank details; Whop handles payment.
- 2(b)Account details, when you log in with Whop: your Whop user ID, username, email and which Lura scripts you own, so we can unlock your downloads and guides.
- 2(c)Support conversations: the messages you send us through the support chat, email or our Discord, and the details you include in them.
- 2(d)Build details, when you use the LuraNBA build customiser: the settings you chose and a build identifier stamped into your file, so we can support that build and trace a leaked copy back to its licence.
- 2(e)Technical data: our host automatically records basic request logs (such as IP address, browser and the page requested) to keep the site running and secure.
- 2(f)Visit data, through the Whop Pixel: the pages you open on lura.gg, the page that sent you here, details about your device and browser (such as screen size) that Whop uses to recognise the same device on later visits, and a visitor identifier Whop keeps in a cookie and in your browser's storage. It shows us which of our ads and links lead to visits and sales. When you are logged in, it also records what you do with your purchase (opening the checkout, downloading or building a script, claiming Discord roles) against your Whop account. Whop runs the pixel and handles this data under its own privacy terms.
- 2(g)Zen details, when you program a script onto your Cronus Zen: the Zen's serial number, the sentence you ticked to tie the script to it, and each time a script is built for a Zen, with your Whop account, IP address and browser, so a licence stays on one Zen and we can settle support requests and disputes about it. The pixel in 2(f) also records when a script is tied to or programmed onto a Zen, with its serial number.
- 2(h)Account activity, while you are logged in: when you visit lura.gg and from which country (worked out from your IP address), with the IP address and browser of each visit; which parts of each video guide you watched, how far you got and how many times you started it; and the Discord account you link when you claim your roles. We use it to help you when you contact support, to settle disputes, and to spot a login shared between people.
3.What we do not collect
- 3(a)Apart from the Whop Pixel in 2(f), we run no analytics, advertising or tracking scripts.
- 3(b)Besides the pixel's identifier, the site stores one setting in your browser, your light or dark choice, and never sends it to us.
- 3(c)We do not sell, rent or trade personal data. Pixel data is used only to measure our own ads and links.
4.Why we use it
- 4(a)To deliver what you bought: unlocking downloads and guides, and sending updates for your script. The basis is the contract you enter when you buy.
- 4(b)To answer support requests and keep a record of them. The basis is our contract with you and our legitimate interest in helping customers well.
- 4(c)To protect the business: preventing fraud, handling chargebacks, and investigating shared licences and leaked files under section 4 of our Terms. The basis is our legitimate interest.
- 4(d)To meet legal duties such as tax and accounting records.
- 4(e)To measure which of our ads and links bring visitors and sales (the Whop Pixel).
- 4(f)To keep a record that you received what you bought (downloads and builds, with their times), in case of a refund request or payment dispute. The basis is our legitimate interest in defending against unfounded claims.
5.Who handles it for us
- 5(a)Whop, for checkout, payments, account login, confirming what you own, and the Whop Pixel.
- 5(b)Vercel, which hosts the site and keeps its request logs.
- 5(c)Supabase, which stores the Zen details in 2(g).
- 5(d)Discord, if you join our server or contact us there.
- 5(e)Each provider processes data only for its own function and under its own privacy terms. Some are based outside your country, including in the United States; where data leaves the UK or EU, it is covered by the provider's standard contractual safeguards.
- 5(f)We may also disclose data where the law requires it, or to establish or defend a legal claim.
6.Your rights
- 6(a)You can ask for a copy of the data we hold about you, ask us to correct it, or ask us to delete it.
- 6(b)Where the law gives you the right, you can object to or restrict how we use it, and receive it in a portable format.
- 6(c)Send any request through Support in the User hub on lura.gg, or our Discord, logged in with the Whop account you bought with, so we know it is you. We reply within 30 days.
- 6(d)If you are unhappy with how we handled your data, you can complain to the data protection authority where you live.
7.How long we keep it
- 7(a)Purchase and licence records: for as long as you hold a licence, then as long as tax and accounting law requires.
- 7(b)Support conversations: up to two years after the last message, unless a dispute needs them longer.
- 7(c)Build identifiers: for the life of the licence, since they are how a leaked file is traced.
- 7(d)Request logs: kept by our host for its standard short period, then deleted.
- 7(e)Pixel data: kept by Whop under its own retention terms.
- 7(f)Zen details: for the life of the licence, since they show which Zen it is tied to.
- 7(g)Visit records: 12 months. Video watching and the linked Discord account: for the life of the licence.
8.Security
- 8(a)Data is held by the providers in section 5, over encrypted connections, and only the people who run Lura can reach it. No system is perfectly secure, and we will tell you promptly if a breach affects your data.
9.Children
- 9(a)Lura is not meant for children. Buyers must meet the age requirement in Terms 1(a), and we do not knowingly collect data from anyone younger.
10.Changes
- 10(a)We may update this policy. The date at the top shows the latest version. If a change affects how we use data you have already given us, we will tell you before it takes effect.

