Privacy Policy

This policy describes what BetJury collects when you read the site, open an account, publish testimony or file a case, why we collect it, and what you can do about it. It is written to be read rather than to be survived, so it is specific about mechanisms instead of reserving every right in general terms.

If you only read one section, read Cookies and tracking. It is the part most gambling sites are least honest about.

Who we are

BetJury publishes casino reviews, an editorial safety audit, community testimony and a public complaint docket. We are the data controller for everything described here. This policy covers what we do with your data; the terms of use cover the agreement for using the site itself, including what happens to testimony you have published if you close your account.

For anything in this policy — a copy of your data, a correction, a deletion, or a question about a specific mechanism — write to privacy@betjury.com. For a subject access request, the usual UK GDPR deadline is one calendar month. A permitted extension for a complex request or multiple requests must be explained within that period. ICO guidance.

What we collect, and why

If you only read the site

An account is not required to read a review. Ordinary server request logs can contain technical data such as an IP address; the application does not attach a reading history to a named account.

Our web server keeps ordinary request logs of the kind every web server keeps, which are used to keep the site running and to investigate abuse, and nothing in the application writes a reading history against a person.

If you open an account

We store your email address, the display name you choose, and — if you set one rather than signing in by emailed link — a password hash. The hash is produced with scrypt; the password itself is never stored and cannot be recovered from it, by us or by anyone who obtained the database.

We create a session when you sign in: a random token in a cookie, and a matching row recording only which account it belongs to and when it expires. Signing out deletes the row.

Why: to give you an account and keep you signed in. Lawful basis: performance of a contract with you.

If you publish testimony

Your rating, optional title and review text are published on the operator's review page, attributed to your Juror handle. Your email address is never shown. Votes marking a review helpful are stored against your account so that the same person cannot vote twice.

Testimony is public by design. Treat anything you write there as permanently readable by anyone, including search engines.

Why: to publish the community score. Lawful basis: performance of a contract with you.

If you file a case in the Tribunal

We store the category, the disputed amount and currency, your description of the dispute, the date you say you contacted the operator, and any evidence you attach.

Two mechanisms matter here.

Attachments are private by default. They are stored outside the public site and are not published with the case unless you ask for a specific document to be included.

Your docket identity is unlinkable across cases. A case shows you as "Juror #1234" — a number derived from a keyed hash of your account and that particular case. The same person filing two cases appears under two different numbers, so a reader, an operator or a scraper cannot connect your cases to each other, or to the testimony you have published under your Juror handle.

Why: to mediate the dispute and publish the record. Lawful basis: performance of a contract with you, and our legitimate interest in publishing an accurate register of disputes.

When you click through to an operator

We record that a click happened: which operator, which jurisdiction, which placement on which page, and when. Alongside it we store a keyed hash of a random identifier held in the affiliate_session cookie.

We deliberately do not record your IP address, your browser's user-agent string or your account ID against a click. The hash exists so that a commission can be reconciled and so that we can tell one visit from another; it is not a profile, it cannot be reversed into an identity, and it is not shared with anyone.

Why: to attribute commission and measure which placements work. Lawful basis: our legitimate interest in operating a funded publication and in verifying that we are paid correctly.

Security and audit records

Security-relevant actions on an account — a password being set, staff acting on a case — are written to an audit log with the action, what it affected, when it happened, and a keyed hash of the originating address. The address itself is not stored. Two entries from the same origin still match each other, which is what a security log needs; the log is not a store of visitor IP addresses tied to named accounts.

Why: to detect and investigate account compromise and abuse. Lawful basis: our legitimate interest in the security of the service.

Email we send you

Sign-in email is transactional. Case notifications are recorded in the application; this policy does not promise that every case event is delivered by email.

The bulletin is separate and consent-based. Subscribing records three things and nothing else: your address, the moment you gave consent, and the page you gave it from. It creates no account and is not connected to anything else you do here.

We are being exact about its state, because the form used to say "You're on the list" while storing nothing at all. No bulletin has been sent yet. Subscribing today records your consent so that you are on the list when the first one goes out, and every message will carry a one-click unsubscribe. You do not have to wait for that: the unsubscribe link works from the moment you subscribe, and writing to privacy@betjury.com removes you just as well.

