Version 2026-11-14, in effect from 2026-11-12.

Privacy Policy

Last updated: 2026-11-14. Version: 2026-11-14.

This text is published in English, Greek, Russian, Ukrainian, Spanish, Brazilian Portuguese and Polish. The English text is the binding version; the translations are provided for convenience, and where a translation differs from the English text, the English text governs.

This policy explains what personal data we collect about you, why we use it, who we share it with, and what you can do about it. It applies to the website at menaris.net, to the accounts and game accounts you hold with us, to our game launcher and the login gate it talks to, and to our game servers.

Who we are

We are the data controller for the personal data described here.

Menaris Network
menaris.net

Menaris Network is run by a company registered in Greece. For anything about this document, about your account, or about the business behind the service, contact menaris@fijisolutions.net. When you pay, the checkout page of the payment provider shows the registered company details in full.

The game master feed: read this before you take a staff role

If you become a member of our staff, this section applies to you. Read it carefully, because it is unusual and it is permanent.

Every medium- and high-risk action a game master takes inside the game, every item a game master moves, and every line a staff member types in a staff chat channel, is captured and published on a feed that every signed-in player can read, automatically and unfiltered, within about a minute. Every action a game master takes, the low-risk ones included, also goes into a fuller staff log that only the owner of Menaris Network and our daily AI review read (see "Chat, item records and the daily review" below). The feed is permanent. There is no redaction, no suppression, no editing and no removal mechanism of any kind, and published events are excluded from every one of our data-retention deletion jobs. Once something is on the feed, we cannot take it off.

This is a condition of holding a staff role. If you accept one, you accept that your staff actions and staff chat lines become a permanent record, readable by every signed-in player and tied to your staff identity. Your low-risk actions are the one exception: they go into the staff log only, and are not published.

We want to be honest about what this means for your rights. If you are or have been a member of staff and you ask us to erase your data, or you object to the publication, we can erase and anonymise your account record in the normal way, but we cannot remove events that have already been published. To that extent, an erasure request or an objection has no practical effect on the feed.

The feed is about staff, not about players. Your ordinary play is not published on it (the one thing about players we publish is the name history of renamed characters and clans, described in "Chat, item records and the daily review" below). If a staff member takes a medium- or high-risk action, or moves an item, that involves your account or your character, that action is published like every other published staff action, and it cannot be taken off afterwards.

What we collect, and where it comes from

Most of it comes from you, when you register, buy something, or contact support. Some of it is generated by our systems while you use the service.

  • Your email address
  • Your password, stored only as an argon2id hash, never in plain text
  • Your display name
  • Your date of birth
  • Your country
  • Your preferred language
  • IP addresses
  • When you vote: the address you voted from and a hash of your browser's identification string (its user agent)
  • When you pay, for a top-up or on the marketplace: a browser fingerprint, a hash of your browser's identification string, languages, platform, screen size and colour depth, number of processor cores, memory class, touch support and time zone, kept with the address and the browser identification string you paid from
  • If you play with our launcher: short result codes about your PC, one-way hashes of some of your PC's hardware identifiers (kept only once that check is switched on), for a PC registered before 2026-11-08 an identifier of its security chip, and the other data described in "The launcher and the login gate" below
  • In the game: your chat lines and every move of your items and adena, under your character name, with the IP address you played from for each move you make, as described in "Chat, item records and the daily review" below
  • Support tickets you send us
  • Orders, payments and ledger entries
  • Your marketplace listings and purchases: what was listed (a character with what it wears, carries and keeps in its warehouse, or an item or adena), its price, our fee and the seller's share, the game account it came from or went to, and the support tickets the marketplace opens, where a seller tells us how they want to be paid
  • How you found us. When you create an account, we save the channel tag in the link you arrived by (for example a Facebook group, a forum or a toplist), or "unknown" if there was none, and, if the sign-up form asks, your answer to "How did you hear about us?". It is linked to your account and we use it only to count sign-ups per channel.

On a payment we also record the version of the Terms of Service you accepted when you registered, the version of the Refund Policy in force when you paid, the exact time and your IP address, so that we can show later which terms applied to that payment.

On the marketplace, other players see what is listed and its price, never who is selling or buying it. Our staff see both, to hand it over and to pay the seller.

The launcher and the login gate

