This notice is based on Regulation (EU) 2016/679 of the European Parliament and of the Council (General Data Protection Regulation, GDPR) and Hungarian Act CXII of 2011 on informational self-determination and freedom of information (Infotv.). It describes what personal data we handle in the Longlight Online closed beta, why, for how long, who we share it with, and what rights you have.
1. The controller
Polyák Csaba, sole proprietor (Polyák Csaba e.v.)
- registered seat and postal address: 4324 Kállósemjén, Kölcsey Ferenc út 11., Hungary
- registration number: 52193909 · tax number: 68747961-1-35
- email: support@longlightonline.com · phone: +36 20 549 4107
We are not required to appoint a data protection officer, and we have not appointed one.
2. What this notice covers
- the player portal (account.longlightonline.com);
- the game running in the browser on the portal (account.longlightonline.com/play/) and the game server (api.longlightonline.com);
- emails sent to support@longlightonline.com;
- the longlightonline.com website (point 8).
3. What data, why, on what legal basis
| # | Category | What exactly | Purpose | Legal basis (GDPR Art. 6(1)) |
|---|---|---|---|---|
| 3.1 | Account | email address and the time it was confirmed; callsign (public in-game name) and its "skeleton" used to filter out look-alike names; language; internal and public identifier; role; account status (active, suspended, banned) and the reason for a restriction; time of creation and of last activity; which invitation you came with. For test accounts created manually before the beta, also the PBKDF2 hash of the password (beta accounts have no password). | creating and running the account | (b) performance of the contract |
| 3.2 | Portal sign-in | the email sign-in code and link (only as digests), the requesting email address, the time and country of the request and a keyed digest of the IP address, the number of attempts; the web session (only a digest of the cookie), when it was created and last used, its country, the browser family and the operating system (for example "Firefox · Windows") | signing in; preventing abuse of codes (for example mail bombing, guessing) | (b); for abuse prevention (f) legitimate interest (4.1) |
| 3.3 | Devices and game session | the game running in the browser needs no device code and no separate key: it signs in with the portal session (3.2), and for the game session the server stores an identifier starting with w_, derived from the portal session, and the device label "Longlight-NyiltUr/<version> web" (shown in the game as "browser"); for devices linked with the former desktop program: the device code used to link the program (only a digest), the country of the request and a keyed digest of the IP address; the approved device's ("token family's") label, the program's name and version, the sign-in method, the time of creation and of last use and its country, expiry, time and reason of revocation; digests of the session and refresh keys | the program's sign-in, identifying the game session, the device list and signing devices out; detecting stolen keys | (b) and (f) (4.1) |
| 3.4 | Security log | sign-ins, device approvals, sign-outs, suspicious events (for example reuse of an already used key, a change in the bot-score level, a suspected-cheating flag – 3.7); a keyed digest of the IP address, country, browser family and operating system (without these for an entry under point 3.7) | protecting accounts, detecting abuse (account takeover, bots, cheating) | (f) (4.1) |
| 3.5 | Bot and cheating signals | the list of in-game write actions (time, action, success, location, yield), the score and level calculated from it (ok / watch / review), a statistical summary of movement (without raw coordinates), and how many accounts share the same network (IP digest) or the same Steam owner | detecting bots, macros and cheating, protecting the shared game world | (f) (4.1) |
| 3.6 | Game state on the server | the game state stored for your account on the game server (the program does not save locally): location (system, station), your ships, the ship in use and its upgrades, LX, cargo, the markets of the stations you visited, missions, offers, signals, statistics, the state of the introduction, reputation, discoveries and other internal game state; where the state came from (taken over from the old cloud save or from a local save on your computer, or a fresh start) and change counters; the bookkeeping entries of the game economy (LX movements); the running session: a random session identifier, the identifier and label of the device (3.3), the time the session started, the account's role and whether the account is eligible for taking over the old save; the summaries kept to enforce the game rules and the anti-cheating limits (earnings of the last hour per minute, the number of actions in the last minute, the identifiers of missions already paid and signals already searched, the times of restarts); the old save, if there is one: the cloud save of a program version before 0.3.0 (the save, one previous version, its size, digest, summary, the time and the label of the saving device) | running the game: the game state is the same on whichever computer you sign in, and one session runs at a time; enforcing the rules of the game economy (prices, cargo space, the limits on earnings); the one-time takeover of the old save, and afterwards investigating questions or complaints about the takeover | (b); for the summaries of the anti-cheating limits (f) (4.1) |
| 3.7 | Suspected-cheating flag | if an earning reported by the program reaches or exceeds the per-earning cap or the hourly budget, or comes close to them; if the 10-minute count of a type of earning comes close to or reaches its limit; if the number of actions, or of actions moving LX, exceeds the per-minute limit; or if, when taking over the old save, the server had to cut something, found invalid data, or the save brought unusually large wealth: one entry in the security log (3.4) – the account, the time, the name of the action, the identifier of the rule, the measured value and the limit –, and in the game state (3.6) the time of the latest entry per rule (for the limit of at most one entry per hour). The entry does not contain location or coordinates, the content of the game state or of the save, the IP address or its digest, country, browser or other device data. At most one entry is made per rule per hour; the suspicious earning action appears in the action list (3.5) marked "unsuccessful", even if the server credited it | detecting cheating and attempts to game the economy, protecting the shared game world | (f) (4.1) |
| 3.8 | Bug report | the description, the category, the screenshot, the end of the program's log (with sign-in keys, email addresses and the user folder name filtered out – both the program and the server filter), the game state (version, build, language, ship, location), the report's status | investigating and fixing the reported bug | (f) (4.2) |
| 3.9 | Correspondence | for emails we send (sign-in code, invitation, new device) the mail log: type, time, delivery status, the sender service's identifier – without the address, the content or the code; your emails to support@: your message, your address and whatever you write | notifications, contact, complaint handling, handling requests | (b); for complaints (c) legal obligation (Section 17/A of the Hungarian consumer protection act); otherwise (f) (4.3) |
| 3.10 | Invitation | the type of invitation (email or code), for email invitations the invitee's address, a digest of the code and its first 4 characters, the number of uses, expiry, revocation, who created it and when, an internal note | organising the closed, invitation-only beta and its size limit | (b) if you asked for the invitation; otherwise (f) (4.4); from redemption (b) |
| 3.11 | Legal acceptance | the version of the accepted terms and of the notice you read, a digest (SHA-256) of the text, the time of acceptance, the time of the 16+ confirmation | proving what you accepted and when | (f) (4.5) |
| 3.12 | AikaHub and Steam link (if available) | the external account's identifier (AikaHub identifier or steamid), for Steam Family Sharing the steamid of the game's owner, the time of linking and of the last sign-in; we never ask for or store your AikaHub email address | signing in with the external account | (b) |
One account, one state (3.6). The game state of Longlight Online is stored on the server, tied to your account: the program does not save the game state locally, and it can only be played signed in and connected to the server. The game economy (LX, cargo, ships, upgrades, market) changes on the server in checked steps: the server calculates prices and cargo capacity; of an earning reported by the program it does not credit the part above the per-earning cap, it rejects an earning that would exceed the hourly budget or the 10-minute count, and it limits the number of actions per minute. One session can run per account at a time: if you sign in on another computer, the new session takes over the game; the game stops on the earlier computer, changes not yet uploaded from there may be lost, and the program shows the time the new session started and – if there is one – the label of its device.
One-time takeover of the old save (3.6). If the account does not yet have a game state on the server, at the first signed-in start of the game the server takes over the old save once; if there is none, the program may upload the local save from before 0.3.0 on your computer once; if there is neither, a fresh start begins. A takeover only happens for accounts created before 1:00 Hungarian time (0:00 UTC) on 16 November 2026 (what counts is when the account was created, not when the takeover happens). In the takeover the server leaves out unknown ships, upgrades and goods, takes over the cargo up to the cargo space and the wealth (LX, ships, upgrades, cargo) up to a cap – cutting the excess from the LX –, and does not take over the markets; if the rest of the old save is invalid, it replaces it with the fresh-start state, and it does not take over an invalid local save (a fresh start begins instead). If it had to cut something, it writes a suspected-cheating flag (3.7). Of a local save, only the taken-over, cleaned game state is kept on the server. At the first signed-in start the program deletes the pre-0.3.0 local save that belongs to your account from the computer – even if the server did not take it over (because it took over the old cloud save, the account already had a game state, or the local save was invalid); a save played without an account is deleted only if it was taken over, otherwise it stays on the computer but the program does not load it. After the takeover the server no longer writes the old save and does not use it as game state; we keep it as set out in point 6 to investigate questions or complaints about the takeover.
Is it mandatory? Without the data in 3.1–3.3, 3.10 and 3.11 an account cannot be created (this is a condition of the contract); the data in 3.4–3.7 is generated while the service runs. Sending a bug report and writing to support@ is voluntary.
Age: only people aged 16 or over can take part in the beta. We do not knowingly handle data of anyone under 16; if we learn of it, we delete the account and its data.
There is no newsletter. If there is one, only with separate, express consent that you can withdraw at any time (Art. 6(1)(a)).
AI providers: we do not pass beta account data to any external artificial-intelligence provider. If we were to give an account a tester role that would involve this, we would inform you separately beforehand.
Profiling, automated decisions. The scoring in 3.5 and the suspected-cheating flag in 3.7 may qualify as profiling. How it works: the server scores six signal families (the rhythm of actions, repeated loops, uninterrupted presence, yield, movement and shared networks), the score decays over time, and only at least two signal families together can reach the "review" level. Under the game rules the server does not credit the part of an earning above the per-earning cap, and rejects an earning that would exceed the hourly budget or the 10-minute count and any action above the per-minute action limit (tester and administrator accounts have a larger hourly budget); it does not take back LX already credited, and it does not suspend or ban the account for this. The score and the suspected-cheating flag are only a signal for a human: there is no automatic ban, deduction or other decision based solely on automated processing that produces legal effects concerning you or similarly significantly affects you (GDPR Art. 22). A human always decides on a sanction, and you can appeal the decision (participation terms 7.3).
4. Legitimate interests – balancing test
4.1. Security and fair play (3.2–3.5, 3.7; from 3.6 the anti-cheating summaries). Our interest is protecting accounts and the shared game world against account takeover, key theft, bots, cheating and overload; this is in your interest too. Without it, a stolen key could be used without limit and abuse could not be detected. We chose the less intrusive means: a keyed digest instead of the raw IP address, only the browser family, only statistics of movement, only the action, the rule, the measured value and the limit in the suspected-cheating flag (without location, game state or IP address), short retention (the action list 7 days, the log 90 days), and a human decides. Logging sign-ins and suspected abuse is reasonably expected in an online game; we do not use the data for advertising and do not sell it.
4.2. Bug reports (3.8). Our interest is fixing reported bugs. You send the report voluntarily; the program and the server filter out keys, email addresses and the user folder name; we do not publish the report's content; the screenshot and the log are deleted after 180 days.
4.3. Correspondence (3.9). Our interest is answering requests and being able to prove what we replied and when. We only handle what you write to us, and only for the period in point 6.
4.4. Invitations (3.10). Our interest is organising an invitation-only beta. We use the invitee's email address only to send and redeem the invitation, and delete it as set out in point 6.
4.5. Proof of acceptance (3.11). Our interest is being able to prove, in a possible dispute, what you accepted and when. We only store the version, the digest of the text and the time, for the general limitation period (Section 6:22 of the Hungarian Civil Code: 5 years).
Right to object (GDPR Art. 21). You can object at any time, on grounds relating to your particular situation, to processing based on legitimate interest, at support@longlightonline.com. We will examine it, and unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing is needed to establish, exercise or defend legal claims, we stop processing the data and delete it. Logging that is strictly necessary for account security probably cannot be switched off while the account exists; in that case you can also ask for the account to be deleted.
5. Who has access – processors, transfers
Cloudflare, Inc. (101 Townsend St, San Francisco, CA 94107, USA) – hosting and infrastructure, as a processor: serving the website, the portal and the game server (Workers, Durable Objects), the database (D1), storage (R2: bug-report attachments, backups), bot protection (Turnstile), email (Cloudflare Email Service: sending outgoing emails and forwarding emails to support@), and short-lived operational logs of requests. Cloudflare may automatically scan outgoing emails for malware and spam.
- Cloudflare's data processing terms (Data Processing Addendum) are part of Cloudflare's service agreement, incorporated by reference without a separate signature (cloudflare.com/terms section 6.1, cloudflare.com/cloudflare-customer-dpa).
- Transfers to the USA: Cloudflare, Inc. is an active, certified participant in the EU–U.S. Data Privacy Framework (dataprivacyframework.gov); if the certification lapsed, Cloudflare's data processing terms provide for the European Commission's standard contractual clauses (Decision (EU) 2021/914).
- Turnstile: according to Cloudflare, bot protection handles the signals strictly necessary to filter out bots (the IP address, the TLS fingerprint, the browser identifier [User-Agent], the site identifier). Cloudflare may also use them as an independent controller to improve its own bot-protection service (Turnstile Privacy Addendum).
Google (Gmail): Cloudflare forwards emails sent to support@longlightonline.com to our mailbox operated by Google (Gmail); we handle correspondence there. Google may store emails outside the European Union, including in the USA; its processing and the safeguards for transfers are described in Google's privacy policy (policies.google.com/privacy).
Valve (Steam): if Steam sign-in is available, we call the service of Valve Corporation (USA) to verify the sign-in; we receive the steamid and, for Family Sharing, the steamid of the game's owner from Valve.
Our own servers (Hungary): a copy of each of the nightly encrypted database backups, the backup made before changes to the database structure (point 6) and the website statistics (point 8) are on our own servers operated in Hungary (requests for the statistics arrive through Cloudflare's network).
There are no other recipients. We do not sell your data or pass it on for advertising; we disclose data to authorities only where the law requires it. Other players can see your callsign, your public identifier and – where the game's shared features show it (for example presence in a system, first discoveries) – the related in-game data; never your email address, devices, old save, the parts of your game state not shown by shared features, or bug reports.
6. How long we keep data
| Data | Retention |
|---|---|
| Account (3.1) | until the account is deleted. At the end of the beta, accounts remain for the live game; if you do not accept the live game's terms within 12 months of the end of the beta, we delete the account; we delete it at any time on request. |
| Sign-in code and link (3.2) | valid for 10 minutes (the registration step after redeeming an invitation for 30 minutes), single use; deleted 24 hours after expiry |
| Web session (3.2) | expires after 30 days of inactivity or after 90 days; deleted immediately on sign-out, or 30 days after expiry |
| Device code (3.3) | valid for 10 minutes; deleted 1 hour after expiry |
| Game session and refresh key (3.3) | the session key is valid for 24 hours, the refresh key for 90 days (replaced on use); the digest of a used key is deleted together with the device's data |
| Device / token family (3.3) | valid for at most 180 days; the data of a revoked or expired device is deleted after 30 days |
| Security log (3.4) | 90 days |
| Bot and cheating signals (3.5) | the action list 7 days (older entries are deleted as the account plays later, at the latest when the account is deleted); the score (which decays over time by itself) until the account is deleted |
| Game state on the server (3.6) | until the account is deleted; the data of the running session is overwritten at the next sign-in |
| Old save (3.6) | until the account is deleted; if you do not use the account for 24 months, we delete the save |
| Suspected-cheating flag (3.7) | the entry 90 days (together with the security log); the time of the latest entry per rule in the game state (3.6) until the account is deleted; the affected action in the action list 7 days (3.5) |
| Bug report (3.8) | the screenshot and the log are deleted 180 days after submission; the rest of the report 365 days after it is closed; we close an open report at the latest 365 days after it was submitted |
| Mail log (3.9) | 90 days |
| Correspondence at support@ (3.9) | 1 year after the request is closed; 3 years for complaints, appeals and data-protection requests (for complaints this is required by Section 17/A(7) of the Hungarian consumer protection act) |
| Invitation (3.10) | we delete the invitee's email address at the latest 30 days after the invitation is used or expires; the rest of the invitation (digest, number of uses) may remain until the account is deleted, to show where the account came from |
| Legal acceptance (3.11) | while the account exists and for 5 years after it ends (Section 6:22 of the Hungarian Civil Code) |
| AikaHub and Steam link (3.12) | until the link is removed or the account is deleted |
| Operational logs at Cloudflare | technical data of requests (including the IP address and the browser identifier) for at most 7 days |
| Backups | Cloudflare's built-in recovery feature keeps the database for 30 days; an encrypted full database backup is made every night, which is kept for 35 days in Cloudflare's R2 storage, as the last 7 copies on our own server, and as daily, weekly and monthly copies on our own backup server for at most 12 months; the nightly backup of the game state on the server is deleted after 30 days, the backup summaries after 35 days; we delete the full backup taken before a change to the database structure after 12 months at the latest |
When an account is deleted – within 30 days of receiving your request at the latest – we delete the personal data belonging to it, except where the law or the table above (legal acceptance, complaints) requires a longer period. The aggregated bookkeeping of the game economy (LX movements) may remain, in a form that can no longer be linked to your account, to check the economy's balance. We do not delete individual items from backups: deleted data disappears when the periods above expire. If we restore data from a backup, we delete again any accounts deleted in the meantime; for this we keep the internal identifier of deleted accounts (and nothing else) until the backups expire.
7. Cookies and local storage
The portal only uses cookies that are strictly necessary for it to work (under Section 155(4) of Hungarian Act C of 2003 on electronic communications, these need no consent). There are no tracking or advertising cookies.
| Cookie | Purpose | Lifetime |
|---|---|---|
__Host-ll_s | the signed-in session (a random identifier; the server only stores its digest) | at most 90 days (on the server it expires after 30 days of inactivity) |
__Host-ll_pre | linking the steps of a sign-in or an invitation redemption to your browser; protection against cross-site request forgery (CSRF) | 30 minutes (renewed on every page load) |
ll_lang | the language you chose (hu / en), if you choose one | 1 year |
| Turnstile (Cloudflare) | bot protection on the sign-in and invitation forms; according to Cloudflare it may use the browser's local storage or cookies to work, and the signals it handles are strictly necessary for bot protection | as set by Cloudflare |
The game running in the browser uses no new cookie: sign-in is provided by the portal's __Host-ll_s cookie (above). The game session identifier reaches the browser only in a form encrypted by the portal and opaque to it, and is kept only in the memory of the open tab – it is not written to the browser's storage (local storage, session storage, IndexedDB, cookies). The game does not save the game state locally. It keeps its settings (language, graphics, sound, the state of the interface) and the times of external account links already shown to you (3.12) in the browser's local storage (localStorage); the browser keeps the game files (code, models, textures, sounds) in its own cache. You can delete these at any time in your browser's settings.
8. The website (longlightonline.com)
The website is served by Cloudflare (point 5); Cloudflare handles the IP address to serve requests and to protect against attacks. The website has no forms and no registration, and it does not use cookies; Cloudflare may set a cookie strictly necessary for a security check (for example with suspicious traffic).
Visitor statistics are produced by our self-operated, cookieless PromNET Statisztika (statisztika.promnet.hu). The measurement requests are received by our collector running on Cloudflare's network, and the data is stored by Umami running on our own server in Hungary. The collector filters out robot traffic: it reads from the request which network (ASN, for example a data centre) the IP address belongs to, and checks for signs of automated browsers; we do not store the ASN. It does not track you across other websites and does not identify you; it stores neither raw IP addresses nor cookies. It links visits with a digest that changes every month and cannot be reversed, so the link ends at the end of the month. It estimates the country (and the city) from the IP address, and the browser, operating system and device type from the browser identifier. We keep the data for at most 24 months. We measure this way only on the website (longlightonline.com); there are no such statistics on the portal (account.longlightonline.com) or in the game. Legal basis: Art. 6(1)(f) – improving the website; you can object to it (point 4).
9. Your rights
- Access (Art. 15) – you can ask for information and a copy of your data.
- Rectification (Art. 16) – we correct inaccurate data.
- Erasure (Art. 17) – for example when the data is no longer needed, or you ask for your account to be deleted.
- Restriction (Art. 18) – for example while we check the accuracy of disputed data.
- Data portability (Art. 20) – you can request the data you provided and that we process under the contract in a machine-readable format.
- Objection (Art. 21) – to processing based on legitimate interest (point 4).
- Withdrawing consent – if processing is ever based on consent (for example a newsletter), at any time; this does not affect the lawfulness of earlier processing.
How to exercise them: write to support@longlightonline.com, preferably from your account's email address; if the request comes from elsewhere, we may ask you to verify your identity. We reply without undue delay and within one month at the latest; in justified cases this can be extended by two further months, and we tell you so within the first month. If we do not take action on your request, we tell you why within one month at the latest, and that you can lodge a complaint with the NAIH or go to court. Requests are free.
10. Complaints, remedies
- Please write to us first: we solve most questions quickly.
- You can lodge a complaint with the supervisory authority: Nemzeti Adatvédelmi és Információszabadság Hatóság (NAIH, Hungarian National Authority for Data Protection and Freedom of Information), address: 1055 Budapest, Falk Miksa utca 9–11., Hungary; postal address: 1363 Budapest, Pf. 9.; phone: +36 1 391 1400; website: naih.hu. If you live in another EU member state, you can also turn to the data protection authority there.
- You can also go to court; you can bring the case before the regional court (törvényszék) of your place of residence or stay.
11. Security and personal data breaches
- Encrypted connections (HTTPS, HSTS),
__Host-prefixed cookies sent only over HTTPS, a strict content security policy (CSP). - Beta accounts have no password. For test accounts created manually before the beta, we store the password only as a PBKDF2 hash. For sign-in codes, keys and sessions we also store only their digests.
- There are no raw IP addresses in our database: only a digest made with a secret key (HMAC). A digest can be compared under the same key, so we keep the key secret.
- Only we have access to backups. Nightly backups are encrypted; the backup taken before a change to the database structure can only be read on our own server with administrator rights.
- In the event of a personal data breach that poses a risk to your rights, we report it to the NAIH within 72 hours (Art. 33), and if the risk is high, we also notify you (Art. 34). We keep a record of every breach.
12. Changes
We may change this notice if our processing or the law changes. We will notify you of material changes by email at least 30 days in advance; changes the law requires immediately can take effect at shorter notice.
Version: privacy-v1.2 · dated 17 November 2026 · in force from 17 November 2026.
Changes: v1.2 (17 November 2026) – aligned with the game running in the browser: the scope (2), the web game session and the "browser" device label (3.3), storage in the browser instead of the desktop program (7); visitor statistics through PromNET Statisztika, with robot filtering; still no measurement on the portal or in the game (8). v1.1 (12 November 2026) – aligned with Longlight Online 0.3.0: the game state on the server, one session, the one-time takeover of the old save (3.6); the suspected-cheating flag instead of the cloud save (3.7); point 3.4, the paragraph on profiling, and points 4.1, 5, 6 and 7 adjusted accordingly. v1.0 (11 November 2026) – first version.