Guard cookies and browser storage policy
Cookie and client-side storage schedules, lawful purposes, consent, retention, and withdrawal for Guard.
Last revised: October 23, 2026
This Cookies and Browser Storage Policy ("Policy") applies to the Guard application, its account-access surfaces, and any public service surfaces operated by Solarius B.V. in connection with Guard. It shall be read together with the Privacy Policy. In the event that browser-stored information constitutes personal data, the applicable data-protection requirements shall apply in addition to the rules governing access to terminal equipment.
Scope and interpretation
Solarius shall determine any exemption from consent separately from the lawful basis for processing personal data. An identifier's first-party origin, technical convenience, or security-related label shall not establish an exemption for an additional purpose. If a mechanism serves multiple purposes, any purpose requiring consent shall remain inactive until valid consent for that purpose has been obtained.
For purposes of this Policy, "Cookies" means small records placed in a browser and returned to the relevant service in accordance with their scope. "Local Storage" means information retained by the browser for the relevant origin across browsing sessions. "Session Storage" means information retained for the relevant tab or browsing session. These terms also encompass an equivalent technology when it performs the same stated function; the use of an alternative mechanism shall not avoid the consent, purpose, or retention limitations herein.
The schedules specify the purposes and maximum lifetimes applicable to service-issued state. A lifetime is a maximum, subject to earlier sign-out, revocation, withdrawal, expiry of the associated authorization, or user deletion. Replacement following an affirmative preference change or renewed authentication can begin a new applicable period. Optional identifiers shall not be silently renewed merely to circumvent a stated expiry.
Strictly necessary authentication and security cookies
The service uses the following authentication and request-security records:
| Name | Purpose and information retained | Maximum lifetime | Access and restrictions |
|---|---|---|---|
__Host-guard_session | Opaque identifier for the authenticated session; the account and role relationship is resolved by the service | 8 hours after issue or authorized renewal, subject to a shorter organization session policy | Secure, HttpOnly, SameSite=Lax, host-only, Path=/; no password or recovery secret in the value |
__Host-guard_csrf | Random anti-forgery value binding a state-changing browser request to the relevant session | Browser session; invalidated on sign-out or session expiry | Secure, SameSite=Lax, host-only, Path=/; made available only to the application flow that must submit the token |
__Host-guard_auth_state | Short-lived state and nonce for a user-initiated authentication or identity-provider callback | 10 minutes; consumed or invalidated when the authentication attempt ends | Secure, HttpOnly, SameSite=Lax, host-only, Path=/; no marketing or cross-site profiling purpose |
guard_privacy_choice | Optional-processing selections, choice timestamp, and version of the applicable preference notice | 12 months, unless the user changes or clears the choice earlier | First-party, Secure, SameSite=Lax; used solely to apply and demonstrate the recorded choice |
Necessary security state shall be used only to provide or protect the service requested by the user. It shall not be repurposed for advertising, general browsing surveillance, or optional product measurement. Consent is not relied upon where a lawful strict-necessity exemption applies; that exemption shall be assessed by reference to the requested function rather than the convenience of a particular implementation.
Authentication expiry might occur earlier on inactivity, organization policy, sign-out, account restriction, or security revocation. A remembered preference shall not extend an authenticated session or preserve a revoked authorization. The existence of a Cookie shall not be treated as proof of the holder's continuing authority over an organization or resource.
User-requested preferences and application storage
The following records preserve the corresponding user-selected preferences:
| Identifier | Mechanism | Stated purpose | Maximum retention |
|---|---|---|---|
guard_workspace | Cookie | Last organization and authorized asset-group view selected by the user | 30 days |
guard_locale | Cookie | Selected language and regional formatting | 12 months |
guard.appearance | Local storage | Selected color scheme and display density | 12 months |
guard.triage.layout | Local storage | Detection-table columns, panel arrangement, and sorting preferences | 90 days |
guard.investigation.range | Local storage | User-selected event time-range preference | 30 days |
guard.response.form | Session storage | Unsaved response-form selections, excluding execution credentials and raw evidence | Until the tab or browser session ends |
Preference storage shall be created only in connection with the corresponding user choice. Where applicable law requires consent for a preference mechanism that is not strictly necessary to the requested function, that mechanism shall remain disabled unless such consent has been obtained. Selection of an appearance or layout option shall not constitute consent to analytics or advertising.
Local Storage does not attach to each HTTP request in the manner of a Cookie, but information in it can be accessible to scripts operating within the relevant origin. Access shall accordingly be limited by the service's security controls and the browser's origin boundary. Application-managed expiry shall remove or disregard a local preference once its stated period expires; a browser might retain inaccessible remnants until its own cleanup takes place. Session Storage might survive a browser's session-recovery feature. Do not use it as a secure vault.
Threat artifacts, quarantined files, employee-content captures, scan credentials, evidence packages, private keys, and SOC collaboration payloads shall not be retained in preference or optional-measurement storage. Client-side form state shall not constitute approval of a response action, evidence preservation, or proof of execution; those matters shall be established by the authorized service records.
Optional product measurement
The following measurement identifier requires opt-in:
| Identifier | Mechanism | Purpose | Maximum lifetime and activation |
|---|---|---|---|
guard_diagnostic_metrics | First-party Cookie | Opt-in interface-error and performance measurement, excluding endpoint telemetry, traffic payloads, employee identifiers, detection narratives, and evidence | 7 days; disabled by default and issued only after opt-in |
Optional measurement shall be limited to the stated reliability and product-improvement purpose. It shall not track the user across unrelated services, incorporate customer content, identify people for advertising, or be disclosed for cross-context behavioral advertising. A random identifier remains personal data where a person or device can reasonably be singled out; it shall not be represented as anonymous solely because it excludes a name.
Rejecting optional measurement shall not prevent access to the purchased service or lower its essential security protections. No optional identifier shall be placed before the applicable affirmative choice. If a measurement activity requires an external provider or materially different category of information, Solarius shall provide the corresponding notice and obtain any required authorization before activation.
Consent, withdrawal, and browser controls
The application Cookie preferences control shall provide Accept optional, Reject optional, and Manage preferences choices with equivalent practical accessibility. Optional categories shall not be preselected. The user can reopen Cookie preferences from the application footer and withdraw an optional selection as readily as it was given. Withdrawal shall prevent further optional collection and invalidate the corresponding identifier, subject to retention of the minimal record needed to honor the choice or satisfy a legal obligation.
Consent shall be specific to the relevant purpose and browser context. Continuing to use the service, accepting the Terms, confirming an operational subscription, or granting browser-notification permission shall not constitute consent to optional tracking. Solarius shall honor any legally applicable universal opt-out signal for the activity to which that signal relates.
Users can also remove Cookies and site data through browser settings. Such removal can end a session, clear preferences, or require a choice to be recorded again. It shall not, without a separate authorized instruction, cancel the subscription, erase server-side business records, or constitute an organization-closure request. Shared-device users should sign out and remove locally retained state when required by their organization's device policy.
Identity providers, notifications, and external surfaces
An identity provider, payment service, or other independent destination selected by the user can place its own state under its own origin and notice. Authorization to complete that flow shall not confer permission for unrelated tracking. Any external embedded content requiring consent shall remain inactive until the applicable choice has been obtained.
Browser push subscriptions and service-worker delivery records, when enabled by the user, exist to route requested operational notices and are separate from optional measurement Cookies. Permission can be revoked through the browser's site-permission controls. Subscriber confirmation, component preferences, and unsubscribe instructions remain governed by the product's notification rules and the Privacy Policy; none authorizes use of a destination for unrelated marketing.
For a self-hosted deployment, the deployment operator is responsible for any independent proxy, identity integration, plugin, or modification it adds. Renamed identifiers or additional technologies must be disclosed accurately for that deployment. Such additions shall not be attributed to Solarius merely because they operate alongside the supplied application.
Inquiries and amendments
Privacy inquiries and requests concerning browser-stored personal information can be submitted to dpo@solarius.me. Solarius shall provide information sufficient to identify the relevant mechanism and exercise applicable rights, subject to appropriate verification and security limitations.
Material additions to purposes, recipients, or optional mechanisms shall be disclosed before activation, with renewed consent where required. An amendment to this Policy shall not retroactively validate prior collection or broaden an existing consent beyond the purpose for which it was obtained.