Geolocation Explained: How Licensed Casinos Confirm Where You Are

Every hand a licensed U.S. operator deals is preceded by a location check most players never notice until it fails.

350 checks GeoComply says it runs per transaction
4.5B Wi-Fi access point identifiers in Locance’s map
10 year floor on New Jersey location records
3 vendors covering most of the regulated market

The short answer

  • What it is: a location check run when you log in and re-run repeatedly while you play, not once at the door.
  • Why it exists: a state license stops at the state line, and the federal intrastate carve-out is conditional on age and location verification written into state law.
  • How it works: IP, Wi-Fi access point triangulation, satellite positioning, cell trilateration, device fingerprinting and VPN detection, fused into one confidence score.
  • The default answer: no. Compliance systems fail closed, so an ambiguous fix is refused rather than approved.
  • Offshore sites: run no certified geolocation at all, only address-level blocking with no audit log a regulator can examine.
THE LEGAL BASIS

Why the Check Exists at All

Geolocation is not an operator preference. It is the condition the entire legal market rests on, written into federal and state law alike.

Behind that check sits a stack of radio signals, a database of several billion mapped routers, a fraud engine hunting for virtual machines, and a rule that says when the evidence is ambiguous, the answer is no. This page takes that mechanism apart, starting with why a licensed online blackjack site drops a session rather than let it run unverified.

A state gaming license is a permission slip with a hard geographic edge. New Jersey’s Division of Gaming Enforcement can authorize a casino to deal blackjack to someone in Hoboken. It has no power to authorize the same hand for someone in Manhattan, four miles away. The operator therefore carries the burden of proving, on every session and repeatedly during it, that the account holder is physically inside the licensing state. That burden is what the licensing process attaches to the permit, and it is why an unlicensed site never bothers.

The federal carve-out is conditional, not automatic

The 2006 federal payments statute carved out an exception for wagers that begin and end inside one state, but only where state law includes “age and location verification requirements reasonably designed to block access to minors and persons located out of such State,” plus data security standards that keep unverified users out. The text sits at 31 U.S.C. Section 5362(10)(B)(ii).

Strip geolocation out of a state’s regime and the intrastate exception arguably evaporates, which is why every regulator that opened an online casino market wrote the requirement into its rules rather than leaving it to operator discretion. Our breakdown of that payments law covers the rest of its structure.

The state rules are blunt, and all three of the biggest markets say the same thing in different words.

StateRuleWhat the operator must do
New Jersey N.J.A.C. 13:69O-1.2(e) “Employ a mechanism to detect the physical location of a patron upon logging into the gaming system and as frequently as specified in the Internet gaming permit holder’s approved submission,” and refuse wagers until the patron is somewhere authorized.
Pennsylvania 58 Pa. Code Section 809a.7 The system “must be equipped to dynamically monitor the player’s location and block unauthorized attempts to access the interactive gaming system throughout the duration of the gaming session.”
Michigan MCL 432.311 Places the same location-verification duty on the licensed operator itself.

Note the phrasing in all three: continuous, not one-and-done. The check that passed at login is re-run while you play. For which states have granted this permission in the first place, start with the legality overview.

LAYER BY LAYER

The Signal Stack, Layer by Layer

No single measurement is trusted. The system gathers several independent estimates of where the device is, then reconciles them.

Understanding each layer explains nearly every failure players hit, because a rejected check is almost always one specific layer going missing or disagreeing with the rest.

IP Address: Present, but Barely Trusted

An IP address identifies the network block a connection came from, and a commercial database maps that block to a registrant address. For home broadband, that usually lands in the right metro area. Everything else degrades fast. Mobile carriers pool subscribers behind carrier-grade network address translation and route them out through regional gateways, so a phone in Camden can present an address registered in Philadelphia. Business, satellite and campus connections are worse, the block often registered to a headquarters in another state. Compliance systems therefore treat IP as context, not evidence: useful for spotting an obvious mismatch, but never enough on its own to approve a wager.

Wi-Fi Access Point Triangulation: The Desktop Workhorse

