Privacy Policy

1Who is responsible

WoRTool is a free, fan-made planning and community tool for the game War of Rights, operated by an individual. For the purposes of the GDPR and UK GDPR, we are the data controller for the personal data described here.

You can reach us about anything in this policy at legal@wortool.com.

2What we collect

Account information

• Your username and email address, and a hash of your password. Passwords are hashed with Argon2id and are never stored, logged, or transmitted in readable form, so we cannot see them.
• An avatar image, if you upload one, and a pending email address while a change of address is waiting to be verified.
• Timestamps for account creation, last update, last sign-in, and email verification.

Linked Discord and Steam accounts

• Discord: your Discord user id, username, avatar URL, and the email address on the Discord account when Discord shares it.
• Steam: your SteamID64, persona name, and avatar URL.

We request the narrowest scopes each provider offers for sign-in and, for the bot, for the server management a community has asked it to do. We never receive your Discord or Steam password. Persona names and avatars are display data refreshed on sign-in; they are never treated as authoritative account fields.

Profile information

Anything you choose to add: a biography, a banner image, a timezone, and the visibility switches that decide who can see your profile and whether your linked accounts, communities, and favorites appear on it.

Security and sign-in records

• Sessions: a hash of the session token, the IP address and browser user agent the session was created from, when it was last active, and when it expires. This is what powers the device list in your security settings and lets you sign other devices out.
• Sign-in history: each sign-in attempt, whether it succeeded, the method used, the reason for any failure, and the IP address and user agent. This is how account takeovers get noticed.
• Passkeys: the credential id, public key, signature counter, authenticator model identifier, and any nickname you give the key. A passkey's private key never leaves your device.
• Two-factor authentication: your authenticator secret, encrypted at rest, hashes of your recovery codes, and any devices you have marked as trusted.

Content you create

Posts, comments, images and video you upload, WoRSketch boards and the drawings on them, community profiles, banners, galleries, events and their attendance, rosters and ranks, catalog contributions and inaccuracy reports, follows, blocks, and favorites. Some of this is public by design; see what other people can see.

Discord server data

Where a community attaches a Discord server, we store the Discord server id, its channels and roles, its member count, and the Discord identifiers and avatars of roster members, so that roles, events, and announcements stay in step between Discord and the site. We also record which account attached it, and when.

We read that from Discord in two ways: the bot reports it as it happens, and the site asks Discord directly when a server is attached or when staff ask for it to be read again. Both read the same things.

A community may map its ranks to Discord roles. Where it has, reading the server can add a member of that server to the community's roster, recording their Discord id, display name, and avatar even if they have no WoRTool account and have never visited the site. A roster entry is internal to that community and its staff, who can remove it. Each community chooses how far this reaches, from treating its roles as the record to switching the behavior off entirely, and staff can also import a role's holders as a one-off. We do not read message content in any case.

Game server credentials

A community can register its dedicated War of Rights server so its staff can edit the configuration and admin list, read the server log, and go through crash dumps from here. Doing so stores the host, port, username, and password of the FTP account the server's host issued, usually gPortal.

That password is encrypted at rest with AES-256-GCM under a key held only in the server's environment, never in the database beside it. It is not hashed, because unlike a password we only ever check, this one has to be replayed to the hosting provider to reach the server at all. It is never returned by our API, never shown back to the community once saved, and never written to a log. Staff replace it rather than read it.

Inside the community, only ranks it has granted the game server permission can use the stored credential. From outside it, only the site owner can, so that a server can be looked at when a community asks us why something is failing. Site administrators cannot: moderating a community and holding the login to its server are separate kinds of trust, and only the second one reaches a machine the community pays for.

Registering, editing, or removing a server, publishing a configuration, and deleting a crash dump are all recorded in that community's audit log; reading a file or a log is not. Removing the server erases the stored password, keeping only what the audit trail needs to say what was removed.

It is a credential to somebody else's service. Use an FTP account scoped to that game server rather than your hosting account's main login, and rotate it as you would any other.

Email delivery records

For each message we send you, we log the recipient address, which template was used, whether it was delivered, and the provider's message id. We never log the body of an email, nor any verification or reset link or token it contains.

Technical logs

Our server and its reverse proxy keep short-lived operational logs containing IP addresses, requested paths, response codes, and user agents. They exist for debugging, abuse prevention, and rate limiting, and are not used to build a profile of you.

3How we use it, and on what basis

We use the information above only for the purposes listed here. For readers in the EU, EEA, or UK, the lawful basis for each is named alongside it.

We do not use your data for automated decision-making that produces legal or similarly significant effects, and we do not profile you for advertising.

4Cookies and browser storage

We set no advertising or analytics cookies. Every cookie below is either strictly necessary to run the service or remembers a preference you set yourself, which is why you are not asked for consent to them.

Stored in your browser only

These never leave your device and are not readable by us. Clearing your browser's site data removes them.

The site also registers a service worker that caches map and unit thumbnails in your browser so the catalog loads quickly on a return visit. It stores images only, never personal data.

5Who we share it with

We do not sell, rent, or trade your personal data. We share it only with the providers needed to run the service, and only what each one needs:

We may also disclose data where the law requires it, in response to a valid legal request, or where it is necessary to investigate a serious breach of the Terms of Service, to prevent fraud, or to protect someone's safety. Where we are permitted to tell you about such a request, we will.

