Fold'em
  1. Help
  2. Leaving early
Leaving early

Who actually unlocks the phone?

Updated September 2026

Fold'em's server does, and the phone never does. Every deadline that could end a block is stamped and held on the server: your term, an exit request, the wait after an approval, the release at the end of it, the lapse window and the deletion lock's window. Your phone reads those answers and applies them, and the code that removes protection can only run from a release the server granted. Its own clock is not an input, which is why turning the phone off, flying, or changing the date in Settings changes nothing.

The split, in one line

The server decides when. The phone decides how. Everything that could make the block weaker is a deadline or a state on the server, and the phone's job is to keep what it was told applied and to ask again whenever it can.

That is not a description of good behaviour. It is the shape of the code: the one function that removes protection can be reached from exactly one place, and that place is a release grant that arrived from the server. There is no path from a timer, from a screen, from a tap, or from an error to a phone that unblocks itself.

What the server owns

The whole list, and it is short. Whether you are under a term and when that term ends. Whether an exit request exists, and whether your keyholder kept the lock or approved. The moment the wait after an approval finishes. Whether a release is available and whether it has been taken. The window after a payment lapse. The window that turns the deletion lock off. And the list of gambling domains the web shield answers for.

Your phone hears about all of that in three ways, which exist so that one of them failing is not a hole: a live connection while the app is open, a silent push that nudges it to look, and a check every time you bring the app to the front. When none of them can reach the server, nothing changes, which on this product means everything stays blocked.

Why the phone's clock does not matter

Every deadline you see is a stamp the server wrote, and the numerals on your screen are a reading of that stamp rather than a timer of their own. Moving the date forward makes the numerals read differently and moves no state. Past the deadline and with no answer from the server yet, the screen deliberately says it is waiting for confirmation instead of showing zeros, because a finished count is not the same fact as a granted release.

The same applies to the app itself. Deleting Fold'em does not end a term, because the term is not stored in the app. Signing back in brings the lock back exactly as it was, never weaker, and the phone is walked through granting Screen Time and picking its apps again because those permissions belong to the device and not to your account.

The phone does keep checking its own work. On every launch and every time you bring the app to the front, it verifies that Screen Time permission is still granted and that the settings it wrote are still on the phone, and it silently writes them again if they are not. What it writes is derived from the record, not from anything the screen is showing, so the repair always follows the server rather than the other way round.

Who unlocks the phone: the server says, the phone applies it A large road. On the left, foldem.app decides: the lock, the term, an exit, a release, a lapse, the deletion lock window, and the web shield are all decided there. An arrow carries the decision to the phone on the right, which only applies what it was told and never decides for itself. Small and apart at the bottom, the one exception: the Games category switch, whose 72 hour release is counted on the phone's own clock, and which touches nothing else. WHO UNLOCKS THE PHONE foldem.app decides all of this The lock, and its lift The term and its end An exit, solo or not The release, held 7 days A lapse, and its window The deletion lock window The web shield's list The phone applies it and decides nothing A timer here unlocks nothing THE ONE EXCEPTION The Games category 72 hours on the phone's own clock. Nothing else moves.
The server decides the lock, the term, an exit, a release, a lapse, the deletion lock window and the web shield's list; the phone applies what it was told. The Games category is the one thing the phone decides on its own clock.

What that looks like at the one moment it matters

  1. The server says the release is available

    The wait finishes on the server, not on your phone, and the server marks the request as a release you may take. The safe reads READY TO OPEN and the key is seated in its lock.

    The Home wall with the safe reading READY TO OPEN, a gold key in the keyhole, and a card saying your exit is ready with Extend the term above Open the apps.

    The release, announced but not taken

  2. Nothing comes off yet

    Every app you sealed is still sealed at this point, every site still blocked, the deletion lock still whatever you set. An announcement is not an unlock, and the phone has no instruction to act on until you give it one.

  3. Your tap asks, and the server answers

    Taking the release sends a request. The server can refuse it, and does, when the release has expired or belongs to a term that is no longer the live one. Only when it agrees does the grant come back and the protection lift. The phone gained a gate here, never a decision.

The one thing the phone decides alone

There is exactly one exception in the whole product, and it is named rather than hidden. If you sealed the Games category, turning that one switch off starts a 72 hour window counted on the phone's own clock, and at the end of it the category opens without asking the server.

It is allowed because that switch was never the server's to begin with: there is no field for it in your account, nothing sends it anywhere, and no rule on the server has ever decided it. And it reaches nothing else. It does not touch your term, an exit, a release, the apps you picked by name, the web shield or the deletion lock, all of which stay exactly where they were. Every other release in Fold'em still comes from the server.

What this does not do

Server authority is not surveillance, and it is not a remote control. Nobody at Fold'em can unlock your phone for you, and neither can your keyholder: support can neither shorten a wait nor end one. It also does not reach past this phone. A second device, a laptop, a betting shop and cash are all outside it, and no amount of authority on this iPhone changes that. What it buys is narrower and worth saying plainly: the phone in your hand cannot be argued into letting you out early, by you or by anyone holding it.

Still stuck? Email support@foldem.app and we answer within two working days.