This layer decides most desktop sessions and is the one players understand least. Your device scans for nearby wireless networks and records two things about each: the BSSID, the hardware address of that access point’s radio, and the received signal strength. That list goes to a lookup service holding known coordinates for hundreds of millions of access points. Match three or more, weight them by signal strength, and you get a fix owing nothing to your IP address and nothing to satellites.

The reference data is enormous. Locance, one of the certified gaming vendors, publishes the following figures for its own map, which is crowdsourced: phones holding a satellite fix while seeing a given access point report the pairing, and coverage fills in over years.

4.5B Wi-Fi access point identifiers
300M cell site identifiers

A desktop has one precise signal, and it is easy to switch off

A desktop has no satellite receiver and no cellular radio, so the Wi-Fi scan is its only precise signal. That is why desktop players must install a helper application or browser extension, and why a laptop wired to Ethernet with its wireless radio off fails the check in the middle of a legal state. The map is also only as fresh as the last time somebody drove past.

Satellite Positioning on Phones and Tablets

Modern handsets receive from several constellations, not just the American GPS system, and compute position from signal travel time. With a clear view of the sky the fix is good to a few meters, far tighter than any border question needs. The trouble is that people play indoors. Walls, metal framing and coated glass attenuate the signal, and downtown it bounces off buildings before reaching you, producing multipath errors that throw a fix a block or more off course. Operators demand location permission because without it this layer does not exist at all.

The permission trap you cannot see

iOS lets a user grant location access while switching off Precise Location, handing the app a coarsened position. That is not a denial, so the app appears to have permission, but the accuracy radius returned is far too wide to place anyone on the correct side of a line. Android’s equivalent is granting approximate rather than exact location. Both produce failures whose cause the player cannot see.

Cell Tower Trilateration

A phone always knows which cell sites it can hear and roughly how far it sits from the serving one, because the network measures the timing advance that keeps transmissions in their assigned slot. Combine the known coordinates of two or three sectors with those distance estimates and a position falls out. In a dense urban grid full of small cells that can be good to a couple of hundred meters; in rural country served by one tall tower the uncertainty balloons to several kilometers. Cell data therefore rarely decides a session alone. Its value is as a cross-check: if the satellite fix says Newark and the serving sector is in Queens, the fraud engine wants to know which one is lying.

Bluetooth Beacons

Beacons serve a narrower purpose. New Jersey draws a much tighter boundary for on-property mobile gaming, permitting it “within the property boundaries of an approved casino hotel facility,” expressly including a pool deck but excluding parking garages. Satellite positioning cannot reliably distinguish a garage level from the lobby above it; short-range Bluetooth transmitters with fixed identities can, and GeoComply sells an on-property product it says resolves to roughly one meter. For statewide play from your living room, beacons are not in the picture.

Device and Browser Fingerprinting

Location fraud is usually not an attempt to fool satellites. It is an attempt to put a real, legally located machine between the player and the casino, then drive it from somewhere else. Fingerprinting catches that. The client inspects characteristics a normal consumer device presents in a normal combination:

  • Graphics adapter and driver names
  • Screen geometry
  • The manufacturer prefix of the network adapter address
  • Timer resolution
  • Sensor availability

Virtual machines betray themselves because hypervisors ship recognizable virtual hardware. Remote desktop sessions expose a virtual display adapter and input latency no local user produces. Mobile emulators report build properties no shipped handset carries, and often expose accelerometer readings that never change because nothing is actually moving. On Android the platform’s mock-location facility is queried directly, as is root status; on iOS the equivalent is jailbreak detection. This is why a technically capable player who spoofs coordinates still gets rejected.

VPN, Proxy and Datacenter Detection

A separate subsystem classifies the connection itself. Every address block belongs to an autonomous system, and telling a residential broadband provider from a commercial hosting company is straightforward: traffic from a cloud provider’s address space is not somebody’s apartment. Beyond ownership, the engine weighs known exit-node lists, transport-layer fingerprints identifying tunneling clients, DNS resolution that leaks a different country, and round-trip latency inconsistent with the claimed position. GeoComply says its detection product draws on a database of more than 270 million addresses.

Privacy tools trip the alarm on innocent players

