My Partner Agreed to a Gambling Blocker. How Do I Set It Up Without Spying?

Set it up together, with them at the keyboard. Give them a standard Windows account and keep the administrator account separate, install a blocker that routes exits through you rather than a shared password, agree the exit rules now, and choose a tool that shows you protection health — not their browsing.

That is the whole guide in one paragraph. The rest of it is the reasoning, in the order you will need it, written for the person who has just been asked to hold the key rather than for the person who asked.

Start from what they agreed to

You are here because they said yes. Hold on to the specific shape of that yes, because it is the thing that makes everything below legitimate. They agreed that some changes to their own computer should go through you. They did not agree to be watched, and the difference between those two arrangements is the difference between accountability and surveillance.

Do the setup together, in one sitting, with them at the keyboard and you next to them. Not because the software needs it, but because a setup done alone is a decision made about someone rather than with them. If they cannot sit down for it this week, that is worth waiting for.

Quebec's provincial gambling helpline, Jeu : aide et référence, says the desire to cut back or stop must come from the gambler. It advises against pressure, blame, accusation, orders, moralizing remarks, and unsolicited advice; instead, it says to ask what the person intends to do and what steps they are willing to take. That source does not discuss blocker setup. GuardianBlock's editorial rule for this agreed arrangement is simple: no ultimatum and no shame. What survives 1 a.m. is a rule you both agreed to while things were calm.

You are also allowed to need something out of this. Living with someone else's gambling is its own kind of hard, and it has its own support. That is the last section of this guide, and it is not an afterthought.

Set up the Windows account first

Before any blocker, there is the account they sign in to every day. Windows separates standard accounts from administrator accounts, and Microsoft's own account documentation is the plain statement of what that separation does. Administrators, it says, have complete control over the system: they can change settings, install software, and access all files. Its own recommendation follows from that — it is safer to have fewer administrators and to use standard user accounts for day-to-day activities.

Use the part Microsoft recommends: limit the number of administrators and let the protected adult use a standard account for day-to-day activities. For this agreed setup, keep the administrator account separate for administrator tasks. That is GuardianBlock's setup guidance, not Microsoft's guidance about gambling.

This is a layer, not a solution, and it is worth being exact about why. It does not decide anything about gambling. It changes what a moment of wanting to undo a decision can accomplish without a second step. This layer stays underneath whatever blocker you choose; it is not something a blocker replaces.

Who holds the administrator credential is a real conversation, not a technicality, and it is one to have out loud rather than by default. Whatever you decide, decide it together and say it plainly.

Choose the lock before you choose the product

The lock on a gambling blocker determines what must happen before its restriction ends. GuardianBlock's lock-model guide documents four arrangements — a secret someone else holds, a waiting period you cannot skip, a period that does not end early, and a person who approves each exit — and sets them out in full in The Four Ways a Gambling Blocker Can Be Locked.

For the person holding the key, a shared-password design creates a particular role: you keep a reusable secret and later decide whether to reveal it when asked. The interaction is about disclosing that secret in the moment. That can be a hard role to hold.

Per-request approval with a waiting period is a different role. You answer a specific request from your own account, and the waiting period separates that answer from any authorization. Neither the request nor your answer makes you responsible for another adult's gambling.

Know what you will see - and what you will not

Decide this before you install anything, because it is the promise you are making to them. In GuardianBlock the answer is fixed and published: you see protection health, and you see the requests they choose to send you. Protection health is a state in plain words — protection is in place, something needs a look, the PC has not checked in recently, protection was interfered with outside the supported path, an unprotected browser is in use, or an update failed and the last good release was restored.

What you do not see is everything else. Not the sites they open. Not the sites a block stopped. Not page titles, screenshots, keystrokes, or their files. An Emergency allow request carries the site and the reason they wrote, because they chose to send it to you. Nothing else about their day travels with it. The full list, and the reasoning behind it, is published on the privacy page for guardians and protected adults and on the accountability alerts page.

This is the point in the setup where good intentions go wrong, so it is worth naming directly: there is no supported way to satisfy the urge to check, and this guide offers no substitute. GuardianBlock shows the agreed health signals and explicit requests; ordinary activity remains outside the arrangement. If that boundary no longer feels acceptable, pause the setup and talk about the boundary rather than widening it yourself.

“

Not knowing what they did today is the part you agreed to. It is also the part that makes this something they said yes to.

Agree the exit before you need it

The hardest conversation is not the one where you set this up. It is the one where they ask you to end it. Have that conversation now, while nobody wants anything, and write down what you decide.

