BitStarz deposit limits, cooling off and self-exclusion

Two different numbers are called a deposit limit

Search for a deposit limit at BitStarz and you will find two unrelated numbers wearing the same name. One is a ceiling the operator sets. The other is a cap you set on yourself. They live in different places, they are published in different documents, and only one of them is a control you can actually use.

The operator's ceiling is a term of the contract. Clause 8.6.1 of the BitStarz terms says the maximum deposit depends on the payment method you choose and appears when you choose it. There is no published table, so the number you see is the number your method allows on the day you look. The crypto minimums work the other way round: clause 8.6.8 says each currency has a minimum shown on the deposit page, and a deposit below it cannot be processed and cannot be returned. That second half is the part worth reading twice, because a small test deposit in the wrong currency is money that goes nowhere.

Your own cap is a control, not a term. It is set inside your account, it runs per day, week or month in the currency you chose, and it is described in the operator's FAQ rather than in the terms. This guide is mostly about that one, because it is the one a reader searching for a deposit limit usually means, and it is the one the public policy page never mentions.

Keeping the two apart matters before you deposit. A review site that quotes a maximum deposit is quoting the operator's ceiling, which protects the operator's payment risk. It says nothing about whether you can cap yourself, how quickly the cap applies, or what happens when you want it lifted.

The four limits, and what each one actually stops

BitStarz describes four separate limits in the responsible gaming section of its FAQ, all set from the same account limits area. They are not variations on one control. Each one caps a different quantity, and choosing between them is a question of which failure you are guarding against.

The deposit limit caps how much you can put in during a day, week or month, in the chosen currency. It is the only one of the four that acts before the money reaches the account, which makes it the most useful of the set for anyone whose problem is topping up.

The loss limit stops play once you have lost a set amount in the period. It acts on net losses rather than on deposits, so it can end a session that your deposit limit would have allowed. If your pattern is depositing once and playing it down, this is the control that matches it.

The wagering limit stops play once a set amount has been wagered. The operator's own description is unusually candid about what that means: you can wager, in its example, €100 without your balance changing very much. That is a turnover cap, not a spend cap, and it is the easiest of the four to misread. A high-turnover, low-house-edge game can move a wagering limit a long way while barely touching your balance.

The session limit logs you out after a set period of play. The FAQ then says you can log back in to start a new session. That is worth knowing before you rely on it: it controls the length of one sitting, not the number of sittings. The operator's own wording makes it a pace control rather than a stop.

Where the setting is, and the 24-hour rule

The limits are not on the Play Safe page, which is where most readers would look first. They are in the account limits area inside your logged-in account, which the FAQ links to directly. We did not log in to observe the screen, so this guide describes the controls from the operator's own description of them rather than from a screenshot.

The rule that decides how you use them is the delay. To raise or remove a limit you edit it in that area, choose a higher amount or disable it, and the operator sends a confirmation email to your registered address. The change takes effect 24 hours after you confirm that email. The FAQ gives the reason in plain language: the delay exists so that you cannot, on an impulse, go over and beyond the limit you chose for yourself.

Two practical consequences follow. First, the 24 hours runs from your confirmation, not from the click, so an email left unconfirmed is a limit that never starts or never lifts. Second, a limit is protection for tomorrow, not for the next ten minutes. If you need a stop right now, a limit is the wrong instrument, and the next section is the one to read.

The FAQ describes the raise and remove path in detail and says nothing about how long it takes to lower a limit or to set one for the first time. It would be reasonable to assume tightening is immediate, but the operator does not say so, and this page will not pretend it does. If the timing matters to you on the day, ask support in writing and keep the reply.

Cooling off or self-exclusion: which one is a wall

BitStarz offers two time-based exits, and the difference between them is the difference between a locked door and a closed one.

A cooling off period runs from one day to six months. During it you can still log in, but you cannot deposit, you cannot receive promotions, and you cannot play for real money. It ends automatically when the period you set runs out, and the FAQ adds that you can reopen sooner after a 24-hour waiting period. So cooling off blocks the money and the play while leaving the account, its balance and its history in front of you.

Self-exclusion runs from one day to permanently. While it is active you cannot log in at all, and the account cannot be reopened before the period ends. The operator emails you when the time is up. That is the harder instrument, and it is the only one of the two that removes the ability to log in rather than the ability to spend.