A commercial VPN, a corporate always-on tunnel, an Apple relay service masking the originating address and some privacy-focused DNS setups all look like evasion from outside. Our page on VPNs and licensed casino accounts covers what follows when a site decides you were hiding something deliberately.

Fusing It Into a Confidence Score

Here is the part most explanations skip. The engine does not pick a winner among these layers. It scores them. Each signal arrives with an estimated uncertainty, and the fusion logic weights the tighter, harder-to-forge signals more heavily while checking every source against every other. Agreement raises confidence. GeoComply describes running roughly 350 checks per transaction. What returns to the operator is not a map pin but a pass or fail plus a reason code, both written to a log a regulator can demand years later.

Contradiction does not average out

A satellite fix 30 miles from your serving cell sector does not resolve into something in between. It collapses the score, because contradiction is the signature of tampering.

THE VENDORS

Who Actually Runs the Check

Operators buy this rather than build it, and from a short list, because regulators insist the vendor itself be vetted.

Michigan licenses these companies as internet gaming suppliers under MCL 432.308; Pennsylvania treats them as interactive gaming service providers; New Jersey approves the methodology as part of the permit holder’s submission, which is why its rule ties check frequency to that “approved submission” instead of naming an interval. The vendor’s software development kit is tested before it goes near a live wager, alongside the game software handled by the independent testing laboratories.

Three names cover most of the regulated market.

VendorPositionWhat it brings
GeoComply The long-standing incumbent A compliance geolocation product plus modules for fraud detection, on-property geofencing and identity verification.
Xpoint Later entrant and challenger Pursuing state-by-state certification on the same path the incumbent walked.
Locance Carlsbad, California The current form of the LocationSmart business, leaning on carrier and network-derived location alongside its Wi-Fi and cell databases.

New Jersey has certified vendors in this category since 2013. For how operator permits are granted in the two largest markets, see the New Jersey DGE and the Pennsylvania Gaming Control Board.

THE BORDER PROBLEM

Why It Breaks Down at State Lines

All of this works well in the middle of a state. Failures cluster within a few miles of a border, and they have specific causes.

The Router Map Goes Stale

Wi-Fi positioning depends on access points being where the database says. Routers move. A family relocates from Philadelphia to Cherry Hill and takes the router along, and for weeks that hardware address still resolves to Pennsylvania. In a border metro, a stale record does not make the fix slightly wrong; it puts you in the wrong jurisdiction.

When the Border Is a River, or a Street

Philadelphia and Camden face each other across the Delaware River, roughly a third of a mile apart at the Benjamin Franklin Bridge. Both sides have legal online casinos, but they are separate regimes with separate licenses, and a Pennsylvania account cannot lawfully play from the Camden waterfront. Rivers are not even the tightest case.

BorderHow close it getsWhy it defeats a fix
Philadelphia and Camden Roughly a third of a mile at the Benjamin Franklin Bridge Two live markets, two separate licenses, and no lawful way to use a Pennsylvania account from the New Jersey bank.
Trenton and Morrisville A few hundred feet Well inside the error bars of several positioning methods at once.
Kansas City One metro area cut in half by a state line running down an ordinary commercial street There is no physical feature separating the two states at all.
Lake Tahoe Bisected by the Nevada-California boundary Casinos are built so close to the line that parking lots cross it.
Delaware An arc drawn 12 miles from the courthouse in New Castle Inside that arc, Delaware’s territory reaches across the river to the New Jersey low-water mark.

Delaware’s border is the strangest of the set. The U.S. Supreme Court reaffirmed that 12-mile arc in New Jersey v. Delaware in 2008, which means someone standing on a pier off the New Jersey shore may be standing in Delaware. Compare our New Jersey, Pennsylvania and Delaware pages, because which side you occupy decides which account you may use.

Towers, Buildings and Overlapping Coverage

Radio does not respect surveying. Carriers place towers to cover population, not to trace boundaries, so a sector on a Pennsylvania hilltop serves customers across the river in New Jersey and a tower in Toledo covers homes in Michigan. Buildings compound it: in a waterfront high-rise, the strongest access points a laptop hears may belong to neighbors whose units were mapped from a different position, and the indoor satellite fix may be off by more than the distance to the border. In the four-mile-wide Northern Panhandle of West Virginia, a Weirton resident has Ohio one way and Pennsylvania the other, with towers from three states audible at one kitchen table. Michigan shows the same geometry against Ohio and Indiana, and Nevada, which licenses online poker but not online casino blackjack, has the Tahoe problem on its western edge.

