Security and data

How we work

What BerryCookie, the cookie consent platform (CMP), keeps, where it keeps it, how accounts are protected and what you can check yourself.

This page is for anyone deciding whether to trust BerryCookie with their website: what we keep, where it is kept, how accounts are protected and what you can check yourself, without taking our word for it.

Who we are

BerryCookie is an independent consent management platform, built and run in the European Union. It is a young product: we have no case studies to show yet, and we do not make them up. Instead, this page says how we work, and the tools below let you check the product yourself. What changes in the product is published on the news page, with its date.

Where the data is

  • Hosting in the EU: the dashboard, the Consent API and the databases run in a data center in the EU, at a hosting provider based in Germany.
  • Delivery and protection: the site's traffic passes through Cloudflare's network (CDN).
  • Fonts and icons are served from our own servers.
  • The full list of providers that process data for us, and what each does, is in the Data Processing Agreement (sub-processors) and the Privacy Policy.

What we keep about your visitors

  • One record per choice in the consent log: a consent ID (random, created in the visitor's browser), the categories chosen, the banner version, the language, the time, the browser's user agent, the page where the choice was made and the visitor's IP address, shortened before it is stored. No full IP address is kept. The DPA lists the same fields.
  • How long: as long as you set for each website (36 months unless you change it, between 6 and 120), then deleted automatically. You can export the log in CSV at any time.
  • On your website, the banner keeps the visitor's decision in the BerryCookieConsent cookie, on your own domain, for the period you choose (12 months by default). It remembers the choice and is not used for tracking.
  • No profiles, no selling. Consent records are used to show you, and prove, what your visitors chose. Nothing else.

How accounts are protected

  • Encrypted connections (HTTPS/TLS) for the banner, the Consent API and the dashboard.
  • Hashed passwords and session tokens, optional two-factor authentication.
  • Roles inside each organization: only its members see its websites and consent records.
  • Rate limits and input validation; the public Consent API is separate from the dashboard API.
  • Regular database backups and monitoring of the service.

What you can check yourself

  • The free check: BerryCookieScanner opens up to 5 pages of a website in a real browser, clicks "Reject" and "Accept" and shows what loads before and after. Try it on your website, or on berrycookie.com itself.
  • The banner script: bc.js is public at cdn.berrycookie.com; anyone can read what it does in the browser's developer tools.
  • Your own data: the consent log exports to CSV, and the compliance file (PDF) puts the banner, the scans, the cookie declaration and the consents in one document, on every plan.
  • What we don't do: BerryCookie is not a Google-certified CMP (IAB TCF). Sites showing Google ads need one; the comparison says so plainly.

Leaving

You can delete a website or your whole organization at any time. Its consent records are deleted within 30 days, unless the law requires keeping them, and backups are in turn deleted after a limited period. Export the log first if you want to keep it.

Reporting a security problem

Write to [email protected] or use the contact page. Our security.txt lists the same addresses. Please give us time to fix a problem before you make it public; we answer by email.

Check it on your own website

The free check shows what your website loads before and after consent. No account needed.