EU privacy, taken further. Hardware-level and fully invisible.

TrustSig vs CaptchaFox

Both are EU-aligned and privacy-minded. The difference is whether the user is ever asked to do anything, and how detection is made.

Where TrustSig goes further

CaptchaFox is a reasonable privacy-first EU choice. Teams move to TrustSig for zero user footprint and a deterministic verdict.

Swap CaptchaFox for TrustSig

Remove the widget mount and verify call; add the invisible scan and a local verify. Two npm packages, no infrastructure changes.

1. 01
   Frontend — remove the widget

   // Before — CaptchaFox widget mount
   // <div className="captchafox" data-sitekey={SITE_KEY} />
   
   // After — TrustSig (no element, runs in the background)
   import { useTrustSig } from "@trustsig/react"
   
   function ActionForm() {
     const { scan } = useTrustSig()
   
     const handleSubmit = async () => {
       const response = await scan()
       await fetch("/api/action", {
         headers: { "X-TrustSig-Response": response?.token || "" },
       })
     }
   }

2. 02
   Backend — replace the verify call

   // Before — CaptchaFox (network round-trip)
   // await fetch("https://api.captchafox.com/siteverify", ...)
   
   // After — TrustSig (verified locally, zero latency)
   import { TrustSig } from "@trustsig/server"
   
   const ts = new TrustSig({ secretKey: process.env.TRUSTSIG_SECRET_KEY })
   
   app.post("/api/action", async (req, res) => {
     const token = req.headers["x-trustsig-response"]
   
     const result = ts.verifyLocal(token)
   
     if (result.action === "BLOCK")
       return res.status(403).json({ error: "Blocked" })
   })

CaptchaFox alternative questions