The page a reader opens before asking support a question
Most account questions do not start with a support ticket. They start with a search, and the page that search is meant to land on is the FAQ. A reader who asks Piratepots support about a deposit route or a verification document is usually sent back to the same page they skipped. The FAQ is not a substitute for the terms, but it is the fastest place to learn which document governs the question and which questions the operator expects readers to answer for themselves.
The value of an FAQ is not that it answers everything. It is that it tells the reader what kind of answer exists, and where the binding version of that answer is published. A reader who understands that distinction can use the FAQ without mistaking a summary for a guarantee.
What an operator FAQ is for
An operator FAQ is a triage page. It collects the questions that recur often enough to be worth answering once, and it answers them in a form shorter than the terms. The answers are usually process descriptions: what a reader needs to submit, which page a setting lives on, what happens after a withdrawal is requested, what a bonus code does and does not do.
Because the FAQ is a summary, it is not the document that binds the operator. The terms and conditions, the privacy policy, the withdrawal policy, and the bonus terms are the binding documents. The FAQ explains them; it does not replace them. A reader who relies on an FAQ sentence that contradicts the terms has no claim based on the FAQ. The operator's own dispute process will point to the terms, not to the support page.
That does not make the FAQ useless. It makes it a map. The map tells the reader which document to open, which section of that document matters, and which items the operator will ask for. The map is not the territory, but a reader without the map often opens the wrong document and reads the wrong section.
Which questions an FAQ can answer bindingly
An FAQ can answer questions about process and route. These are the questions whose answers do not change by account, by amount, or by date. Examples of the kind of question an FAQ can answer:
- Which documents the operator asks for when an account reaches verification, and in what format those documents must be supplied.
- Which deposit methods the cashier lists, and whether a deposit method is also offered as a withdrawal route.
- What the operator does with a withdrawal request after it is submitted, and where the reader can see the status of that request.
- Which page of the operator's site carries the bonus terms, and which page carries the privacy policy.
- What the operator means by a specific term it uses in its own documents, such as "wagering requirement" or "self-exclusion".
These are binding in the limited sense that the operator states them as its own process. If the FAQ says a document must be a photo and not a scan, that is a process statement the reader can rely on when preparing the document. If the FAQ says a withdrawal route is not offered for a given deposit method, that is a route statement the reader can rely on when choosing a method.
What the FAQ cannot do is state an amount, a percentage, a timeframe, a fee, or a limit as if it were fixed for this reader. Those items live in the terms or in the reader's own account, and they change.
Which questions an FAQ cannot answer, and where the answer lives instead
Any question whose answer depends on the reader's own account cannot be answered by a public FAQ. The FAQ does not know the reader's balance, their verification status, their bonus eligibility, or their withdrawal history. A question like "why is my withdrawal pending" has no FAQ answer, because the answer is specific to one account and one transaction. The reader must ask support, and support will answer from the account record, not from the FAQ.
Any question whose answer depends on current terms cannot be answered by an FAQ that was written months ago. Bonus percentages, wagering multiples, withdrawal minimums, and payment method lists all change. The FAQ may state them at the time of writing, but the reader who reads a figure in an FAQ should treat it as a pointer to the terms page, not as the current figure. The terms page is the only place the operator states the current figure as binding.
Any question about a specific transaction cannot be answered by an FAQ. The FAQ can say what normally happens after a withdrawal is requested; it cannot say what is happening to this withdrawal. The reader's transaction history, the cashier page, and the support channel are the only places that carry the answer for a specific transaction.
The table below sets out the split for the items that matter most on a casino FAQ.
| Item to confirm | Why it can change | Where it is stated |
|---|---|---|
| Deposit methods offered | Payment providers are added and removed; a method listed today may not be listed next month | The cashier page, not the FAQ |
| Withdrawal routes per deposit method | Routes are tied to provider rules and operator policy, both of which change | The withdrawal policy and the cashier page |
| Verification documents required | The document list can change when the operator updates its KYC process | The verification section of the terms or the account page |
| Bonus percentage and wagering multiple | Promotions are revised frequently; a figure in an FAQ is often stale | The promotions terms page for the specific bonus |
| Withdrawal processing time | Timeframes vary by method, by verification status, and by operator policy | The withdrawal policy and the transaction status page |
| Self-exclusion procedure | The procedure itself is stable, but the contact channel and the form location can move | The responsible gaming page and the support channel |
How to read an FAQ answer without being misled
The first thing to check in any FAQ answer is whether it states a process or a figure. A process answer is usually safe to act on: it tells the reader what to do, what to submit, or where to click. A figure answer is a snapshot, not a promise. The reader should note the figure, then open the document the FAQ points to and read the current figure there.
The second thing to check is the date. Many operator FAQs carry no visible date on individual answers. A reader who finds a figure in an undated FAQ answer should assume the figure may be out of date and verify it against the terms. A reader who finds a process answer in an undated FAQ answer can usually act on it, because processes change less often than figures.
The third thing to check is whether the answer names a document. A good FAQ answer names the document that governs the question: "see section 7 of the terms", "see the withdrawal policy", "see the bonus terms for this promotion". An answer that names no document is a summary with no anchor. The reader should treat it as a starting point, not as the end of the question.
When the FAQ does not state an item at all, that absence is itself information. If the FAQ does not name a testing laboratory, there is no laboratory named for the reader to verify, and the reader should not assume one exists. If the FAQ does not state a withdrawal minimum, the reader should read the withdrawal policy for the current minimum, and should not assume there is none. If the FAQ does not state a bonus percentage, the reader should read the promotion terms for the specific bonus, and should not assume the bonus has no percentage.
Where the binding answer lives
For every question an FAQ answers, there is a document that answers it more fully and more bindingly. The reader who knows which document that is can skip the FAQ for that question and go straight to the source. The reader who does not know which document that is can use the FAQ as an index to find it.
The terms and conditions are the master document. They govern the account relationship, the bonus rules, the withdrawal rules, and the dispute process. The privacy policy governs data. The withdrawal policy governs payouts. The promotions terms govern each bonus. The responsible gaming page governs limits and self-exclusion. The cashier page governs payment methods. The FAQ governs none of these; it only points to them.
A reader who asks support a question that the FAQ answers will usually be told to read the FAQ. A reader who asks support a question that the FAQ does not answer will usually be told to read the terms, or will be given an account-specific answer. Neither response is a refusal; both are the operator directing the reader to the document that governs the question.
What to do when the FAQ and the terms disagree
When an FAQ answer and a terms clause say different things, the terms clause wins. The FAQ is a summary; the terms are the contract. A reader who notices a disagreement should follow the terms, and should also note the disagreement, because it may indicate that the FAQ is out of date.
The reader should not ask support to resolve the disagreement in the reader's favor on the basis of the FAQ. Support will apply the terms. The reader can, however, ask support to confirm which document is current, and that question is a reasonable one to ask. The answer will tell the reader whether the FAQ is stale or the terms have been updated.
In practice, disagreements between an FAQ and the terms are usually small: a figure that changed, a method that was added or removed, a document that was renamed. The reader who treats the FAQ as an index and the terms as the source will rarely be harmed by such a disagreement. The reader who treats the FAQ as the source will sometimes be surprised.
FAQ
Can I rely on the Piratepots FAQ for current bonus percentages?
No. An FAQ answer about a bonus percentage is a snapshot, and bonus figures change frequently across operators. The binding figure is on the promotions terms page for the specific bonus, and that is the page to read before claiming anything.
What should I do if the FAQ does not answer my withdrawal question?
Read the withdrawal policy first, because that is the document that governs payouts. If the question is about a specific transaction, open the transaction status page in your account, and if the answer is still not clear, contact support with the transaction reference.
Is the FAQ the same as the terms and conditions?
No. The FAQ is a summary and an index. The terms and conditions are the binding document. When the two disagree, the terms apply. Use the FAQ to find the right section of the terms, not as a substitute for reading it.
Why does the FAQ not state a withdrawal processing time?
Because processing time varies by payment method, by verification status, and by operator policy, and a single figure would mislead more than it would help. The withdrawal policy states the timeframes that apply, and the transaction status page shows the current state of a specific withdrawal.
This page is an independent summary of what an operator FAQ covers and where it stops; it is not published by Piratepots, and it states no figure or status for them, so the operator's own FAQ and terms pages are the only binding sources for any question about their service.
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.
