Why gambling blockers fail, and which failures are yours

Two kinds of failure, and only one of them is the app's

People arrive here after a blocker did not hold, and almost always describe it as the app being weak. Sometimes that is right. More often the app did exactly what it said and the arrangement around it had no cost in it, so the block came off in four seconds at the hour it was built for.

The two have different fixes. A tool failure is fixed by changing tools. A setup failure follows you to the next tool, and to the one after that.

The tool's failures

A configuration profile you can remove. Many blockers install a profile or a DNS setting that redirects lookups. It is a real mechanism and it stops real pages. It also lives in Settings on a device you own, and removing it takes about as long as adding it did, so a blocker of this class is exactly as strong as your willingness to leave the setting alone.

An unlock you can buy or ask for. If ending the block early involves a payment, a support ticket or a code, there is a price on the thing you were trying to make expensive. It does not matter how high that price is at three in the afternoon; the question is what it costs at one in the morning, and a payment takes seconds.

A filter that only reaches one browser. Apple's own website filter takes effect inside Safari and nowhere else. A blocker built on it alone leaves every other browser open, and it leaves the browsers that live inside other apps, which is where a great deal of betting happens. The fix is a layer that answers below the browser rather than inside one.

A block that is really a reminder. A daily limit, a nudge, a screen you can dismiss. Useful for a habit, and the wrong class of object for this, because every one of them ends in a control that says continue.

The setup's failures

These survive changing products, and they are worth being honest with yourself about before installing anything else.

You hold the passcode. The common self built version is a Screen Time passcode somebody else typed in. Better than nothing, and not what it looks like: 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 it does not need the friend.

There is a second device. Every on device blocker holds the device it is installed on. A tablet in a drawer, an old handset and a shared computer are outside it, and no setting on the phone changes that.

The whole thing comes off as fast as it went on. If uninstalling the blocker ends the block, the block is one long press away and the strength of everything underneath it is irrelevant. This is the failure that decides most of the others.

Nobody knows. A block only you can see is one only you can undo, at no cost but a private decision at the worst hour. That is what a second person is for, and it is why this product is built around one.

What a block that is not a reminder looks like

A Screen Time shield is not a message asking you to reconsider. The app stays installed and simply does not open: a screen lands over it, and there is no control on it that continues.

If you came here looking for how to take one off

That deserves a straight answer rather than a lecture. Every blocker on iOS is removable by the person holding the phone, because iOS gives no app the power to prevent it. What differs between products is not whether you can, but how long it takes and who finds out.

With most of them: remove the profile or the setting in Settings, or delete the app, and it is over in under a minute, silently. With this one: deleting the app removes the settings it applied, and does not end the term, and within a day the person holding your key is told the phone stopped confirming. There is no code, no support path and no payment that shortens a wait.

If what you want is out, the route is the exit request, and it is slower on purpose rather than by accident. If what you want is for tonight to be different, what a cool down is for is the more useful page.

Fold'em's edges, in the same words

Everything above applies here, and the edges are the same four every on device blocker has.

A second phone, a computer, a betting shop and cash are outside it. Screen Time permission is yours and can be withdrawn in iOS Settings; the encrypted DNS setting is yours and can be switched off there too. Fold'em can read both and report both, and it can turn neither back on against you. What it does about the edges is refuse to be quiet: withdrawing the permission freezes your earned figures, 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 exception is deliberately on that list rather than hidden. Switching the DNS setting off sends no email at all, 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. A page claiming a keyholder is always told when protection drops would be wrong about exactly this case.

Fold'em's own failure paths

Three routes end a block here without anybody's approval. Naming them is the only way the rest of this page is worth reading.

Deleting the app. An optional restriction stops apps being deleted while it holds, and it is off unless you turn it on, deliberately, because it is device wide: while it holds no app on the phone can be deleted, ours included. Turning it off does nothing on its own, because it opens a 72 hour wait on the server, and the wait is written into what your keyholder can see, without an email. With it off, deleting Fold'em removes the settings Fold'em applied. It does not end the term: the record lives on the server, so signing in again brings back the term with its end date, the day count unbroken, your keyholder and the lock, and a reinstall can never bring back a weaker one. Granting Screen Time and picking the apps are then done again by hand, because Apple never lets the app pick leave the phone that made it. Until they are, a keyholder's pass reads Checking in, and past a grace of 12 hours it escalates to Revoked and alerts.

Letting the subscription lapse. When the plan ends a window of 72 hours starts, and at the end of it the server flips the release. It is the fastest exit the product has, it is deliberate, and your keyholder is sent a letter carrying the date.

Waiting out an exit. Fourteen days without a keyholder, or 72 hours after one approves in person. Seven days of silence from a keyholder approves the request on its own and turns the wait into fourteen days. None of that is a way round anything; it is the product working, and the wait is the whole of the friction.

The question about deleting a betting app and installing it again

This comes up constantly, and the honest answer is partly a not known.

What is known: you pick apps in Apple's own picker, and it hands Fold'em opaque tokens rather than names. Apple's developer documentation says a token exists to restrict and filter device applications without access to personal user data and that the system uses one to preserve user privacy and prevent anyone outside of a Family Sharing group from identifying what apps and websites the family accesses. What that documentation does not state, anywhere we could read it, is whether a token keeps matching an app after that app has been deleted and installed again. So this page does not tell you that it does, and you should be careful of any page that does tell you, because the same documentation is all it has.

Two things do not depend on the answer. The web layer answers the address rather than the app, so a betting site fails to load in any browser on the phone whatever happened to the app. And the Games category shield, which is a separate switch, blocks every app in the App Store's Games category including ones installed later, which is what catches a new betting app filed as a game. Switching that one off starts a wait of 72 hours, timed by the phone rather than the server, because that switch was never the server's to hold.

If something is getting through anyway, the troubleshooting page works through the scenarios one at a time and says which are the block working at its edge and which are a setting to change.