30% off forever with FOUNDER30 →
Lienks
Sign in

Consent

In Cookie mode, Lienks uses a cookie only after consent. Your banner tells Lienks the visitor’s decision.

When do you need this?

Only in the Cookie tracking mode. In Minimal and Cookieless, Lienks sets no cookie, so Lienks itself needs no connection to a banner. This describes what Lienks does technically, not what applies to you: other services on your website can have requirements of their own.

Connect your consent banner

Call window.lienks.setConsent(true) after consent, and window.lienks.setConsent(false) on rejection or withdrawal:

// After consent
window.lienks.setConsent(true);

// On rejection or withdrawal
window.lienks.setConsent(false);

Only boolean values are accepted, anything else is ignored. The call itself sends nothing, it only changes how the next events are handled.

Write it defensively in case the script isn’t loaded, for example because of an ad blocker:

window.lienks?.setConsent(true);

The snippet uses defer, so window.lienks exists once the Lienks script has run. Make the call after that, for example from a script placed below the snippet.

Call it on every page load

Lienks doesn’t remember consent, neither in a cookie nor in local storage. After every reload it is back to “unknown”. Your banner or consent tool therefore has to call setConsent(true) on every page view if the visitor has consented before.

The existing cookie stays in the browser, but without this call it is neither read nor sent.

As pseudocode:

// Pseudocode: ask your consent tool for the stored decision
if (yourConsentTool.hasConsented()) {
  window.lienks?.setConsent(true);
}

What happens in each state

  • Unknown (the default after every load): the cookie is not read, not created and not sent. Lienks works the Cookieless way.
  • Consented: an existing cookie is read and sent right away. A new cookie is only created once the server has confirmed that the site runs in Cookie mode. So the very first event right after consent can still go out without a cookie, and the cookie is created with the next event (often milliseconds later).
  • Rejected or withdrawn: an existing cookie is deleted right away, nothing is read or sent. If the visitor consents again, a new cookie is created, the old identifier never returns.

Cookie details

The cookie is called _lienks_vid. It is first-party and only for your domain (no Domain attribute), valid for a fixed 24 hours, SameSite=Lax, and Secure only on https. The value is a random ID that the server hashes. More in Tracking modes.

Privacy policy text and consent snippet in the app

In each site’s settings there is a Privacy card with two tabs: Privacy Policy (a text block for your privacy policy that matches the site’s actual configuration) and Cookie Consent & Integration (the matching code for your mode). Both are technical descriptions, not legal advice.

Limitations

  • Lienks doesn’t come with its own banner, doesn’t store consent and doesn’t detect third-party consent tools. setConsent is the interface your tool calls.
  • The cookie’s lifetime isn’t adjustable.

Next steps

This page describes the technical operation of Lienks and does not constitute legal advice. Other services on your website may create additional requirements.