The Accuracy Radius, and What “Fail Closed” Means

This is the technical heart of the border problem. A position fix is never a point. It is a coordinate plus a horizontal uncertainty, properly read as a circle: the device is somewhere in here, with stated confidence. When that circle sits wholly inside the licensed state, the answer is easy. When it straddles the border, the honest answer is that the system does not know which side you are on. At that point the software fails closed.

A system that fails closed

  • Denial is the default outcome, reversed only by affirmative proof.
  • An ambiguous accuracy radius straddling a border is refused, not approved.
  • The worst case is an annoyed customer and a support ticket.
  • This is how every licensed compliance system is built.

A system that fails open

  • Approval is the default, refused only when a reason to refuse is found.
  • An ambiguous fix quietly gets waved through.
  • The worst case is a permanently recorded regulatory violation.
  • No operator with a license worth hundreds of millions of dollars builds it this way.

The asymmetry of consequences settles it. New Jersey requires operators to retain everything needed to reconstruct account activity, “including any identity or location verifications, for a period of no less than 10 years,” and to let the Division query and export it. Weighed against the license, the operator loses the customer every time. Anyone who moves between jurisdictions should read what happens when you cross a state line mid-session.

TROUBLESHOOTING

What a Failed Check Looks Like, and How to Clear It

False rejections cluster in browsers rather than apps, and within a few miles of a state line. Nearly all of the rest are fixable in a few minutes.

The message is usually some variation of “we could not confirm your location,” with a reference code. That code matters: it maps to a specific reason on the vendor’s side, and support can read it. Causes, roughly in order of frequency:

  1. Operating system location services switched off entirely.
  2. Permission granted but coarsened: Precise Location off on iOS, approximate location on Android, or the browser prompt dismissed rather than allowed.
  3. The desktop helper or browser extension not installed, not running after a reboot, or out of date.
  4. A VPN, system-wide proxy, corporate tunnel or privacy relay masking the connection.
  5. A work, campus or hotel network exiting in another state.
  6. Play attempted inside a virtual machine or over a remote desktop session.
  7. A laptop on Ethernet with the wireless radio disabled, leaving nothing to scan.
  8. A stale access point record after a move or equipment swap.
  9. Genuine border proximity, rarer than players assume and the one cause no troubleshooting fixes.

Work through the fixes in this order.

1

Turn location on, then make it precise

Enable location services at the operating system level, then set the app or browser to precise rather than approximate.

2

Switch the Wi-Fi radio on even if you are wired

It need not connect to anything. It needs to scan.

3

Re-grant the site’s location permission

Clear the permission in browser settings and grant it again so the prompt appears fresh.

4

Reinstall the geolocation helper

Take it from the casino’s own download page, never from a search result, then restart the machine.

5

Strip out every tunnel

Disconnect every VPN, disable split tunneling, turn off any private relay, and confirm no system proxy is set.

6

Switch networks

Move from corporate Wi-Fi to a personal hotspot, or from a hotspot to home broadband.

7

Get a look at the sky

Move toward a window or step outside for 30 seconds to acquire a satellite fix, then retry.

8

Try the native application

The app carries more signals than the browser and resolves inside a tighter radius.

9

Hand support the reference code

Still failing? Give support the code and the time of the attempt. The vendor log shows which layer disagreed.

Do not try to defeat the check

Manipulating location is an account-closure offense under every operator’s terms and can void balances, as covered in what players actually risk.

APPS VERSUS BROWSERS

Why the App Beats the Browser

Phones win because they carry more radios, and a native application is allowed to use all of them.

The native application

  • Satellite positioning, cellular measurements, Wi-Fi scanning and motion sensors that corroborate one another.
  • Runs the vendor’s detection kit in its own process.
  • Sees operating system location interfaces, root and jailbreak status, mock-location flags and sensor streams.
  • Sustains session-long monitoring without depending on a tab staying open.

