The full answer
Keep protection is the filled button on every step, and it asks first: Keep protection? Your request closes and your keyholder is told, and protection stays on. Nothing about the block changes when you withdraw, because nothing about it changed when you asked. Only you can do it, and the one moment it is no longer offered is after you have ended protection.
Three stages, and you can stop at all three
A request passes through three states, and withdrawing it is available in every one of them. While it is waiting on your keyholder, withdrawing closes it before they answer, and they see that you asked and that you withdrew it. While the wait is counting, the 48 hours after their yes or the 7 days when nobody holds your key, withdrawing stops the count. Once the wait is over and the request is ready but not used, withdrawing gives it up.
A ready request is not something in flight: it is an offer standing on a phone whose blocks are all still on, so turning it down is an ordinary decision rather than a race against the server.
What the confirmation says
Withdrawing asks first rather than happening on the tap, and it is the same alert on every step. It is titled Keep protection?, and it says that your request closes, that your keyholder is told, and that protection stays on; with nobody holding your key, it says only that your request closes and protection stays on. Its two buttons are Keep protection, which withdraws, and Keep request, which is the easy default and changes nothing.
Withdrawing, step by step
-
Open the request from anywhere it shows
The request card on Today and the End protection row in Settings open the same thing, and it always opens at the step the request is actually on, because it reads its position from the one record on the server.
-
Tap Keep protection
It is the filled button at the foot of every step. Once the wait is over, the last step asks End protection now? and puts Keep protection above the hold that ends it. Tapping Keep protection raises the confirmation and nothing else.
-
Confirm, and watch nothing move
The request closes, Request withdrawn shows for a moment, the card leaves Today, the apps stay blocked exactly as they were, and your gambling free count and the money you kept are untouched. There was never a moment when the block was softer.
If it cannot reach the server
Withdrawing is built to fail toward more protection, not less. The withdrawal is a message to the server. If it cannot get through, the app either says nothing changed or keeps trying until the server has it, and your blocks stay on the whole time, so there is no state in which a failed withdrawal has left something open.
What this does not do
Withdrawing does not change what is blocked, and an agreement your keyholder already gave does not carry over: asking again later is a new request that starts at the beginning. It does not hide anything either. Your keyholder sees that a request was open and sees that you withdrew it. Nobody else can do it for you, including your keyholder and including support, because the rules on the server allow only the owner of a request to touch it. And there is one moment when it is no longer offered: after you have ended protection, there is nothing left to withdraw.
Write to us and a person reads it. We answer within two working days, and we would rather hear the question twice than not at all.