Cookie Policy

1. Scope

This Cookie Policy explains cookies, local storage and similar technologies used by LogisticsAI. It should be read with the Privacy Notice. The operator identified in the Legal Notice is responsible for the consent interface.

2. Your choice

Non-essential technologies are off by default. On the first visit, you can reject non-essential technologies, accept all, or choose categories. Reject and accept are offered at the same level. You can withdraw or change your choice at any time through Cookie preferences in the footer. Withdrawal does not affect processing that occurred before withdrawal.

The consent choice is stored locally for up to six months and then requested again. Clearing browser storage may cause the banner to reappear sooner.

3. Strictly necessary storage

Necessary storage cannot be disabled through the banner because it is required to provide a requested service, maintain authentication, protect sessions, apply rate limits, remember locale or theme, and record the consent choice.

• Supabase authentication cookies: maintain a signed-in session and refresh authentication; duration is session-based or follows the configured authentication lifetime
• cookie_consent in localStorage: records necessary, analytics and support choices, consent version and expiry; maximum duration six months
• locale preference in localStorage and a first-party cookie: remembers the requested interface language for up to one year; theme in localStorage remains until changed or cleared
• guest_token: HttpOnly first-party cookie that reconnects a requested guest workflow for up to seven days
• guest_sync_session: HttpOnly first-party cookie used for a requested guest-to-account transfer for up to one hour
• logisticsai_wizard_draft and lgsai_rating_shown in localStorage: preserve an unfinished upload workflow or avoid repeating a rating prompt until the workflow completes or browser storage is cleared

4. Optional analytics

If analytics is enabled, PostHog receives product events such as page views and feature usage, and Google Ads may receive advertising attribution and a completed lead-conversion event with a non-personal deduplication identifier. We do not send form contents or direct contact details to Google Ads, and enhanced conversions are disabled for this implementation. These providers may use browser storage and identifiers according to their service configuration. Disabling analytics stops new optional captures and updates Google consent signals to denied.

Vercel Web Analytics may process limited, aggregated and cookie-less request information to measure site traffic. It does not set third-party cookies for this purpose. Technical error diagnostics from Sentry are limited to reliability and security purposes; session replay is disabled.

5. Optional support chat

If support is enabled, Crisp loads the chat widget and may store a session identifier, chat content and related technical data. Do not place sensitive or unnecessary personal data in chat. Disabling support hides the widget and resets its local session where technically available; Crisp may retain prior support records for the period necessary to handle the conversation and legal obligations.

6. Browser controls

Browser controls can block or delete cookies and local storage, but blocking necessary storage may prevent login or requested functionality. Browser privacy signals do not replace the visible category controls unless applicable law or supported technology requires otherwise.

7. Changes and contact

Providers, purposes and durations may change as the service evolves. Material changes will update this Policy and, where required, trigger a new consent request. Privacy contact details are in the Legal Notice.