Custom blocks

Block the sites you've decided are off-limits.

Gambling is where GuardianBlock starts. From there, you decide what else belongs on your own no-go list — and an accountability partner helps you hold that line.

Private beta
Your no-go list

Start with gambling, then add your own.

GuardianBlock leads with gambling and the funding routes around it, but the list is yours to extend. You declare the domains you've decided to stay away from, and they become part of what your protection holds.

People on the private beta add things like betting sites, trading apps, shopping, adult sites.

These are examples, not a list of what GuardianBlock will reach on its own. It works from the domains you declare — it doesn't try to police the entire internet for you.

How scope works

You see what a block will match before you confirm it.

When you add a domain, GuardianBlock shows a preview of the scope it will cover, so there are no surprises about what's included.

  • Whole domain, by default

    Declaring a domain off-limits also covers its subdomains, so you don't have to list each one by hand. The preview shows you that scope before you confirm.

  • Exact host, when you want it

    Prefer to narrow a block to a single host instead of the whole registrable domain? That's available as an advanced option.

  • Path-level isn't in this build

    Blocking one specific path inside a larger site isn't part of the private beta yet. Scope today is the domain or the exact host.

Who adds a block

Your partner can suggest one — you decide.

The no-go list belongs to the person it protects. A partner can help shape it, but nothing is added without your say-so.

  • You build the list

    The no-go list is yours. You add the domains you've decided to stay away from, in your own words.

  • Your partner can propose

    An accountability partner can suggest a domain worth adding, but a proposal only becomes a block when you confirm it. Nothing is added behind your back.

Not monitoring

A custom block is a decision, not a feed.

What a custom block keeps

The domain or exact host you declared off-limits.
An optional short note to yourself about why — kept minimal.
Whether the block is currently active.

What a custom block is not

A record of the sites you actually visit.
Your browsing history, searches, or keystrokes.
A monitoring feed sent to your accountability partner.

Your partner can see which domains you've declared off-limits, so a removal stays accountable — but they never see your browsing history or the private note behind a block.

Removing a block

Taking a site off the list is a deliberate, accountable change.

Adding a block should be easy; undoing one in a weak moment should not be. Removals stay accountable instead of being a quiet switch.

  • Not a silent one-tap toggle

    Removing a domain from your no-go list is a real change, not a switch you can flip on impulse and forget about.

  • Your keyholder is in the loop

    Because removals are partner-accountable, your keyholder sees the request and can help you honour the decision you made earlier, when it was easier to think clearly.

More on what an accountability partner can and can't see lives on the privacy overview, and the FAQ answers the common questions.

Decide your no-go list while it's easy.

Set the lines you don't want to cross in a calmer moment, and let an accountability partner help you hold them.

Request early access