What does my keyholder see?

Everything your keyholder sees

1. The character you chose for yourself, and your first name. Never your full name.
2. Whether protection is on, as one of the five words their card can carry: Protection on, Not confirmed yet, Protection at risk, Protection off or Protection ended.
3. A count of days from the day your protection started, and its milestone days, while the Gambling free run switch in Sharing is on.
4. If someone holds your key: that a request to end protection is open, the date they must answer by, and how it ends, whether they agreed and you confirmed it, they declined, you withdrew it, or it closed unanswered.
5. If someone holds your key: that you started the 72 hour wait to turn off Deletion delay, when, and whether Deletion delay stayed on or turned off.
6. A handover: that one is running and the first name of the person taking over, shown to your keyholder and to that person and to nobody else.
7. Asked for support, when you ask for it.
8. If your subscription ends while protection is on: that your protection is ending, shown as Protection at risk, and a Remind button that sends you a reminder about the payment.
9. The nudges between you, as a kind and a time, never as words.
10. If someone holds your key: a notice, once, if you close your account.
11. If someone holds your key: that you asked them to end a Lockdown sooner, when it would end on its own, and the note you wrote with the ask, if you wrote one.

Never your check ins, your goal, Money kept, that you gambled, how many attempts were blocked, which apps or sites you blocked, anything you browse, or anything else you typed. Nobody is told when a Lockdown starts, is extended or ends on its own.

A supporter without the key sees the same list less the four things that travel with the key, the request to end protection, the Deletion delay wait, the handover and a Lockdown end request, and less the once notice if you close your account. They see your card change state, never the request behind it, and they never hold the code that agrees to one.

The character beside your name on their phone is the one you chose for yourself, and the face you see for each of them is the one they chose. Any phone number you save for someone in your circle stays on your phone.

Why the list is short

There is no spend figure anywhere in what reaches a supporter, which is why no screen can leak one by accident. Money kept is worked out on your phone from a figure you set yourself, and nothing sends it on. The same is true of what you browse and of the apps you blocked: Screen Time hands the app tokens back to the phone in a form nothing can read as a name, so there is nothing to send even if a surface wanted to.

Free text is kept off the supporter path. A request to end protection carries no message from you and no reply from them, a nudge is one of a few fixed kinds, and your check ins never leave your phone. The one exception is the note you can write when you ask your keyholder to end a Lockdown sooner, which only your keyholder reads.

Why an event is on the list at all

Several of the eleven are events rather than states, because a keyholder who learns nothing is not a keyholder. The ones that matter most, a request to end protection or a Lockdown end request opening, protection turning off and your phone no longer confirming it, reach the person holding your key whatever any switch says. Each one is a kind and a count, never the thing that happened.

What you can read back

Each person in Your circle on People has a History page on their own page: the nudges they sent and the thanks you sent back, the day they joined your circle or accepted your key, and the answers they gave to your requests.

What this does not do

The list does not shrink because you would like it to: sharing is set once, in Settings, for everyone. The list does not grow either, because the same eleven items are written on this site and in the privacy policy, and a change has to reach all of them. It does not hand them any control: only you change what is shared, so a keyholder cannot widen what they see about you. And it does not describe what they can do about the block: they can say no to your request, or say yes in person by showing you their code, and they can never cancel a wait that is already running.