To play, you start the game with our launcher, a Windows program. It runs as a normal program and never asks for administrator permission. Before the game logs in, the launcher asks our login gate, a service on our game machine, for a one-time ticket. This section describes what that involves. Some of the checks below can be switched on and off by us; where a check is not switched on, the data it needs is not collected or not used. Each paragraph below says which check it depends on.

The PC check. Most PCs have a security chip, the TPM (Trusted Platform Module). The game starts with or without one. Each time the launcher starts, it checks quietly in the background what your PC's chip allows and which kinds of hardware identifiers your PC has. It asks you nothing and never stops you from playing. For the check it may create one temporary key in the chip, and it deletes that key at once. Once a day, with a ticket request, the launcher sends the gate short result codes: whether the PC has a usable chip and which version, the chip's maker, whether the chip's built-in key and its certificate could be read, whether the chip could prove it is genuine, how long the check took, and the names of the kinds of hardware identifiers the PC has (for example "disk" or "network adapter"). These codes contain no key, no certificate, no identifier and no hash of one. The gate writes one line with these codes, without your account or your address, and counts them, so that we learn how our players' PCs can be told apart. This check always runs, and it never refuses anything.

PCs registered earlier. Before 2026-11-08, earlier versions of the launcher registered some PCs' security chips, with your permission and an administrator prompt. The launcher no longer registers any chip, and nothing new can be registered. For a PC registered earlier, the gate still keeps an identifier of its chip: a hash of its endorsement key (the chip's built-in key), made with a secret key that exists only on our game machine, so that it cannot be matched against any other service. The endorsement key and its certificates are not stored. With it the gate keeps the public part of a signing key the launcher created inside the chip, and when that key was registered and last used. A registration names no account. A launcher on such a PC still uses that key to prove its chip at each login.

Your PC's fingerprint. To tell one PC from another, the launcher reads some hardware identifiers of the PC it runs on: the PC's system ID (its SMBIOS UUID), the serial numbers of the PC and of its main board, the serial numbers of its fixed disks, and the hardware (MAC) addresses of its wired and wireless network adapters. It does not read the processor, the Windows installation ID, your files, your programs or anything about other devices. The launcher sends only a one-way hash of each identifier, with each ticket request and each check while you play, over the encrypted connection to the gate. The identifiers themselves never leave your PC. While this check is switched off, the gate only counts the hashes it receives, then discards them and keeps nothing. While it is switched on, the gate hashes each one again with a secret key that only our server holds, and keeps only that. From it the gate keeps a PC number, which of your game accounts logged in from that PC (successful logins only), and when each was first and last seen; the PC number is also kept with your ticket and with each check while you play. Nothing is kept that lets anyone, us included, read back a serial number or an address. The PC number is there to tell PCs apart for the rule of one game window per PC, for limits on how many PCs a game account may use, and for PC bans; today none of these uses it yet. Staff can see a PC number and the game accounts linked to it, never a hash or a serial number. The fingerprint is not shared with anyone else.

Which accounts log in from which PC. For a PC registered earlier, each time the launcher asks for a ticket from it, the gate records which game account asked from which chip, with the first and the last time it did. This happens before your game password is checked, so it records an attempt, not a successful login. We use these links for the limits on PCs and accounts and for bans. For the fingerprint, the links are described above. When you ask, staff can look up which PCs your game accounts were used from.

One game per PC, limits and bans. The launcher lets only one game run on a PC at a time, whichever Windows user starts it. It does this with a lock inside Windows, and it stores and sends nothing for it. The game server may also limit how many game windows one PC runs at once; today it can tell PCs apart for this only by the chip of a PC registered earlier, and in the strictest setting a character over the limit is taken out of the world. For PCs registered earlier, while these checks are switched on, a game account may be used from at most 3 such PCs, and one such PC may log in to at most 10 game accounts. When a member of staff bans a PC registered earlier, the gate keeps the chip's identifier, the reason and the date, and the ban has no end date. The ban is the PC's: the banned PC gets no ticket, and a game account linked to it cannot log in without proof from a registered chip, but it can still log in from another PC that is not banned. Limits and bans by the PC fingerprint are not in use.

