Privacy Policy

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

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, and to our game launcher and the login gate it talks to.

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 public 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 action a game master takes inside the game, and every line a staff member types in a staff chat channel, is captured and published on a public feed, automatically and unfiltered, within about a minute. 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 public record tied to your staff identity.

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. If a staff member takes an action that involves your account or your character, that action is published like every other 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 top up: 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: an identifier of your PC's security chip and the other data described in "The launcher and the login gate" below
• Support tickets you send us
• Orders, payments and ledger entries

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.

The launcher and the login gate

To play, you start the game with our launcher, a Windows program. 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.

Your PC's security chip. Most PCs have a security chip, the TPM (Trusted Platform Module). The launcher does not start the game on a PC without a usable one, whichever checks are switched on. While chip registration is switched on, the launcher registers your PC's chip once, after asking you, and Windows asks you for administrator permission. For this the launcher sends the gate the chip's endorsement certificate, the certificate of its endorsement key (the chip's built-in key), and the certificates that issued it. The gate then keeps only an identifier of the chip: a hash of its endorsement 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 creates inside the chip, and when that key was registered and last used. A registration names no account.

Which accounts log in from which PC. While chip registration is switched on, each time the launcher asks for a ticket from a registered PC, 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. When you ask, staff can look up which PCs your game accounts were used from and delete a link.

Limits and bans. While these checks are switched on, a game account may be used from at most 3 PCs, and one PC may log in to at most 10 game accounts; a PC may also be limited in how many game windows it runs at once, and in the strictest setting a character over that limit is taken out of the world. When a member of staff bans a PC, 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.

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 the outcome of the chip registration. 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 your PC's chip is registered. 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 and your address 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 only: a flag is a line for a game master to look at, and it never kicks, bans or slows anyone on its own. These logs are kept for 14 days in our log store; the game machine also keeps copies, limited in size, until the game server is next redeployed.

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) and never leaves your PC; and the record of its updates and of the chip 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. Once your PC's chip is registered, 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.

Why we use it, and our lawful basis

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. Analytics is withdrawn with one click on the Cookie settings page, linked at the bottom of every page, exactly as it is given. 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.

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 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. Consent only. We use Vercel Web Analytics, which sets no cookie.
• 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.

Nothing outside the strictly necessary category is placed or loaded until you have given the matching consent. The check happens on our server before the page is sent to you, not in a script that runs afterwards. Refusing costs you nothing, and we do not ask you again on the next page. You can change your analytics choice from the Cookie settings link at the bottom of every page.

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 only if you allow analytics
• Amazon SES: email
• Cloudflare: Turnstile, our bot defence, and delivery of the launcher and game files

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.

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. 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, 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 top-up: the address, the browser identification string and the browser fingerprint. 24 months, then deleted from the payment record.
• Your PC's chip registration at the login gate. Deleted when it has not been used for 365 days.
• The links between your game accounts and your PCs. 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.
• 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.
• Server logs and behaviour telemetry. 14 days in our log store; the copies on the game machine, limited in size, until the game server is next redeployed.
• Backups. Our game machine keeps nightly backups of the game database, which holds the login gate's records, for about 15 days, so a deleted record can remain in a backup for up to about 15 days. A backup that fails its integrity check is kept until a member of staff removes it.
• 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 and the chip registration, which names no account, are not); 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.

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 the game on a PC without a usable TPM security chip, or when the login gate does not answer, and while we set a lowest launcher version, the gate refuses a ticket to an older launcher. While chip registration and the limits are switched on, the gate also refuses to register a virtual security chip, and refuses a login when the PC is banned, when a game account or a PC is over the limits above, or, in the strictest setting, when the login comes without proof from a registered chip; 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, and you can open a support ticket for a member of staff to look at it. Behaviour telemetry never acts on its own.

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 are always different values: the game password is generated by us, is shown to you exactly once, and is not stored by the portal.

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, and your age is checked at the moment of purchase.

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.