Cookies and tracking

We set two cookies, and neither of them is for advertising.

There is no advertising cookie, no remarketing pixel, no social-network tracker, and no cross-site profile of you anywhere in this site.

Analytics. No analytics provider is running on this deployment. If one is ever added it will be a cookieless one — the component that would load it can only load cookieless providers and will not accept Google Analytics — because anything storing an identifier on your device requires consent we do not currently ask for, and we would rather run without measurement than run without consent.

Fonts. Typefaces are served from this domain. They are compiled into the site at build time, so your browser never makes a request to a font host and no third party learns that you visited.

Who else sees your data

Very few parties, and none of them for their own purposes.

• Our hosting provider, which runs the servers and the database.
• Our email provider, which delivers sign-in links and notifications. It sees your email address and the content of those messages.
• The operator named in a case, which is shown the case as published — your allegation, under your unlinkable docket number, without your email address or your account name.

We do not sell personal data. We do not share it with advertisers, data brokers or affiliate networks. An operator learns that a click came from BetJury; it does not learn anything about you from us.

How long we keep it

• Account data for as long as your account exists, and then as described under deletion below.
• Published testimony and cases indefinitely, because a register that can be quietly rewritten is not a register. Deleting your account removes your name from them rather than removing the record.
• Sessions until they expire or you sign out, whichever is first.
• Click records for as long as a commission from them could still be queried or reconciled — in practice a small number of years, since an affiliate accounting dispute has a long tail. They hold no address, no user-agent and no account id, so what survives is a hashed session identifier and which page it came from.
• Audit entries for as long as they are useful for investigating account compromise, which means years rather than months: a security log that is cleared quickly cannot show a pattern, which is the only thing it is for. The originating address is a keyed hash, never the address.
• Bulletin subscriptions until you unsubscribe, plus a record that the address unsubscribed — kept precisely so we do not mail an address that asked us not to.

Your rights

Under the UK GDPR and the EU GDPR you can ask us to give you a copy of your data, correct it, delete it, restrict or object to how we use it, or receive it in a portable format. You can also withdraw consent to the bulletin at any time without affecting anything else.

Getting a copy right now. Sign in and open your data export. It returns everything we hold that is tied to your account — profile, testimony, cases, helpful votes and badges — as a JSON file, immediately and without asking us.

Deleting your account. Write to privacy@betjury.com from the address on the account. We remove your profile and detach your name from anything you published: testimony is either removed or shown without attribution, and existing cases keep their docket number and their facts but lose their connection to you. We are being plain that this is currently a request handled by a person rather than a button in your settings, because a policy promising a button that does not exist is worse than one that tells you where to write.

Complaining about us. If you think we have handled your data badly, tell us first — we would rather fix it. You also have the right to complain to a supervisory authority: in the UK the Information Commissioner's Office (ico.org.uk), and in the EU the authority in the country where you live.

Automated decisions, and what we do not do

Our scores are computed by software, and they are about operators, not about you. Nothing on this site makes an automated decision that produces a legal effect on you or similarly significantly affects you, and there is no profiling of visitors for advertising, pricing or eligibility.

The one automated thing attached to an account is the Juror level, which rises with published testimony and helpful votes. It changes how your testimony is weighted in an operator's community score. It has no effect outside this site and no bearing on anything you are offered.

Giving us any of this data is voluntary. You need an email address to hold an account, publish testimony or file a case, because there is no way to run those without one — but nothing on this site requires an account to read.

Children

This site is for adults. Nothing here is directed at anyone under 18, we do not knowingly hold data about a minor, and if you believe we have some, write to privacy@betjury.com and we will remove it.

Where your data is held

BetJury uses hosting and email providers to operate the site. The precise processing locations and transfer arrangements have not been confirmed for this update. The earlier specific claim that all data stayed on a Manchester server was unsupported and has been removed. Ask privacy@betjury.com for the applicable provider and transfer information before supplying sensitive material.

Changes

When this policy changes materially we say so on the page and date the change rather than editing quietly — including the removal of the unsupported hosting-location claim above.

This version: 9 September 2026.