What Epsilon sends and stores

The plugin checks players on the server by itself. Two things leave a server, and each has a switch in plugins/epsilon/config.yml.

To Epsilon's cloud

Epsilon's cloud checks players with more than the plugin carries, and sends back what to do about them: a kick, a ban, or less damage dealt.

It receives gameplay data: what each player does in the game, with their name and UUID. It never receives the words players type in chat, on signs or in books.

Technical information: the server's IP address and software versions, and each player's client version, brand, settings and mods. Never a player's IP address.

A false-flag report from staff also carries the staff member's name and their note.

cloud: false stops all contact with the cloud. The plugin goes on checking players by itself.

To the update server

To run the newest release, Epsilon asks the update server for it. Each request carries only Epsilon/<version> (<state>).

auto-update: false stops all contact, including the withdrawal of a faulty release.

On epsilon.ac

Signing in creates an Epsilon account storing your email address, optional display name, and linked Discord ID and handle if you connect Discord. Signed-in browsers receive an encrypted HttpOnly session cookie, and active sessions record the browser family and a truncated /24 or /48 network prefix so you can sign out unfamiliar devices.

Billing

Paid Epsilon Cloud subscriptions are processed by Polar (polar.sh) as Merchant of Record, which handles payment methods, tax calculation, and invoices. Epsilon stores your plan status and Polar customer and subscription identifiers, and never receives or stores your card details.

Your data

To see, correct or delete what Epsilon holds about you, write to support@epsilon.ac.