Cookie Policy

Note: The German version of this document is the legally binding version. This English text is provided for convenience only.

Last updated: May 13, 2026

1. Scope

This Cookie Policy explains how Ride Assignment uses cookies and similar browser-side storage mechanisms.

Ride Assignment uses browser-side storage for strictly necessary service functions, optionally consented preference storage inside the authenticated application, and optionally consented analytics and client-side error tracking through PostHog.

2. What We Use

Ride Assignment currently uses the following cookies and similar browser-side storage mechanisms:

• locale

Stores the selected language for localized routes and server-side rendering.

• site_access

Used only when preview password protection is enabled. Stores a signed access token after the shared preview password has been accepted.

• ride_assign_cookie_consent

Stores the current cookie consent selection after the user has made a choice. This cookie records whether preference storage and analytics storage are enabled or disabled.

• ride_assign_cookie_consent_id

Stores a pseudonymous consent subject identifier after the user has made a choice. The identifier is used so that the recorded consent or rejection can be linked to the consent ledger stored by Ride Assignment.

• sidebar_state

Stores whether the left application sidebar is open or collapsed. This cookie is only written if the user has consented to the preferences category.

• sidebar_right_state

Stores whether the right application sidebar is open or collapsed. This cookie is only written if the user has consented to the preferences category.

• selected_event_id

Stores the last selected project inside the authenticated application. This cookie is only written if the user has consented to the preferences category.

• drivers_table_sorting

Stores the current sorting state of the drivers table. This cookie is only written if the user has consented to the preferences category.

• passengers_table_sorting

Stores the current sorting state of the passengers table. This cookie is only written if the user has consented to the preferences category.

• ph_phc_<project_token>_posthog

PostHog browser cookie used only after consent to the analytics category. It stores a pseudonymous distinct identifier, session-related state, and related metadata used for web analytics, product analytics, and client-side error tracking.

• Supabase authentication or session cookies

Used to keep authenticated users signed in and to support server-side session handling. The exact cookie names can depend on Supabase SDK and project configuration.

Ride Assignment also uses limited browser local storage entries for interface preferences inside the authenticated app. These entries are written only if the user has consented to the preferences category. This currently includes:

• export-type

Stores the last selected export format.

• export-options

Stores the last selected export options.

• drivers-table-column-visibility

Stores the current column visibility preferences in the drivers table.

• passengers-table-column-visibility

Stores the current column visibility preferences in the passengers table.

3. Categories and Legal Basis

Ride Assignment distinguishes the following categories:

• Strictly necessary storage, such as language, authentication and session handling, preview access protection, and storing the user’s cookie decision. These mechanisms are used to provide the service requested by the user.
• Preference storage, such as sidebar state, selected project, table sorting, export options, and table column visibility. These mechanisms are used only after consent and only to preserve user-selected interface preferences.
• Analytics storage, currently implemented through PostHog. These mechanisms are used only after consent and only for web analytics, product analytics, and client-side error tracking.

Where cookies or similar storage are strictly necessary for the requested digital service, they are used on the basis of the applicable legal rules for providing the service, including the applicable ePrivacy rules and, where relevant, the corresponding GDPR legal bases for related personal-data processing.

Where preference storage or analytics storage is not strictly necessary, Ride Assignment stores or reads such information only after the user has granted consent. For the related personal-data processing, the legal basis is consent under Article 6(1)(a) GDPR. The user can reject non-essential storage, accept all, or choose categories separately.

4. Analytics and Error Tracking with PostHog

Ride Assignment initializes the PostHog browser SDK immediately in no-consent mode. If the user consents to the analytics category, PostHog is used for persistent:

• understanding page visits and navigation flows;
• understanding which product functions are used;
• measuring operational usage patterns in the web application; and
• capturing client-side exceptions and related browser error information.

PostHog is configured so that personal workspace content such as names, email addresses, phone numbers, addresses, coordinates, notes, CSV content, and route content is not intentionally sent to PostHog. Automatic session recording and autocapture of form or DOM content are not part of the intended PostHog use.

Before analytics consent is granted, Ride Assignment does not intentionally write the PostHog browser cookie or PostHog local/session storage. If the user rejects analytics, PostHog remains cookieless and may only perform privacy-preserving audience measurement without persistent browser identifiers.

5. Cookie Durations

Cookie durations are currently configured as follows:

• The locale cookie is stored for 365 days.
• The site_access cookie is stored for 365 days.
• The ride_assign_cookie_consent cookie is stored for 365 days after the user has made a choice.
• The ride_assign_cookie_consent_id cookie is stored for 365 days after the user has made a choice.
• Sidebar preference cookies and table-sorting cookies are stored for 7 days once the user has consented to the preferences category.
• The selected-project cookie is stored for 365 days once the user has consented to the preferences category.
• The PostHog browser cookie duration is determined by the active PostHog SDK configuration and is used only after consent to analytics has been granted.
• Authentication and session cookies may be session-based or persistent depending on Supabase authentication configuration.
• Local storage entries remain until they are deleted in the browser, overwritten by newer preferences, or cleared as part of site data removal.

6. Managing Choices

Users can reject non-essential storage, accept all categories, or choose categories separately through the cookie banner and the cookie settings dialog linked from the Cookie Policy page.

Users can change their selection at any time through the cookie settings dialog. If preference storage is disabled, the corresponding optional cookies and local storage entries are cleared. If analytics storage is disabled, persistent PostHog browser storage is disabled for subsequent page loads and PostHog remains in cookieless mode.

7. Browser Controls

Users can also manage or delete cookies through browser settings. Please note that disabling strictly necessary cookies may prevent Ride Assignment from working correctly, including login, localization, and protected preview access.

8. Contact

If you have questions about this Cookie Policy, contact support@ride-assign.com.