Is Borgata safe? The short version is yes, within the bounds of a state-licensed NJ/PA operator. The fuller version includes a real stumble: in 2019, New Jersey regulators found that self-excluded players had kept gambling for real money on the platform, and fined the operators over it. Understanding that incident — and what changed after it — is a better safety check than a one-line rating.

The 2019 Self-Exclusion Failure

In a March 2019 ruling, the New Jersey Division of Gaming Enforcement found that a software failure on the Borgata-bwin.party online gaming platform had allowed at least 12 people who had formally self-excluded to continue placing real-money bets. The DGE ordered Borgata to forfeit $41,759 those players had won, and jointly fined Borgata and GVC Holdings (bwin.party’s parent company at the time) $81,000 for the underlying failure — $122,759 in total penalties tied to one breakdown in the exclusion system.

Why this counts as a safety story, not just a fine. Self-exclusion exists specifically to protect players who have identified their own gambling as a problem. A gap that lets those players back in is a more serious failure than a late withdrawal or a bookkeeping error — and it is exactly the kind of thing a real regulator, with real enforcement power, is positioned to catch and punish. An offshore site with no equivalent overseer would have no comparable mechanism to surface the same failure.

What Actually Keeps a Session Safe Today

Two mechanisms do most of the work. First, geolocation: every Borgata Online session runs through a DGE- or PGCB-licensed location-verification vendor — GeoComply is the one most commonly used across New Jersey and Pennsylvania operators — which checks device location at login and again periodically during play, confirming the player is physically inside one of the two licensed states rather than trusting an address on file.

Second, self-exclusion is enrolled at the state level, not through Borgata individually. New Jersey players sign up through the DGE’s own portal at njportal.com, and Pennsylvania players enroll through responsibleplay.pa.gov, choosing a one-year or five-year exclusion period. The design intent is that one enrollment blocks a player across every licensed site in that state at once — which is the exact gap the 2019 case exposed, and the reason that incident led to closer scrutiny of how operators actually apply the list rather than just accept it.

Encryption and Everyday Account Security

On the more ordinary side of “is Borgata safe,” the platform runs standard TLS encryption on login, account, and cashier pages, which both New Jersey and Pennsylvania require of licensed operators as a baseline technical standard. There is no disclosed player-data breach on record separate from the 2019 enforcement matter, and that incident was a process failure in applying an exclusion list rather than an intrusion into account data or payment information.

Weighed Against an Offshore Site

The comparison that matters is not “has Borgata ever had a problem” — it has — but what happens when it does. A licensed NJ/PA operator with a broken safeguard gets investigated by a state regulator, forced to forfeit winnings tied to the failure, fined, and named in a public ruling. An offshore operator with the same broken safeguard typically has no external body checking for it in the first place, so equivalent failures simply never surface. Borgata’s 2019 record is uncomfortable, but it exists precisely because real oversight was watching.

None of this makes gambling risk-free, and no safety feature changes the math of the games themselves. Treat any deposit as entertainment spending, never as income, and use Borgata’s deposit limits or the state self-exclusion programs above if play stops feeling that way. 21+ and physically present in NJ or PA only. 1-800-GAMBLER.