Cookies and local storage

1. Current approach

Vidense uses Plausible for cookieless aggregate audience and campaign measurement. Google Ads conversion measurement is optional and remains disabled until you actively consent through the displayed banner.

2. Required authentication storage

Supabase sets technically necessary session information so sign-in, security refresh and protected account areas work. The number and content of cookie fragments may vary technically. A session is generally designed for up to 30 days and may end earlier on logout or expiry.

For the free browser analyses, we also set a random, technically necessary first-party device identifier (vidense_intro_device) for up to 365 days. It is used only to enforce the free allowance across new sessions, not for advertising.

3. Temporary upload preview

For a locally generated upload preview, the browser may store an image in the current tab's sessionStorage. It is used only for the immediate display and is discarded by the browser when the tab is closed; a new selection may overwrite it sooner.

4. Cloudflare Turnstile

During registration, login, password recovery and use of the contact or cancellation form, Cloudflare Turnstile may process technical information or necessary device signals to prevent automated abuse. It is used for security, not advertising or cross-service Vidense tracking.

5. Optional Google Ads conversion measurement

After consent, Vidense loads the Google tag to attribute a confirmed subscription purchase to a preceding Google ad and optimise campaigns for purchases. Google may set or read first-party advertising cookies such as identifiers in the _gcl_* family and process the complete page URL including ad-click parameters, IP address and browser/connection information.

For a confirmed subscription purchase, Vidense sends the purchase value, currency and an opaque analytics-outbox UUID as the transaction ID. Names, email addresses, account IDs and payment-card details are not included. Enhanced Conversions and advertising personalisation are not enabled.

The choice is stored in localStorage under vidense.google_ads_consent.v2. After consent, vidense.registration_attribution.v1 in this tab's sessionStorage holds entry page, referral domain and permitted campaign/click parameters for optional registration attribution (up to 24 hours; on the server up to 90 days until regular cleanup). You can withdraw through 'Cookie settings' in the footer; this removes local attribution, stops new collection and requests deletion of stored attribution while signed in or on the next sign-in. Withdrawal also prevents future Google Ads tag use by Vidense; browser controls can additionally remove previously stored site data.

6. Legal basis and controls

Required storage and access are necessary to provide the digital service expressly requested by the user under section 25(2)(2) of the German TDDDG. Google Ads measurement is based on consent and remains disabled without it. Subsequent personal-data processing uses the legal bases described in the Privacy Policy.

Browsers allow users to clear or block cookies and site data. Without required session storage, sign-in and protected areas will not work reliably.