Data & privacy

The whole product is built to hold casinos accountable without exposing the players who make it possible.

What we read, and what we hide

You upload the whole screenshot, because the casino's own interface around the transaction is what makes it evidence. When we read it we detect and mask the fields we do not need, and hide your balance, then ask you to approve the masked version before anything publishes. (spec 2.6)

• Files are scanned for malware and stripped of location and other EXIF data.
• The unmasked original is kept only long enough to verify the record, then destroyed. The masked version stays while the record is published.
• If masking fails, the record files as typed-only and the image is not stored.

Amounts are always banded

Public pages, the ticker, and shared links show amounts in bands, never exact. An exact amount at a named casino on a named date could identify you, an operator's payment team could match it in under a minute. You may reveal an exact amount on your own records if you choose. (spec 3.1)

We never build a sellable file on you

We never sell, and never expose, a per-person cross-casino view. The link between your accounts is stored so that it cannot be rebuilt or exported even if the company is sold, subpoenaed, or breached. Protecting that graph comes before any feature that depends on it. (chapter 11 / graph protection)

Your rights

You can request a copy of your data or its deletion at any time through Contact. Deleting your account removes your identity link, published records stay on the casino page in banded, de-identified form because they are part of the public record.