If the service is ever transferred to someone else, your data may transfer with it. We would give notice before that happened and this policy would continue to apply until you were told otherwise.

6What other people can see

Some of what you do here is deliberately visible. Knowing exactly what is visible, and to whom, is part of privacy.

• Public by default: your username, your avatar, and any posts, comments, catalog contributions, or community content you publish to a public area.
• Controlled by you: your profile page. Set it to public, to signed-in members only, or to private, and choose separately whether your linked Discord and Steam accounts, your communities, and your favorites appear on it. Linked accounts are hidden until you turn them on.
• Visible to a community you join: your membership, rank, roster entry, event attendance, and, where the roster is synced, your Discord identity. Community staff can see and edit these.
• Visible to a board's participants: your display name and cursor on any WoRSketch board you join, including as a guest.
• Never shown to other users: your email address, your password hash, your sessions and IP addresses, your sign-in history, your passkeys, and your two-factor secrets and recovery codes.

Blocking another user hides your content from them and theirs from you within the service. It does not retract content that was already public.

7Game server credentials

The server editor connects to a game host you name, over the FTP login that host issued you. That login is a credential to a third-party system, so it is worth setting out exactly what happens to it.

A server registered by a community stores the address, the port, the username, and the password, because the whole point is that the tool can reconnect without anybody typing them again. The password is encrypted at rest with a key held outside the database. It is never shown back, never returned by the API, never written to a log, and never sent to your browser: the only thing that ever reads it is the service, at the moment it opens a connection. Somebody who can manage the server can replace the password; nobody can read the stored one.

Who can reach it is decided by the community, through the rank permission for managing servers. A member without that permission cannot see the server, connect to it, or read anything on it. The one account outside the community that can is the site owner, kept for diagnosing a server a community has asked us about; site administrators are not given this, because moderating a community is not the same as holding the login to its machine.

What we record is the fact of each action, not the contents of the credential: who connected, who published a file, who deleted one, and when, in the community's audit log. A copy of each configuration or admin list this tool overwrites is kept, so a bad edit can be undone. Those copies are the game server's files, which is to say they can contain whatever your unit put in them, including a server password or an RCON password if you keep one in the configuration.

The public tool at /tools/server-editor stores nothing. The credentials you type there are held encrypted, in memory, for the length of one session and no longer, and the session ends when you disconnect, close the tab, or leave it idle. Your browser remembers the address and username so the form is not retyped; it never remembers the password.

Connecting reaches out to a host you chose, which is neither ours nor operated by us. What that host does with the connection, and what it logs about it, is between you and them.

8How long we keep it

We keep personal data only as long as it serves the purpose it was collected for.

We may keep specific records longer where we need them to establish, exercise, or defend a legal claim, or to enforce a ban against someone who would otherwise evade it.

9How we protect it

• Passwords are hashed with Argon2id. Session tokens, reset tokens, and recovery codes are stored only as hashes, so a copy of the database does not yield a working credential.
• Two-factor secrets are encrypted at rest with a key held outside the database.
• Traffic to wortool.com is served over HTTPS. Session cookies are HttpOnly, Secure, and same-site restricted.
• Passkeys and two-factor authentication are available on every account, and we recommend turning one of them on.
• Access to production systems is limited to the operator, and secrets are supplied to services at runtime rather than built into any image or committed to source control.

No system is perfectly secure. If a breach affects your personal data and is likely to put you at risk, we will notify you and the relevant supervisory authority without undue delay and, where the GDPR applies, within 72 hours of becoming aware of it.

10Your rights

Wherever you live, you can ask us to:

• Access the personal data we hold about you.
• Correct anything inaccurate or incomplete.
• Delete your account and personal data. Some records may be retained where the law allows or requires it, as set out under how long we keep it.
• Export a machine-readable copy of the data you gave us.
• Restrict or object to processing we carry out on the basis of legitimate interests.
• Withdraw consent at any time where consent is the basis, including by unlinking Discord or Steam in your settings. Withdrawing does not undo processing already carried out.

Much of this you can do yourself from your account settings: edit your profile and its visibility, change your email or password, review and revoke sessions, and unlink providers. For access, export, or deletion requests, write to legal@wortool.com from the address on your account. We will respond within 30 days and will never charge you for a first request.

If you are in the EU, EEA, or UK and you think we have handled your data badly, you can complain to your national data protection authority. We would rather you told us first so we can put it right.

11International transfers

Our servers and our providers are located in the United States and in Europe, so using WoRTool involves transferring your data across borders. Where data leaves the EEA or the UK, we rely on the European Commission's Standard Contractual Clauses, the UK International Data Transfer Addendum, or an adequacy decision, as applicable to each provider. You can ask us for details of the safeguards in place for any specific transfer.

12Children

WoRTool is not intended for children. You must be at least 13 years old to hold an account, or 16 in the EU, EEA, or UK. We do not knowingly collect data from anyone below those ages. If you believe a child has created an account, write to legal@wortool.com and we will delete it.

13Changes to this policy

We will update this policy as the service changes. The effective date at the top of the page always reflects the current version. Where a change materially affects how we handle your data, we will give notice on the site, and by email where we hold a verified address for you, before it takes effect.

14Contact

For any privacy question, data request, or complaint, write to legal@wortool.com. Account email such as verification and password resets is sent from accounts@wortool.com; we will never ask you for your password in an email.