□One Account Open the partner account
Affiliate disclosure. The partner link in the masthead and in the bands beside the copy on this page is a sponsored link to a partner operator, and this site may be paid if you open an account through it, at no extra cost to you. It carries rel="sponsored noopener" and opens in a new tab. That matters on this desk in particular: the subject is the rule that one person holds one account, and this site's own revenue depends on a reader opening an account of their own. There is no ranking, no review and no recommendation of any operator anywhere on this site.
One Account / The one-player rule
The clause itself

An account is a relationship with one person

The clause is short and it is doing more work than any other in the terms. It is what makes an identity check meaningful, what gives a deposit limit something to attach to, and what lets an operator act on a self-exclusion. This page reads it as a piece of drafting, clause by clause, and separates what it prohibits from what it permits.

Joins the two: one artefact, one person expectedKeeps them apart: a verified fact that differsA person decides: an overlap a household also produces
Direct answerThe clause states three things: that an account is personal to the individual who opened it, that it cannot be shared, sold, lent or transferred to anyone else, and that only one account per person is permitted with that operator. It is enforced by comparison rather than by consent, and its purpose is to keep every other rule attached to a known person - which is why a second account is treated as a threat to the first one rather than as an extra account.
Personal: named holder onlyNon-transferable: no sale, no giftSingular: one per operatorPurpose: every other rule needs a person

The four obligations the clause creates

A

use Only the holder may play. A third party using the account is using it without a grant. It does not matter whether the holder consented, or that the third party lost their own money: the facility was extended to one person and used by another.

B

hold Only one account each. Not one login, not one device - one account. Two accounts held by one person at one operator is the breach the clause is written for, and it is detected by matching that person's own signals against both records.

C

fund Funds come from the holder. The terms usually require deposits to be made from a payment instrument in the holder's own name, because a card in a third party's name breaks the link between the account and the person it is supposed to represent.

D

truth The declared details are the holder's own. Supplying another person's details, or a document that is not the holder's, is treated separately from sharing an account and usually more seriously - the agreement desk explains how that obligation sits inside the wider contract.

What the rule permits

Being clear about the permitted cases is the whole reason this page is readable. The singular obligation is per operator, and four ordinary situations are not breaches of it.

Worked example - singular per operator, not singular per person (illustrative) One holder, five operators. Accounts held: 5. Breaches of a one-account clause written per operator: 0. The same holder, then opening a second account at one of those five: accounts at that operator 2, breaches 1. So the count that matters is accounts per operator, not accounts in total. A reader with a dozen accounts across a dozen sites has a dozen relationships and no breach; a reader with two at one site has one breach and, in the operator's system, two records that will be compared against each other and resolved in favour of the earlier one. The practical reading: the rule is narrow, it is about duplication at a single counterparty, and the arithmetic that exposes a reader is always a pair - never a total.

Why the clause is written so briefly

Because its purpose is structural rather than commercial. Every control the series has described elsewhere presumes a known individual: a deposit limit is a limit on one person, an exclusion excludes a person, a wagering condition is assessed against one account's play, a tax obligation attaches to a person, and an anti-money-laundering regime is built on knowing who the customer is. A second account held by a known customer is not a new problem - it is a second surface where the same obligations apply without the first one being able to see it.

That is why the consequence of a match is usually heavier than a reader expects from a clause this short. The operator is not protecting a commercial interest in one account; it is protecting the integrity of every rule it wrote about the first one. The consequences page sets out what it does with the money.

Reading the clause in your own terms

  1. Find the words. Search the terms for personal, non-transferable, one account, third party and own name. The obligations in this desk are almost always present, usually within one screen of each other.
  2. Check the scope of "one". Is the singular obligation per person, per operator, per household or per device? That word decides whether a household is exposed, and it is the difference between a narrow clause and a wide one.
  3. Check the funding requirement. Whether deposits must come from an instrument in the holder's own name is stated separately from the sharing prohibition, and it is the obligation a shared card actually breaks.
  4. Check what follows a breach. The remedy clause is where a balance is dealt with, and it is normally written to allow the operator to void and retain. Knowing its shape in advance is the only preparation available.
One point this page will not soften. Using another person's document to open or verify an account is identity fraud in most jurisdictions, and no reading of the clause above makes it a paperwork problem. It also fails on its own terms: the selfie check, the name-to-payment-instrument match and the address trail exist to catch exactly that. The honest cases on this desk are the shared ones, and the honest route is disclosure with evidence rather than substitution.