Who we are and what this policy covers
Lynx sells subscriptions to game modification apps on iOS and Android. This policy explains what personal data we handle when you use the service.
In this policy, "we", "us", and "Lynx" mean the operator of this service. We decide why and how your data is processed.
This policy covers this website, the dashboard, the reseller and admin dashboards, the API documentation, the Lynx apps, the live chat and its assistant, our Discord and Telegram bots, and the script marketplace. It does not cover the games you use Lynx with, Discord or Telegram themselves, or any other site we link to.
What data we collect
Data you give us
- Account details. Your email address, your name if you give one, your username, and your sign-in credentials. Our sign-in provider, WorkOS, stores the credentials. We store your email address, your name, your username, and your account ID.
- Guest purchases. If you bought without an account before credits, the email address you entered. The purchase waits on it until you sign in with that address.
- Billing details. What the payment processor needs to take a payment. You enter your card on Stripe's page, and the card number never reaches our servers.
- Subscriptions, orders, and balances. What you bought or redeemed, the plan, the period, the price, the tax, your order history, and the movements on your credits.
- Checkout agreement. When you ticked the agreement boxes and which policy versions you accepted, kept with the order or with the card payment at Stripe. For a cart checkout, also the IP address and browser that sent the order.
- Support conversations. What you write in the live chat, by email, or on Discord, including your name and email if you type them, and any file or voice note you attach.
- Linked accounts. If you link Discord or Telegram, your ID, username, and profile picture there.
- Reseller, affiliate, and marketplace details. Business name, contact details, VAT number where you give one, payout and withdrawal addresses, your listings, your scripts, and your reviews. We validate VAT numbers with VIES or HMRC and keep the result.
Data collected automatically
- Device identifiers. The iOS verification profile gives us your device's UDID. The Android app gives us a hardware identifier. The app sends the identifier with each licence check.
- Device and app context. Platform, OS version, app version, device model, and the keys the app uses to prove it is genuine.
- Connection data. Your IP address, its country, your browser's user agent, and the time of your requests. We keep the last IP address and country seen on your account, and the IP address that linked each device.
- Licence checks and app events. When the app checks a subscription, what it reports about its own health, and the signals our abuse detection uses.
- Game data. The in-game player ID of an account you use with Lynx, and, when you send one, a match export file.
- Payment signals from Stripe. Whether a payment succeeded, the card's country and fingerprint, the billing country, postcode, and region, and Stripe's fraud risk rating. We never receive the full card number.
- Usage analytics. Which pages you open, what you click (without the text on the element), page speed, and errors. When you are signed in to a dashboard, the analytics carry your account ID. See analytics.
- Clipboard. When you click or paste into a licence key field, the dashboard reads the clipboard once to find a key. It does not read the clipboard at any other time, and it sends nothing it reads unless you use it.
Data we get from third parties
- From resellers. A reseller who redeems a key for you gives us the details needed to do that. The reseller is responsible for having your permission.
- From Stripe and NOWPayments. The payment signals above.
- From affiliates. The referral code in the link you followed, which tells us which affiliate sent you.
What we do not collect
We do not collect your game account credentials, your full card number, your precise location, your contacts, photos, camera, microphone, messages in other apps, identity documents for an ordinary purchase, or biometric data. We do not ask for your date of birth.
We do not sell personal data. We do not run advertising trackers.
Device linking
A subscription includes one device seat per platform unless you add seats. To enforce that, the app sends us a device identifier when you link the device and with each licence check. On iOS a temporary verification profile provides it. We store that value against your account. That is the link.
To link a device without typing a code, we can match the app to the dashboard you opened on the same network. For that we compare the IP address and the kind of device, within a short window.
We use the identifier to check that the device is linked to your account, to enforce the seat limit, and to detect sharing and multi-accounting. We do not use it for advertising or for tracking you across other apps.
Resets. If you change device, request a reset from your dashboard. Our team clears the link, and the next device takes the seat. We keep a record of past links to spot repeated abuse.
How we use your data, and our legal basis
| Purpose | Data used | Legal basis |
|---|---|---|
| Create your account and sign you in | Account | Performance of a contract |
| Take payments, deliver purchases, issue refunds and receipts | Billing, orders, checkout agreement | Performance of a contract |
| Validate your subscription in the app | Subscriptions, device | Performance of a contract |
| Keep proof of what you agreed to at checkout | Checkout agreement | Legitimate interests, and our legal obligations under consumer law |
| Enforce the seat limit and detect sharing, fraud, and chargeback abuse | Device, connection data, payment signals, game data | Legitimate interests |
| Answer support requests, including with the assistant | Support conversations, account, subscriptions, device | Performance of a contract |
| Link your Discord or Telegram account and run the bots | Linked accounts | Performance of a contract |
| Understand how the sites are used and fix what breaks | Usage analytics | Legitimate interests |
| Keep the service running and protect it against attack | Connection data | Legitimate interests |
| Run the reseller, affiliate, and marketplace programmes and pay rewards | Reseller, affiliate, and marketplace details | Performance of a contract |
| Keep accounting and tax records, including proof of your country for VAT | Billing, orders, payment signals | Legal obligation |
| Respond to lawful legal requests | What the order compels | Legal obligation |
Automated decisions. Our abuse detection can block a device on its own when it sees strong signs of sharing or tampering. When a payment is disputed, we automatically suspend the account and the accounts that used the same card or IP address. If an automated decision affects you, email us: a person reviews it, and you can explain your side.
Analytics
We use PostHog, in the United States, to count page views and clicks and to find errors. The web site and dashboards send it the page address, the element you clicked without its text, your browser and device type, and page speed. Our servers forward your IP address so that PostHog can estimate your country. When you are signed in, we add your account ID, but not your email address.
PostHog keeps a random visitor ID in a cookie and in local storage, so that a visit to the web site and to the dashboards counts as one visitor. We do not record sessions, and personal data in page addresses, such as a search term or an email address, is masked before it leaves your browser.
Cookies and local storage
We set no advertising cookies. The only analytics cookie is the PostHog visitor ID below; everything else is what the sites need to work.
lynx-session. Your sign-in session, shared across the Lynx sites so you sign in once. It lasts up to 400 days, and signing out removes it.wos-auth-verifier. Protects the sign-in step. It lasts 10 minutes.PARAGLIDE_LOCALE. Your language choice, if you pick one. It lasts up to 400 days.lynx_cart. The cart of a visitor who is not signed in. It lasts 30 days.ph_<project key>_posthog. The PostHog visitor ID, shared across Lynx sites, with a copy in local storage. It lasts up to 1 year.
The live chat keeps your chat session, and the name and email you type, in your browser's local storage, so the conversation survives a reload. The dashboard keeps a few display choices there, such as a dismissed banner or a gift code you are about to redeem. None of it is sent to anyone else.
You can clear cookies and site data in your browser. Clearing the session cookie signs you out.
Who we share data with
We share data with the companies that run parts of the service, and with nobody else unless the law forces us to.
| Who | What they get | Why |
|---|---|---|
| Stripe | Payment and billing details you enter at checkout, your email address, and, after a disputed payment, the card fingerprint, email, and IP address for its fraud blocklists | Card payments, receipts, refunds, chargebacks, and fraud prevention |
| NOWPayments | The payment amount, the coin you pay with, and the order reference | Crypto payments |
| WorkOS | Your email address, name, and sign-in credentials | Sign-in for the dashboards |
| Cloudflare | Requests to the websites and the dashboards, and your IP address | Hosting, finding your country, and protection against attack |
| Convex | Everything we store | The database and the API |
| PostHog | Usage analytics, your IP address, and your account ID when signed in | Analytics |
| Google (Gemini) or DeepSeek, depending on which we have configured | Your support messages, the name and email you gave, the page you are on, and a summary of your account and subscriptions | The support assistant, and the script assistant in the app |
| OpenAI or Anthropic | Your script assistant prompts, only if you add your own key for them | The script assistant |
| Discord | Your support conversation and attachments, which our staff read in a private channel; your Discord ID if you link it; match exports | Support, community roles, and match review |
| Telegram | Messages between you and our bot | The Telegram bot |
| Railway | The requests handled by our Discord bot and our iOS signing service, including your device's UDID | Hosting those two services |
| VIES and HMRC | A VAT number you give us | VAT number validation |
| YouTube | Your IP address, when a product page shows a video | Embedded videos, loaded from youtube-nocookie.com |
| Resellers | The status of the keys they issued and, for each device linked with one, its platform, model, OS version, status, last-seen time, and the last four characters of its identifier | Managing the keys they sold |
Resellers. A reseller can see the keys they issued, their status, and whether they were redeemed. A reseller cannot see your name, username, or email address, sign in to your account, read your support messages, or see your IP address or full device identifier.
Business transfers. If the business is sold, account data moves to the buyer. We tell you first.
Legal requests. We disclose data when a valid, binding order from a court or authority with jurisdiction compels us. We disclose only what the order covers, and we tell the affected user unless the order forbids it.
International transfers
Your data is stored and processed in the United States, and by the providers above in the countries where they operate, which include countries outside the EU and the UK. Where the law requires a safeguard for such a transfer, we rely on the one the provider offers in its data processing terms, such as the European Commission's standard contractual clauses.
How long we keep it
- App events, abuse signals, and app health reports: 30 days or less.
- Device-linking records (the IP address, browser, and device identifier we matched a device on): for as long as you have an account.
- Match exports: 14 days.
- Support channels on Discord: deleted 3 days after the ticket closes. The conversation stays in our database with your account.
- Account, order, device-link, and support records: for as long as you have an account, and deleted or anonymised after you ask us to delete it.
- Payment and tax records: for as long as tax law requires, usually up to 10 years.
- Records of an account we banned for fraud, chargeback abuse, or sharing: the minimum needed to recognise the same person, for as long as that remains necessary.
Your rights
Depending on where you live, you can ask us to show you the data we hold, correct it, delete it, give it to you in a machine-readable file, restrict how we use it, or stop processing that we base on legitimate interests.
Email samzsakerz@gmail.com from the address on your account. Your sign-in confirms that the request is yours. We handle each request by hand, and we reply as soon as we can, and at the latest within the period the law sets.
What deletion does not remove. We keep payment records for as long as tax law requires. Where we banned an account for fraud, chargeback abuse, or sharing, we keep the minimum needed to recognise the same person.
Children
Lynx is not for children. You must be at least 18 to hold an account or to buy, and you confirm your age at checkout. We do not knowingly collect data from anyone under 18. If you believe a child has an account, email us and we delete it.
Security
TLS encrypts all traffic to the sites, the dashboards, and the API. Our sign-in provider stores credentials. Card numbers never reach our systems. We limit access to production data to staff who need it.
No system is fully secure. If a breach affects your data and creates a real risk to you, we tell you and the relevant authority within the deadline the law sets.
Use a password you use nowhere else, and do not share your account.
Changes to this policy
We update this policy when what we do changes. The date at the top of the page is the date of the current version. For a material change, we announce it on this site before it takes effect.
How to contact us and how to complain
For anything in this policy, including a rights request, email samzsakerz@gmail.com.
If you are unhappy with how we handled your data, tell us first. If that does not resolve it, you can complain to the data protection authority in the country where you live.