Protection that holds when willpower doesn't.

ShieldBet works across four layers: AI detection, behavioural interruption, two-person accountability and continuous monitoring. Together they close every gap that existing tools leave open.

Layer 1

AI detects gambling content, not just gambling domains.

Every other blocker works from a list of known gambling websites. That approach fails the moment a new site launches, a mirror domain appears, or someone switches to a crypto casino that has never been listed anywhere.

ShieldBet scans the actual content and structure of every page you visit. It analyses text signals, action signals, structural signals and crypto signals simultaneously. A brand new offshore casino launched yesterday will be caught. A mirror site with a random domain will be caught. A crypto casino with no recognisable name will be caught.

When the keyword score reaches an ambiguous range, a second AI verification layer activates. This examines the page's overall context and visual structure, the same way a human would assess it, to confirm or override the initial score.

The AI layer means ShieldBet never needs manual updates to catch new sites. Detection improves automatically as patterns are refined centrally and pushed to all users.

SignalTypeScore
roulette, blackjack, slotsText5 pts
sportsbook, live dealerText5 pts
provably fair, crash gameCrypto5 pts
bet now, deposit bonusAction4 pts
free spins, jackpotAction4 pts
wallet connect, BTC depositCrypto4 pts
odds table, betting slipStructural3 pts
odds, stake, betting tipsText1-2 pts
support, recovery, GamCareSafety-3 pts
10+ ptsImmediate block. Full screen overlay with 30-second timer.
6 to 9 ptsWarning screen. AI verification triggered. 10-second pause.
4 to 5 ptsAI verification only. No visible action unless confirmed.
Below 4Page allowed through. Score logged silently.
Layer 2

A deliberate pause before the page.

When a gambling site is detected, ShieldBet does not simply display an error. It activates a full-screen block that obscures the entire page before any content is visible or interactive.

A 30-second countdown timer runs before any further option appears. This timer is not a technical requirement. It is a psychological one. Thirty seconds is often enough time for rational thinking to reassert itself over an impulse. The pause exists to create that space.

After the timer, the user is shown two options: leave the page or continue. If they choose to continue, a second confirmation is required. Every decision at every step is logged with a timestamp and sent to the trusted partner.

The block screen is designed to feel supportive rather than punishing. It reminds the user that they put this protection in place at a stronger moment than this one.

1

Page obscured immediately

Content hidden before any text or images are visible. No interaction possible.

2

Supportive message displayed

"You put this protection in place at a stronger moment than this one."

3

30-second countdown timer

Impulse-breaking pause. Cannot be skipped or dismissed.

4

Two options presented

Leave the page or continue. Both choices are logged.

5

Second confirmation if continuing

An additional deliberate step required before access is granted.

6

Partner notified

Full event log sent to trusted partner with timestamp and site details.

Layer 3

Two people required to disable protection.

This is the feature that separates ShieldBet from every other tool in existence. Disabling protection is not a solo action. It requires your password and your trusted partner's separately held approval code.

When you attempt to disable ShieldBet, a request is sent to your trusted partner with the timestamp and device details. They receive a notification and must enter their own password to generate an approval code. That code is sent directly to them, not to you. You must ask them for it.

You can optionally enable a 24-hour cooling-off delay. Even after your partner approves a removal request, protection stays active for a further 24 hours. This addresses the scenario where an impulse fades overnight and the person wakes up grateful that the delay was in place.

Your partner can also activate an emergency lock that prevents any removal request from being processed for a set period. This is designed for periods of known high risk.

1

You request to disable protection

A warning screen explains that partner approval is required.

2

You enter your own password

Failed attempts are immediately reported to your partner.

3

Partner receives an alert

Email with timestamp, device name and a clear approval request.

4

Partner enters their password

They generate an approval code that is sent only to them.

5

You must ask your partner for the code

They choose whether to share it. They can decline for any reason.

6

Optional 24-hour delay

If enabled, protection stays active for one more day after approval.

Layer 4

Continuous monitoring so nothing slips through silently.

ShieldBet sends a regular heartbeat signal to its monitoring system while it is active. If that heartbeat stops while the user is marked as active, something has gone wrong and the trusted partner is notified immediately.

This addresses the silent bypass problem. Someone who uninstalls the extension, disables it through Chrome's settings, or finds a technical workaround cannot do so without triggering an escalating alert sequence.

The first missed heartbeat triggers an initial warning to the partner. If the heartbeat remains absent, a second escalation alert is sent stating that protection may have been disabled or removed. This gives the partner the information they need to check in.

The heartbeat system also tracks the user's idle state. If the browser is closed or the computer is locked, heartbeats pause automatically so partners do not receive false alerts overnight.

1

Regular heartbeat sent while active

ShieldBet checks in automatically every few minutes during active browsing.

2

Missed heartbeat detected

If the signal stops while the user is marked active, the system flags it immediately.

3

First warning to partner

Partner receives an initial alert that protection has stopped responding.

4

Escalation if signal remains absent

A second alert states protection may have been disabled or removed.

5

Idle state awareness

Heartbeats pause when computer is locked or browser closed, preventing false alerts.

Ready to start?

Install the Chrome extension for free and set up your trusted partner in under ten minutes.