Being someone's keyholder.
On a normal day, being there is the whole job. They know the changes that would weaken their protection need your yes.
They ask, with a reason.
You answer.
Their protectionProtected
You're their keyholder · You don't see their browsing
Needs you 1
Corner Bookshop
Request pending · Requested 2 minutes ago
- Their reason
- "Need to check an order"
- Asked for
- 15 minutes
Approve for how long?
Access can end early on a device that can't confirm protection is running.
Now and then, a clear yes or no.
A pending request is not an approval.
Support, not surveillance.
You see protection health, alerts, their Custom Blocks and their requests. Never their browsing, searches, keystrokes or screen.
You hear when protection changes.
If protection is paused, removed, or interfered with, you can be alerted where the device leaves evidence of it.
You are not a monitor.
No alert for every blocked visit by default, and a declared Custom Block is not evidence of a visit.
You do not operate their device.
There is no console to operate, lock, or wipe their computer.
You do not remove protection for them.
During the commitment, ordinary early deactivation needs your approval and at least 24 hours of cooling-off, and you can still cancel until the release is final. Support and safety recovery stay available, and once the commitment ends, they no longer need your yes.
Asked to hold someone's key? Set it up together.
Both of you opt in.
They start GuardianBlock and send you an invite.
A one-time link to one person. If nobody accepts it, it stops working after about seven days.
You accept from your own account, or decline.
Nothing is set up unless you accept.
Either side can step back.
An established role ends through the supported process, never silently. A lost device, a changed mind, or an unreachable keyholder never leaves either person stuck.