Every new connection has to be approved. Who approves it is the decision that matters.
Guardian sits in front of remote access on the PC. When something asks to connect, the answer is no until an approval arrives. Where that approval comes from decides how much the lock is actually worth.
You're protected
| Asking to connect | 102.54.9.17 |
| Using | AnyDesk |
| Approval | Dave |
Held — nothing connects until Dave approves
A demonstration of the approval prompt. This website is not scanning your computer.
The principle: the approval has to be somewhere the attacker isn't
A remote-support scam takes two things at once — control of the computer, and the attention of the person using it. Any approval that can be reached from either of those is an approval the attacker can get.
That is the whole test. Not who has the authority to say yes, but whether the place they say it is inside the attacker's reach. Everything below is ordered by that one question.
Who allows a connection
You pick this on the website when you set Guardian up, and you can change it here whenever you like. It is deliberately not in the app, so a person controlling the PC cannot reach it.
-
Strongest · Default
Someone else approves
The right choice when the PC belongs to someone likely to be the one on the phone.
- Something asks to connect to the protected PC.
- Guardian refuses it and holds it while it asks.
- Your Trusted Guardian gets an email with the address, the tool, and the time, and sees the same request in the dashboard here. Nothing to install on their phone — both open in a browser.
- They choose allow this connection only, always allow this address, or refuse.
- No answer means no connection.
The caller has no route to that mailbox. Stops a live scam call.
-
Convenience
You approve, for your own PC
When you look after your own machine and have nobody sensible to nominate. Two ways of doing it, sharing one limit.
- Something asks to connect. Guardian refuses and holds it.
- By link: the request arrives in your email and dashboard, and you answer it from wherever you read it. Read it on your phone rather than on the protected PC.
- By PIN: Guardian holds the connection, explains on screen what letting a stranger control this computer would mean, and asks for the unlock PIN. A missing or wrong PIN drops the session.
- Either way: allow once, always allow that address, or refuse.
Stops strangers and automation. Not a determined live call — see below.
The PIN is set in your account on this website and is never displayed in the Guardian app, so somebody watching the screen — or driving it remotely — cannot read it or reset it.
The approver doesn't need to be an expert
One question decides it, and the scam has no answer for it.
“Did you ask someone to connect?”
The person being scammed cannot verify anything, because the only person available to verify with is the scammer. Someone who is not on that call can simply ask — and there is no version of this attack that survives being asked, because the caller cannot take part in that conversation.
Nothing technical is required
No alert to interpret and no risk score to second-guess. If the answer is no, or nobody can be reached, the answer is refuse. Refusing costs a phone call. Approving wrongly can cost a bank account.
Prompts stay rare by design
Support you allow once can be whitelisted so the next visit goes straight through. A request appearing at all is an address nobody has approved before — the opposite of a prompt you learn to click past.
Why approving for yourself is the weaker option
Two things work against it, and it is worth naming both rather than letting a setting quietly decide whether this product's central claim is true.
Your mailbox may be on the machine under attack. Email goes to an account, not to a device. If that mailbox is signed in on the protected PC — a webmail tab, a mail client, a saved session — then somebody who has taken control of that PC can open the approval request and click Approve themselves, with no persuasion at all. The dashboard has the same property if the browser there is still logged in. So read approvals on your phone, and keep that mailbox off the machine Guardian is protecting.
And you are still the one on the call. Even on a separate device, a caller who has got that far can simply tell you to check your email and tap Allow. Answering somewhere else makes them work harder — you read the address and the tool on a screen they cannot control — but it does not make you a different person.
Nominating somebody else removes both at once. Their mailbox was never on your PC, and they are not on the call, so there is no conversation in which they can be worn down. That is the whole reason it is the default.
| What it stops | Someone else approves | You approve |
|---|---|---|
| A stranger connecting while nobody is at the PC | Stopped | Stopped |
| Repeated automated attempts on the same address | Stopped | Stopped |
| Somebody controlling the PC approving their own connection | Stopped | Only if your email isn't open on that PC |
| A caller talking the person at the PC into approving | Stopped | Not reliably |
What happens when a connection is refused
- The session is dropped before any control is handed over. Nothing is shared, and nothing is installed.
- The attempt is recorded with its address, the tool, and the time.
- Guardian counts the failures for that address.
- After five failures, that address goes on Blocked IPs and is refused outright — no more emails, no more prompts.
You can see and edit Blocked IPs and your whitelist in the dashboard. An address you added by mistake can be taken off the list again.
After approval, Guardian keeps watching
Saying yes to a connection is not the same as saying yes to anything that follows. A technician you approved is still a session Guardian is looking at.
- 01 Connection approved
- 02 Session running
- 03 File transfer
- 04 Privilege escalation
- 05 Guardian stops it
If an approved session begins transferring installers and reaching for administrator rights, Guardian can end it. Guardian Story then explains what happened in a sentence a person can read, with the technical view underneath.
Support you booked still works
Guardian is a lock, not a wall. When your own technician connects, approve them once for that session, or add their address to the whitelist so the next visit goes straight through. Businesses can whitelist the tools and addresses their support desk actually uses.