Cookie Policy

Cookies are small pieces of information stored by a browser. Similar technologies may be used to maintain session state, remember preferences, protect services or understand how a website is used.

Some technologies may be required for security, session management or functionality expressly requested by the visitor. Where they are necessary for those purposes, they are not used separately for marketing activity.

Preference technologies can remember choices such as language. Analytics may help Nördia understand usage, errors and performance where the relevant tool has been enabled under an appropriate consent model.

If marketing or advertising technologies are introduced, their purpose should be disclosed and any consent required by applicable law should be obtained before non-essential tracking begins.

Where consent is required, non-essential technologies should remain inactive until a valid choice has been made. Visitors should also have a reasonable way to revisit or change that choice.

The production policy should identify the providers, purposes and retention periods in use. Nördia does not list hypothetical tools or cookie categories that are not present on the live service.

A consent interface should reflect the categories and providers present on the website. It should not ask visitors to agree to vague future tracking simply because a generic template supports additional categories.

Where consent is required, the visitor's choice should be recorded and the relevant technology should not be enabled until the applicable condition has been met.

Web infrastructure may create technical logs for security, diagnostics, abuse prevention and service operation. Those records serve a different purpose from behavioural advertising or campaign profiling, even though both may involve technical identifiers.

The policy and consent model should distinguish operational necessity from optional analytics or marketing use.

Video players, maps, chat tools, payment widgets or other embedded third-party interfaces may set or read browser storage as part of their normal operation. Their behaviour should be considered before they are included rather than discovered after deployment.

Where an embedded service is optional, the website can defer loading it until the appropriate choice has been made.

Cookie documentation becomes misleading when it is copied from a template and never checked against the live website. Providers, names, purposes and retention periods can change through ordinary releases.

The production configuration should therefore be reviewed whenever the published cookie information is updated.