The case
This is a document case, not a live account test. The reader is a resident of an open state who plans a trip to Nevada. The reader has a Fortune Coins account and wants to know whether the account will work from Nevada. The case is dated 11 November 2026.
The reader is anonymised. No account was created or used for this file, and no deposit or redemption was attempted. The case is built from the public terms, the state list and the Nevada state page.
The case matters because it is the cleanest example of the travel problem: the state page and the operator's list point in different directions. The reader has to decide which record controls.
The decision is not a legal opinion. It is a documented answer to the question “what should the reader do before the trip?”
The parties
The reader is a resident of an open state. The reader's account is verified to the home address. The trip is a short stay in Nevada, not a move. The reader does not intend to change residency.
Fortune Coins is the operator. Its terms are the contract. Its state list is the public eligibility statement. The brand is one of the five operators in the travel dossier.
The Nevada state page is the public legal record. It records an operator exit: the state has no sweepstakes-specific statute in the site's record, but the operators have left after the 2025 enforcement change.
The reader's home state page is the second legal record. It is open in the site's map. The reader's residency is therefore eligible at home.
The parties are the reader, the operator and the two state records. The case has no regulator, no court and no support thread beyond the public documents.
The documents
The first document is the Fortune Coins terms, version 4.8, dated 31 July 2026. The terms name California, Idaho, Michigan, New York and Washington as excluded territories. Nevada is not named.
The second document is the Fortune Coins state list as recorded in the coverage matrix. The list matches the terms: five excluded states. Nevada is not named.
The third document is the Nevada state page. It records a closed tier, a licensed casino market and an operator exit after SB 256 (2025). It does not record a sweepstakes-specific statute.
The fourth document is the reader's home state page. It is open. The reader's address is verified there.
The fifth document is the travel dossier's test table. It says physical location, residency, contractual location and geolocation are separate tests. The Fortune Coins list answers only the contractual-location question.
The documents are the record. The case does not use a support message, because no support message was sent for this file.
| Document | Date | Says | Does not say | Weight |
|---|---|---|---|---|
| Fortune Coins terms v4.8 | 31 July 2026 | Five excluded states | Whether Nevada play is allowed | Contract |
| Fortune Coins state list | 4 November 2026 | Nevada not named | Whether the cashier accepts Nevada | Public summary |
| Nevada state page | 11 November 2026 | Operator exit; no sweepstakes statute | Whether a traveller may play | Legal context |
| Home state page | 11 November 2026 | State open | Whether the operator accepts travel | Residency context |
| Travel dossier test table | 11 November 2026 | Four separate tests | The operator's individual rule | Method |
The timeline
31 July 2026: Fortune Coins terms v4.8 is dated. The five-state exclusion list is published.
4 November 2026: the site's coverage matrix records the Fortune Coins list. Nevada is not named.
9 November 2026: the operator-exit dossier is published. It records Nevada as an exit, not a statute.
11 November 2026: the reader plans the trip and reads the travel dossier. The case is opened.
The timeline shows the gap. The terms are three months old, the state record is current and the trip is future. The reader has to reconcile them.
The timeline also shows the limit. There is no support message, no cashier test and no account review. The case is a documents-only case.
The discrepancy
The discrepancy is simple: Nevada is not named on the Fortune Coins list, but Nevada is closed in the site's market map. A reader who reads only the list could conclude that Nevada is available. A reader who reads only the state page could conclude that the account is blocked.
The list answers a narrow question: is Nevada on the operator's exclusion list? The answer is no. The state page answers a broader question: is Nevada a market the documented operators serve? The answer is no.
The discrepancy is not a contradiction. The list can be silent on Nevada because the operator does not serve the state for a different reason: a payment-rail decision, a risk assessment or a state-law reading. The state page records the outcome, not the operator's clause.
The reader should not treat the omission as a permission. The list is a summary; the cashier and the terms are the mechanism.
The discrepancy is the case's central finding. It is also the reason the travel dossier separates the four tests.
The reader's decision should be based on the cashier test and the written support answer, not on the list alone.
The decision
The decision is: do not play from Nevada until the cashier and the support answer confirm that the account is eligible. The omission is not enough.
The reader should ask support in writing which test applies: residency, location or both. The reader should include the trip dates, the home state and the Nevada destination.
The reader should test the cashier before depositing. If the session is blocked, the reader should stop. If the session is open, the reader should still ask support for the rule.
The reader should keep the terms version and the support answer. The record is the protection if the account is later restricted.
The decision is cautious because the cost of a wrong assumption is a frozen account. The cost of a support message is a few minutes.
The decision is not a prediction. It is the action the documents support.
The reader's profile
The reader is an adult resident of an open state. The account is verified to a home address in that state, and the reader has used the account from home without a location block. The trip is a short stay in Nevada, not a move.
The reader's home state page is open. The reader has no reason to change residency. The trip is for work, and the reader plans to return home after a week.
The reader's account has a balance. The reader does not want to deposit from Nevada; the question is whether the existing balance can be used or redeemed during the trip.
The reader has read the travel dossier and wants a case-level answer, not a general rule. The case file is that answer at the document layer.
The reader's profile matters because the residency test and the location test point in different directions. The home address is open; the destination is closed.
The operator's public record
Fortune Coins publishes a five-state exclusion list: California, Idaho, Michigan, New York and Washington. Nevada is not named. The list is the public eligibility statement.
The terms are version 4.8, dated 31 July 2026. The terms are the contract. The list is a summary of the state rows, not the whole agreement.
The terms may contain a location rule that is broader than the list. The public summary does not show a Nevada-specific clause. The reader cannot conclude that Nevada is allowed from the absence of a row.
The operator's public record is silent on Nevada travel. Silence is not a permission. The cashier and the support answer are the missing evidence.
The operator's record is one of the five in the travel dossier. The case uses it because the omission is the clearest example of the gap.
The state's public record
Nevada is a licensed casino state. The state page records a closed tier, a licensed market and an operator exit after the 2025 enforcement change. It does not record a sweepstakes-specific statute.
The state's public record is not a player-level rule. It tells the reader that the market is closed, not that a particular account is blocked.
The reader should not read the state page as a ban on travel. It is a market record, not a personal prohibition.
The state page and the operator list are different records. The state page says the market is closed; the list does not name Nevada. The gap is the case.
The state record is the legal context. The operator record is the contract. The reader needs both.
The decision record
The decision is to ask support before playing from Nevada. The reader should state the trip dates, the home state, the Nevada destination and the account balance.
The reader should ask which test applies: residency, location or both. The answer should be in writing and should cite the terms section.
The reader should test the cashier before depositing. If the session is blocked, the reader should stop. If the session is open, the reader should still keep the support answer.
The reader should not use a VPN. The terms usually prohibit it, and the risk is a frozen account.
The decision record is the support request, the answer and the cashier result. The case is complete when those three documents exist.
The documents in detail
The terms are the first document. The reader should save the version and the date, and highlight the state list, the location clause and the VPN clause.
The state list is the second document. The reader should save the page and note that Nevada is not named.
The Nevada page is the third document. The reader should save the mechanism and the date. The page says the market is closed, not that the account is banned.
The home page is the fourth document. The reader should save the open status and the residency record.
The travel dossier is the fifth document. It explains the four tests and the sequence. The case applies the method to one operator.
The gap in the record
The gap is the missing support answer. The public records cannot say whether Fortune Coins will accept a Nevada session.
The gap is also the missing cashier result. The reader has not tested the deposit page from Nevada.
The gap is not a failure of the reader. It is the limit of a public-record case.
The reader should fill the gap before the trip, not after a block.
The gap is the reason the decision is cautious.
The final decision
The final decision is: ask first, test second, play only if both answers are clear.
The reader should keep the support answer and the cashier result. The case is complete when those documents exist.
The decision is not a guarantee of access. It is the action the public record supports.
The final decision is the record.
The case chronology
The chronology starts with the terms version on 31 July 2026. The five-state list is published.
The coverage matrix records the list on 4 November 2026. Nevada is not named.
The operator-exit dossier is published on 9 November 2026. Nevada is recorded as an exit.
The reader plans the trip on 11 November 2026. The case is opened.
The chronology ends with a support request that has not yet been answered. The case is open at the account layer.
The case conclusion
The case conclusion is a decision, not a legal ruling. The reader should ask support and test the cashier before playing from Nevada.
The public record is enough to show the gap and not enough to resolve it.
The reader should keep the five documents and the two future records.
The case is a document case with a clear next step.
The conclusion is the record.
The reader's next step
The next step is a written support request. The reader should state the account, the home state, the Nevada trip dates and the balance.
The reader should ask which test applies and request the terms section. The answer should be by email, not chat.
The reader should test the cashier before depositing. If the session is blocked, the reader should stop.
The reader should keep the request, the answer and the cashier result. The case is complete when those three documents exist.
The next step is the only step that changes the case.
The final record
The final record has the five public documents and the two future records. The public documents show the gap; the future records decide the account.
The reader should keep the record and repeat the test if the terms change.
The final record is the case file.
The case is a document case with a clear next step.
The final record is the answer.
The last note
The reader should not treat the list as a permission. The list is a summary; the cashier and the support answer are the mechanism.
The reader should keep the record and ask before the trip, not after the block, because the answer is easier to obtain than a reversal, and the record is easier to keep than a dispute, because the record is the first thing a dispute will ask for, and the date is the first thing the record will need, before the argument and after the fact, and keep it now and later, always, today.
What the case proves
The case proves that a state list can be silent while the state is closed. The omission is not a permission.
The case proves that the state page and the operator's list answer different questions. The state page is the legal context; the list is the public summary.
The case proves that a traveller needs the cashier and the support answer, not only the list.
The case proves that the four-test method in the travel dossier is useful. The Fortune Coins list answers one test, not four.
The case is a document case, and the documents are enough to show the gap.
What the case does not prove
It does not prove that Fortune Coins will block a Nevada session. The cashier was not tested.
It does not prove that Fortune Coins will accept a Nevada session. The support answer was not obtained.
It does not prove that Nevada is open or closed in law. The state page is the public record, not a court ruling.
It does not prove that a different operator would behave the same way. The case is one operator and one list.
The case is a documented gap, not a universal rule.
The record
The record has the terms, the state list, the Nevada page, the home page and the travel dossier. The five documents are dated.
The record should be kept with the support request and the cashier result when the reader obtains them. The case is incomplete without those two documents.
The record is the reader's protection. The decision is the reader's action.
The case is closed at the document layer and open at the account layer.