Cookie Policy

Cookies are small text files stored by your browser when you visit a website. Similar technologies may include local storage objects, pixel tags, SDK identifiers, and server-side session tokens that support equivalent technical functions.

These technologies help systems recognize sessions, preserve preferences, maintain secure authentication states, and measure feature behavior over time. Some are required for core functionality, while others are optional and controlled through consent settings.

We organize cookies into categories so users can make informed choices: strictly necessary, functional, analytics/performance, and marketing where applicable. Each category has a distinct legal basis and user-control expectation depending on local requirements.

Category labels may appear in cookie banners, preference centers, or policy notices. If classification changes due to product updates or regulatory guidance, we update this policy and consent controls accordingly.

Strictly necessary cookies enable core operations such as sign-in, session continuity, security protections, fraud prevention, and account-request routing. Without these cookies, essential parts of the platform cannot function safely or reliably.

Because they are required for service operation, strictly necessary cookies are generally enabled by default and cannot be disabled through optional preference controls. Users may still remove them through browser settings, but that can break login and critical workflows.

Functional cookies remember user-selected settings such as language, display preferences, and interface behavior that improve usability across sessions. They reduce repeated setup effort and help provide a consistent experience for returning users.

These cookies do not typically track broad advertising profiles. Where consent is required in your jurisdiction, functional cookies may be activated only after user approval, unless a specific function is required to deliver an explicitly requested service.

Analytics cookies help us understand feature usage patterns, navigation flow, and aggregate performance trends. This supports reliability improvements, user experience refinement, and product planning based on observed behavior rather than assumptions.

Where feasible, analytics data is aggregated, pseudonymized, and retention-limited. We avoid collecting unnecessary personally identifiable details in analytics pipelines and apply access controls to reports and dashboards used by internal teams.

Performance cookies and related diagnostics can capture timing, error frequency, and delivery metrics to support incident response and scalability planning. They help engineering teams identify regressions and improve page load consistency under real usage conditions.

These measurements are focused on service quality, not individual profiling. Retention windows are set to the minimum useful period for troubleshooting and trend analysis, after which records are deleted or summarized.

F-Løsning keeps marketing cookies limited. If marketing technologies are used, they are disclosed in consent controls and this policy, with clear options to decline before activation where legally required.

Marketing cookies can measure campaign effectiveness and communication relevance, but they are never required for core product access. Declining marketing cookies does not prevent use of essential service features.

Where consent is required, we present a cookie banner or preference panel that allows users to accept all, reject non-essential categories, or configure category-level choices. Consent records are stored to demonstrate compliance and prevent repetitive prompts after a valid choice.

Users may withdraw or modify consent at any time through available preference controls. Consent withdrawal applies prospectively; it does not retroactively erase processing already performed on a valid legal basis before the updated choice was recorded.

Most browsers allow users to review, block, or delete cookies through privacy settings. Device-level controls may also limit tracking technologies depending on operating system and browser configuration.

Blocking all cookies can interfere with authentication, session persistence, and other critical workflows. Users should evaluate browser-level controls carefully and combine them with in-app preference settings for predictable behavior.

Some cookies expire at the end of a browser session, while others remain for a defined period to preserve settings, maintain security state, or support analytics continuity. Retention duration depends on function, legal basis, and technical necessity.

We periodically review cookie lifetimes and remove or shorten retention where practical. Expired cookies are automatically cleared by the browser or replaced according to updated policy and consent preferences.

Certain service components may rely on third-party providers for infrastructure, analytics, monitoring, or embedded features. These providers may set cookies or similar identifiers when their services are loaded, subject to their own contractual and legal obligations.

We aim to use reputable providers with strong security and privacy controls. Customers with strict compliance requirements can request additional information about subprocessors and supported technical restrictions through support channels.

Some browsers offer "Do Not Track" or similar signals, and some jurisdictions recognize browser-based global privacy control mechanisms. Where legally required and technically feasible, we evaluate and honor recognized preference signals for non-essential processing.

Because standards are still evolving, behavior may differ by browser, jurisdiction, and technical environment. We recommend using both browser controls and in-product consent tools to ensure your intended privacy settings are applied.

We may update this Cookie Policy when technologies change, provider relationships evolve, legal standards are revised, or product architecture is updated. Material changes are communicated through visible notices and updated policy publication.

The date shown on this page indicates the latest revision. Continued use of the service after an update means the revised policy applies, subject to additional consent prompts where required by law.

If you have questions about our cookie usage, consent logic, or privacy controls, contact us through your organization support channel or by email at support@flosning.dk. Include your organization name and environment details so we can route your request quickly.

For broader data protection matters beyond cookies, refer to our Privacy Policy. If a conflict appears between these documents, we interpret them together and apply the stricter privacy-protective approach where legally appropriate.