Refusal codes. When the launcher or the gate refuses to start the game, for example because a game already runs on that PC, the launcher shows you a short reference code that you can give to support. The gate writes one line with the code, the reason and the launcher's version. When the launcher refused on its own, it sends the gate only the code and the reason, without your account, and the gate writes the same kind of line. These lines name no account, no address and nothing about your PC.

The check for virtual machines. With every ticket request the launcher sends a set of readings that show whether the game runs inside a virtual machine (the VM signal set): the processor architecture, the processor's hypervisor flag and vendor string, the manufacturer, product and firmware names of the PC and its main board, the vendor codes of the PC's hardware devices, the maker codes recorded in its firmware tables, which of a fixed list of virtual-machine drivers and services are running, and whether the PC has a usable security chip and a chip registered earlier. It never contains a serial number, a hardware UUID, a product code or an asset tag. While this check is switched off, the gate does not read the set. While it is switched on, the gate judges the set in memory and gives a verdict: a virtual machine or not. It does not store the set; it keeps only a count of which kinds of reading matched, and writes one log line per request naming only those kinds. In its strictest setting, a login whose verdict is a virtual machine is refused.

The ticket and its outcome. This happens each time you start the game, whichever checks are switched on. A ticket request names the game account and carries the address you connect from and the launcher's version; the gate keeps these with the ticket, together with the chip's identifier when the PC was registered earlier, and the PC number while the fingerprint check is switched on. The gate keeps the ticket for 60 seconds and deletes it 10 minutes after it expires; while the login server's ticket check is switched on, the ticket also records what came of the login (for example accepted, wrong password or account banned). While you play, the launcher asks the gate every minute for a fresh check value, and the gate keeps each one with your game account name, your address and, while the fingerprint check is switched on, the PC number, for about 13 minutes. In the strictest setting of the checks while you play, a session whose launcher stops answering them is disconnected.

