Cybereinforce logo

Cybereinforce Threat Enforcement

Legal & policy information
Cookie Policy

Cookie policy for the Cybereinforce website and platform.

This version gives proper detail about necessary cookies, analytics, browser storage, Azure-hosted services, and how your own cookie consent mechanism should behave.

Public legal page
Written for Cybereinforce services
Review with legal counsel before publishing
01

What This Cookie Policy Covers

Purpose of this page

This Cookie Policy explains how Cybereinforce uses cookies, local storage, similar browser technologies, and third-party services on its public website, customer portal, and related web properties.

Because Cybereinforce operates security and login-protected services, some technically necessary storage items are used to keep sessions secure, maintain authentication, and remember privacy choices.

02

Types of Technologies We May Use

Cookies, storage, and related identifiers
Technology Purpose Category
Session cookies Keep authenticated users logged in securely and protect account-related requests. Necessary
Preference cookies Remember language, cookie choices, or interface preferences. Preferences
Analytics cookies or scripts Help understand page usage, navigation behaviour, and performance trends. Analytics
Local storage May store privacy choices, UI settings, or temporary browser-side state. Browser storage
Not every technology listed above is always active. Some are used only if you enable them, or only in authenticated sections of the site.
03

Strictly Necessary Cookies

Items required for secure operation

These cookies or storage mechanisms are required for the website and portal to function correctly. They may be used for login sessions, security validation, fraud prevention, load distribution, or storing the fact that a user has already made a cookie choice.

  • Authentication session cookies used by the hosting and identity stack
  • Security-related request validation and session protection
  • Cookie-consent status storage so the banner does not reappear after a valid choice
  • Basic operational storage required to deliver protected customer pages

Strictly necessary cookies do not require prior consent where applicable law allows their use because they are essential to provide the website or the service explicitly requested by the user.

04

Analytics and Measurement

How site usage may be measured

Cybereinforce may use analytics tools, including tools such as Google Analytics, to understand which pages are visited, how visitors navigate the site, which devices are commonly used, and how the public website can be improved.

  • Analytics scripts are intended to run only after a visitor has granted analytics consent.
  • Analytics data may include IP-derived location approximations, browser type, operating system, pages visited, time on page, and referral source.
  • Cybereinforce may configure analytics features to reduce identifiable data where appropriate.
If you choose Reject optional cookies, analytics scripts should not be loaded by the consent banner logic.
05

Third-Party Services and Sharing

Who may receive information

Cybereinforce may use Microsoft Azure and related cloud services to host websites, authenticate users, deliver application pages, or operate APIs. In addition, analytics or monitoring providers may process technical information if the relevant cookie category has been accepted.

Microsoft / Azure

Hosting, identity, static app operation, routing, and platform-level diagnostic functions may involve Microsoft infrastructure.

Google Analytics

If enabled by consent, measurement data may be processed by Google for traffic and usage analysis.

Third-party providers may process technical metadata such as IP address, browser, device type, page views, timestamps, referring URL, and cookie identifiers according to their own service role and applicable agreements.

06

Cookie Duration and Retention

How long browser-side items may remain
Category Typical duration Example
Session cookies Until browser closes or session expires Login and session-security cookies
Preference cookies From a few days up to 12 months Remembering consent or language choice
Analytics cookies Varies by provider settings Traffic and behaviour measurement
Local storage entries Until removed by the user or application logic Consent state or UI preference storage
07

How Users Can Manage Cookies

Control options
  • Use the cookie banner shown on first visit to accept or reject optional cookies.
  • Reopen cookie settings through a footer link or privacy settings control added to the website.
  • Delete cookies directly in the browser settings.
  • Block or restrict third-party cookies in the browser where supported.

Please note that blocking necessary cookies may impair login functions, account security, or general website operation.

09

Changes to This Policy

Updates and revisions

Cybereinforce may update this Cookie Policy from time to time to reflect changes in technology, legal requirements, site structure, or third-party services used.

Questions About Cookies or Tracking

If you have questions about cookie usage, consent settings, or third-party technologies used on the Cybereinforce website, contact Cybeurope directly.