Home › Access layers
I trace the access paths
I treat every gambling session as a path, not a single website. A path has a device, an account on that device, a network, and an app or browser. Close one segment and the others can still connect. These comparisons are character sketches of the platforms, not steps I claim to have verified on your hardware.
I compare four platform families
| Platform | Familiar control surface | What often remains open |
|---|---|---|
| Windows | Hosts file, firewall rules, and per-browser extensions. The hosts file is an old name-to-address map that can point a name nowhere. | Another user account, a portable browser, and apps that ignore the system hosts file or use their own resolver. |
| macOS | Hosts file, configuration profiles, and Screen Time content limits on Apple devices. Profiles can be harder for the same user to undo than a bookmark. | A second browser profile, a virtual machine, or a phone signed into a different Apple ID. |
| Android | Digital Wellbeing app timers, private DNS, and work profiles. Private DNS can send name lookups to a resolver the reader chose. | Sideloaded browsers, a VPN that replaces DNS, and mobile data that never sees a home router rule. |
| iOS | Screen Time and content restrictions, which Apple has long offered as device limits rather than as a gambling product. | Another person’s unlocked phone, a web app saved to the home screen if the rule was only an app removal, and iCloud accounts that restore what was deleted. |
I do not rank these families. Windows and macOS make a hosts file easy to describe in text. Android and iOS make app-level limits more visible and system-file edits less appropriate for a general reader. If a vendor screen has moved, the vendor’s own help is the place to check the current labels.
I watch the network, not only the icon
A home router can filter DNS for devices that use it. A phone on cellular data does not ask that router. A laptop on a café network does not ask it either. I therefore treat a router rule as a house rule, not a person rule. When the person leaves the house, the rule stays behind.
VPNs add another fork. Some people use a VPN for ordinary privacy. The same tunnel can also bypass a DNS filter that only sees unencrypted lookups. I do not walk through how to evade a filter; I only note that if a VPN is installed, a local plan that ignores it is unfinished.
I account for apps that are not browsers
Sportsbook and casino access is often an installed app, a progressive web app, or a link inside a social app. Removing one icon does not remove the account on the server. I never name operators, and I do not list store pages. What I do say is: if the path is an app, a browser extension will not see it. The matching control is an app limit, an uninstall, or an account closure done with the provider — and account closure is their process, not something this site can perform.
I keep shared machines in view
On a family Windows or macOS computer, an administrator can undo a hosts edit. On a shared iPad, Screen Time only holds if the passcode is not known to the person being limited. I am uncertain how any household should share that passcode; that is a relationship question, and a technical note that pretends otherwise would be false. If the device is not solely yours, say so in the plan before you edit system files.
I stop at the edge of the device
Cash venues, lottery counters, and another adult’s login are outside every row of the table. So is a friend who offers a phone “just to check a score.” I link that limit back to the boundary notes rather than inventing a social script. Related reading: safer boundaries and the local build.