The moment a FAQ stops being enough
A player opens an operator's FAQ because a decision is stuck. A deposit has not appeared, a withdrawal is pending, a document was rejected, or a bonus did not credit. The FAQ is the first place most readers look, and it is useful for exactly one category of question: questions whose answer is the same for every account. The moment the answer depends on the reader's own balance, history, verification state, or the current version of a promotion, the FAQ stops being a source and becomes a signpost. It can tell the reader which department handles the matter and which document governs it. It cannot tell the reader what will happen to their account. That distinction is the whole structure of this page.
Bitofgold publishes its FAQ as a collection of short answers grouped by topic. The page is designed to reduce contact volume, so it answers the questions that recur most often and that do not require looking at an individual account. A reader who understands that boundary will save time: they will use the FAQ for routes and document lists, and they will go to the binding source for anything that involves a number, a deadline, or a status.
What a FAQ can answer bindingly
An operator FAQ is binding when it describes a process that is identical for every player. The list of documents accepted for identity verification is one example. The steps to enable two-factor authentication is another. The route a withdrawal takes once approved, and the fact that a deposit method may not be available for withdrawal, are process facts that do not change from account to account. The FAQ can also state which department receives a particular kind of request, such as a self-exclusion request or a complaint about a game round.
These answers are binding in a limited sense: they describe the operator's current procedure. They do not create a right. If the FAQ says a withdrawal is processed by the payments team after verification, that tells the reader who does what. It does not tell the reader that their withdrawal will be approved, or when. The binding force of a process answer is that the operator has described its own procedure; if the procedure changes, the FAQ should change with it, but the reader's remedy is not the FAQ text.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Accepted identity documents | Compliance requirements evolve; new document types may be added or old ones dropped | The FAQ's verification or KYC section, and the account verification page |
| Withdrawal method availability | Payment providers change their rules; a method may be removed for withdrawals while remaining for deposits | The FAQ's payments section and the cashier's withdrawal screen |
| Steps to enable two-factor authentication | The security interface is updated; the sequence of taps changes | The FAQ's security section and the account settings page |
| Department for self-exclusion requests | Internal team names and contact routes are reorganized | The FAQ's responsible gambling section and the support contact page |
| Bonus eligibility conditions | Promotions are rewritten frequently; a condition in force this month may be gone next month | The promotions terms page, not the FAQ summary |
| Verification review time | Queue length and staffing change; any stated window is an estimate, not a promise | The FAQ may give a typical range, but the account's verification status page is the live source |
What a FAQ cannot answer, and why
A FAQ cannot answer anything that depends on the reader's individual account. A question like "why is my withdrawal still pending?" has no single answer that is true for every player. One account may be waiting for a document; another may have triggered a review threshold; a third may be within a normal processing window. The FAQ can list the common reasons for a pending withdrawal. It cannot say which reason applies to a specific reader. The only place that information exists is the account's withdrawal history and any message the operator has sent to that account.
The same limit applies to every question that involves a current figure. A FAQ may explain that a wagering requirement applies to bonus funds and that it is expressed as a multiple of the bonus amount. It cannot state the multiple for a particular promotion, because that number is set in the promotion's own terms and changes from one offer to the next. A FAQ may explain that withdrawal limits exist and that they are usually stated per day, week, or month. It cannot state the limit that applies to a reader's account, because limits vary by player class, verification level, and the current terms. The reader who wants a number must read the terms page, the cashier, or the promotion page, not the FAQ.
There is a second reason a FAQ cannot be the final source for figures. FAQ pages are maintained by support teams, not by the teams that write terms and conditions. When a promotion changes, the terms page is updated first. The FAQ summary may lag behind, or it may be deliberately vague so that it does not need to change every time a number changes. A reader who relies on a FAQ figure and later disputes an outcome will be pointed to the terms page. The FAQ's silence on a number is not a defect; it is the correct design, because the number lives elsewhere.
Where the binding answer lives
For every question the FAQ cannot answer, there is a document that can. The hierarchy is stable across operators. Terms and conditions govern the contract: what the operator may do, what the player agrees to, and what happens in a dispute. The privacy policy governs data: what is collected, why, and how long it is kept. The AML policy governs thresholds: what triggers a review, what documents are requested, and what happens if a review is not passed. The promotions terms govern bonuses: the wagering multiple, the eligible games, the time limit, and the maximum withdrawal from bonus winnings. The cashier and the account pages govern the reader's own state: balance, pending withdrawals, verification status, and available methods.
The FAQ's proper role is to route the reader to the right one of these. A well-built FAQ does not restate a wagering multiple; it says that wagering requirements are set per promotion and points to the promotions terms. It does not restate a withdrawal limit; it says limits are shown in the cashier and in the terms. It does not promise a verification time; it says the account page shows the current status and that the support team can be contacted if the status has not changed. The reader who treats the FAQ as a map, not as the destination, will find the binding answer faster.
Reading a FAQ answer without being misled
There is a common misreading of FAQ pages, and it costs players money. The misreading is to treat a general statement as a personal guarantee. "Withdrawals are processed after verification" is a general statement. It is true for every account that passes verification. It does not mean that a particular withdrawal will be processed, or that it will be processed within any particular time. "Bonuses are subject to wagering requirements" is a general statement. It does not mean that a particular bonus has a low or high requirement. The reader's job is to notice which kind of sentence they are reading: a process sentence, which describes a sequence, or a status sentence, which describes an outcome. A FAQ is full of process sentences. A status sentence about the reader's own account can only come from the account itself.
A second misreading is to assume that silence means permission. If the FAQ does not say that a deposit method can be used for withdrawal, the reader cannot assume it can. If the FAQ does not say that a bonus can be withdrawn immediately, the reader cannot assume it can. Silence in a FAQ is usually deliberate: the operator does not want to state a rule in a place where it might be read as a promise, and the rule itself is in the terms. The reader who reads silence as permission will be disappointed, and the terms will be cited against them.
A third misreading is to treat the FAQ as a substitute for the terms in a dispute. When a player and an operator disagree, the operator will cite the terms, not the FAQ. The FAQ may be used to show what the operator told the player, but it is not the contract. The reader who wants to protect themselves should read the terms before depositing, not after a dispute has begun. The FAQ is a good place to learn which terms matter; it is not a good place to learn what the terms say.
What to do when the FAQ does not answer
When the FAQ does not answer a question, the reader has three moves. The first is to check the binding document directly. If the question is about a bonus, read the promotion's terms. If it is about a withdrawal, open the cashier and the withdrawal policy. If it is about data, read the privacy policy. The second move is to check the account pages. The account's transaction history, verification status, and message inbox often contain the answer that the FAQ cannot give because it is account-specific. The third move is to contact support. Support can see the account and can give a status answer. The FAQ's contact section should state which channel to use and what information to include so that the request is not bounced back.
A reader should not contact support for a question the FAQ answers. Support queues are long, and a question that is answered in the FAQ will receive a copy of the FAQ answer. A reader should contact support when the FAQ points to a document but the document does not state the item, or when the account pages show a status that contradicts the FAQ's process description. In those cases, the reader has found either an outdated FAQ or an account-specific condition, and only support can resolve which it is.
This page is an independent summary of what an operator FAQ covers and where its limits are; it is not published by Bitofgold, and it states no figure or status for that operator, whose own FAQ and terms pages are the only binding sources for any question about an account or a current offer.
FAQ
What kind of question is a casino FAQ good for?
A FAQ is good for process questions whose answer is the same for every account: which documents are accepted, how to enable a security feature, which department handles a request. It is not good for questions whose answer depends on the reader's own account or on a current figure.
Why doesn't the FAQ state the wagering requirement for a bonus?
Because the wagering multiple is set per promotion and changes frequently. The FAQ may explain that a requirement exists and how it works, but the number itself lives in the promotion's own terms page, which is updated when the offer changes.
If the FAQ says withdrawals are processed after verification, is that a promise?
No. It is a description of the sequence: verification happens, then processing happens. It does not say that a particular withdrawal will be approved, or when. The account's withdrawal status page is the live source for that.
What should a player do when the FAQ and the terms page disagree?
Treat the terms page as binding. The FAQ is a summary maintained by support; the terms are the contract. If the disagreement affects a pending transaction, contact support and point to both pages so that the discrepancy can be resolved.
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.
