A player opens the ShadowBet FAQ because something is stuck: a deposit has not appeared, a withdrawal is pending, or a document was rejected. The first question is not what the FAQ says about that specific problem. The first question is what an FAQ page is structurally able to settle, because the answer determines whether the reader should keep reading or go somewhere else entirely.
The split every FAQ page is built on
An operator FAQ is a collection of short answers to recurring questions. The word that matters is recurring. The page exists to absorb questions that many players ask, so that support staff do not answer the same thing hundreds of times. That purpose shapes what the page can and cannot do.
An FAQ can answer questions whose answer is the same for every reader: which documents are accepted for verification, what the deposit routes are, where a transaction history is displayed, how a self-exclusion request is submitted, what happens to an abandoned session. These are process questions. The answer describes a route, a list, or a sequence of steps, and it does not change from one account to the next.
An FAQ cannot answer questions whose answer depends on the reader's account: why a specific withdrawal is still pending, whether a particular document was accepted, what bonus is attached to a particular deposit, whether a self-exclusion has taken effect. Those answers live in the account itself, in the cashier, in the verification screen, or in a message from support. No FAQ can contain them, because no FAQ knows who is reading it.
What the FAQ can settle bindingly
When an FAQ page states a process, that statement is usually reliable in a way that a promotional figure is not. A process changes rarely, and when it changes the operator has to update every page that describes it. So the reader can treat the FAQ as a useful source for these categories:
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted verification documents | Compliance requirements are revised, and the list of accepted documents can be shortened or extended | The FAQ's verification or KYC section, cross-checked against the account verification screen |
| Deposit and withdrawal routes | Payment providers are added and removed, and a route available for deposits may not be available for withdrawals | The FAQ's payments section, cross-checked against the cashier for the reader's own region and method |
| How to submit a self-exclusion request | The channel for the request may move from a form to a support ticket or a dedicated tool | The FAQ's responsible-gaming section, cross-checked against the account settings |
| What happens to an abandoned session | Timeout lengths and the treatment of unfinished rounds are configurable and may be revised | The FAQ's account or security section, cross-checked against the terms of use |
| Where transaction history is displayed | Interface changes move the history link or rename the screen | The FAQ's account section, cross-checked against the actual account menu |
| Which support channels exist | Channels are added, removed, or have their hours changed | The FAQ's contact or support section, cross-checked against the support page itself |
The pattern is visible in the third column: the FAQ is a starting point, not the end. The reader confirms the FAQ's statement against the screen where the process happens. That is not distrust of the FAQ; it is the recognition that an FAQ is a summary, and a summary can lag behind the interface it describes.
Where the FAQ stops being binding
The moment a question contains the word "my" — my withdrawal, my bonus, my verification status, my account — the FAQ stops being the source of truth. The page cannot know which account is reading it, so any answer it gives to a my-question is necessarily generic. It describes what usually happens, or what the operator's policy is, but it does not describe what is happening to this reader right now.
Three examples make the boundary concrete. A reader asks why a withdrawal has been pending for three days. The FAQ may say that withdrawals are processed within a certain window, but that window is a policy statement, not a status report. The reader's actual withdrawal has a status — pending, under review, awaiting documents, released — and that status is visible only in the cashier or in the account's transaction history. The FAQ cannot see it.
A reader asks whether a bonus is active. The FAQ may describe how bonuses are credited in general, but the reader's specific bonus has a state: active, wagering in progress, expired, forfeited. That state is in the account's bonus panel, not in the FAQ.
A reader asks whether a document was accepted. The FAQ may list the requirements a document must meet, but the acceptance decision is made per account, per document, by a process that leaves a record in the verification screen or in a support message. The FAQ cannot confirm or deny it.
The items that migrate out of the FAQ
Some questions start in the FAQ and end somewhere else because the answer is too volatile to live in a static page. A reader who finds a bonus percentage in an FAQ should treat it as a snapshot, not a promise. Promotional terms are revised constantly, and the operator's incentive is to keep the current terms on the promotions page, not to chase every FAQ mention of an old figure.
The same applies to any figure that looks like a limit: a minimum deposit, a maximum withdrawal, a wagering multiple, a fee. These are terms, and terms have a single binding home. The FAQ may repeat them for convenience, but the repetition is only as good as the last time someone updated it. The reader who needs the figure should read it off the page that governs it — the promotions terms for bonus figures, the cashier for deposit and withdrawal limits, the terms of use for account-level rules.
There is a subtler category: questions the FAQ may answer with a sentence that is true but incomplete. "Contact support" is not an answer to "why is my withdrawal pending"; it is a routing instruction. "Documents are reviewed in order received" is not an answer to "why was mine rejected"; it is a description of a queue. The reader should recognise these as pointers, not resolutions. They mean the answer is account-specific and lives in a channel the FAQ cannot access.
What the absence of an item means
An FAQ page is selective by design. It answers the questions the operator expects to be asked most often. The absence of a question from the FAQ does not mean the operator has no policy on it; it means the operator has not chosen to put that policy in the FAQ. The binding statement, if one exists, is elsewhere — in the terms of use, the privacy policy, the AML page, or a support response.
This matters most for questions with financial consequences. If the FAQ does not state a withdrawal fee, the reader cannot conclude there is no fee. The fee, if any, is stated in the cashier or the withdrawal policy. If the FAQ does not state a wagering multiple, the reader cannot conclude there is no wagering requirement. The multiple, if any, is stated in the promotions terms. An FAQ is not a complete contract; it is a curated list of answers, and curation is omission.
The reader's correct move when an item is missing is not to assume the most favourable answer. It is to find the page that governs the item and read it there. The FAQ's silence is not evidence of anything except that the operator did not put the answer in the FAQ.
Reading the FAQ as a map, not a contract
The useful mental model is that the FAQ is a map of the operator's pages and processes, not a contract between the reader and the operator. A map tells you where things are; it does not tell you what they will say when you get there. The FAQ tells the reader that verification exists, that withdrawals exist, that bonuses exist, and roughly how each works. The binding details are on the pages the FAQ points to.
That is why the cross-checking habit is the single most valuable thing a reader can take from any FAQ. For every process answer, the reader should ask: which screen or document states this in a way that is binding on my account? The FAQ's answer is a summary; the screen's answer is the state. The two can differ, and when they differ, the screen wins.
This page is an independent summary of what an operator FAQ page covers and where it stops. It is not published by ShadowBet, and it states no figure or status for that operator; the operator's own FAQ and the pages it points to are the only binding sources for any specific question.
FAQ
Can I rely on the ShadowBet FAQ for withdrawal times?
The FAQ may state a general processing window, but that window is a policy statement, not a status report for any specific withdrawal. The reader's own withdrawal status is shown in the cashier or transaction history, and that is the binding source for that withdrawal.
What should I do when the FAQ does not answer my question?
Find the page that governs the topic — promotions terms for bonus figures, the cashier for payment limits, the terms of use for account rules — and read it there. If the answer is account-specific, the support channel is the only place it can be obtained.
Does the FAQ tell me whether my verification document was accepted?
No. The FAQ can list the requirements a document must meet, but the acceptance decision is made per account and is recorded in the verification screen or in a support message. The FAQ cannot see the reader's account.
Why might a figure in the FAQ differ from the promotions page?
Promotional terms change frequently, and the FAQ is a static page that may not be updated every time a figure changes. The promotions page is the binding source for bonus terms, and any conflict should be resolved in its favour.
Play responsibly
Gambling should be treated as paid entertainment, never as a way to earn income or recover losses. 1-800-MY-RESET (1-800-697-3738)
18+ or 21+ depending on where you are; follow the minimum age that applies to you.
This article is general information about how these mechanics work. It is not legal advice and not a recommendation to gamble or to use any particular operator. Availability and legality differ by jurisdiction — check the rules that apply where you are.