In GuardianBlock, turning protection off is a sequence rather than a switch, and each step has to finish before the next one starts. They request deactivation. You approve or deny it from inside your own account, with recent multi-factor authentication — a passkey or an authenticator app, never SMS alone. A 24-hour cooling-off period runs, during which nothing on their PC has changed and no authorization exists yet. Only then does GuardianBlock issue a signed, single-use authorization for that one device, valid for 48 hours, which the uninstaller checks before removing protection.

Read that sequence as four separate things, because that is what it is: your decision, the wait, the authorization, and the uninstall. Your approval by itself does not turn anything off. Neither approval nor denial makes you responsible for another adult's gambling.

The rules you agree on are about what a request means, not about proving whether it is genuine. Decide together how you will use the 24 hours and how you will communicate during them. On the day, follow the process you both chose rather than judge the person making the request.

One thing not to try: refusing forever. It is not a strategy, and the product does not rely on it. Replacing a keyholder with their approval takes effect 24 hours after the new keyholder accepts and sets up multi-factor authentication; without that cooperation, GuardianBlock uses a seven-day identity-verified review, and documented safety, abuse, account-loss, or wrong-person cases can be expedited by support. Nobody ends up permanently locked out. Your refusal is not the wall, and it was never meant to be.

A device blocker is one layer of several

A device blocker, operator self-exclusion, and bank or card payment blocks act at different layers. Review them as separate choices rather than assuming that one duplicates another. The comparison is set out on self-exclusion versus device blocking, the Canadian programs and how to enrol are in How to Block Gambling Sites in Canada, and the gaps self-exclusion leaves are in Self-Exclusion Works - But It Leaks.

Walk through the whole stack together in the same sitting, for the same reason as everything else here: it is their arrangement, and they should be able to see and choose every layer.

There is support for you, not only for them

This is the section people skip, so it is the one worth reading twice. The World Health Organization's gambling fact sheet states that harm from gambling by others is widespread, and that for every person who gambles at high-risk levels an average of six others — usually people who do not gamble themselves — are affected. It lists relationship breakdown, financial distress, and stigma among those harms, and it notes that stigma and shame often prevent people from seeking help. That last sentence is about you as much as it is about them.

England's national guideline on harmful gambling, NICE NG248, recommends offering support to affected others in their own right: help and advice by themselves as well as together with the person if both agree, techniques to manage their own distress and prioritise their needs, and support with non-judgemental communication. Read that recommendation on its own terms: support is offered to the affected other. This guide does not turn it into a duty to manage someone else's gambling.

In Canada, the Responsible Gambling Council publishes a directory of provincial and territorial gambling helplines, and CAMH in Toronto runs a four-session support group for family members and loved ones that accepts self-referral and runs a few times per year as needed.

The same guideline that says to involve a partner says to do it if that is what both people agree to. That condition is the through-line of this entire guide, and it is worth carrying past the setup: what you are building only works while it stays something they said yes to.

Setting up GuardianBlock, step by step

If GuardianBlock is the tool you land on, this is the order it happens in. They choose their keyholder when they set up their GuardianBlock account, so the first thing that involves you is an invitation rather than a download.

• They create their GuardianBlock account and name you as their keyholder.
• You accept, set up multi-factor authentication on your own account — a passkey or an authenticator app, never SMS alone — and make GuardianBlock decisions in that account.
• The setup wizard confirms you are ready before it installs anything.
• They run the signed Windows setup wizard on their PC: eligibility, keyholder, preflight checks, protection posture, and browser verification, each on its own screen.
• Windows shows its normal User Account Control prompt during installation. GuardianBlock never asks for or stores a Windows administrator password.

It installs from a signed graphical wizard — a single setup file, no terminal, no scripts, nothing to paste. What it adds is visible: one entry in Windows Settings under Apps and installed apps, a tray status app that shows protection health and has no off switch, and browser policy plus the GuardianBlock browser extension for Chrome, Edge, and Firefox.

Two things are worth doing on the day and not later. Check that their PC meets the system requirements before you sit down, so the evening is not spent troubleshooting. And read what GuardianBlock does and does not promise on the limitations page together — it is the page that tells you where the edges are, so read it before setup rather than discovering an edge alone at 1 a.m.

The step-by-step install and the supported way to turn protection off are on the install and uninstall page. Your side of it — what a decision requires, what you are shown when you make one, and what the role does not include — is on the keyholder approval page.

Then the setup is done, and the part that actually matters starts: two people who agreed on something, one of whom is not being watched.