Security
Kindnod handles two kinds of data: the consent records of visitors to sites that use the banner, and the account data of the people who run those sites. This page says what each is, where it lives, and how long we keep it.
What a consent record contains
One row per decision: the site key, a timestamp, the method (clicked, implied by region, carried over from Cookiebot, or Global Privacy Control), four booleans for the categories, a two-letter country code, and a 24-character one-way hash of the visitor's truncated IP address and browser user agent. The last octet of an IPv4 address and the last 64 bits of an IPv6 address are dropped before hashing. We do not store full IP addresses, names, emails, page URLs, or any identifier that survives outside Kindnod. The banner sets one first-party cookie on the site, kindnod_consent, which holds the choice and a random stamp. Kindnod sets no cookies of its own on visitors.
Where it is stored
Application and database run in Frankfurt (eu-central-1) on Vercel and Neon. The banner script is served from Vercel's edge network, which caches a static file; no visitor data passes through it. Backups are encrypted and kept in the same region. Email goes through Resend; payments through Stripe, which holds card details so we never see them.
Retention
- Consent records: 30 days on the Free plan, 5 years on Pro and Agency. A weekly job deletes records past their retention. Site owners on paid plans can export the log as CSV at any time.
- Account data: for the life of the account plus 30 days after deletion.
- Scan results: replaced on each scan; the previous result is not kept.
- Bill-checker runs: domain, detected consent tool, and page count, kept indefinitely for aggregate statistics. No personal data.
Access
Site owners see the records for their own sites. Kindnod staff access production only to investigate a fault, from named accounts with two-factor authentication, and that access is logged. Nobody else has access. We do not sell, share, or train models on consent records.
In transit and at rest
TLS 1.2 or newer everywhere, including between the application and the database. Database storage is encrypted at rest by the provider. Site keys are public by design (they appear in the page source) and grant no access to anything but the banner's own configuration. Dashboard sessions use database-backed tokens issued by emailed sign-in links; there are no passwords to leak.
Sub-processors
| Provider | Purpose | Region |
|---|---|---|
| Vercel | Hosting, edge network | Frankfurt, global edge cache for static files |
| Neon | Postgres database | Frankfurt |
| Resend | Transactional email | EU and US |
| Stripe | Payments | EU and US |
Certifications
Kindnod does not hold SOC 2 or ISO 27001 certification. Our hosting providers do. Given the data involved (no names, no emails, no raw IP addresses), we think the measures above are the appropriate ones under GDPR Article 32, and the data processing agreement below commits us to them in writing. If a certification would change your decision, tell us: hello@kindnod.com.
Reporting a vulnerability
Email security@kindnod.com. We reply within two working days and credit reporters who want it.
See also the data processing agreement and the privacy policy. Last reviewed 21 October 2026.