Skip to content

Cookies and browser storage

The application uses browser storage for sign-in and requested functions. This page describes the storage mechanisms actually used.

Last updated: 16 September 2026

1. Legal bases

Storage of or access to information on your device is governed by section 25 of the German TDDDG. Without consent, it is permitted only where a statutory exception applies, particularly where strictly necessary to provide a service you expressly request. Legitimate interest alone does not replace required consent. Subsequent processing of personal data also requires a GDPR legal basis.

The application does not use Google Analytics or advertising cookies, so there is no control for those trackers. Continuing to browse is not consent. Any future technologies requiring consent must wait for your active agreement.

2. Sign-in

Supabase stores the account session in Local Storage under a project-specific name following the pattern sb-…-auth-token. Some sign-in methods may temporarily add an associated code-verifier. These data support signed-in use and session renewal. They remain until sign-out, removal by the application or deletion of site data in the browser; the validity of individual access tokens is separate from this storage duration.

3. Language and drafts

The language you choose can be stored in Local Storage as i18nextLng. In the public e-label viewer, language is held only in memory for the current page.

The public generator saves your entered draft as vinum.playground.wine so it is available when you return. If you request saving through an email sign-in link, the draft is also temporarily stored as vinum.pendingWine for transfer to your account. Transfer data are removed after successful import. Local Storage has no fixed automatic expiry; you can delete saved drafts through your browser’s site-data settings.

4. Error references

After a technical error outside the public e-label viewer, vinum:last-failure may be saved in Session Storage. It contains a support reference, error category, broad page category, version and time, not messages or form contents. This storage ends with the relevant browser session.

5. Abuse protection and payment

Selected account forms load Cloudflare Turnstile for security checks. The privacy notice describes the browser information processed. Stripe’s payment page and customer portal open only when you request them; Stripe uses its own payment and fraud-prevention technologies there. See the linked provider information for details.

6. Managing storage

You can inspect and delete stored data or block storage in your browser settings. You may then need to sign in again or re-enter drafts and preferences. Public e-labels require neither sign-in nor persistent browser storage by the application.

Contact

Service provider
lekuhe Invest GmbH
Torstraße 105
10119 Berlin
Deutschland
Managing director
Leonhard Kühne-Hellmessen