Server logs and behaviour telemetry. Our game and login servers always keep their ordinary logs: they name characters (for example when an item is traded, dropped or used), account names (for example when an account is created) and, when a character is deleted or restored, the address it was done from, and they record what game masters did and to which character or account. We can also switch on records on our game and login servers that write your game account name and your address to our server logs at each login, each game window over the limit and each check while you play. We can also switch on behaviour telemetry: it counts what each character does (monsters killed, skills used, items picked up, moves) and flags patterns that look like a bot, under your character and account names. It groups characters played from the same address under a code made from that address with a key that changes at every server restart, so the address itself is never logged. Telemetry is evidence: a flag is a line for a game master to look at, and it never kicks, bans or slows anyone on its own. Our log store keeps these logs for 14 days, for searching. The game machine keeps the game and login servers' logs across redeploys and archives them once a day: each day's archive, and its encrypted copy off-site, is kept for 2 years and then deleted. This includes the anti-cheat evidence lines (the telemetry flags, the checks while you play, the game-window limit and the login server's ticket check), which are also kept for 2 years. The login gate's own log lines (its verdicts on virtual machines, the PC check lines and the refusal lines) are not archived: our log store keeps them for 14 days, and the game machine keeps only the newest 30 MB of them.

What stays on your PC. The launcher keeps its files in your Windows user folder: the game accounts you save, with their passwords encrypted by Windows so that only your Windows user on that PC can open them; your settings; its own log, which names the folders it uses (they usually contain your Windows user name), holds the PC check's result codes and never leaves your PC; the record of its updates; the date of its last daily PC check report; and, on a PC registered earlier, the record of that registration. The launcher's links open our pages in your own browser, where the Cookie Policy applies as on the website; the launcher keeps no browser cookies or page storage of its own. Earlier versions of the launcher kept the cookies and page storage of a browser built into them in a folder of their own inside the launcher's folder; the launcher deletes that folder at its next start. On a PC registered earlier, the launcher's signing key also stays inside the chip itself: deleting the launcher's folder does not remove it, clearing the TPM in Windows does. Your game password goes from the launcher to the game on your PC, never to the gate.

Where it goes. To download the game and the launcher's updates, the launcher fetches files from Amazon Web Services and Cloudflare, who see the address you connect from.

Chat, item records and the daily review

Our first world, Eternal, never wipes, so it keeps a history of what happens in it.

Chat. Every line typed in the game's chat is recorded, in every channel, whispers and friend messages included, with the character who wrote it, the character it was sent to for a whisper or a friend message, the channel and the time. We use these records only to investigate reports of scams, theft, harassment, real-money trading and cheating. They are deleted after 2 years.

Items and adena. Every move of an item or of adena is recorded, with the characters involved, the item, the amount, the time and the IP address of the player who made the move: trades, private shops, the warehouse, drops, pickups and loot, items destroyed, enchants, and what you buy from and sell to the game's NPCs. We use these records for the same investigations and to put things right after a theft or a bug. They are deleted after 2 years.

The daily review. Once a day, the chat records and the staff log are reviewed by an outside AI service in the United States, which looks for signs of scams, real-money trading, harassment and unusual staff behaviour. It does not train on them and keeps them for up to 30 days. Its report goes to a private channel on Discord that only the owner of Menaris Network reads. The review never punishes anyone: it points a human at something to look at, and a human decides what, if anything, happens. The report quotes the chat lines it points at, and it is kept in that channel no longer than the chat records it quotes.

A record tied to an open case or a ban is copied out before its 2 years end, and kept as long as that case or that ban.

Name history. When a character or a clan is renamed for adena in the game, we record its old name, its new name and the date, and publish them on a public page of our website, so that a rename cannot hide a character's or a clan's past from the players who deal with it. The page shows nothing else: not your account, not the price and not who paid. We also keep, for staff only, which character paid and how much. The name history is kept for as long as the world runs, also after the character or the clan is deleted.

Why we use it, and our lawful basis

What we use it forLawful basis
Running your account, your game accounts and your characters, delivering what you buy, and running the marketplace for you as a buyer or a sellerArticle 6(1)(b) GDPR, performance of a contract with you
Taking payments and keeping order, wallet and payment recordsArticle 6(1)(b) GDPR, performance of a contract with you
Keeping tax, VAT and accounting records, including the evidence of your country that VAT rules requireArticle 6(1)(c) GDPR, legal obligation
Refusing registration below the digital-consent age of your countryArticle 6(1)(c) GDPR, legal obligation, read with Article 8 GDPR
Checking that you are 18 or over at the moment of purchase, and when you list on the marketplaceArticle 6(1)(f) GDPR, our legitimate interest in keeping minors out of paid transactions
Preventing fraud and vote-farming, telling PCs apart with the PC check, the PC fingerprint and the chip of a PC registered earlier, enforcing one game window per PC and the limits on PCs and accounts, checking for virtual machines and bot patterns, banning PCs, and keeping the service secureArticle 6(1)(f) GDPR, our legitimate interests in fair play, protecting the service and other players
Publishing the game master feed, if you hold a staff roleArticle 6(1)(f) GDPR, our legitimate interest in being accountable to our players for what staff do with their powers
Recording chat and item and adena moves, keeping the anti-cheat evidence lines, and the daily AI review, to investigate reports of scams, theft, harassment, real-money trading and cheatingArticle 6(1)(f) GDPR, our legitimate interests in protecting other players and the service
Keeping the full staff log and reviewing it daily, if you hold a staff roleArticle 6(1)(f) GDPR, our legitimate interest in overseeing what staff do with their powers
Publishing the name history of renamed characters and clansArticle 6(1)(f) GDPR, our legitimate interest, and the other players', in not being deceived by a rename
Counting sign-ups per channel from how you found usArticle 6(1)(f) GDPR, our legitimate interest in knowing which channels bring players, so we spend on the ones that work
Counting page views with Vercel Web Analytics, which sets no cookie and stores nothing on your deviceArticle 6(1)(f) GDPR, our legitimate interest in knowing which pages are used, so we can improve the site
News about games that are announced but not yet openArticle 6(1)(a) GDPR, your consent

Where we rely on consent, you can withdraw it at any time, and withdrawing does not affect the lawfulness of what we did before you withdrew. Game interest is withdrawn by writing to menaris@fijisolutions.net or opening a support ticket, and we then delete your address from every list it is on.

You can object to analytics at any time. It stores nothing on your device that could single you out later, so the way to stop it is to block it in your browser, as the Cookie Policy explains; you can also write to menaris@fijisolutions.net.

Some of this data is required: without an email address, a password and a date of birth we cannot give you an account, and a verified email address is required before you create a game account or make any purchase.

Cookies and similar technologies

There are exactly four categories, and the Cookie Policy explains each of them and names every cookie we set, including those kept inside the launcher:

  • Strictly necessary. Always on and cannot be refused. Without them you cannot log in or pay.
  • Analytics. We use Vercel Web Analytics, which sets no cookie and stores nothing on your device, so it loads for every visitor without a question first. Your browser can block it.
  • Third-party beacons. Consent only. None are in use today.
  • Game interest. A marketing consent, for news about games that are announced but not yet open.

Apart from analytics, nothing outside the strictly necessary category is placed or loaded until you have given the matching consent, and we use no third-party beacon today. Refusing costs you nothing. Until 2026-11-12 we asked about analytics too; the records of those answers are kept as proof of what was asked and answered, and no longer decide anything.

Who we share it with

We use these processors, and they act on our instructions only.

  • Amazon Web Services: hosting, in the EU
  • Vercel: website delivery, and Vercel Web Analytics, which counts page views
  • Amazon SES: email
  • Cloudflare: Turnstile, our bot defence, and delivery of the launcher and game files
  • Discord: the private channel the daily review reports to, in the United States

Stripe and PayPal take our payments. They handle your card and PayPal details directly, and we never see or store a card number. For parts of that work they decide things for themselves, such as what they must keep to meet their own legal and anti-fraud duties.

An outside AI service in the United States receives the chat records and the staff log for the daily review, as described under "The daily review".

How you found us is not shared with anyone and not used for ads or profiling.

We also share data where the law requires it, for example with tax authorities.

International transfers

Our hosting is in the EU. Some of our processors, or their support teams, are outside the European Economic Area, so some data leaves it. Where that happens, the transfer relies either on an adequacy decision of the European Commission or on the European Commission's standard contractual clauses with that processor. Discord is in the United States: the transfer to it relies on the EU-U.S. Data Privacy Framework where it is certified under it, and otherwise on the standard contractual clauses. The daily review's AI service is in the United States too: the data goes to it under the EU-U.S. Data Privacy Framework. Write to menaris@fijisolutions.net to ask which applies to a given processor.

How long we keep things

  • Your account record. For as long as your account exists. If you ask us to erase it, we do not delete the row: we anonymise it in place and mark it erased, so that our financial records stay valid.
  • Financial records: orders, payments, marketplace sales, ledger entries, tax records and the evidence kept on a payment. Seven years, because the law requires it. After erasure they remain, keyed to the anonymised record rather than to you. The IP address recorded on a payment is part of that record and is kept for the same seven years.
  • IP addresses held to detect fraud and vote-farming. Only as long as they are needed for that.
  • The evidence kept on a payment: the address, the browser identification string and the browser fingerprint. 24 months, then deleted from the payment record.
  • The chip registration of a PC registered earlier. Deleted when it has not been used for 365 days.
  • The links between your game accounts and a PC registered earlier. Each link is deleted 365 days after its last use, except the links to a banned chip, which are kept as long as the ban.
  • Your PC's fingerprint at the login gate (its keyed hashes, its PC number and its links to your game accounts). Deleted 1 year after the PC was last seen; a link to a game account, 1 year after its last login.
  • A PC ban. Until a member of staff lifts it.
  • Tickets and the check values of the login gate. Deleted within about 13 minutes, as described above.
  • Chat records. 2 years, then deleted.
  • Item and adena records. 2 years, then deleted.
  • Server logs, behaviour telemetry and the anti-cheat evidence lines. 2 years on the game machine and in its encrypted off-site archive, then deleted; 14 days in our log store.
  • The login gate's own log lines (virtual-machine verdicts, PC check lines, refusal lines). 14 days in our log store; on the game machine only the newest 30 MB.
  • The staff log. 2 years, then deleted.
  • The daily review's reports. In the private Discord channel, no longer than the chat records they quote.
  • The daily review's input at the AI service. Up to 30 days, as described under "The daily review".
  • The name history of renamed characters and clans. For as long as the world runs, also after the character or the clan is deleted.
  • A record tied to an open case or a ban. As long as that case or that ban, as described above.
  • Backups. Our game machine keeps nightly backups of the game database, which holds your characters, the item records and the login gate's records, for 14 days, so a deleted record can remain in a backup there for up to about 15 days, and in the database's own change log for up to about 8 days. An encrypted copy of each nightly backup is kept off-site, at Amazon Web Services in the EU, for 30 days, so a deleted record can remain in that copy for up to about 31 days. A backup that fails its integrity check is kept until a member of staff removes it.
  • How you found us. As long as your account exists; deleted when the account is erased.
  • Support tickets. As long as we need them to deal with your request and to show what we did.
  • Published game master feed events. Permanently, and excluded from every deletion job. See the section above.

Erasure, and what happens to your balance

Ask by support ticket or by email to menaris@fijisolutions.net. The statutory 30-day clock starts when we receive your request.

When we erase your account: your game accounts are disabled; the login gate's links between those game accounts and your PCs are deleted, with their tickets and check values (a PC ban, a chip registration, and a PC's number and fingerprint, none of which names an account, are not: they are deleted as described above); your account record is anonymised in place and marked erased; any bonus balance is forfeited; and any purchased balance simply ends with the account. Balance is never paid out in any form. Financial records are kept for seven years as described above. We cannot erase an account while it has marketplace business open: a listing, a sale not yet handed over, or a payout or refund still owed. Once that is settled, we can.