The choice is not about severity, it is about which behaviour you are trying to interrupt. If the problem is the deposit button, cooling off answers it and leaves your account and its balance in front of you. If the problem is opening the site at all, self-exclusion is the tool that matches, because cooling off still lets you in.

One warning before you choose. The FAQ does not say what happens to an active bonus or a pending withdrawal during either period. If you are holding bonus funds or waiting on a payout, ask support what will happen to them before you act, and get the answer in writing. A hard stop that quietly forfeits a balance is a worse outcome than the one you were avoiding.

The policy page and the FAQ do not say the same thing

Clause 1.9 of the terms binds every player to the operator's policies, including a Responsible Gaming Policy described as accessible via the Play Safe page. That page is therefore not decorative. It is contractually part of what you agreed to. Its entire body text, read in full on 17 October 2026, is four short paragraphs.

Those paragraphs say that if you think you may be showing signs of problem gambling you can opt to self-exclude by contacting support at the published address. They then list three external organisations: GamCare, Gordon House, and a link labelled Gam-Anon that points at gamblersanonymous.org. Gam-Anon is a separate fellowship for the families of gamblers, so the label and the destination do not match, which tells you something about how closely the page is maintained.

What the page does not contain is the policy it is named for. There is no deposit limit, no loss limit, no wagering limit, no session limit, no cooling off period, no description of the 24-hour rule, and no link to a separate policy document. A reader who trusts the policy page would reasonably conclude that BitStarz offers self-exclusion and nothing else.

The FAQ says otherwise. The four limits and both time-based exits are described there, in more operational detail than most operators publish, including the reasoning behind the delay. The gap is a publishing problem rather than a product problem: the tools appear to exist, and the page that is supposed to explain them does not mention them.

That gap has a practical cost. If you want a limit, the FAQ is the document to read, not the policy page. And if you are comparing BitStarz with another operator on player-protection grounds, compare the FAQ, because that is where this operator actually documents what it does.

The parts that are not a hard stop

Four things about these controls are easy to overestimate, and all four follow either from the operator's own wording or from its silence.

A daily limit is not a monthly limit. The four controls run per day, week or month, and that period is a choice you make when you set them. A daily cap resets every day, so a month of daily caps can be a very different number from the monthly figure you had in mind. If your concern is the month, set the month.

A cooling off period is not permanent, and it is not even fixed. It ends automatically at the time you chose, and it can be ended sooner after a 24-hour wait. If you need something that cannot be undone early, cooling off is not it.

A deposit limit is set in the chosen currency. The FAQ does not explain how a limit behaves if you deposit in more than one currency, and this page will not guess. If you hold balances in several, ask support whether one limit covers the total or one limit applies per currency, because the answer changes what the limit is worth.

The fourth is the one that costs money. Clause 8.2 says that if an account holds both real money and bonus funds, the bonus is only available for wagering once the real money has been used, and that withdrawing your deposit before fulfilling the bonus turnover forfeits the bonus and the winnings from it. A spending control and a bonus commitment can therefore pull in opposite directions. If you have an active bonus and you are about to set a hard limit, read clause 8.2 first, or ask support what the limit will do to the bonus.

Setting it up before you deposit

The sequence below is the one that survives the 24-hour rule and the currency question, and most of it happens before you open the deposit screen.

Decide the number away from the site. A limit set while the deposit page is open is a limit chosen by the same mood that opened it. Decide a monthly figure first, then divide it into the period you will actually set, and write it down somewhere outside the account.

Set the deposit limit first and the loss limit second, in that order, because they cap different things and the deposit limit is the one that acts before the money moves. If your pattern is one deposit played down over several sessions, the loss limit is the one doing the real work.

Confirm the email immediately, then check the result. The 24 hours runs from your confirmation, so the email is the step that starts the clock, and it is the step people skip. After the delay, open the account limits area and confirm the value is the one you chose. If it is not, you have a support ticket with a date and a confirmation email behind it, which is a much stronger position than a recollection.

And if what you need is a stop today rather than a cap for next month, the limits are the wrong instrument. Cooling off blocks deposits and real-money play; self-exclusion blocks login. Neither carries the 24-hour raise rule, which is what makes them different in kind rather than in degree. The FAQ does not say how quickly either is applied once you request it, so ask support when you ask for the block, and keep the reply. The limits are for the version of you who will be back tomorrow. This page cannot tell you what your number should be, and it will not pretend that a well-documented control is the same thing as a decision.