Companion app — approvals for your own sessions only.
Link this phone
Enter the 6-digit invite code you were given. One code links one approver — the account owner, or a customer whose session it is.
Waiting for your approval
No checkpoints waiting. When an agent hits a verification wall on your session, it lands here.
Alerts on this phone
Checking notification status…
On iPhone, push works from the Home Screen app: tap Share → Add to Home Screen, open HumanGate from that icon, then enable notifications here.
Standing permission — checkpoints
About standing permission ▾
Permission you grant once. Inside it, your agent completes checkpoints itself; outside it, a card asks you — and the run parks instead of dying. Puzzles, SMS codes and passkey QRs are refused no matter what you set here.
All agents
Checking pause state…
A preset sets the checkpoint rules below. You can still tune any row.
Signal checks
Invisible bot-signal checks (Turnstile-class). No puzzle, no codes.
Presence checks
“I'm not a robot” checkbox class, in your own session.
Everything else
QR-link handoffs, block pages, live-view.
always ask
Default for new sites
Applies when no per-site rule matches.
Per-site rules
No per-site rules — defaults apply everywhere.
Vault — agent logins
About the vault ▾
Credentials your agents may fill under your policy — stored encrypted, filled only by your browser layer, never shown to the agent itself.
Default for new sites:
No credentials stored yet.
Add a login
Import my browser
How import works ▾
One action, two halves. Passwords: export a file from Chrome, Edge, Firefox, Safari, Brave, Opera, Google Password Manager, Apple Passwords, 1Password, Bitwarden, LastPass, Dashlane, KeePass, NordPass, Proton Pass, Enpass or RoboForm and pick it below — it is parsed on this device and goes straight into your encrypted vault; duplicates are skipped, never overwritten. Sites (optional): pick a Google Takeout history file (BrowserHistory.json) and/or a bookmarks HTML export — only the site names are added to Policies, at the default "ask" rule; full page addresses and titles are never sent. Notes and authenticator codes found in password files are not stored yet. Nothing is imported until you press Import.
Invite a customer
Give a customer their own invite code and their checkpoints route to their phone — never to yours.
Team members — delegated approvers
How members work ▾
A member approves checkpoints within your policy when you're busy — from their own phone, under their own name, and every decision is recorded against them. They can't change policy, add or view credentials, or approve a site you marked Never. First decision wins; a deny is final. Remove a member and their devices stop working immediately.
May approve:
Members
No members yet.
Recent activity
No activity yet.
Your devices
Link code or invite code? ▾
Opening the companion somewhere new — like the Home Screen app — starts it unpaired. A link code joins that device to this account: same vault, same approvals, same alerts. (An invite code would create a separate, empty account instead.)
Session
Live takeover
Connecting…
VIEW ONLY
Screen and input are end-to-end encrypted between this phone and the agent's browser — the server relays ciphertext only and stores nothing. The agent pauses while you control. Compare the safety number with the agent's log if you ever doubt the connection.