How to ask them, and when they ask for the key back

The ask

You are not asking them to stop, to explain, or to promise. Those asks land on the person, and the person is already carrying it. You are asking for one small structural change: that ending the block early takes a conversation with you instead of a tap they can make alone at one in the morning.

Three things tend to make that land.

Be specific about what you get, and about what you do not. Say it out loud, because they will assume the worst. You will not see which apps or sites were involved. You will not see their browsing. You will not see any amount of money, and there is no amount of money anywhere in what reaches a second person. If it helps, send them the page that lists what a keyholder is shown and let them read it themselves rather than taking your word for it.

Be specific about what you would have to do. One thing, and only if they ask for it. If they request an early end, you answer. That is the role, in full.

Let them set the terms. They choose which apps and sites to seal and how long for. A block they designed is one they can defend to themselves at four in the morning. A block imposed on them is one they will spend that hour arguing with.

What not to do: do not set anything up on their phone, and do not ask for the Screen Time passcode. The passcode arrangement is what people reach for, and it is fragile in a way that costs a relationship. It can be reset, and resetting it looks like an accusation the moment it is discovered. A named key is the same idea with the argument removed.

The first week, so you are not surprised by the quiet

In a term where nothing goes wrong, holding a key is almost silent. The letters a keyholder gets are the one that carried their Wallet pass at the start, a milestone day at 7, 30 and 90 days, and one closing letter if the account ever ends. Everything else is an exception.

Three events would break the quiet, and they are the same three for everybody: protection went off, the phone stopped confirming for 24 hours, and the subscription lapsed. A request to leave early is the fourth thing that reaches you, and it is the one you answer rather than simply read. What reaches you and what does not sets all of it out, including the one weakening of protection that sends no letter.

The day they ask

It will probably happen, and it is not a failure of the arrangement. It is the arrangement working: the thing that used to take a thumb now takes you.

An email arrives, and your Wallet pass carries the ask on its face with a date to decide by. Nothing about their phone changes while you are deciding. There is no message from them attached, because an exit request carries no text field in either direction, so you are answering the request and not a paragraph written at midnight.

Keeping the lock

One tap, from anywhere, on the page the email links to. Your phone confirms it is you before the tap counts, so a forwarded link cannot answer in your name.

If you keep the lock they are told, with no reason attached, and they can ask again after 48 hours. You do not owe an explanation and there is nowhere to write one. Keeping the lock is the easy choice on purpose: it is one tap, it changes nothing, and it is the answer that leaves the world as it was.

Saying yes, which cannot be done at a distance

There is no approve button on any page, in any email, or on the pass. Letting somebody out is only ever done in person: they scan a code carried on your Wallet pass with the app on their phone, while the two of you are standing together.

That is not friction for its own sake. It is the difference between a decision made in the room and one made by a tired person tapping a link, and it is the single feature most worth understanding before you accept a key.

Even then nothing opens that day. Scanning the code records your approval and starts a wait of at least 72 hours from the moment you said yes. If the key has recently changed hands, or a keyholder stepped away or was removed, that wait can run to fourteen days instead. When it ends, the server marks a release they still have to take, and it holds that release for thirty days. Nothing opens by itself, on any path.

The two facts to know before you accept

Both of these surprise people, and both of them make silence a worse answer than an honest one.

Seven days of silence approves the request on its own. If you do not answer, the server approves it and records it as though they had no keyholder at all. Because it is recorded that way, the wait that follows is fourteen days rather than the 72 hours your yes would have started. Keeping the lock stays available for the whole of those seven days, and nothing about their phone changes during them. Not deciding is a decision, and it is the slower version of letting them out.

A lapsed subscription opens the block faster than any request. If the plan runs out, a window of 72 hours starts, and at the end of it the server releases the protection. You are told when the lapse happens. It is the fastest way out the product has, it is deliberate rather than a hole, and it is worth knowing so that a letter about billing does not read to you as an administrative footnote.

Neither of these is something you can change. You cannot shorten a wait, cancel one, or extend a term, and you cannot choose which updates reach you. What you can do is answer, and answering is the whole job.

If you want to stop holding it

Handing the key back is supported, from your own status page, at any time, and it is better than holding one and not reading the mail. Their protection continues without a keyholder, and no early exit can then complete in under fourteen days from that moment. Your device confirms it is you before it happens.

Saying yes to a key and later finding it too heavy is common enough that the way out is built in. It is not a betrayal to use it.