Reference

Cookies & consent

Nalloo sets one first-party analytics cookie. This page gives you the text to add to your cookie policy, and shows how to load Nalloo only after your visitors accept analytics cookies.

What Nalloo stores

Nalloo sets a single first-party cookie, NUI, for analytics — to measure how the site is used. It stores a random identifier only: no name, email or personal profile.

Because it’s an analytics cookie (not “strictly necessary”), EU ePrivacy rules mean you should disclose it and obtain consent before it’s set — the same as any analytics cookie.

Practical guidance to help you configure Nalloo — not legal advice. Confirm your final cookie and consent setup with your own data-protection adviser.

Two things to do

Cookie declaration

Add these details to your cookie policy:

Or copy this ready-made text:

cookie-policy.txt
NUI — Nalloo (Ecofin Cloud S.L.). First-party analytics cookie.
Measures site usage. Stores a random ID only — no personal data.
Duration: 12 months. Category: Analytics / Statistics.

Load Nalloo only after consent

Pick the option that matches your setup. In every case, Nalloo (and the NUI cookie) should run only once the visitor has accepted analytics cookies. Replace YOUR_SITE_KEY with your key.

Generic (any consent banner)

Call loadNalloo() from your banner’s “accept” callback.

index.html
<script>
  function loadNalloo(){
    if (window.__nalloo) return; window.__nalloo = true;
    var s = document.createElement('script');
    s.async = true; s.defer = true;
    s.src = 'https://nalloo.com/nalloo.min.js';
    s.setAttribute('data-key', 'YOUR_SITE_KEY');
    document.head.appendChild(s);
  }
  // Run loadNalloo() when the visitor accepts analytics cookies.
</script>

Cookiebot

Mark the script as statistics; Cookiebot keeps it blocked until consent.

Cookiebot
<script async defer
  src="https://nalloo.com/nalloo.min.js"
  data-key="YOUR_SITE_KEY"
  data-cookieconsent="statistics"
  type="text/plain"></script>

OneTrust

Tag it with the Performance category (C0002); OneTrust unblocks it on consent.

OneTrust
<script async defer
  src="https://nalloo.com/nalloo.min.js"
  data-key="YOUR_SITE_KEY"
  class="optanon-category-C0002"
  type="text/plain"></script>

Google Tag Manager (Consent Mode v2)

If you run Google Tag / GTM, this is the cleanest route — GTM holds Nalloo back until consent, with no code on the page:

GTM then fires Nalloo only once your consent banner grants analytics through Consent Mode v2.

FAQ

Questions, answered.

Do visitors have to consent before Nalloo runs?

Yes. Treat Nalloo like analytics: load it only after the visitor accepts analytics cookies. If they haven’t consented, don’t load it.

What happens if a visitor declines?

Nalloo simply doesn’t run for that visit and no cookie is set — that’s the expected, compliant behaviour.

Is Nalloo still GDPR-friendly?

Yes. Nalloo stores no personal data of visitors and is EU-hosted. Cookie consent is a separate ePrivacy requirement, handled by the disclosure and consent steps above.

Which consent category should I use?

Analytics / Statistics / Performance — whichever name your consent tool uses for measurement cookies.