verifi analyzes behavioral and hardware signals to determine whether a visitor is human. none of this is personally identifiable:
verifi does not read form field values, passwords, email addresses, or any content you type.
on page load, verifi queries a reputation API to retrieve your IP address, then hashes it with HMAC-SHA256 using a server-side secret before any storage. the hash cannot be reversed to the original IP. it's stored alongside a bot likelihood score and used to apply stricter or more lenient verification on future visits.
known malicious IP ranges from public threat intelligence feeds are pre-loaded in hashed form.
verifi uses a small on-device neural network to improve bot detection. after a challenge, an anonymized weight delta is sent to a central server — no behavioral data, only the direction the model weights moved. deltas are averaged across all sessions globally; no individual session can be reconstructed from one.
after passing verification, verifi issues a short-lived signed token (HMAC-SHA256, 5 minute expiry) containing only: site ID, issue/expiry time, human probability, and confidence score. verified server-side by the site you're visiting — verifi does not log token verifications.
verifi uses Supabase to store federated model weights and hashed IP reputation data. verifi is deployed on Cloudflare Pages. IP lookup on page load uses whatismyip.com to retrieve the visitor's IP address for hashing.
verifi does not process personal data as defined by GDPR. behavioral signals are not linked to any individual and cannot be used to identify a person. IP addresses are hashed before storage and cannot be reversed. no consent banner or data processing agreement is required to use verifi.
if you believe this analysis is incorrect for your jurisdiction, contact privacy@zo0p.dev.