The browser

  • A desktop often has one of those signal sources and sometimes none.
  • Sandboxed by design.
  • Can request only what the standard web geolocation interface exposes.
  • On a desktop with no wireless scan it quietly degrades to an address-derived guess.

The radio count alone makes mobile checks likelier to resolve inside a tight radius, and the software gap widens it from there. Our mobile blackjack guide covers that side.

DATA AND RETENTION

What the Check Collects, and How Long It Is Kept

A geolocation transaction captures a defined and fairly narrow set of data, and keeps it for a very long time.

Each check records:

  • Latitude, longitude and accuracy radius
  • Identifiers and signal strengths of nearby access points
  • Visible cell site identifiers
  • The public IP address
  • A device and browser fingerprint
  • Operating system and application version
  • A timestamp and the session reference

What it does not do

It does not read your messages, photos, contacts or browsing history, and it does not follow you off the casino site.

Retention is set by regulation rather than operator preference, and it is long. New Jersey’s 10-year floor on records that include location verifications is the clearest published example. The vendor keeps transaction logs to answer an audit; the operator keeps the account-level record. A check you failed in 2026 stays reconstructable well into the 2030s. What that means for you is set out on privacy and player data.

WHERE THE WAGER HAPPENS

Tribal Servers and Where a Wager Legally Happens

Geolocation answers where the player is. A separate question asks where the wager occurs, and the two are not the same.

01

Federal law: routing does not decide it

Under 31 U.S.C. Section 5362(10)(E), “the intermediate routing of electronic data shall not determine the location or locations in which a bet or wager is initiated, received, or otherwise made.” Packets crossing a state line en route to a server do not turn a lawful in-state wager unlawful.

02

States then legislate a deeming rule

Michigan’s is unusually explicit: MCL 432.304 provides that an internet wager received by a licensed operator is gambling conducted in that operator’s Michigan casino, and repeats the intermediate-routing language. New Jersey solves it physically instead, requiring at 13:69O-1.2(n) that primary gaming equipment sit in a restricted area within the territorial limits of Atlantic City.

03

Tribal gaming adds a third layer

Class III gaming under the federal tribal gaming statute must occur on Indian lands, meaning reservation lands and trust lands over which a tribe exercises governmental power, and must proceed under a state compact.

Michigan drew its carve-out narrowly: tribal exclusivity applies where the individual placing the wager “is physically present on Indian lands when the wager is initiated and the wager is received or otherwise made on equipment that is physically located on Indian lands.” Both ends, in other words. Other states took a broader path, deeming a bet placed anywhere in the state to occur at the tribal server receiving it. That theory survived its main federal test in West Flagler Associates, Ltd. v. Haaland, decided by the D.C. Circuit on June 30, 2023 on docket 21-5265, though the court resolved it on administrative grounds rather than endorsing the theory outright.

Connecticut’s market runs on a compact structure with the Mashantucket Pequot and Mohegan tribes, and players there still face an ordinary statewide fence. The mechanics are unpacked on our tribal gaming page.

THE OFFSHORE CONTRAST

What Offshore Sites Do Instead

Offshore operators run no certified geolocation because no regulator requires it of them.

They typically deploy address-level blocking: a lookup against a commercial IP database, and a refusal if the address resolves to a state their lawyers flagged. Bovada currently turns away visitors from roughly 19 states plus the District of Columbia. That is legal risk management, not player protection, and the list changes without notice.

The weakness is structural

Address blocking is the least reliable layer in the stack, applied alone, with no access point scan, no satellite fix, no device integrity check and no audit log a regulator can examine. It fails both ways: refusing a legal player whose carrier routes oddly, accepting one nowhere near where the address suggests.

Nothing there establishes that your real money account plays under any state’s authority, which is the distinction drawn in offshore versus state-licensed casinos.

If gambling has stopped being entertainment

Help exists. Several states mandate 1-800-GAMBLER in casino advertising and it still connects. Support is free, confidential and always open on 1-800-697-3738.

Reviewed and brought current on Aug. 25, 2026. Rules and vendor certifications change on their own schedules; check anything time-sensitive against the regulator’s published text.