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

TrustSig vs CaptchaFox

Both are EU-aligned and privacy-minded. These rows cover the challenge, the detection model and the verify path.

Invisible at every risk level, not most of them

CaptchaFox is a reasonable EU choice, so the move is usually about the challenge fallback.

Swap CaptchaFox for TrustSig

Delete the widget mount, then add the scan and one verify call on the server. Two npm packages, and your infrastructure is untouched.

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 { getResponse } = useTrustSig()
   
     const handleSubmit = async () => {
       const response = await getResponse()
       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 (one verify call at the edge)
   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 = await ts.verifyRemote(token)
   
     if (result.action !== "ALLOW")
       return res.status(403).json({ error: "Blocked" })
   })

CaptchaFox alternative questions