Cookie Policy — LYNKODE LLC
Last updated: 2026-05-19
Effective date: 2026-05-19
Version: v2.0
This Cookie Policy explains what cookies and similar storage technologies LYNKODE LLC uses on the marketing website https://lynkode.no (the “Website”) and on the operator-only dashboard at https://dashboard.lynkode.no (the “Dashboard”), why they are used, and how you can control them. It supplements the Privacy Policy.
1. Legal framework
Cookies and similar technologies are regulated by:
- GDPR (Regulation (EU) 2016/679) — when cookie data constitutes personal data (most identifier cookies do).
- ePrivacy Directive (Directive 2002/58/EC, as amended by 2009/136/EC), Art. 5(3) — the rule that any storage or access to information on a user’s terminal equipment requires the user’s prior consent, except where strictly necessary for service requested by the user.
- Norwegian Electronic Communications Act (ekomloven) §2-7b (LOV-2003-07-04-83) — Norwegian implementation of the ePrivacy storage rule. Datatilsynet and Forbrukertilsynet enforce.
- Bulgarian Electronic Communications Act (Закон за електронните съобщения) — equivalent rule in Bulgaria.
- EDPB Guidelines 2/2023 on Article 5(3) of the ePrivacy Directive (and Norwegian/Bulgarian implementations).
- GDPR Recital 30 — cookies as online identifiers.
Pre-ticked boxes are not consent (CJEU Case C-673/17 Planet49).
2. What is a cookie
A “cookie” is a small text file a website stores on the user’s device through the browser. “Similar storage technologies” include localStorage, sessionStorage, IndexedDB, web beacons / pixels, and server-side fingerprinting techniques. For brevity, this Policy refers to all of them as “cookies”.
Cookies can be classified by:
- Origin — first-party (set by the site you are visiting) vs third-party (set by an external domain).
- Duration — session (deleted on browser close) vs persistent (deleted after a stated expiry).
- Purpose — strictly necessary, functional / preferences, analytics / statistics, marketing / advertising / tracking.
3. Lawful basis for cookies
| Cookie category | Legal basis for setting / reading |
|---|---|
| Strictly necessary | No consent required — ePrivacy Art. 5(3) second sentence; ekomloven §2-7b second paragraph; service that the user has expressly requested. |
| Functional preferences (where they fall outside “strictly necessary”) | Consent — ePrivacy Art. 5(3); GDPR Art. 6(1)(a). |
| Analytics / statistics | Consent — same as above. |
| Marketing / advertising / tracking | Consent — same as above. |
Consent is collected through the consent banner on the Website (Complianz GDPR / CCPA Cookie Consent). Decision is granular — the user may accept all, reject all, or accept only certain categories. The banner does not pre-tick any non-essential category.
4. Cookies on dashboard.lynkode.no (operator-only dashboard)
The Dashboard is an authenticated tool used solely by LYNKODE LLC operators. It is not exposed to public end users. It uses only strictly-necessary storage:
| Cookie / storage | Type | Purpose | Retention |
|---|---|---|---|
PHPSESSID |
First-party session cookie | Maintain the authenticated operator session (HTTP basic auth + PHP session) | Session — deleted when the browser closes |
localStorage.theme |
First-party local storage | Remember the operator’s light / dark theme preference | Until manually cleared |
localStorage.lang |
First-party local storage | Remember the operator’s UI language preference | Until manually cleared |
localStorage.t6215ToolbarResponsiveApplied and similar one-time UI migration markers |
First-party local storage | Mark that a one-off UI migration has executed in this browser | Until manually cleared |
The Dashboard sets no analytics, marketing or third-party tracking cookies. No consent banner is shown because no consent-requiring storage is used.
5. Cookies on lynkode.no (public marketing site)
The cookies actually present on the Website as of the date above are listed below. The list is maintained by automated scanning (Complianz cookie scanner) and is updated when a scan detects a new cookie.
5.1 Strictly necessary
| Cookie | Provider | Purpose | Retention | Category |
|---|---|---|---|---|
cmplz_functional |
Complianz (first-party) | Stores the user’s cookie-consent decision | 365 days | Strictly necessary |
cmplz_consent_status |
Complianz (first-party) | Stores the consent state used to gate non-essential scripts | 365 days | Strictly necessary |
complianz_policy_id |
Complianz (first-party) | Identifies the cookie-policy version against which consent was given | 365 days | Strictly necessary |
complianz_consent_status |
Complianz (first-party) | Records consent acceptance for re-display logic | 365 days | Strictly necessary |
cmplz_marketing, cmplz_statistics, cmplz_preferences |
Complianz (first-party) | Granular per-category consent state | 365 days | Strictly necessary |
wp-settings-{user_id} |
WordPress (first-party) | Persists individual WordPress admin user preferences (only set for logged-in WordPress administrators) | 1 year | Strictly necessary |
wp-settings-time-{user_id} |
WordPress (first-party) | Companion timestamp to wp-settings-{user_id} (only for logged-in administrators) |
1 year | Strictly necessary |
| Session cookies set by the WordPress hosting platform | Hosting provider (first-party) | Operate the WordPress runtime | Session | Strictly necessary |
5.2 Functional preferences
None currently in use.
5.3 Analytics / statistics
None currently in use. If Google Analytics, Meta Pixel, LinkedIn Insight Tag or any other analytics tool is later enabled, this Policy will be updated to list every such cookie with name, provider, purpose, retention and category, and the consent banner will collect prior consent before loading the corresponding scripts.
5.4 Marketing / advertising
None currently in use. Same forward-looking commitment as §5.3.
5.5 Local storage and similar
| Item | Provider | Purpose | Retention |
|---|---|---|---|
complianz_policy_id (also in localStorage) |
Complianz | Mirror of the consent-policy version identifier | Until manually cleared |
6. Third-party content and embeds
When the Website embeds third-party content (e.g. a YouTube video, a LinkedIn or Instagram post, a Google Maps iframe, a Vimeo player), that content may set its own cookies under the third party’s own privacy and cookie policies. As of the date above, the Website does not embed such content; if embedded content is added, this Policy will be updated and the embeds will be consent-gated unless they qualify as strictly necessary.
7. Consent — granting, viewing and withdrawing
7.1 How consent is collected
When you visit lynkode.no for the first time, a consent banner appears before any non-essential cookie is set. The banner offers, with equal prominence:
- “Accept all” — consents to all cookie categories.
- “Reject all” — declines all non-essential cookies.
- “Settings / Preferences” — granular per-category selection (Functional / Statistics / Marketing).
Until you make a choice, only strictly-necessary cookies are set. Continued browsing is not consent.
7.2 How long consent lasts
Consent is recorded for 365 days. After expiry, the banner is shown again on the next visit. You may re-display the banner at any time via the “Cookie settings” link in the Website footer.
7.3 How to withdraw consent
Withdrawing consent is as easy as giving it:
- Click the “Cookie settings” link in the Website footer.
- Toggle off the categories you no longer wish to allow.
- Confirm. Non-essential cookies in the disallowed categories are removed on the next page navigation.
Alternatively, clear the cookies for lynkode.no in your browser; the next visit will re-display the banner.
7.4 Demonstrating consent
LYNKODE LLC, through the Complianz plugin, stores a record of each consent decision: timestamp, category granularity, policy version, anonymised consent ID and IP-derived region. This record is retained for 5 years after withdrawal or expiry, in accordance with GDPR Art. 7(1) (burden of proof of consent).
8. Browser-level controls
Independently of the banner, every modern browser lets you:
- view and delete cookies;
- block third-party cookies;
- block all cookies (with the trade-off that the Website may not work as intended);
- use private / incognito mode (cookies are isolated and removed on session end).
Major browsers’ help pages:
- Chrome:
https://support.google.com/chrome/answer/95647 - Firefox:
https://support.mozilla.org/en-US/kb/cookies-information-websites-store-on-your-computer - Safari:
https://support.apple.com/guide/safari/manage-cookies-and-website-data-sfri11471/mac - Edge:
https://support.microsoft.com/en-us/microsoft-edge/delete-cookies-in-microsoft-edge-63947406-40ac-c3b8-57b9-2a946a29ae09
9. Do Not Track and Global Privacy Control
LYNKODE LLC does not yet implement automated honoring of the “Do Not Track” header or Global Privacy Control signal at the technical level on lynkode.no. However, no analytics or marketing cookies are currently loaded; the result is functionally equivalent. If analytics is enabled in the future, signal-level honoring will be added.
10. Updates to this Policy
This Cookie Policy is updated whenever the set of cookies on the Website materially changes — a new cookie added by an integrated plugin, retention changes, new third-party processor — and on every change to the consent mechanism. The “Last updated” date at the top reflects the current version.
This Policy must be updated before any analytics, marketing or third-party tracking cookie is enabled on lynkode.no.
11. Your rights and how to contact us
Where cookie data constitutes personal data, the rights under the GDPR (Arts 12–22) apply — see Privacy Policy §7.
For any question about this Cookie Policy or about a specific cookie, contact:
privacy@lynkode.no
LYNKODE LLC, 1 Vitosha Blvd., 5th floor, 1000 Sofia, Bulgaria, ЕИК 2281488228.
You may also lodge a complaint with KZLD (Bulgaria), Datatilsynet (Norway) or Forbrukertilsynet — see Privacy Policy §8.