Cookies, browser storage and similar technologies.

1. What these technologies are

A cookie is a small text file stored on a device by a website. Similar technologies include local storage, session storage, pixels, scripts, tags, software-development kits and device identifiers. UK privacy rules may apply when a website stores information on, or accesses information from, a visitor's device, even where the technology is not technically a cookie.

2. What this website currently uses

The current MNessa build does not intentionally set advertising or cross-site tracking cookies. It uses the following first-party browser-storage items:

The hosting or security provider may also use strictly necessary network or security mechanisms to deliver, protect and balance the website. If the selected host adds a visitor-facing storage item, this table will be updated to describe it.

3. Technology categories

• Strictly necessary: needed to provide a service requested by the visitor or protect and operate the website.
• Preferences or functionality: remember choices or adapt the website's appearance or behaviour.
• Statistics or analytics: help understand how the website performs and is used.
• Marketing: measure campaigns, build audiences, personalise advertising or track visitors across services.

A technology's name does not determine the legal rule by itself. MNessa will assess its purpose, operation, data use and whether a statutory exception applies.

4. Consent and legal exceptions

Where consent is legally required, MNessa will not activate the relevant technology before you choose it. The consent interface will provide clear and comparably prominent choices to accept or reject optional categories, allow granular preferences where appropriate and make withdrawal as easy as giving consent.

Consent is not required for every storage or access technology. UK law contains exceptions, including for technologies that are strictly necessary to provide a service requested by the user and, subject to legal conditions, certain security, functionality or statistical purposes. MNessa will rely on an exception only after checking that its conditions are met and will still provide appropriate information.

The current light/dark preference and session-based loader flag are used only to provide requested or expected website functionality. Because no optional tracking technology is currently enabled, the current build does not display a performative consent banner that has nothing meaningful to control.

5. Analytics, embeds and marketing added later

MNessa may later consider privacy-conscious analytics, performance monitoring, appointment tools, video embeds, chat, advertising measurement or social-media integrations. Before enabling any such service, MNessa should complete a deployment review covering:

• the exact cookies and similar technologies used;
• whether personal information is processed and by whom;
• the purpose, lawful basis and any PECR exception;
• whether the technology is blocked until consent where consent is required;
• retention periods and international transfers; and
• updates to this notice, the Privacy Notice and the on-page preference controls.

Third-party content may set technologies when loaded. Where appropriate, embedded content will be withheld behind a privacy-enhanced mode or consent choice until the visitor asks to load it.

6. How to control browser storage

You can delete or block cookies and site data through your browser settings. You can also clear local and session storage for this website. Blocking strictly necessary technologies may prevent parts of a website from working. Clearing mnessa-theme resets the saved theme choice; clearing the session closes or resets the loader preference.

When optional technologies are introduced, a Cookie preferences control should remain available from the footer so choices can be reviewed or withdrawn without searching browser settings.

7. Changes to this notice

This notice will be reviewed whenever website technologies, suppliers or legal guidance change. The version and date above identify the current published notice. The cookie table should always describe the live site, not merely technologies that might be installed later.