Entity: OperaHouse Ventures ("OperaHouse Ventures," "we," "us"), a sole proprietorship of Alistair Farr operating under the trade name "OperaHouse Ventures."
Product: Argus, server-side anti-cheat for Minecraft Paper servers, including the Argus proxy plugin, the Argus dashboard, and the replay viewer ("Argus")

1. Overview

This policy explains what data Argus handles, where it goes, and the choices server owners and players have. It covers two groups of people:

  • Server owners and their staff, who buy Argus, install it, and use the dashboard. They're our customers.
  • Players on servers that run Argus.

Argus v1.0 isn't released yet. This policy describes how Argus v1.0 will handle data. The pre-release build sends us no data at all. Pre-order purchases and the Argus waitlist are covered by the ohventures.cc Privacy Policy, not this one.

2. Who decides what happens to player data

  • The server owner is in charge of their players' data. They choose to run Argus, decide how to act on its findings, and hold the secret that links Argus's records to real players. Under laws like the GDPR, the server owner is the "controller".
  • We handle case data on the server owner's behalf to run the dashboard and replay viewer, and only on their instructions. For that, we're their "processor" or "service provider".
  • Model training is the exception. If a server owner opts in (Section 6), we use that server's data to improve our detection models, and for that use we decide how the data is processed.
  • For data about server owners and their staff (licences, accounts, support), we're the controller.

3. What stays on the server

Argus runs on the server as a plugin. Players install nothing, and Argus never reads a player's device, files, or hardware. On the server:

  • Most gameplay data is never saved. Argus reads the movement, aim, clicks, and game events the player's game already sends to the server, holds a few seconds of it in memory, and discards it.
  • Players are pseudonymised. Saved records are labelled with a code made from the player's account ID and a secret generated on that server. The secret never leaves the server, so we can't work out who a code belongs to, and we can't link the same player across two different servers.
  • Argus never collects IP addresses, hardware identifiers, chat messages, or anything outside the game.

4. What reaches us

Case data, for the dashboard and replay viewer

The Argus dashboard is hosted by us and included with every licence. When Argus flags something, the server sends us a case:

  • the check that fired, its reason, and the evidence behind it: the player's movement, aim, clicks, game events, and connection timing, from 30 seconds before the flagged moment to 10 seconds after;
  • for the replay clip, the blocks around the player and the positions of nearby players and mobs over the same 40 seconds (other players appear only as generic figures, without names, skins, or account IDs);
  • any action taken (a kick or ban) and staff decisions on the case, such as confirming or overturning it.

Cases we store contain no usernames, account IDs, IP addresses, hardware IDs, or chat. Players are identified only by the pseudonymous code. When signed-in staff open a case, the dashboard asks their own server to show the player's current username and skin. We don't store those.

Licence and service data

  • Licence checks: your licence key, the Argus version, and the number of servers using the licence, so we can confirm the licence covers them.
  • Staff accounts: the details staff use to sign in to the dashboard (such as an email address) and which server or network they belong to.
  • Security logs: like any website, the dashboard's hosting records the IP addresses and browser details of the people who use it, to keep the service secure.
  • Support: what you send us when you ask for help.

5. How we use data

  • To run the dashboard and replay viewer for the server the data came from, and to show it only to that server's signed-in staff.
  • To check licences, provide support, and keep Argus secure.
  • To train our models, only when a server has opted in (Section 6).

We never sell Argus data. We never share it with third parties, except the providers that host and run Argus for us (Section 8), and where the law requires it. We don't use it for advertising, and we don't build profiles of players.

6. Model training is opt-in

  • The dashboard settings include "Opt in to train our models". It's off by default, including when you upgrade. Unless a server owner turns it on, we don't use that server's data to train or improve our models at all.
  • If it's on, we use that server's pseudonymised case data, and summary measurements taken from it (for example, how regular a player's clicks were), to improve detection. It's still labelled only by the pseudonymous code, so we can't tell who a player is.
  • Turning it off stops any new data being used for training. Data already contributed is kept for the training periods in Section 7, unless the server owner asks us to delete it.
  • Server owners who turn it on are responsible for telling their players first.

7. How long we keep data

  • Cases: deleted 30 days after their last activity by default. A server owner can change this, but never beyond 90 days.
  • Training data (opt-in only): case evidence up to 12 months. Summary measurements are kept in our versioned training datasets until they're deleted on request. When data is deleted, we build a new version of the dataset without it and destroy the old one.
  • When a licence ends: we delete that server's case data within 30 days.
  • Staff accounts: while the licence is active, and deleted within 30 days after it ends or when the server owner removes the account.
  • Purchase records: see the ohventures.cc Privacy Policy. We keep them as long as tax and accounting law requires.

8. Service providers

  • Hosting for the dashboard: we haven't chosen these providers yet. We'll list them here, with where they store data, before Argus v1.0 is released.
  • Stripe handles payments, Resend sends our emails, and Google Workspace hosts our support inbox, as described in the ohventures.cc Privacy Policy.

Each provider handles data only to provide its service to us, under confidentiality and data protection terms.

9. Automatic kicks and bans

If a server owner turns on automatic enforcement, Argus can kick or ban a player on its own. Each check only acts after meeting the accuracy thresholds in our documentation, and every action is saved with the evidence behind it. The server owner decides whether to use automatic enforcement and handles appeals. A player who thinks they were wrongly actioned should contact that server's staff.

10. Your rights

Players

Contact the server's owner or staff first. Only the server holds the secret that links Argus records to you. The server owner can find your data, export it, and delete it, including from any training data contributed from that server. Argus is designed so a request can be completed within 30 days. If a server owner doesn't respond, or you have a question about us, email [email protected]. We'll help, although we can't identify you from our records on our own.

Server owners and staff

You can access, correct, export, or delete your account data, or have us delete your server's case and training data, by emailing [email protected]. Residents of the European Economic Area, the United Kingdom, and some U.S. states have additional rights under local law. We'll respond within the time your law requires.

11. Children

Many Minecraft players are young. Argus is designed to collect as little as possible about any player: no names, account IDs, IP addresses, or chat in the cases we store, and nothing that lets us identify a player. Server owners are responsible for any notices or consents their players' ages require. Argus licences and dashboard accounts are for server owners and their staff, not for children under 13.

12. International users

OperaHouse Ventures is based in the United States. Data we receive may be processed in the United States or wherever our hosting providers operate (Section 8). If you're in the EEA, the UK, or another place that requires safeguards for cross-border transfers, contact [email protected] to learn which safeguards apply.

13. Security

We encrypt data in transit, pseudonymise players before anything leaves the server, limit who on our side can access data, and keep secrets on the server side only. No system is completely secure. If you think Argus data has been exposed, contact [email protected].

14. Changes to this policy

We'll update this policy when Argus changes, and before v1.0 is released. The date at the top shows the latest version. We'll tell server owners about material changes by email before they take effect.

15. Contact