Eternal never wipes, so erasure does not remove your characters from the world's history: the chat lines, item and adena records, anti-cheat evidence lines and staff log entries that name your characters are kept until their 2 years end, and then deleted. From erasure on they are tied to the anonymised account record, not to you. The name history of a renamed character or clan stays published, as described above; it never names your account.

Your rights

Under the GDPR you have the right to:

  • access the personal data we hold about you
  • have inaccurate data corrected
  • have your data erased
  • restrict how we use your data
  • receive your data in a portable form
  • object to processing we base on legitimate interests
  • withdraw any consent you gave

To use any of these rights, open a support ticket or write to menaris@fijisolutions.net.

Two honest limits. Published game master feed events cannot be removed, as explained above. And you cannot edit your date of birth yourself: support can correct it once, on a written reason, which is what keeps the age rules meaningful. Neither limit removes your right to ask us to correct data that is genuinely wrong, and we deal with every such request on its merits.

You also have the right to complain to a supervisory authority. In Greece this is the Hellenic Data Protection Authority, www.dpa.gr. You can also complain to the authority in your own country.

Automated decision-making

We do not make any automated decision about you that produces legal effects or similarly significantly affects you. We do run automated checks for fraud and vote-farming, and a human decides what happens next. Some refusals are automatic. The launcher does not start a second game on a PC where one already runs, or start the game when the login gate does not answer, and while we set a lowest launcher version, the gate refuses a ticket to an older launcher. A PC with no usable security chip is never refused for that reason. For a PC registered earlier, while the limits are switched on, the gate refuses a login when that PC is banned, or when a game account or that PC is over the limits above; while the check for virtual machines is switched on in its strictest setting, it refuses a login when the PC looks like a virtual machine. While the checks while you play are switched on in their strictest setting, the game server disconnects a session whose launcher stops answering them, and takes a character out of the world when the PC runs more game windows than allowed. Such a refusal or disconnection affects that login or that session only: it does not change your account, your balance or anything you bought. The launcher shows a reference code for it, and you can open a support ticket for a member of staff to look at it.

Behaviour telemetry and the daily review. Behaviour telemetry never acts on its own, and the daily AI review never acts at all: both only point a human at something to look at.

How we protect your data

Passwords are hashed with argon2id and never stored in plain text. Traffic between you and us is encrypted in transit. We hold no card numbers. Your portal password and your game password must be different. You choose the game password. The portal passes it to the game server without storing it, and the game server keeps only a hash of it.

Children

Your date of birth is required at registration. We refuse registration below the digital-consent age of your own country under Article 8 GDPR: that is 16, unless your country has set a lower age, and never below 13. You must be 18 or over to buy anything or to sell on the marketplace, and your age is checked at the moment of purchase and when you list on the marketplace.

Changes to this policy

If we change this policy, we will update the date at the top and, where the change matters to you, tell you directly. A new version applies from the date it is published, and never backwards.

Contact

Write to menaris@fijisolutions.net, or open a support ticket from your account. Support tickets are our only two-way channel: there is no forum, no comment section, no profile feed and no follow system anywhere on the site.

Every version