Privacy
Nolgard helps sites distinguish people from automated traffic. We process the context needed to run and secure the service.
Data we process
We process browser, device, network and interaction context, page URLs and referrers, and verification results. We don't collect typed passwords or the contents of keystrokes.
When a customer sends account context, we store their account id as given (up to 256 characters), a masked email (first character and domain), and salted account-link hashes for 30 days after the last verification. We do not store the full email in the account directory.
Portal accounts store your email, optional name, public passkey credentials and account activity. Private passkey keys stay on your device or with your passkey provider.
No raw IP storage
IP addresses are processed temporarily for verification and rate limits. Stored network identifiers are salted hashes. Raw IP addresses are not stored.
Optional abuse network
Customers can opt in to sharing and receiving cross-customer fraud-prevention matches. Only keyed hashes of device fingerprints, normalized emails and non-freemail email domains are shared within this network, retained for 90 days. Raw values, visitor ids and IP addresses are never shared. Reports from at least two other account owners are required for a match. Sites that opt out neither contribute nor receive matches.
Payment events (Stripe)
If a customer connects their Stripe account, their Stripe sends payment events to us by webhook. We never receive card numbers, cardholder names, emails or addresses, and we hold no Stripe API key.
Per event we store: the Stripe outcome kind, livemode flag, amount, currency, decline or dispute reason, card country, an HMAC of Stripe's card fingerprint, and salted actor hashes linking the event to the device and account that checked out.
Payment events and their links are kept 180 days, processed Stripe event ids 30 days, and released holds 30 days.
Retention
Events are deleted within an hour of reaching 30 days old. Account audit history is kept for 365 days. Account and site settings remain while your account is active. Aggregated statistics don't identify individual visitors.
Hosting and sharing
Data is stored in Cloudflare's EU jurisdiction (D1 and Durable Objects). The edge is global, so network processing may happen outside the EU. We don't sell visitor data or use it for advertising.
Integrations you configure send aggregate alerts to your chosen webhook, Slack or Telegram destination. Those providers have their own privacy terms.
Cookies and analytics
The portal uses a secure, HttpOnly session cookie for login. The public site doesn't load third-party analytics.
Our own site analytics set no cookies and use no browser storage. For each page view we record the page, the referring site, campaign tags, country, a mobile/desktop flag and a few button events. A visitor counter is a hash of the IP address and browser that changes every day, so visits can't be linked across days. Raw IP addresses and user agents aren't stored. Page views are deleted after 90 days. Browsers that send Global Privacy Control aren't counted. When you create a portal account, we keep the page and campaign that led you to sign up.
Customers must provide the notices and collect the consent their own sites require.
Your choices
For access, correction, deletion or privacy questions, email privacy@nolgard.com. If you visited a customer site that uses Nolgard, contact that site about its processing too.