When quitting gambling did not stick

No app can make gambling impossible on an iPhone. The phone belongs to the person holding it, the Screen Time permission a blocker runs on is theirs to withdraw, and a product that says otherwise is claiming a power iOS does not give it. What a circle changes is the cost of undoing it, because ending a term early takes a request, a wait measured in days rather than seconds, and a second person who is told when protection goes off, when the phone stops confirming, and when the subscription lapses.

People who do this for a living, first

None of what follows is treatment, and a page about phones is a poor substitute for a conversation. These organisations are free, they are not run by us, and they answer whether or not you ever install anything.

• In the United States the National Council on Problem Gambling runs the National Problem Gambling Helpline, printed on its own pages as 1-800-MY-RESET, with call, text and chat. Its Help by State directory describes itself as a way to connect with local support and resources across all 50 states.
• In the United Kingdom the National Gambling Helpline is run by GamCare on 0808 8020 133. The NHS page on gambling states that it is free, that it runs 24 hours a day and 7 days a week, and that it is there for information, support and counselling. The same page names the NHS gambling treatment clinics in England.
• If the person struggling is somebody else, Gam-Anon is a fellowship of meetings for family and friends, and the first thing the NHS lists for anyone affected by another person's gambling. The pages for the person beside them start there.

The block at the foot carries the numbers again.

Why it came back is not a character question

The common story is not that a decision was never made. It is that the decision was made once, in daylight, by somebody calm, and then had to survive being undone by the same person at midnight with about four seconds of friction in the way. Deleting an app takes those four seconds. Reinstalling it takes fifteen. A limit you set yourself is a limit you can lift yourself.

So the useful question is not how to want it more. It is what stands between an urge and an open betting app, and how long that thing takes to remove. Everything below answers that, and each answer states its own limit.

The three layers, and what each one holds

Fold'em is three layers on one iPhone, with separate failure modes, which is why the app names them separately instead of selling one word.

The apps. You pick betting apps in Apple's own picker and Fold'em asks Screen Time to shield them, so tapping one draws a block screen over it instead of opening it. The picker hands over opaque tokens rather than names: the app counts how many you sealed and never learns which, and only that count goes to the server. There is no daily window and no schedule, and the phone writes the seal back on every launch. How the app seal works.

The addresses. A separate setting points every lookup this phone makes at Fold'em's own encrypted resolver, which answers a known gambling domain with 0.0.0.0, the address for nowhere, so the page never loads. That reaches every browser on the phone, browsers inside other apps included, and it needs no tunnel. The list it answers for is about 356,500 domains. Screen Time adds a second, much smaller filter that works in Safari alone, and any website you tick yourself is shielded the way an app is.

The term and the person. The first two are settings, and a setting you can change is not a commitment. So the record of the term lives on the server rather than in the app, and the server decides when protection comes off. The phone reads that answer and applies it. Its own clock is not an input, which is why turning the phone off, flying, or changing the date in Settings changes nothing. Who actually unlocks the phone sets out every deadline and where each is held.

What leaving early actually costs

This is the part that decides whether the other two matter.

You ask inside the app, and the request goes to the server rather than to a switch on the phone. If you named a keyholder, they either keep the lock, which is one tap from anywhere, or they approve in person, which means standing with you while you scan the code carried on their Wallet pass. There is no approve button on any page, in any email, or on the pass. An approval starts a wait of at least 72 hours counted from the moment they said yes.

Two facts are usually left out, and both are true here. If your keyholder says nothing for seven days, the request approves itself and is recorded as though you had no keyholder, which starts a wait of fourteen days rather than 72 hours; without a keyholder it approves immediately, with the same fourteen days. So an early exit does not need anybody's yes. It needs time, and the time is longer when nobody answers.

At the end of any wait the server marks a release you still have to take. Nothing opens by itself. The release is held for thirty days and then closes, and your protection simply carries on. What a cool down is for goes through the waits one at a time.

What none of it reaches

Every on device blocker has the same boundary, and a page that hides it leaves you to find it at a bad hour.

