Cookie Policy

1. What are cookies and similar technologies?

Cookies are small text files stored through your browser on your device. Modern web applications also use other local storage mechanisms such as Session Storage, Local Storage, IndexedDB and comparable browser functions.

In this policy, the term cookies is used as a general label for these technologies where they are used to recognise the browser, maintain sessions, store technical state, retain preferences or preserve local working data.

2. Why Betabace uses them

Betabace is an interactive web application rather than a static website. Features such as login, maps, route drafts, upload flows, editor state and account preferences would not work reliably without technically necessary browser storage.

• maintaining login and session status
• storing language and preference settings
• preserving route draft and editor state locally in the browser
• ensuring technical stability, form handling and consistent navigation
• maintaining temporary state during authentication, maps or payment flows

3. Categories currently used

Betabace currently relies primarily on technically necessary cookies and functional browser storage. This includes session and security information for authentication, as well as functional storage used for local drafts, editor state and language preferences.

Where you actively use third-party functionality such as OAuth sign-in, checkout, map search or 3D map services, those providers may also use their own technically required storage mechanisms.

At the current product stage, Betabace does not operate a separate classic analytics or advertising cookie stack comparable to a dedicated marketing analytics installation. If that changes, this policy and any consent interface will be updated accordingly.

4. Examples from the current product state

• session and sign-in information for authenticated users
• language preferences for English or German rendering
• local storage of route drafts in the browser
• editor-related temporary data and larger working objects via Local Storage or IndexedDB
• technical state used during OAuth redirects, payment flows or service-specific dialogs

In the route and editor areas, the current implementation may store both small metadata and larger temporary working data locally in the browser so that editing progress is not lost immediately when the interface changes.

5. Third-party services

When you use certain features, third-party providers may set their own cookies or similar technical storage depending on the service and device involved.

• Supabase for authentication, session handling and backend functions
• Stripe for checkout, billing portal and subscription processing
• Google Maps Platform for places, maps, 3D and tiles-related features
• Mapbox for map and geo data rendering
• OAuth providers such as Google, Apple and Facebook when you sign in through those services

The exact cookies or storage items used by those providers depend on the service called, your device and your provider-specific settings.

6. Legal basis

Technically necessary cookies and comparable storage mechanisms are used on the basis of Article 6(1)(f) GDPR and the national rules applicable to strictly necessary access to terminal device storage. Our legitimate interest lies in the secure and functional provision of the platform.

If optional consent-based technologies are introduced in the future, they will only be activated after the required consent has been obtained.

7. Retention periods

The duration of storage depends on the underlying technology and purpose. Some data is needed only for the active session and disappears when the session ends. Other local data remains stored until you remove it, your browser clears it or the application overwrites it.

• session data typically until sign-out or end of session
• functional preferences until changed or cleared
• local drafts and editor state until removed through browser tools or overwritten inside the application

8. Management and deletion

You can delete, block or restrict browser cookies through your browser settings. Please note that doing so may impair or fully disable parts of Betabace.

Data stored through Local Storage or IndexedDB can usually be removed through your browser's site-data tools. This may delete drafts, editor state or convenience settings.