Privacy Policy
What Mizan holds about players and organizations, where it comes from, why, and how long it's kept.
Last updated .
Who Handles Your Data
KORDU LTD runs Mizan, at mizan.ac and api.mizan.ac, and is the data controller for everything on this page. Company number 16836154, registered in England and Wales. The registered office is First Floor Office, 3 Hornton Place, London W8 4LZ.
What Mizan Holds About Players
Bans from public lists. Mizan reads the ban lists game communities publish on their own websites; the communities page lists every one. For each ban it keeps what the list shows: the player's account ID (usually a SteamID), the name the list gives them, the reason, when the ban started and ends, the game or server it was given on, and the admin who gave it when the list names one. Where a reason says the player is another account ("alt of ..."), Mizan notes the link between the two accounts.
Bans organizations add. An organization that contributes can send its own bans through the API, with the same kinds of details.
Mizan's own findings. Mizan's anti-cheat runs on Justified's game servers. When it catches cheating, the record shows the account, what was detected and when. Justified's own privacy policy covers what its servers record while you play there.
Public Steam details. When someone looks up a Steam account, Mizan reads what Steam publishes about it: its name and avatar, names it used before, Steam's own ban flags, and its friends list and game library if they're public. Whatever Steam keeps private stays private here.
Lookups. We see the account ID that was looked up and the IP address the request came from, which is used to apply rate limits. We count how often each record is viewed each day, without keeping who viewed it, and we don't keep a history of who looked up whom.
What Mizan Holds About Organizations
An organization that uses the API gives us its name and description, its servers' names, games and addresses, the accounts of the people who manage it, and its API keys. Each request it makes is checked against its key and counted against its rate limit.
Who Can See What
Anyone can read a player's record on mizan.ac: each ban with its reason and dates, under the name of the community or organization that published it, the admin's name where that list shows it publicly, and Mizan's own findings. Organizations with a key read the same record through the API.
A Steam avatar on a record is loaded from Steam's servers, so Steam can see the visitor's IP address.
Why We Use It
- To keep and publish player records, so game communities can keep cheaters and rule breakers off their servers and players can see what is said about them. This is our legitimate interest. The bans come from lists their communities already publish.
- To apply rate limits and keep Mizan running and safe from abuse. This is our legitimate interest.
- To provide an organization's account and API access. This processing is necessary to perform our contract with it.
- To answer requests from the police or a court. This processing is required to meet our legal obligations.
Cookies
mizan.ac uses no advertising or analytics cookies. If you sign in to manage an organization, a cookie keeps you signed in. The network in front of the site may set its own cookies to keep the site up and block attacks.
Who Else Handles It
- Our hosting, database and network providers
- Steam, for public profile details and the avatars shown on records
- Organizations with an API key, which read player records
- The police or a court, when the law requires it
We don't sell personal data, and we don't work with advertisers or data brokers. Some of our providers process data outside the UK, including in the United States. Where a US provider is certified under the UK Extension to the EU-US Data Privacy Framework, that covers the transfer. For any other transfer, contact us and we'll tell you which safeguard applies.
How Long We Keep It
| What | How long |
|---|---|
| Bans read from a community's public list | While the list publishes them. A ban the list lifts or drops stays on the record, marked as ended |
| Bans an organization adds through the API | While the organization keeps them. A ban it ends stays on the record, marked as ended |
| Findings of Mizan's anti-cheat | On the player's record, unless a review clears them |
| The history of changes to each ban | 90 days |
| Public Steam profile details read during a lookup | With the player's record, refreshed when the account is looked up again |
| The IP address a request comes from | Counted against the rate limit for the minute it covers. Our hosting provider's request logs keep it for up to 7 days |
| Organization accounts, their servers and keys | While the organization exists |
Your Rights
Under UK data protection law you can ask us to:
- Give you a copy of the personal data we hold about you
- Correct anything inaccurate
- Delete it
- Restrict how we use it
- Give it to you in a format you can take elsewhere
You can also object to anything we do on the basis of our legitimate interests, including publishing your record. We'll stop unless we have compelling grounds to continue, and we'll tell you what they are.
A ban from a community's list is that community's decision, so the quickest way to get one corrected or removed is usually through them. The corrections page explains how, and what we do when you come to us directly. We'll ask you to prove the account is yours, then answer within one month.
You can complain to the Information Commissioner's Office at ico.org.uk. If you live in the EEA, you can also complain to your local data protection authority.
Changes
We update this page when what Mizan holds or how it uses it changes. The date at the top shows the current version.
Contact
Mizan's email address will be listed here. By post, write to KORDU LTD, First Floor Office, 3 Hornton Place, London W8 4LZ, and say your letter is about Mizan.