Fold'em holds one iPhone. A second phone, a tablet, a laptop, a betting shop and cash are all outside it. On the phone itself, Screen Time permission is yours and can be withdrawn in iOS Settings, and no app on iOS can stop that. Neither can the encrypted DNS setting be held on against you: Fold'em can read whether it is on and say so, and only iOS Settings can turn it off.

What the design does about all of that is refuse to be quiet. Withdrawing Screen Time is not blocked, it is reported: your figures freeze where they were, the days without the permission show as holes in the run, and a keyholder's card turns to Protection off within seconds. After 24 hours with no reading of any kind the card reads Not confirmed instead of staying green. That is deterrence rather than an operating system lock, and it is the honest word for it.

One weakening is deliberately not on that list, and you should know which. Switching the DNS setting off in iOS Settings 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. Anyone telling you a keyholder is always told when protection drops has not read the product.

Fold'em's own ways out, stated plainly

Two of them exist and neither is hidden. Naming them is the only way the rest of this page is worth trusting.

Deleting Fold'em removes the settings Fold'em applied. An optional restriction stops apps being deleted while it holds, and it is off unless you turn it on. Deleting is not an unlock, though: the term 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 itself, and a reinstall can never bring back a weaker one. Granting Screen Time and picking the apps have to be done again by hand, because Apple never lets the app pick leave the phone that made it.

A lapsed subscription releases the block. 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 way out the product has, and your keyholder is sent a letter carrying the date. The fuller account of both, with the deletion lock's own wait.

Can I just give my Screen Time passcode to someone I trust?

It is the most common advice you will find, and it is worth understanding before you build on it. A Screen Time passcode can be reset without the person holding it. Apple's own page on a forgotten passcode says to open Settings, tap Screen Time, tap Change Screen Time Passcode, then again, and, if asked, enter the Apple Account email address and password that you used to set up the Screen Time passcode. If that account is yours, the spare key is in your pocket. The pattern is not worthless, because a friend holding a passcode still puts a conversation in the way, but it is a lock whose reset path belongs to the person it is meant to hold. What changes that is moving the record off the phone: the term lives on the server, so there is no passcode to reset. Source: Apple, if you forgot the Screen Time passcode, read 3 September 2026.

Can a self exclusion be cancelled once it has started?

That depends which one you mean, and the two answers have nothing to do with each other. A national scheme sets its own minimum length and its own route back, in its own words, and those move without telling anybody, so the country pages here quote each scheme's own page with the day it was read: the United Kingdom, the United States, Canada and Australia. On this phone the answer is fixed and it is written above: a request rather than a switch, a wait of at least 72 hours behind a keyholder's yes, fourteen days behind their silence or behind no keyholder at all, and a release at the end that you still have to take.

I blocked the betting sites and I am still getting through. What is missing?

Almost always a layer rather than a fault in the one you set. An app seal stops an app opening and does nothing about that operator's website. Apple's own website filter works inside Safari and in no other browser, so Chrome, Firefox, Edge and the browser living inside a social app are all still open. A DNS answer sits underneath the browser and reaches every one of them at once, which is why the two layers are set together rather than either on its own. And if this phone is covered but a laptop, a tablet or somebody else's handset is not, nothing on this phone reaches those. Which failures are the blocker's and which are the setup's takes them one at a time.

Is deleting the betting apps enough?

No, and the reason is the clock rather than your resolve. Deleting takes about four seconds and reinstalling takes about fifteen, so a deleted app is a decision with nothing standing behind it at one in the morning. Two things change that. The address layer answers the operator's website with nowhere, so the browser route closes at the same moment as the app route. And a shield can cover the whole App Store Games category, which reaches apps installed later, so a betting app filed as a game is covered before you have heard of it; it is off until you seal it, and switching it off starts a wait of 72 hours. What the Games category shield does.

Where to go from here

If it happened tonight, start at what to do before you sleep. If a blocker did not hold, which failures are the blocker's and which are the setup's. If you are registered with a national scheme and still getting through, what self exclusion covers. If you are starting from nothing, the order that holds, or the phone version at how to stop gambling on your phone. And if the question underneath all of it is why none of this has worked yet, what actually stops me.