Cookie Richtlinie

Last updated: 8 July 2026

Overview

This Cookie Policy explains how AssetObserve uses cookies, local storage, session storage, and similar technologies on the public website and SaaS platform. It should be read together with the Privacy Policy.

What cookies and similar technologies do

Cookies are small files stored on a device. Similar technologies, including local storage and session storage, can store or access information on a device without using a traditional cookie. These technologies can support login sessions, security, preferences, language, product settings, analytics, payment flows, and integrations.

Current default approach

AssetObserve should use only strictly necessary or user-requested storage by default. Non-essential analytics, marketing, advertising, heatmap, replay, or cross-site tracking tools should not be enabled unless they are listed in this policy, blocked until valid consent where required, and supported by a consent mechanism that allows users to accept, reject, and later withdraw consent as easily as it was given.

Strictly necessary technologies

We may use strictly necessary cookies and storage to provide login sessions, authentication, fraud and abuse prevention, security, load balancing, payment checkout, account registration, contact forms, support forms, scan workflows, and requested workspace features. These technologies are required to provide the service and cannot be disabled through our consent tools, although browser settings may still block them and may break the service.

Preference technologies

We may use first-party storage to remember choices requested by the user, such as theme preference, sidebar state, language selection, dismissed notifications, cookie choices, or similar interface preferences.

Analytics technologies

If analytics are enabled, they should be used to understand product usage, diagnose performance, and improve the website and service. Analytics that are not strictly necessary will be used only where legally permitted and, where required, after consent. Analytics should be configured to minimize personal data where practical.

Marketing technologies

If marketing, advertising, retargeting, social media pixels, affiliate tracking, or similar technologies are enabled, they will be disclosed here and used only where legally permitted and, where required, after consent. AssetObserve should not use sensitive-data profiling or targeted advertising to children.

Third-party technologies

Third-party providers may set cookies or similar technologies when you use payment checkout, single sign-on, embedded support tools, video content, analytics, monitoring, or other integrations. Their use is governed by their own notices and contracts. We aim to limit third-party technologies to what is necessary for the requested feature or validly consented purpose.

Technologies we expect to use

• assetobserve_session: first-party session cookie used for login and authenticated SaaS access; category: strictly necessary; typical duration: up to the configured session period or logout.
• assetobserve_theme: first-party local storage used to remember a user-selected light or dark theme; category: preference; duration: until cleared by the user.
• assetobserve_sidebar_collapsed: first-party local storage used to remember workspace sidebar layout; category: preference; duration: until cleared by the user.
• assetobserve_workspace_notifications_seen: first-party local storage used to remember dismissed workspace notifications; category: preference or service functionality; duration: until cleared or overwritten.
• assetobserve_admin_notifications_seen: first-party local storage used to remember dismissed admin notifications; category: preference or service functionality; duration: until cleared or overwritten.
• Payment provider cookies: third-party cookies that may be used during checkout or fraud prevention; category: strictly necessary for payment where checkout is requested; duration: set by the provider.
• Identity provider cookies: third-party cookies that may be used during Google, Microsoft, Apple, or other single sign-on flows; category: strictly necessary for requested authentication; duration: set by the provider.
• Optional analytics cookies: only if enabled and disclosed in the admin/legal configuration; category: analytics; duration: provider-specific.
• Optional marketing cookies: only if enabled and disclosed in the admin/legal configuration; category: marketing; duration: provider-specific.

Consent

Where consent is required, we will ask before setting non-essential cookies or similar technologies. Consent must be freely given, specific, informed, and unambiguous. Rejecting non-essential technologies should not prevent access to the service unless the technology is strictly necessary for the feature requested by the user.

How to manage choices

If a cookie banner or preference center is available, you can change your choices there. You can also block or delete cookies and storage through your browser settings. Blocking strictly necessary technologies may prevent login, checkout, security checks, or other requested features from working.

Browser and device controls

Most browsers allow users to delete cookies, block third-party cookies, clear local storage, or restrict tracking. Some browsers and devices also offer privacy signals. We will honor legally binding signals where required by applicable law and technically feasible.

Changes to this policy

We may update this Cookie Policy when we add, remove, or change cookies, storage, providers, purposes, retention periods, or consent mechanisms. Material changes should be reflected before new non-essential technologies are deployed.

Contact

Questions about cookies or similar technologies can be sent to contact@assetobserve.com.

Placeholder notice

Before launch, verify the actual cookies, local storage keys, payment providers, identity providers, analytics tools, marketing tools, consent banner behavior, retention periods, and regional cookie-law requirements. Do not enable non-essential tracking until the implementation matches this policy.