Both of you opt in.
GuardianBlock only starts when two adults agree to it — the person setting their own limits, and the accountability partner they ask to hold the key. Consent is mutual, voluntary, and something either side can step back from.
An invite only you can send, accepted only by them.
No one is added quietly in the background. The protected adult starts the partnership, and the partner has to actively accept it from their own account.
You send the invite
From your own signed-in account, you invite one person to be your accountability partner. GuardianBlock creates a one-time invite link and keeps only a hashed version of it on the server — never the raw link.
They accept in their own session
Your partner opens the link and accepts while signed in to their own GuardianBlock account. Their identity comes from their session, not from anything typed into your device.
They see what they're agreeing to
Before accepting, your partner reads plainly what the role means: you've asked them to hold your key, they're an accountability partner and not a browser monitor, and eligible exception requests come to them for a simple yes or no — while hard categories like gambling and funding routes can't be approved by anyone.
An unused invite expires
If the invite is never accepted, it stops working after about seven days. A link nobody used quietly lapses instead of lingering.
Either side can step back.
Decline before accepting
Someone who's asked but doesn't want the role can simply decline. Nothing is set up unless and until they accept.
Revoke an invite you sent
Change your mind? You can revoke an invite before it's accepted, and an established partnership can be unwound through the supported process rather than vanishing silently.
There's always a way back
GuardianBlock includes a recovery path, so a lost device, a changed mind, or an unreachable partner never leaves either person without a way forward. Replacing an accountability partner goes through a cooling-off and recovery flow, not an instant swap.
Sensitive changes ask you to prove it's really you.
Everyday accountability is light-touch. But sensitive actions — the ones that change what's protected — are designed to require a recent sign-in before they go through, so an unattended session can't be used to weaken protection. Stronger multi-factor verification is part of the account-security design we're continuing to build; consent itself is recorded from each person's own signed-in session.
Clear about what your partner can and can't do.
Saying yes sets up accountability, not surveillance or remote control.
What your consent grants
Lets your partner authorize the sensitive changes you've asked them to gate.
Lets them receive accountability alerts if protection is paused, removed, or tampered with.
Lets them answer the eligible exception requests you explicitly send, with a yes or no.
Lets them see whether your protection is healthy and current — not what you do online.
What it never grants
Your browsing history, the sites you visit, your searches, keystrokes, or screen.
The ability to remotely operate, unlock, or take over your device.
Any password or secret entered on your device — each person stays in their own account.
Approval power over hard categories like gambling and funding routes, which no one can override.
Want the other side of the story? being an accountability partner, how your privacy is protected, or the FAQ.