Legal & privacy

Legal notice

Who operates METANICUS, how personal data is handled, and which third-party rights apply.

Last updated: 21 August 2026

Publisher, hosting and release status

METANICUS is published and operated by Fabien Lanselle, acting as a private individual in France. He is also responsible for the personal data processed by the service.

The public instance at www.metanicus.comis deployed through Railway. Its application service is configured in Railway's EU West Metal region in Amsterdam, Netherlands (europe-west4-drams3a). Brevo is used for transactional email.

Public-release legal clearance remains incomplete. A dedicated contact address still needs to be published; the legally required publisher and hosting details, the actual processor arrangements and the unresolved opponent-data safeguards below still need to be supplied and reviewed.

Personal data and purposes

To operate accounts and team-tournament features, METANICUS processes account email addresses and display names; team memberships, roles and invitations; event, roster and round data; factions, detachments and army lists; matchup estimates, pairing decisions, scores and comments; and a functional audit trail linked to internal identifiers. An email address is required to sign in. Other information is required only when the corresponding feature is used.

The current processing register relies on performance of the service agreement for account and feature data, and on legitimate interests for security, abuse prevention, functional auditability and internal team statistics. The contractual basis and user terms have not yet received documented legal validation for public operation. METANICUS does not ask users to enter special-category personal data, and users should not add it to free-text fields.

An IP address is used transiently to rate-limit magic-link requests but is not stored. Browser user-agent strings are not stored. There is no advertising, behavioural profiling, audience analytics or third-party tracking.

Players without an account

Team staff may enter an invited player's email address and display name. They may also record an opponent's pseudonym, faction, detachment and army list, usually from an event roster or information supplied for the match. Opponent data is used to prepare and review a round, on the basis of legitimate interest, and is visible only to the team concerned.

METANICUS does not yet apply an automatic post-event retention period to opponent data or provide those players with a direct information and rights flow. This feature is not cleared for public use until that retention period and the indirect-collection process have been decided and implemented.

Recipients and browser storage

Personal data is available only to members or staff authorised for the teams and events concerned. Railway hosts the application service in the region identified above. Its Data Processing Addendum states that Railway's primary processing operations take place in the United States and provides transfer mechanisms including the EU-U.S. Data Privacy Framework or the EU Standard Contractual Clauses, as applicable. Brevo receives the recipient address and transactional message content, including sign-in or invitation links, solely to deliver those messages. The applicable DPA, authorised subprocessors, database and backup locations, and any international-transfer safeguards still need to be confirmed against the contracts and services actually in force.

METANICUS uses a strictly necessary, HTTP-only session cookie with a rolling 30-day lifetime. For offline viewing, supported browsers may also keep up to eight AES-GCM encrypted snapshots of recently viewed product screens in Cache Storage. The encryption key is held in sessionStorage for the tab, and a lifecycle marker is held in localStorage. Identity-scoped caches are purged on sign-out or account deletion; the tab key disappears when the tab closes.

These storage mechanisms are used only to provide authentication, security and the requested offline feature. No advertising or analytics storage is used, so METANICUS does not display a tracking-consent banner.

Retention and your rights

Magic links expire after 15 minutes, invitations after 30 days and sessions after 30 rolling days. An account that has never joined a team is erased 30 days after creation. An inactivity reminder is sent after 34 months and the account is erased after 36 months without activity. Encrypted backups are retained for 14 days. When an account is erased, direct identifiers and copied display names are removed; historical game facts may remain in pseudonymised form where necessary to preserve team statistics and accountability.

You may request access, rectification, erasure or restriction of your personal data, object to processing based on legitimate interests, and request portability where applicable. The Profile page provides a JSON export, display-name correction and account erasure. Other requests, including requests about data entered without an account, require the dedicated contact channel that still needs to be published as noted above.

You may also lodge a complaint with the CNIL.

A suspected personal-data breach is assessed and, where required, reported to the CNIL within 72 hours. Affected people are informed when the risk is high.

You must be at least 15 years old to use METANICUS.

Intellectual property and data credits

METANICUS is an unofficial fan-made tool. It is not affiliated with, endorsed, sponsored or approved by Games Workshop Limited. Warhammer 40,000 and associated names and marks belong to Games Workshop Limited and their respective owners. They are used solely for identification and interoperability, with no claim of ownership.

METANICUS does not intentionally reproduce Games Workshop rules text or official artwork. Mission names and identifiers are accompanied by links to external reference sources.

Detachment and terrain geometry data is adapted from 40kdc-data v1.2.6 (commit 5c093d1), © 2026 Alpaca Software and 40kdc community contributors, under the CC BY 4.0. This provisional source snapshot was modified for METANICUS: matched-play data and selected Battlemaster layouts were retained, identifiers and variants were normalised, terrain footprints were re-centred, and rules text, artwork, logos, descriptions and unused metadata were removed. This attribution does not imply endorsement by the source contributors.