Cookies and consent
Loomduct sets no cookies. When you might still need consent, and what to do then.
Loomduct sets no cookies and writes nothing to your visitors' devices: no cookies, no localStorage, no sessionStorage. It does not need a cookie banner for itself.
Why Loomduct needs no cookies
- Visitors are counted with a daily hash, computed on Loomduct's servers. See How Loomduct counts visitors.
- IP addresses are never stored.
- The only thing the SDK reads from the device is the
loomduct_ignoreopt-out flag, if you set it.
When you might still need consent
- Reading device details. In the EU, ePrivacy rules can cover reading information from the device, like the screen size or time zone, even without cookies.
- Client hints. The
clientHintsplugin reads the exact OS version and device model. It is off unless you add it. - Identified users. When you identify users, you link analytics to people. Mention it in your privacy policy.
If you need consent first, start tracking after consent.
GDPR
- Your visitors' data is stored in the EU.
- Loomduct processes it for you: you are the controller and Loomduct is the processor.
- The Data Processing Agreement applies automatically when you use Loomduct.
- Mention Loomduct in your own privacy policy. The data we collect page lists what to cover.