Privacy
What PlexusX stores, what leaves your machine, and what never does.
ČeskyPlexusX — Privacy
Last updated 2026-11-21. Controller: Lucie Uhlířová, IČO 74213873. Address: Operator & legal details. Contact: support@plexusx.lol.
This describes what PlexusX actually does, written from the code rather than from a template. If you find something here that does not match the application's behaviour, that is a bug and we want to hear about it.
There are two halves to it: the application on your PC, and the website at plexusx.lol where you sign in and buy. They store different things, and both are described.
The short version
The application never sends us what you do with it on its own: never your settings, your colours, what you play, or anything on your screen. After a crash that closes PlexusX it asks whether to send us the crash report, and sends it only if you press Yes. Other errors are only written to the crash folder. A bug report you choose to send is an exception: it includes your current saturation setting.
It does talk to our server, plexusx.lol, on its own. It checks for updates and installs
them, checks that your version and your licence are still allowed to run, and fetches the
shared looks and crosshairs for the Library. While a licence is on your PC, it also checks in
with us about every two minutes, so the server can confirm what your plan includes. That
check-in names your licence and your PC. Each of these is listed below, with exactly what it
sends.
Rating an update is switched off in this version. The What's New window offered a thumbs up and a thumbs down; it does not, in the build you are running, and nothing about an update is sent. The section below says how it would work if it is ever switched back on, because a policy that quietly drops a paragraph is harder to trust than one that says what changed.
It does have an account, because that is how a licence reaches your machine. Signing in happens in your browser. You sign in again when you release or move a PC, or first use the Dark Boost week buttons in a run. After that PlexusX checks your licence on your own computer, and the plan check-in keeps what your plan unlocks up to date.
Part one — the application
What is stored on your PC
| What | Where |
|---|---|
| Your colour settings, theme, hotkeys, crosshair, window position | %APPDATA%\PlexusX\settings.json |
| A spare copy of your settings, used if the main file is damaged | %APPDATA%\PlexusX\settings.bak |
| A copy of the picture or GIF you chose as the application's background | %APPDATA%\PlexusX\background.png, background.gif, background.jpg, background.jpeg, background.bmp or background.webp |
| The shared looks and crosshairs the Library last showed you | %APPDATA%\PlexusX\community-presets.json |
| Your licence | %LOCALAPPDATA%\PlexusX\licence.dat |
| The email you signed in with, shown on the Account page | %LOCALAPPDATA%\PlexusX\account.txt |
| The plan check-in's latest signed answer | %LOCALAPPDATA%\PlexusX\entitlement* |
| Per-game colour profiles | %LOCALAPPDATA%\PlexusX\profiles.json |
| Cached status, switch and revocation checks | %LOCALAPPDATA%\PlexusX\*.json |
| The start time of this run, removed on a clean exit so the next start can spot an interrupted run | %LOCALAPPDATA%\PlexusX\running.marker |
| Update installers and unfinished downloads. On a later start, PlexusX removes those for its version or older. Uninstalling does not remove them | %TEMP%\PlexusX-Setup-*.exe and %TEMP%\PlexusX-Setup-*.partial |
| Crash reports: the error and stack trace, versions of PlexusX, Windows and .NET, the program file's hash, and resource use. No file size cap. At startup, files older than 30 days and all but the newest 50 are deleted. Only the crash report you agree to send is uploaded | %LOCALAPPDATA%\PlexusX\crashes\crash-*.txt |
| Failed licence checks. No size cap or automatic deletion. Never uploaded by the application | %LOCALAPPDATA%\PlexusX\crashes\license-fail.log |
| Failed sign-in steps, error chains and socket errors. No size cap or automatic deletion. Never uploaded by the application | %LOCALAPPDATA%\PlexusX\crashes\signin-fail.log |
| NVIDIA driver failures and the switch to software colour. No size cap or automatic deletion. Never uploaded by the application | %LOCALAPPDATA%\PlexusX\crashes\nvapi-fail.log |
| Custom resolution steps and refusals. No size cap or automatic deletion. Never uploaded by the application | %LOCALAPPDATA%\PlexusX\crashes\custom-mode.log |
| Skipped startup steps and why, including pins that could not be fixed. No size cap or automatic deletion. Never uploaded by the application | %LOCALAPPDATA%\PlexusX\crashes\startup-skipped.log |
| A difference between the running program's hash and the published hash. No size cap or automatic deletion. Never uploaded by the application | %LOCALAPPDATA%\PlexusX\crashes\update-integrity.log |
Only with --trace-colour: colour drawing methods, full-screen state and counts and timings of colour writes. Replaced each minute, with no size cap or automatic deletion. Never uploaded by the application | %LOCALAPPDATA%\PlexusX\crashes\colour-trace.txt |
| A log of what Hold to zoom did: its key being set or cleared, each press and release, a press it ignored and why, and how Windows answered. Nothing in it says who you are. On the next write after it passes 128 KB, it is cut to its last 64 KB. There is no automatic deletion. It is never uploaded | %LOCALAPPDATA%\PlexusX\logs\zoom.log |
| A log of when the screen colour effect is held or released, with the time and saturation. Nothing in it says who you are. On the next write after it passes 256 KB, it is cut to its last 128 KB. There is no automatic deletion. It is never uploaded | %LOCALAPPDATA%\PlexusX\logs\screen-effect.log |
| Crosshair images you import | %LOCALAPPDATA%\PlexusX\crosshairs |
| Your random installation id and private signing key, encrypted for this Windows user. This file and the private key are never uploaded | %LOCALAPPDATA%\PlexusX\installation.dpapi |
| Screenshots you take with the screenshot key | Pictures\PlexusX |
The Dark Boost free week leaves dark-boost-free-week.json in the licence folder on your
PC. It holds the licence serial, whether the week was used, and its end date. Whether your
account has already used the Monthly trial is recorded with your account on our server,
not on this machine. With an account, saturation and the Resolution tab are free, and a
plan you buy is held with your account.
Uninstalling removes the application. To remove the data as well, delete the two PlexusX
folders above and the Pictures\PlexusX folder if you have taken screenshots.
Update installers and unfinished downloads can also remain in %TEMP%, as the table says.
Settings PlexusX changes on your PC
The Customize tab changes how PlexusX itself looks: its colour mode, background picture,
backdrop, dim, blur and window opacity. These are saved in settings.json.
It does not change Windows' appearance settings in the registry.
If an older version saved a taskbar tint, PlexusX reapplies it while running.
The tray's Reset taskbar turns it off. The Store version never changes the taskbar.
If Start with Windows is on, PlexusX adds itself to
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run. Turning it off removes
the entry. Turning it on also enables PlexusX in Task Manager's startup list if you had
switched it off there, using StartupApproved\Run. Turning it off leaves that value alone.
At launch, PlexusX repairs its own existing Run entry if the path is wrong. When that entry belongs to this copy, it also removes the old VibranceHud entry even if its program still exists. Otherwise it removes the old entry only if its program is gone. Uninstalling removes both Run entries.
At startup, the installed copy reads the taskbar pins in
%APPDATA%\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar.
It points a PlexusX pin at this copy if its program is gone, or if it points to an older copy
in this install folder. Pins to another PlexusX product or other programs are left alone.
A pin it cannot fix is noted in startup-skipped.log.
The installer registers plexusx:// links under HKEY_CURRENT_USER\Software\Classes\plexusx,
with an icon and command pointing to PlexusX.exe, so website setup links open in the app.
Uninstalling removes that entry. Setup also adds a Start menu shortcut and, if you tick its
box, a desktop shortcut.
The Resolution tab can save a display mode in Windows' display settings. A custom resolution you keep is saved in the NVIDIA driver, with full-screen GPU scaling. These changes stay after PlexusX closes.
What leaves your machine
Checks that run on their own. Each goes to plexusx.lol, apart from the one rare case
named in the first. The first three carry nothing that names you: not your account, your
licence or your PC id. The Library also names your licence and PC while a licence is installed. The update and status checks do name the version of PlexusX you are
running, and the status check also names which kind of build it is, which is how we know how
many copies of each version are still in use. The server sees your IP address, as any server
does for any request. The fifth is how your plan reaches the application, and it does identify
your licence.
- Update check — when PlexusX starts, and every two hours while it runs, it asks whether
a newer version exists. If one does, PlexusX downloads it, checks it is exactly the file we
signed, and installs it by itself: straight away while it is starting, or later at a moment
when nothing is running full screen. The What's New window then says what changed. Its text
is built into the application; only a build that shipped without it would read it from
GitHub's public API (
api.github.com) instead, naming the version and nothing else. - Status check — when PlexusX starts, and every two hours while it runs: the oldest version still allowed to run, any build we have stopped, any part of the application we have switched off for everyone, and any notice we want to show. It is how you are told when an old build has been retired.
- Licence revocation list — when PlexusX starts, and every five minutes while it runs, so a licence that has been withdrawn stops working. The list contains only one-way hashes, never anybody's licence key.
- The Library — when PlexusX starts, and every three hours while it runs, it asks for shared looks and crosshairs. While a licence is installed, it sends the licence serial, your PC id, the build id (a hash of the program file) and the application version. It also sends the installation proof described below. Without a licence, it downloads the public list and sends only the application version, with no licence, PC id or installation proof.
- Plan check-in —
plexusx.lol, only while a licence is installed: when PlexusX starts, straight after you sign in or enter a key, and then about every two minutes while it runs. It sends your licence key, your PC id, the application's version and build, and a fingerprint (a one-way hash) of the program file, so the server can say which features your plan includes on this computer. It also checks when you switch back to PlexusX, at most once every two minutes, unless an answer was just kept. If paid features are not already on, it asks again when Windows says the network is back or has changed. It asks after your PC wakes. During the first minute after a start or wake that could not reach us, it makes quick retries, with waits of about 3, 6, 12 and 24 seconds. It also sends the second hash described under Your PC id, which our server does not keep. If it kept paid features on while it could not reach us, it sends agracereport: how long ago that time ended and how long it lasted. It repeats this until it keeps an answer. Each check-in carries a random one-timechallenge, so the app can tell the answer belongs to this request. The server sends that code back in its signed answer and does not store the challenge itself. We keep a note of check-ins for 30 days: a one-way hash of the licence key, the version and build type, a code for which features were granted, the program file's fingerprint, and the time. Successful check-ins with no change are noted at most once per half hour per PC. Refusals, changes and check-ins with a grace report are noted each time. That fingerprint is the same for every unchanged copy of one release, so on its own it tells us which build checked in, not who you are. It lets us count changed copies of PlexusX that run under a real licence. A grace report is kept with a hash of the licence key and PC id, its start, end, length, version and report time, for 30 days after that time ended. Each signed answer also leaves a random answer code, hashes of the licence key and PC id, the names of the granted features and its time, for about 25 hours. Invite-week checks also use these records to see whether a PC was used before. A separate record keeps the two hashes, version, build type, program fingerprint, feature code and time for about two hours, to avoid counting unchanged check-ins twice. If an active licence is no longer bound to a PC, a check-in can bind it to the asking PC and record the activation time. A free Dark Boost week must be activated separately first.
The plan check-in, Library requests with a licence, licence key activation and renewal, and the app sign-in for invite week also carry an installation proof: a random installation id made on this PC and a signature proving the request came from this installation. It includes the time and a fresh random code for each request. If the saved installation key is missing or cannot be read, these requests go without the proof. Signing in to activate also sends the installation id, signature and public key, as listed below. The private key stays on your PC. A valid request proof also leaves the installation id and the request's random code on the server, until just over two minutes after the request time, to stop the same proof being used twice.
Reporting a bug
Settings has a box for reporting a bug. Nothing is sent until you press Send. Then
PlexusX sends plexusx.lol what you typed, the email or Discord name you put in the contact
box if you filled it in, the PlexusX version and build type, and these technical facts: your
Windows version, the make of your graphics card, how many monitors you have, whether HDR is
on, whether NVIDIA's own vibrance is available, whether PlexusX is running as administrator,
how each monitor answered PlexusX's colour, which way PlexusX is drawing colour, whether a
game ran in exclusive full screen, and how often and how slowly PlexusX has re-applied your
colour. It does not send your account, your licence key or your PC id.
It also sends your current saturation setting, whether the screen colour effect is held,
how Windows handled the colour ramp and the gamma range Windows allows.
Each monitor's Windows device name goes with its colour result.
Our server drops the saturation, held-state, ramp-result and gamma-range fields and does not keep them.
The report is stored on our server with the time, version, text, contact if you gave one, and the technical facts the server accepts. It reaches the developer as a private Discord message. It also has a code made from your IP address, the request's browser-style identifier, the day and a secret. That code changes every day. A separate flood limit keeps your full IP address for up to 24 hours. Bug reports have no automatic deletion yet.
Free weeks of Dark Boost
The Dark Boost page talks to plexusx.lol when you use its week and invite buttons.
The first use in a run asks you to sign in in your browser. It keeps that sign-in token
in memory for later requests, and asks again if the server says to sign in again.
Each request sends that token. Free week and Get my week ask for a week.
Opening your invite asks for your invite code and how many friends have counted this month.
Using a friend's code sends that code, your PC id, the second hash described below and the
installation proof. It asks for the invited week and sends the app sign-in again after a grant.
When a week is given, PlexusX checks in again at once. If this PC holds only the free plan or an earlier week, it first activates the week on this PC, which sends what Activating a licence lists. The Lifetime Free week only checks in.
Checking the program on VirusTotal
Settings shows a fingerprint of the PlexusX program file. Check on VirusTotal opens
www.virustotal.com in your browser at the page for that fingerprint.
VirusTotal sees your IP address and that fingerprint. The fingerprint is the same for every
unchanged copy. This happens only if you press the button.
Signing in
When you press Sign in, PlexusX opens your browser and starts a short-lived web server on
127.0.0.1 — your own machine, reachable only from it — so the browser can hand the result
back to the application. It closes as soon as you are signed in, or after five minutes if
you never finish. Nothing else can reach it and it is not open to the network.
Controlling PlexusX from your phone
This one is open to your home network, which is the whole point of it, and it is the only part of PlexusX that ever is. It is off until you open it, and it exists only while that window is open.
When you press Phone on the Display page, PlexusX starts a small web server on this computer and shows a QR code containing its address and a one-time key. Then:
- It only starts when you press that button. Nothing is listening before you do, and closing the window stops it immediately.
- A fresh key every time. Scanning an old code does not work.
- It only answers your own network. A request from anywhere other than this machine or the network the code advertised is refused, as is any request without the key.
- Nothing leaves your house. Your phone talks to this computer directly. No part of it goes to us or to anybody else, and we never learn that you used it.
- It only changes colour. Saturation, vibrance, brightness, gamma, contrast, temperature, highlights, shadows and the scene presets. Nothing else on the machine can be reached through it.
Windows will ask whether to allow PlexusX to use the network the first time. That prompt is this feature, and nothing else in PlexusX needs it.
Discord
If the Discord app is running on this PC, PlexusX shows "PlexusX" as your activity on your Discord profile, with the preset you picked, which can include the game's name. PlexusX hands this to your own Discord app on this computer, and Discord shows it to the people who can see your activity, the same way it does for a game. None of it comes to us. Discord's own settings decide who can see your activity. This is on when you first install PlexusX. To turn it off, switch off Show PlexusX on my Discord profile in Settings.
Activating a licence
Once you are signed in, the application asks plexusx.lol for a licence for this computer.
It sends the following when you activate, and again when PlexusX renews a licence that is
about to run out:
| What | Why |
|---|---|
| If you signed in: proof of that sign-in. If you typed in a licence key, or PlexusX is renewing the licence already on this PC: that licence key | To look up which licence you are activating |
| Your PC id — the truncated hash described below | So the licence issued back is bound to this computer |
| A second hash, of your PC's hardware without the computer name (described below) | It is meant to let our server see that this is still the same PC after a Windows reset gives it a new name. Our server does not use it for that yet, and does not keep it |
| The application's version number | So a licence issued for a newer scheme is not sent to an older build |
| A random installation id made on this PC and a signature proving the request came from this installation; its public key when you activate by signing in | To prove this installation made the request. The private key stays on your PC |
It sends no settings, no colours, no user name, and no hardware details beyond these two hashes. What comes back is your signed licence file, stored locally. From that point on PlexusX checks it on your own machine, alongside the plan check-in above.
Releasing or moving a PC. If you press Release this PC or Move it here, you sign in
first, and the application sends your licence key together with that sign-in to
plexusx.lol, so a machine is unbound only on the word of the account that owns the licence.
With the same sign-in it first asks plexusx.lol which licence your account owns, and whether
it is on a PC, so it never releases a licence that is not yours or one that is already free.
Move it here then activates this computer, as above.
Your PC id
Your licence is tied to one computer. To do that, PlexusX computes a one-way SHA-256 hash of three things:
- your CPU's identifier,
- your first disk's serial number,
- your Windows computer name.
The hash is truncated to 16 characters and shown to you as your PC id. The three inputs are never written to disk and never sent anywhere — only hashes of them exist, and a hash cannot be reversed back into your computer name or your hardware.
PlexusX also makes a second hash the same way, from only two of those things: your CPU's identifier and your first disk's serial number, without the computer name. It is also cut to 16 characters. It is sent with your PC id when you activate or renew a licence, when you use a friend's code on the Dark Boost page, and with the plan check-in. It is left out if PlexusX cannot read your CPU or your disk. It is meant to let our server see that a PC is still the same one after a Windows reset gives it a new name. Our server does not use it for that yet, and does not keep it.
The PC id leaves your machine when you activate or renew a licence, when you use a friend's code on the Dark Boost page, and with the plan check-in and Library requests while a licence is installed. The plan check-in runs in the background while a licence is installed (see Checks that run on their own); the update, status and revocation checks do not send the PC id. It is embedded in the signed licence so the application can check it is running on the right computer.
Because the computer name is part of the input, renaming your PC changes your PC id, as does changing your CPU or boot drive. If that happens, press Move it here in the application, or release the licence from your dashboard and activate again. Renaming your PC does not change the second hash, but our server does not use it yet, so you still need to do this.
Crash reports
When PlexusX crashes it writes a plain-text file locally containing the error, the stack trace, the application, Windows and .NET versions, the program file's hash, and resource use: GDI and USER objects, handles, private memory in MB and minutes since start. It removes matching user paths, licence serials, PC ids and email addresses before writing, and redacts the crash report again before sending. It also replaces Steam and Epic path markers.
Nothing is sent unless you press Yes in the question after a crash. Then PlexusX sends that crash report with a short heading, limited to 2,000 characters, plus the application version, build type and Windows version. It sends no contact details. It uses the same route as a bug report from Settings, so the server keeps it and passes it to the developer in a private Discord message, as described under Reporting a bug. It does not attach any of the other log files listed above.
A separate file records failed licence checks. It is not uploaded by the application. The files are plain text, so you can read them on your PC.
At startup, PlexusX deletes crash-*.txt files older than 30 days and keeps at most the newest 50.
The other logs have no automatic deletion, as the table above says.
Screenshots
PlexusX has a screenshot hotkey, because an ordinary screenshot does not capture the colour
changes you are looking at. It only fires when you press that key. The image is written to
Pictures\PlexusX and copied to your clipboard, and that is the end of it — it is never
uploaded.
Settings also has Test my recording setup. After you agree to run it, it reads the desktop several times to measure how colourful the captured picture is. It keeps the measurements, not the pictures, and puts a text report on your clipboard. It does not save or upload it.
Which games you have
PlexusX looks for installed games so it can offer you per-game profiles. It reads Steam's
registry entry for its install path and then Steam's local library folders on your own disk.
It also reads Epic Games install files (*.item) in
%ProgramData%\Epic\EpicGamesLauncher\Data\Manifests to find Epic-installed games.
That list stays on your machine and is never sent anywhere.
Rating an update — NOT ACTIVE IN THIS VERSION
The version you are running does not ask this and does not send it. The window has no thumbs and no box, and there is no code path from it to the internet.
What follows describes the feature as it is built and as it would behave if it were switched back on. It is written here in advance rather than afterwards: a rule that exists before the feature does is a rule the feature has to be built to.
After PlexusX updates itself, the What's New window asks whether the update was any good. Two buttons and an optional box for what you would change.
This would be the only thing the application sends that is about your opinion rather than your licence, so the rules around it are narrow on purpose:
- It is sent only if you choose one and press OK. Opening the window sends nothing. Closing it, with the X or with Escape, sends nothing. Typing in the box and then closing sends nothing. Pressing the same thumb twice unchooses it.
- It carries nothing that identifies you. Not your account, not your email, not your licence, not your PC id. The message is three things: the version number, the word "up" or "down", and your note if you wrote one.
- You are counted once per release. To stop one machine voting a hundred times, the server keeps a code made by hashing your IP address and browser-style identifier together with the day and a secret. It cannot be reversed, your IP is never stored, and the code changes every day — which is also why it cannot be used to follow you.
- If it fails to send, nothing happens. No retry, no error, no queue on your disk.
What the application never collects
No browsing history. No keystrokes. No screen contents outside the screenshot key and the recording test you choose to run. No advertising identifiers. No profiling, and no automated decision-making.
If you installed PlexusX from the Microsoft Store
The Microsoft Store version works the same way, with these differences:
- Updates come from the Microsoft Store. It never runs the update check in point 1 above, and it never downloads or installs an update itself.
- The Store download is covered by Microsoft's own privacy statement.
- Its files are the ones in the table above, in folders called
PlexusX Storeinstead ofPlexusX. Screenshots still go toPictures\PlexusX. - Start with Windows uses Windows' own list of startup apps, not the Run key. You can also switch it off in Task Manager.
- The status check (point 2) also says that it is the Store version.
- It never changes your taskbar.
Part two — the website
Signing in, buying and managing your licence happen at plexusx.lol. That is a server we run, so unlike the application it does hold data about you.
What the account holds
You need to give us your email to have an account and to buy; everything else is optional.
| What | Why | Kept |
|---|---|---|
| Your email address | It is your account | Until you delete the account |
| When you confirmed you are 15 or older | To record your answer when the account was made | Until you delete the account |
| A hash of your password, if you use one | To sign you in. Never the password itself | Until you delete the account |
| Your Discord or Google user id, display name and avatar, if you sign in that way | To recognise you on the next sign-in | Until you delete the account |
| Your licence: its key, plan, expiry, and the PC id it is bound to | It is what you bought | Until you delete the account |
| Your Discord user id and the time, if you check your key with our Discord bot | To keep that key from being claimed by a different Discord member | With the licence record |
| Stripe's customer id | To use the same payment customer for this account | Until you delete the account |
| Dark Boost & Zoom free weeks: which kind, when they began and ended | To record which free weeks the account has used | Until you delete the account, including after a week ends |
| The network the licence last activated from, and the application version | To spot a key being shared across many machines | With the licence record |
| If we switched an extra feature on for your account: a note of which feature, which account, and the date | So your PC gets that feature when it checks your plan | Until we take it off your account, or you delete the account |
| Your choice on the offers box when you made the account, which wording of that box you were shown, and when you were asked (on our older forms: the offers switch, the email switch, or whether you ticked "Don't send me offers") | So we keep to your answer, and can show which notice you saw | Until you delete the account |
| If you came through a creator's link: that creator's code, the terms it carried on that day, and the time | So the sale counts for the creator who sent you | Until you delete the account |
| Full IP addresses, and for some actions your sign-in email, account id or Discord user id, a one-way hash of your licence key, email or IP address, or your app's installation id, with the action, count and time | Rate limiting - to stop password or key guessing and floods of requests | 24 hours after the counter is created |
| A session cookie | To keep you signed in for twelve hours | Twelve hours |
Your full IP address is not kept with your licence. It is cut down to its network before
it is stored — 203.0.113.47 becomes 203.0.113.0/24 — which is enough to notice one key
being used from several places, and not enough to point at a household. The same cut IPv6
addresses get, at /48.
If you join the waitlist we keep the address you gave and when you joined. A waitlist email is sent when you join. Nothing sends a later launch email or deletes the waitlist record automatically yet.
If you press Email me the link in the download window on your phone, we use the address once, to send you the link to our site. We do not put it on a list or send it anything else. Like every email we send, our note of the sent email keeps the address (see the table below).
Our server's logs
Like any website, ours writes logs. We keep them short:
| What | Why | Kept |
|---|---|---|
Our web server's log: the time, the page address without anything after ?, your IP address cut to its network (the same cut as the licence record), and how the server answered. No browser details: request headers are not logged | To keep the site running and spot attacks | 14 days |
| Our server's error and event log, which can include your email address or account id (for example when you reset your password) | To find and fix faults | 14 days |
Our API does not keep its own log of requests.
Who else sees it
-
Stripe processes payments; its company Link (Sold through Link, LLC) is merchant of record — it charges your card, appears on your bank statement and accounts for any VAT, while the licence itself is sold to you by us. Your card number goes to Stripe and is not stored by us. We see whether a payment succeeded and its identifier. To open checkout, we send Stripe your account email, your display name if you gave one, and your account id. We keep Stripe's customer id on your account. When Stripe provides a card fingerprint, we keep it with your checkout records. It is a code for matching the same card across accounts, not the card number. We use it to stop older subscriptions whose payments failed when a new one starts on that card, including on other accounts, and to check that an invite is from a different person. How the charge is described on your statement is shown at the foot of every page on plexusx.lol and in your purchase email. Payments taken before 27 August 2026 went through a different provider; the only payment records we keep are described in the storage table below.
-
Discord or Google, if you choose to sign in with them. They tell us your email address, your user id, your display name and your avatar, and they learn that you signed in to PlexusX. After that, your dashboard shows your picture straight from their servers, so they see that request. A bug report you send from the application also reaches the developer as a private Discord message, so Discord carries its text. A dashboard withdrawal also reaches the developer there, with your email, name, note and plan.
-
Resend sends our emails — your purchase email and licence, password resets and account messages. To do that it receives your email address and the message itself.
-
Trustpilot (Trustpilot A/S, Denmark), only for buyers whose review request we hand to it. About a week after a purchase we may ask you, once, for a review. For up to 140 buyers a month, picked only by the date of their purchase and never by how it went, Trustpilot sends that request instead of us. In some months that can be most of the buyers we ask. For that we give Trustpilot your email address, the name on your account if you typed one or your Google or Discord sign-in gave one (otherwise "PlexusX user"; never your email address or part of it) and an order reference we make for this purpose, not your payment details. Trustpilot does this for us under its data processing agreement (GDPR Art. 28): it keeps our hand-over email for 30 days and the rest for up to 2 years. If you write a review through that request, Trustpilot can show that it came from a real order and can show us the reference with it. Your review and any Trustpilot account you make are covered by Trustpilot's own privacy policy. Either way you get one review request in total, never two.
-
Hetzner hosts the server in Germany that plexusx.lol runs on, so everything in the table above is stored on their machines. They host it; they do not use it.
-
A person who helps us with the creator programme, on a page of the Creator Hub made for this work, and TikTok, Instagram (Meta) or Discord as the services that carry their messages: see Creator Hub and People who ask us about the creator programme.
We also use other service providers to run our email, customer support and business tools. They receive what that job needs. Some of these tools are run by companies in the United States. There is no advertising, and no third-party analytics or tracking on the website. Apart from the sign-in picture on your dashboard, nothing you load from us reports to Google, Meta or anyone like them.
Emails we send
- About your account and what you bought — your purchase email and licence, password resets, and messages about a payment or subscription (for example a card that was declined). These are part of the service, so they come regardless of the setting below.
- About PlexusX offers — emails about the PlexusX app itself and nothing else: tips for the free version, its paid plans and add-ons (for example what the padlocks open, or a reminder that a discount you were given is about to end), and a request to review PlexusX on Trustpilot, an independent review site. For up to 140 buyers a month, Trustpilot sends that request instead of us (see Who else sees it). When the request comes from us, we send Trustpilot nothing about you, and the link goes through our site, where we note the click, and then opens Trustpilot's page, where Trustpilot's own privacy rules apply. Nobody gets both. We send these, and have Trustpilot send its request, without asking for consent because you have an account with us (Czech Act 480/2004, section 7(3); EU Court, case C-654/23). When you make an account, the box Email me offers about the PlexusX app is ticked: untick it and we send you no offers at all (on our older forms, turning off the offers switch or the email switch, or ticking Don't send me offers, did the same). Every offer carries a one-click unsubscribe link: press it and offers stop at once, for good. Trustpilot's request carries Trustpilot's own link to stop its requests, and we hand nobody to Trustpilot who has unsubscribed from us. We cannot see who presses Trustpilot's link, so once we hand you to Trustpilot we send you no more offers; emails about your account and purchases continue. Replies to Trustpilot's request reach us at support@plexusx.lol.
We never sell your address, and we do not send anybody else's offers. Who gets it from us, and for which job, is listed under Who else sees it.
We keep a note of each email we send: when, which kind, and the address it went to. We use it to count how many emails go out each day.
Counting
We do keep our own counts, on our own server, so we know whether the thing works: a page opened, a download started, an account created, a licence activated on a PC, a waitlist signup. No third party is involved and no cookie is set for it. We also count your answers to the two questions after a download (which games you play and what bothers you), pricing and FAQ clicks, steps through the site, which of our links sent you, and which recognised AI assistant or search engine sent you, under the same daily-changing key.
Visits are counted under a key made by hashing your IP address, your browser's user-agent string and today's date together with a secret. The raw IP address is never stored in these counts, the hash cannot be reversed back to you, and the key changes every day — so the counts cannot be joined up into a history of one person. Activations are counted under a hash of the PC identifier described above instead.
Creating an account is counted against your account id. That event goes when your account goes. A refused licence activation also records your account id, reason, response status, app version and whether installation proof was sent. These refusal records have no automatic deletion yet and stay after you delete the account.
Our visit counter. We also run a small visit counter of our own, on our own server. When you open a page, it sends the page address, the address you came from, your screen width, your time zone and the name of the event (for example "pageview"). It does not load at all on a page whose address carries a private code, such as a password reset, an unsubscribe link, a checkout or the app's sign-in, or when the page before it carried one. It also sends nothing when you move to such a page inside the site. It stores nothing in your browser, and if your browser sends Do Not Track or Global Privacy Control, it sends nothing at all. Its records are kept 90 days. Speed measurements (web vitals) are switched off.
How many people are on the site right now. While a page of ours is open and in front of you, it says "still here" to our server every twenty seconds, along with which page you are on. Nothing is written to your device — no cookie, no storage, nothing that survives you closing the tab.
To avoid counting one person as several, the server groups those messages by a short code it works out from your network address and your browser's description of itself, mixed with a secret of ours. That code is one-way: it cannot be turned back into either of the things it was made from, and it cannot be worked out in advance without the secret. The presence record is deleted after one minute. A separate flood limit stores your full IP address for up to 24 hours. Browser error reports, pricing clicks, site steps and the after-download answers use that flood limit too.
Pressing refresh does not add a second visitor, and neither does opening the same page in a new tab. What we still cannot do is tell who you are, connect today's visit to yesterday's, or follow you anywhere.
Totals we show on the site
Two lines on plexusx.lol are counted from our own order records. Both show a number about the shop and nothing about any person: no name, no email, no country, no amount.
- How many people bought Lifetime. Rounded down to the nearest ten, and not shown at all below 50. Refunds, test purchases and our own accounts are left out.
- Bought in the last 3 days. How many orders came in over the last three full days, and how many of them were Monthly and how many Lifetime. It appears only once we switch it on; until then nothing is recorded for it. Once it is on, the site keeps a short note of each new order for it — which order and payment it was, the account, the plan and when it was paid — and deletes that note within four days, or at once if the order is refunded, disputed or withdrawn, or the account is deleted.
Reviews and shared looks
If you post a review, or share a look or a crosshair in the Library, part of it is public: your display name, what you wrote, the look itself, the picture if you added one, and the date. Your email address and your account are not shown.
Your display name is the name on your account. If you signed up without giving one, it is the part of your email address before the @, or the name Discord or Google gave us.
A look stays up until you delete it from your dashboard or delete your account. A review stays until you delete your account, or ask us to take it down.
If you report a look, we keep your report: your account, the reason you picked, what you wrote and when. We use it to decide, and to tell you what we decided. It is kept until you delete your account. A report you send by email is kept like any other email to us (below).
If we refuse or take down your look or review, we keep a note of what we did and why, and show it to you in your dashboard. The note goes when the look or review goes.
Creators
If you are one of our creators, we keep your creator code, your name, how to reach you, your channels, your commission and the discount your code gives, and the payouts we have recorded, with their amount and date. We count the sales made with your code from our sales ledger. We need all of this to pay you. Nothing deletes it automatically yet.
Creator Hub
If you join the Creator Hub, we keep your application, linked account details, submitted original videos, post links and titles, briefs, publication dates and view checks. We make thumbnails and file/similarity fingerprints to help review originality. We also keep review decisions and reasons, corrections, appeals, drafts, completed lessons, rank progress and filming-access periods. These records support the programme, reviews, access and commission. A similarity flag is not proof of copying; a manager reviews the evidence.
A person who helps us with the programme may message you from their own account on TikTok, at the handle you gave in your application (on another platform only at an account you gave us yourself), to tell you where you stand in the programme (for example that your first video is still missing or came back with a note) and what the next step is.
They write only to a channel we have confirmed is yours (until then we may ask you about it in the hub), and only after we have chosen to show you to them. They see you on a page of the Creator Hub made for this work. It shows them only a case number, your public channel handle, the step you are at, the end date and target of your current hub period, a reviewer's note if your video came back, and which of our standard messages is due; it never shows your name, email address, videos, views or money. On that page they mark when they sent a message and, if you answer, the closest reason from a short fixed list (for example that you do not know how to record the colours); if you look younger than 18, they press one button that hands you back to us, and you leave their page. We keep this under a number instead of your name. We count these reasons, without names, to see what to fix in the programme. The page also shows them totals that name nobody, for example how many of the creators they wrote to sent us a video afterwards; a small total can still tell them whom it is about. They act only on our written instructions and have no manager access: they cannot see your email address, your private messages to us or your payouts. Apart from that page, they see in the hub no more than every creator sees, and they do not use it for these messages.
Unless you answer, they send no more than two messages. Say stop and they stop; your hub works as before. We then keep on our "do not write" list your handle, the date, your account id (so that the stop still holds if you change your handle) and whether the stop was entered by the person who helps us or by us. Don't want these messages at all? Write to support@plexusx.lol or in the message box on your hub's Earnings page, and nobody will send you these messages. TikTok, Instagram or Discord carry these messages under their own privacy rules.
If you add payment details, we store your chosen payout method, account holder's name and account country, plus the details that method needs: for a bank transfer your IBAN and optional BIC/SWIFT code; for Revolut your Revolut tag; for a gift card the brand you chose (from a list we maintain) and the email address the card should be sent to (your account email unless you enter another). The payment-details record is encrypted in our database. After you save it, the hub shows you only a shortened version (for example the last four digits of an IBAN). Authorised programme managers can see the full details in order to send your payment; other creators cannot see them.
We store your private panel messages with their sender, role and time so you and programme managers can discuss your work and payments. Message text is stored as readable text in the database, not encrypted like the payment-details record. This is not end-to-end encrypted messaging. Keep bank details in the payment form rather than messages.
The shared Creator chat is visible to accepted creators and programme managers. We store message text, the sender's account identifier and display name or channel handle, role, time, and each participant's last-read position. It does not expose email or bank details. Chat messages are readable in the database and are not end-to-end encrypted. The author or a manager can remove a message: its text is cleared from the active room, while sender, time, removal and retry records remain. Earlier backups can still contain the text until they rotate. Do not post bank details or other private information in the shared room.
Managers arrange and send payments separately, by bank transfer, Revolut or gift card. The hub records the amount, reference, date, recording manager and any note; it does not execute a payment. A payment marked as sent is the manager's record, not confirmation from your bank, Revolut or the gift-card shop.
Once a month we email the programme owner a list of the payments that are due, so they can be sent. For each creator it shows the name, creator code, amount and where the payment goes: a bank number shortened to its last four digits, or the Revolut tag or gift-card email in full. It is sent through Resend like our other emails and stays in the owner's mailbox as the record of what was paid. Nothing deletes it automatically yet. The full bank details stay in the manager view.
You and authorised programme managers can see your submitted files, review feedback, payment details and private conversation. Other signed-in hub participants can see the internal leaderboard: your display name, channel handle, rank, progress, approved-video count, checked views and commission tier. It does not show your bank details, messages, uploaded original files or payout amounts.
A public Creator League, if offered, is separate and optional. With your permission, it can show your chosen pseudonym, position and eligible sales count. Public display does not include your email, bank details, private messages or earnings amounts. Withdrawing public-display permission does not end your private programme participation or remove money already earned.
If you connect TikTok, TikTok asks permission to share account and video information. We store the linked account identifier, granted permissions, connection/expiry times and encrypted access and refresh tokens to check the account and its posts/views. The connection does not publish videos for you. TikTok operates under its own privacy policy.
Disconnecting removes the active connection and its tokens from our hub. We also ask TikTok to revoke access; if that fails, remove the app in TikTok's connected-app settings. Disconnecting does not erase earlier submissions, view evidence, reviews or private backups.
To check views when your account is not connected, we read the view count from the public page of each video you submitted on TikTok or YouTube - the same number any visitor sees. We store the number, the time we read it and that it came from the public page ("public"). If YouTube only shows a rounded number (for example 27.6M), we show it to you as approximate and do not use it for rank or commission.
Hub records, including payment details and messages, are not automatically deleted when participation ends or the website account is deleted. Our record of creator programme messages is the exception: we delete it within one month after you leave the programme (see How long we keep it). Ask support@plexusx.lol for access or erasure; separate hub records, payment records and backups require operator handling. We will explain what can be removed and any records that must be retained. Saving a new draft replaces the previous draft; successful submission removes it. Unmarking a completed lesson removes that completion record.
Private hub backups contain its database, including encrypted payment details and connection tokens, readable messages, and submitted originals. These archives do not include the encryption keys. When backup maintenance is enabled, it retains seven owned archives by default and removes older ones only after a new backup is verified. There is no guaranteed automatic erasure date while maintenance is disabled or failing. Erasure requests require operator handling of backup copies too.
Add smoothness runs on your PC. The downloaded Finisher does not send us the video you choose for processing. Setup downloads the official Blur installer. Sending an original to the hub for programme review is a separate action.
People who ask us about the creator programme
We do not send a first message about the creator programme to creators who have not contacted us. If you ask a person who helps us with the programme about it before you have joined, they answer you from their own TikTok, Instagram or Discord account and say that they write for PlexusX. If you write to support@plexusx.lol, we answer you from there. If you e-mail that person, they only point you to support@plexusx.lol and delete your e-mail.
To answer you, they look at your public profile and public videos and note in a table we keep: your public channel handle, where and when you wrote, which of our standard answers they sent, and your reply. That comes from your message and your public profile. We do not note your age, your email address or links to your clips, and we do not copy your videos. One exception: if you tell us you are 16 or 17, we note that, because a parent or guardian must agree before you join. TikTok, Instagram or Discord carry the messages under their own privacy rules.
We use this to answer your question about joining (GDPR Art. 6(1)(b): steps you asked for before joining). The person who helps us acts only on our written instructions. They have no manager access: they cannot see our emails, your email address, your private messages to us or anyone's payouts. Apart from a page for helping creators who have already joined, which holds nothing about people who only asked us, they see in the Creator Hub no more than every creator sees (the shared Creator chat and the internal leaderboard), and they do not use it for these messages.
If you do not apply, we delete the row by hand 30 days after the last message. The conversation itself stays in that person's inbox for up to 3 years after the last message, only as proof that you asked first, and is then deleted by hand, unless a complaint about it is still open. If you apply, the Creator Hub section above applies from then. The programme is for people aged 16 or older: if you are younger, we only tell you so, keep nothing about you and delete the conversation.
Say stop, in the chat or to support@plexusx.lol, and nobody writes to you about the programme again. To make sure of that, we keep only your handle or email address, the date and the word "stop" on a "do not write" list (our legitimate interest, Art. 6(1)(f)); if you have been accepted into the creator programme, the list keeps a little more, see Creator Hub. We keep that list while we run the creator programme and delete it by hand when the programme ends.
Invite week
Invite week: when you use a friend's code on the Dark Boost page, or when any free Dark Boost & Zoom week (an invite week, the inviter's week or a Lifetime week) is first activated on a PC, we keep a one-way hash of that PC's id as an 'already seen' marker. The marker is not linked to your account. We use it only to stop one PC getting more than one free week, and we delete it after 24 months. While an invite is being checked, a copy sits on that invite for up to 45 days. The same app sign-in also records your account id and the first sign-in time for this invite system. That record, your invite code and invite links are deleted with your account.
Withdrawals
If you use Withdraw from contract on your dashboard, we keep what you sent: your name, your note, your email address, your account, your plan and the time. We email a copy to you and one to ourselves, and we note what we decided. Your email, name, note and plan also reach the developer in a private Discord message. We keep it as a record of what you asked and what we did. Deleting your account does not delete it, and nothing deletes it automatically yet.
Discord bot forms and prizes
If you use our Discord bot's lag/FPS, paid-but-locked, bug, refund or suggestion forms, we store your Discord user id, Discord name, your answers (including an email you type), the time and the report's status. The refund form keeps the email and reason you type. The bot tries to post your suggestion in our Discord with a +1 button for other members, with email addresses removed. We keep the Discord user ids of members who +1 it. For a locked-out report, we also keep whether that email has a live licence and its plan. A giveaway prize claim keeps your Discord user id, the email you typed, your account id, the giveaway, claim time and prize status. Neither has automatic deletion yet, and these records stay after you delete your account.
Email to support@plexusx.lol
When you email support@plexusx.lol, your email stays in our support mailbox, which our email provider hosts for us. We also keep copies on our own computers to answer you. Nothing deletes either automatically yet.
Lock clicks
If you press a padlock in the application, it opens our site. If you are signed in there, we note which paid feature you pressed, and when. A day later we may send you one email about that feature. It is an offer, so the rules above apply: it carries the unsubscribe link, and you do not get it if you unticked the offers box (on our older forms: turned off the offers switch or the email switch, or ticked Don't send me offers) or unsubscribed. We delete the note 7 days after you pressed.
Cookies, and everything else kept in your browser
This is everything the site can put in your browser. Some of it appears as soon as you arrive through a certain kind of link. "This tab only" means it is gone when you close the tab.
| What | When it appears | How long | What it is |
|---|---|---|---|
access_token | When you sign in | 12 hours | The cookie that keeps you signed in |
plexusx.ref | When you open a creator's link (one with ?ref= and a creator code) | Until you are signed in and our server has read it | The creator's code, waiting for an account to attach it to |
plexusx.ribbon.free-2026-09 | When you close the "PlexusX is free now" strip | Until you clear it | Keeps the strip closed |
plexusx.ribbon.halloween-2026 | When you close the Halloween trial strip | Until you clear it | Keeps the strip closed |
plexusx.mode | When you press the light/dark switch at the top of the page | Until you clear it | Whether you picked the light or the dark look |
plexusx.lock | When the application opens our site from a padlock | This tab only, and removed once you are signed in | Which paid feature you pressed, until we can note it on your account |
plexusx.fromApp | When the application opens our site | This tab only | That you came from the application, so the page remembers it after you make an account |
plexusx.from-free-email | When you arrive from one of our emails about the free version | This tab only | Which of those emails you came from, so the page keeps showing its steps |
plexusx.virusHelper.dismissed | When you close the "Is it a virus?" box | This tab only | Keeps the box closed |
plexusx:chunk-reloaded | Only if part of a page fails to load and the page reloads itself | This tab only | Stops the page reloading more than once |
plexusx-shop-section | Only on our own staff pages | This tab only | Which staff page was open |
plexusx.creator-art.current.v1 | When the Creators art playground opens or its controls change | Until you clear it | Artwork mode, density, speed, pointer response, colour and texture |
plexusx.creator-art.favourite.v1 | When you press Save favourite in the Creators art playground | Until you clear it | Your saved artwork settings for that page |
plexusx.creator-art.home-halloween.current.v1 | When the local Halloween art demo opens or its controls change | Until you clear it | The Halloween demo's artwork settings, separate from Creators |
plexusx.creator-art.home-halloween.favourite.v1 | When you press Save favourite in the local Halloween art demo | Until you clear it | Your saved artwork settings for that demo |
The first is strictly necessary — without it you cannot stay signed in. The rest only remember a step you took on the site or where you came from. None of them is used to track you, none is shared, and there are no analytics or advertising cookies at all — so there is no consent banner to click.
The site no longer keeps your look or colour slider in your browser. If your browser still
holds plexusx-theme or plexusx-vibe from an older visit, the site ignores them.
The live visitor count described above was built the same way on purpose. Had it kept an identifier on your computer, it would have needed a banner, and we would rather have a rougher number than a banner.
Fonts and everything else the page loads. Every file a page of ours needs — scripts, styles, images and all four typefaces — comes from our own servers, apart from the sign-in picture on your dashboard. Most websites load their fonts from Google or a similar service, which quietly sends your IP address to that company before the page has even finished drawing. Ours used to do that too, until 30 August 2026. It does not any more.
How long we keep it
| What | How long |
|---|---|
| Your account — email, password hash, Discord or Google id, display name, avatar, age confirmation time and Stripe customer id | While the account exists. Delete the account and it goes. |
| Your licence and the PC id it is bound to, plus your Discord user id and verification time if you used the bot | Until you delete the account |
| A note of an extra feature we switched on for your account | Until we take it off your account, or you delete the account |
| Your answer on the offers box and which wording of it you were shown (on our older forms: the offers switch, the email switch or "Don't send me offers"), and the creator's code you came through | Until you delete the account |
| Checkout records — which checkout you opened, and whether it was paid, and Stripe's card fingerprint when available | Until you delete the account |
| Our sales ledger — for each payment: the amount, the currency, the plan, the date, Stripe's identifier for it, and the creator discount if one was used | Nothing deletes it automatically yet, and it stays after you delete your account. Stripe keeps its own records under its own rules. |
| Rate-limit counters: full IP addresses, and for some actions sign-in emails, account ids or Discord user ids, one-way hashes of licence keys, emails or IP addresses, or app installation ids | 24 hours after the counter is created |
| The cut-down network an activation came from | With the licence record |
| Our web server's log | 14 days |
| Our server's error and event log | 14 days |
| Our visit counter's records | 90 days |
| Counted plan check-ins from the application — a hash of the licence key, the version and build type, a code for which features were granted, a fingerprint of the program file, the time | 30 days, then deleted automatically |
| Grace reports: hashes of the licence key and PC id, start, end, length, version and report time | 30 days after the window ended |
| Signed-answer records: random answer code, licence-key hash, PC-id hash, granted feature names and time | About 25 hours |
| Half-hour counting marks: licence-key hash, PC-id hash, version, build type, program fingerprint, feature code and time | About two hours |
| Enrolled installations: installation id, public key, account id, licence key, PC-id hash, creation and revocation times and active flag | Nothing deletes these automatically yet, and they stay after you delete your account |
| Used installation request proofs: installation id and random request code | Until just over two minutes after the request time |
| Dark Boost & Zoom free weeks: kind, start and end | Until you delete the account, including after a week ends |
| Your session cookie | Twelve hours |
| Messages you post in the PlexusX Discord server | 90 days. They are deleted automatically after that. |
| Discord bot forms and giveaway prize claims, as described above | Nothing deletes these automatically yet, and they stay after you delete your account |
| Errors your browser reports from our website: error text and stack, source, page, full user-agent string and daily-changing key | 60 days, then deleted automatically |
| Bug reports you send us from the application | While we are working on the bug. Nothing deletes these automatically yet, and saying so is more use to you than a number we do not keep to. |
| Our own counts — pages opened, downloads started | Only as counts. The key they are grouped under changes every day and cannot be turned back into you. |
| Refused licence activations: account id, reason, status, app version and whether proof was sent | Nothing deletes these automatically yet, and they stay after you delete your account |
| "How many people are on the site right now" | One minute |
| Notes kept for "Bought in the last 3 days", once it is switched on | Under four days, and removed at once after a refund, a dispute, a withdrawal or the account being deleted |
| Which paid feature you pressed in the application | 7 days |
| Looks and reviews you post, and our notes on them | A look: until you delete it or your account. A review: until you delete your account or ask us to take it down |
| Your reports of a look, and what we decided | Until you delete your account |
| A withdrawal you sent from the dashboard | Nothing deletes it automatically yet, and it stays after you delete your account |
| A creator's code, details and payouts | Nothing deletes them automatically yet |
| Creator Hub applications, originals, review/appeal evidence, access periods, progress, encrypted payment details, private and shared messages, read positions and transfer records | No automatic deletion yet. Separate hub records and backups need operator handling for erasure requests; see Creator Hub above |
| What the Creator Hub page shows the person who helps us with creators: a case number, public channel handle, programme step, period end date and target, a reviewer's note, which message is due | We give them no list and no copy outside the hub; they copy only the message they send you. The page shows you only while a message is due or for 14 days after the last one, and never after you leave the programme or say stop |
| Our record of creator programme messages on that page: date, which message, the reason you gave if you answered, the step, a mark if they thought you might be under 18, under a number without name or handle | Until you leave the programme; then we delete your rows within one month |
| Messages between you and the person who helps us, in their TikTok, Instagram or Discord inbox (accepted creators) | Until you leave the programme or they stop helping us, whichever comes first; then they delete the conversation by hand within one month |
| Someone who asked us about the programme and did not apply: public channel handle, where and when they wrote, our answer, their reply | We delete it by hand 30 days after the last message |
| The message in which someone who has not joined asked us about the programme, and our answer, in that person's inbox | Up to 3 years after the last message, or until they stop helping us if that comes first, only as proof that you asked first; then deleted by hand, unless a complaint about it is still open |
| The "do not write" list: handle or email address, date and "stop"; for an accepted creator also the account id and whether the stop was entered by the person who helps us or by us | While we run the creator programme; we delete it by hand when the programme ends |
| The "already seen" PC marker for invite week (a one-way hash of your PC's id, not linked to your account) | 24 months, then deleted |
| The copy on an invite while it is being checked | Up to 45 days |
| Your invite code and invite links, and your account id and first app sign-in time in the invite system | Until you delete the account |
| Emails you send to support@plexusx.lol | Nothing deletes them automatically yet |
| Our note of each email we send you | Nothing deletes it automatically yet, and it stays after you delete your account |
| What we hand to Trustpilot for its review request (up to 140 buyers a month): your email address, the name on your account (as described above) and an order reference | At Trustpilot: our hand-over email 30 days, the rest up to 2 years (its data processing agreement). With us: the reference and the time, in our note of the emails we send |
| Your waitlist address and join time, if you joined one | Nothing deletes them automatically yet |
Deleting your account deletes your checkout records and your licences. Our sales ledger stays after you delete your account. Enrolled installation records also stay: they include your licence key and account id. So do refused activation records, Discord bot forms, giveaway claims, a withdrawal you sent and our notes of the emails we sent you, as the table says. Everything the table keeps "until you delete the account" goes. Our daily account-database backups still hold a copy for 16 days at the most; then those backups are deleted too. Creator Hub backups have the separate rotation described above. If you ask us to delete your account, we do it for you in the same way.
Children
PlexusX accounts are for people aged 15 or older. In Czechia that is the age at which you can agree to an online service yourself; if you are younger than 15, a parent has to agree and set the account up with you. We ask you to confirm this when you create an account, and we do not knowingly collect anything from a child under 15.
Why we are allowed to use it
- To give you what you signed up for or bought (GDPR Art. 6(1)(b), a contract): the account, any extra feature we switched on for it, the licence, the PC id and the second hash of your hardware, sign-in, the plan check-in, receipts and account emails. For a creator, the same basis covers operating the programme, reviewing submitted work, handling appeals, filming access, the creator code and paying you.
- To keep a record of sales for tax and accounting law (Art. 6(1)(c), a legal duty).
- To handle reports and explain our decisions about looks and reviews, as the EU's Digital Services Act requires of us (Art. 6(1)(c), a legal duty).
- Our legitimate interests (Art. 6(1)(f)): stopping key sharing and password guessing, keeping short server logs so the site runs and attacks are spotted, counting changed copies of PlexusX that run under a real licence, counting visits on our own server, showing the sales totals above, matching the same card across accounts by its fingerprint, running the Discord bot's forms and giveaways, the waitlist, browser error reports, recording refused activations, keeping what we need to establish or defend a legal claim, answering you and your bug reports, keeping a record of a withdrawal and what we did about it, and noting which padlock you pressed and which links in our emails you clicked, to choose which offer email to send, to stop sending them, and to count how many people clicked the link to the review page, and giving Trustpilot the name on your account and an order reference with the review request it sends for us, so that it can address you and show that a review came from a real order (you can object to this at any time, free of charge).
- Creator programme messages from a person who helps us (Art. 6(1)(f), our legitimate interest in helping accepted creators finish the steps of the programme they joined): showing that person a creator's public channel handle, programme step and the other details listed under Creator Hub on a page of the hub made for this work, their reminders, the record on that page of which message was sent when and the reason a creator gave, a mark that a creator may be under 18 so that only we deal with them, counting those reasons without names to improve the programme, and the "do not write" list of people who said stop. Answering someone who asks us about joining the programme rests on Art. 6(1)(b) (steps you asked for before joining). You can object at any time, free of charge: say stop, and the messages end. Keeping the conversation with someone who asked us, for up to 3 years, rests on Art. 6(1)(f): our legitimate interest in being able to show that we wrote only because they asked.
- Offer emails to people who have an account rest on the e-mail rule for a trader's own customers (Directive 2002/58/EC, Art. 13(2); Czech Act 480/2004, section 7(3)), not on Art. 6(1): the EU Court held that Art. 6(1) does not apply to them (case C-654/23). That includes the review request Trustpilot sends instead of us: Trustpilot only carries it out for us, as our processor (GDPR Art. 28). You can object to them at any time, free of charge (Art. 21(2)-(3)): one press of the unsubscribe link stops them at once.
- If you post in the PlexusX Discord server, we read and keep copies of those messages so we can answer support questions and spot bugs (legitimate interest). Discord's own privacy policy covers everything else Discord does.
Data outside the EU
Some of the companies above (Stripe, Resend, Discord, Google) are based in, or use servers in, the United States. Where your data leaves the EU, it does so under the safeguards the GDPR requires — the EU–US Data Privacy Framework or the European Commission's Standard Contractual Clauses in each company's data processing terms. Trustpilot is in Denmark; its data processing agreement allows a transfer outside the EEA and the UK only with the safeguards data protection law requires, such as an adequacy decision or those Standard Contractual Clauses.
The person who helps us with the creator programme works only from the EU, the EEA, the UK or Switzerland. The UK and Switzerland have an EU adequacy decision, so no further safeguard is needed there.
Your rights under the GDPR
You can ask us for a copy of what we hold, ask us to correct it, or ask us to delete it. You can also ask us to restrict how we use it, to hand it to you in a machine-readable form, and you can object to any use based on our legitimate interests, and at any time and free of charge to offer emails, which stop the moment you unsubscribe. You can also delete the account yourself from the dashboard, which removes the account and its licence record.
Everything the application stores is on your own computer, and the files listed above are yours: deleting them deletes all of it.
The PC id in a licence record is a one-way hash. It cannot be turned back into your computer name or your hardware, but it does identify your installation, so we treat it as personal data rather than pretending otherwise.
To ask what we hold, correct it, or have it erased, contact us at support@plexusx.lol. We answer within one month. You also have the right to complain to a data protection authority — in the Czech Republic that is the Úřad pro ochranu osobních údajů (uoou.gov.cz), or the one where you live.
Changes
If this policy changes, the date at the top changes with it. The current version is always at plexusx.lol/privacy. The application carries the version that was current when it was built, under Settings → Legal & licences.
2026-11-21: The person who helps us with the creator programme works only from the EU, the EEA, the UK or Switzerland. The UK and Switzerland have an EU adequacy decision, so no further safeguard is needed there.
2026-11-18: For an accepted creator, the "do not write" list also keeps the account id and who entered the stop; Creator Hub, People who ask us about the creator programme and How long we keep it now say so. Creator Hub now gives an example of the totals the person who helps us sees, says that a small total can show whom it is about, and names the hub record that is deleted automatically after you leave the programme. The table now also lists the case number that page shows.
2026-11-18: A person who helps us with the creator programme may now message accepted creators on the channel handle they gave, and answers people who ask about the programme. They work from a page of the Creator Hub that shows them only what each message needs. What they see, why, and how long it is kept is under Creator Hub, People who ask us about the creator programme and How long we keep it.
2026-11-17: Trustpilot may now send our review request to up to 140 buyers a month; before, it was up to 50. So in some months most of the buyers we ask get the request from Trustpilot and not from us. What we give Trustpilot, why, and how long it is kept did not change. If you want no review request at all, untick or unsubscribe from our offers (see Emails we send).