How to stop gambling on your phone for good

Five surfaces, not one

The usual version of this is deleting two apps, and it fails within a week for a reason that has nothing to do with willpower: it covers one of five ways the same page reaches you. Naming all five is most of the work.

1. The betting apps themselves.
2. The betting sites, which are the same operators without the download.
3. Browsers that are not Safari, since Apple's own website filter reaches Safari alone.
4. The browsers inside other apps, the ones that open when you tap a link in a message or a social app.
5. The App Store, which puts a deleted app back in about fifteen seconds.

What follows is what reaches each of them on iOS, with the limit of each stated where it belongs.

The apps

Apple's Screen Time can shield chosen apps. Tapping a shielded app draws a block screen over it instead of opening it: the app stays installed and simply does not open, and there is no control on that screen that continues.

You choose them in Apple's own picker, which is the only way iOS allows it, and the picker hands an app opaque tokens rather than names. So the count of what you sealed can leave the phone and the identities never do. Fold'em applies the seal with no schedule and no daily window, and writes it back on every launch. The app seal in full.

There is a second switch for the apps you have not installed yet: a shield over the whole App Store Games category, which covers apps added later, and is what catches a new betting app filed as a game. It is off until you seal it, and switching it off starts a wait of 72 hours before the games open. That wait is the one thing on this list your phone times for itself.

The sites, and every browser at once

An app you cannot open is a website you can, so this half is not optional. The mechanism that reaches all of it works below the browser rather than inside one.

An encrypted DNS setting points every lookup this phone makes at a resolver that answers a known gambling domain with 0.0.0.0, the address for nowhere, so the page never loads. The list it answers for is about 356,500 domains. Because it sits under the browser, it reaches Safari, Chrome, Firefox, Edge and the browsers that open inside other apps, all at once, and it needs no tunnel. How the site blocking works.

Two smaller lists sit beside it and are never added to it. Screen Time carries its own curated website filter, ten domains today, and it works in Safari alone. And any website you tick yourself in the picker, up to 50, is shielded the way an app is.

Why Safari is filtered and Chrome is sealed

This looks inconsistent from the outside and is the only arrangement iOS allows. Screen Time's website filter takes effect inside Safari and nowhere else. Every other browser has no such filter, so the only way to cover one is to shield the browser itself as an app, which is why Chrome, Firefox and Edge are standing entries when you pick your apps.

Safari is deliberately left installed and filtered rather than sealed shut, because sealing Safari as an app would take the filter's own home away and leave the phone with less coverage than it started with. The longer version.

The App Store

Screen Time can restrict installing apps. Apple's own page on parental controls states that under Content and Privacy Restrictions you can prevent your child from being able to install or delete apps, make in-app purchases in apps installed from the App Store, and more, and it is worth noticing that Apple documents this as a way to manage somebody else's device rather than your own. Applied to your own phone it is real and it is a switch in the same Settings app you are already in, which is the whole problem with it as a last line.

The version that survives being alone with the phone is not a stronger restriction. It is one whose removal costs time and is visible to somebody: an optional restriction here stops apps being deleted while it holds, and turning it off does nothing on its own, because it opens a 72 hour wait on the server, written into what your keyholder can see, without an email. It is off unless you turn it on, because while it holds no app on the phone can be deleted, ours included.

The passcode question

The standard advice is to set a Screen Time passcode and give it to somebody. It is genuinely better than nothing and it is not what most people think it is.

Apple's own page on a forgotten Screen Time passcode says to open Settings, tap Screen Time, tap Change Screen Time Passcode twice, and, if asked, enter the Apple Account email address and password that you used to set up the Screen Time passcode. If the Apple Account is yours, so is the reset, and the friend never hears about it. The arrangement also has a social cost that people underrate: the reset is discovered later and looks exactly like an accusation.

A named keyholder is the same idea with both problems removed. Ending a term early becomes a request that goes to a server, the person is told when the Screen Time seal goes off, and there is nothing to reset because the answer was never held on the phone.

The limit, stated once

Screen Time permission is granted by you through a prompt iOS raises, and it can be withdrawn by you in iOS Settings. The encrypted DNS setting is likewise yours, and only iOS Settings can turn it off. No app on iOS can prevent either, and Fold'em does not claim to.

What it does instead is refuse to be quiet about it. Withdrawing the permission freezes your earned figures where they were, shows the days without it as holes in the run, and turns a keyholder's card to Protection off within seconds; after 24 hours with no reading of any kind the card reads Not confirmed. One weakening is honestly not on that list: switching the DNS setting off sends no email, and on a phone whose apps are sealed it changes nothing on the pass either; only a phone that sealed the web shield alone shows it there. Which failures are the tool's and which are the setup's is the page about all of it.