Cookie Policy

This Cookie Policy explains how Actualog (“we”, “us”, “our”) uses cookies and similar technologies (for example local storage, session storage, SDK/device identifiers, and pixels) when you visit our websites and use the Actualog B2B SaaS platform (the “Services”).

This policy should be read together with our Privacy Policy and Terms of Service.

1) Hosting / infrastructure

Hosting / infrastructure: Actualog is hosted in Microsoft Azure. We may use Azure-native services (eg. load balancing, security controls, monitoring) that require technical identifiers to operate the platform securely and reliably.

2) What cookies are

Cookies are small text files stored on your device by your browser. They are commonly used to:

• keep you signed in,
• protect the platform from abuse,
• remember preferences (language, theme),
• help us understand how the platform performs.

Similar technologies (local storage and device identifiers) can provide comparable functionality.

Cookies and similar technologies may qualify as online identifiers because they can be linked to a browser/device and (in some cases) an account.

3) Why we use cookies

Actualog uses cookies and similar technologies for the purposes below. Some are strictly necessary for the service you request (for example secure sign-in). Others are optional and used only when allowed by your settings and applicable law.

A) Strictly necessary (Essential)

These are required for the Services to work securely and reliably.

Typical uses:

• authentication and secure session management,
• security controls (anti-forgery/CSRF, request integrity, fraud prevention),
• load balancing and infrastructure reliability,
• saving critical application state required for navigation.

Under EU-style cookie rules, storing/accessing information on a user’s device generally requires consent, with an exception for cookies that are strictly necessary to provide a service explicitly requested by the user.

B) Preferences (Functional)

These remember your choices and improve usability.

Typical uses:

• UI language selection,
• theme / appearance preferences (Dark / Light),
• remembering dismissed banners and view modes.

C) Analytics (Performance)

These help us understand usage patterns and platform performance so we can improve reliability and user experience.

Typical uses:

• aggregated usage statistics (feature adoption, page flows),
• diagnostics and performance telemetry,
• error monitoring.

Where required, we use analytics cookies only after you have provided consent (or enabled analytics in your cookie preferences). Cookie banner practices and consent expectations (eg. clear choice, no “consent by default”) are actively enforced by EU/EEA regulators. :contentReference[oaicite:1]

D) Third-party services (Security and Sign-in)

Some features use third-party providers that may set their own cookies or identifiers.

Typical uses:

• CAPTCHA / anti-abuse protections on registration or sign-in,
• external identity providers (enterprise/social sign-in),
• embedded content you choose to interact with (if used).

Third parties act under their own policies. We recommend reviewing their cookie/privacy documentation when you use those features.

4) Legal basis and consent (high-level)

Cookie rules vary by jurisdiction, but the common structure is:

• Essential cookies: permitted because they are required for the service you request (eg. secure sign-in).
• Optional cookies (preferences/analytics/marketing where applicable): used only when you have provided consent or enabled them in a preference center, where required by law.
• UK context: the UK has a similar “terminal equipment” framework, including statutory exemptions for certain purposes and evolving guidance on exceptions.

Actualog does not use “pre-ticked boxes” or “implied consent” patterns where consent is required; consent must be a clear affirmative choice, and you must be able to change your mind later (withdraw consent as easily as you gave it).

5) Cookie inventory (what we set)

We maintain an internal cookie inventory and update it as the platform evolves.

Below is an example structure (replace with your real cookie list from production):

Important: If you block essential cookies, sign-in and secure navigation may not work.

6) Managing cookies (your choices)

A) Cookie preferences (if available)

If we present a cookie banner or preference center, you can:

• accept or reject optional cookies,
• change your choices later.

B) Browser controls

Most browsers let you:

• delete existing cookies,
• block cookies,
• block third-party cookies,
• set per-site rules.

C) “Do Not Track”

Some browsers offer “Do Not Track”. Actualog may not respond to all DNT signals consistently because implementations differ and the signal is not a uniform legal standard.

7) Retention

Cookies can be:

• Session cookies (deleted when you close your browser), or
• Persistent cookies (kept for a defined period).

We keep cookies only as long as necessary for their purpose, and we review retention periodically as the platform evolves. Guidance from EU regulators typically expects proportionate retention and purpose limitation (especially for analytics). :contentReference[oaicite:6]

8) International transfers and service providers

Because Actualog is hosted in Azure and may use global service providers, cookie-related identifiers (and related telemetry) may be processed in countries outside your own. When required, we implement appropriate safeguards (for example contractual protections and access controls) consistent with our Privacy Policy.

9) Updates to this policy

We may update this Cookie Policy to reflect platform improvements, new security measures, and regulatory changes. The newest version is published on this page with the updated “Last updated” date.