Cookies and local storage

Last updated:

What this is about

For ucando to work, the application has to keep some information on your device — your login session, your language choice and your personal settings, for example. This page lists every one of those items.

We use no advertising or tracking technologies that recognise you, neither in the application nor on our websites: no ad networks, no analytics cookies and no embedded third-party content. We count visits to our public websites without cookies and without storing anything on your device; how that works and how to switch it off is described below under "Audience measurement without cookies". Our emails contain a counting pixel from our email provider that records opens and clicks as totals only, without linking them to you; details are in the privacy notice.

The legal framework

The relevant provision is § 25 TDDDG. Under it, any storing of information on your device and any access to it requires consent — regardless of whether the mechanism is technically a cookie, local storage, session storage or something else.

Exempt from that requirement, under § 25(2) no. 2 TDDDG, is whatever is strictly necessary for us to provide the service you have expressly requested. Every entry listed below falls under that exemption.

Independently of this, we inform you about the processing pursuant to Art. 13 GDPR — which is what this page is for.

Complete overview

The list below is generated directly from the inventory the application itself maintains, grouped by storage mechanism.

Cookies

Sent to our server with every request.

NamePurposeRetentionNecessary
NEXT_LOCALEStores your chosen display language so the application is served in the right language from the very first page load.1 yearYes
sidebar_stateRemembers whether the sidebar is expanded or collapsed.7 daysYes
orbit_measurement_optoutRemembers that you objected to the audience measurement. Only set when you switch the measurement off.1 yearYes

Local storage

Stay in the browser and are not sent along automatically like cookies. The application itself sends individual entries where they are needed – your login token with every request, for example.

NamePurposeRetentionNecessary
oidc.user:… / oidc.…Login session: access token and the cryptographic protection of the sign-in flow. Signing in is not possible without this entry.Until you sign outYes
orbit:rolesCache of your role and permissions, so that what you are allowed to see does not have to be requested again on every page change.2 hoursYes
orbit-personalizationYour personal settings, such as language, token-usage display and your opt-in to long-term memory.Until you clear your browser dataYes
orbit:upload-hashesChecksums of files already uploaded, so the same file is not transferred and charged twice.Until you clear your browser dataYes
orbit:pwa-install-dismissedRemembers that you dismissed the prompt to install the app, so it does not reappear.Until you clear your browser dataYes
orbit:free-trial-welcome-seenRemembers that you have already been shown the welcome note about the free allowance.Until you clear your browser dataYes

Session storage

Stay in the browser and are deleted when the tab is closed.

NamePurposeRetentionNecessary
orbit:returnToRemembers the page you were on during sign-in, so you can carry on where you left off.Until the tab is closedYes
orbit:signingOutMarks a sign-out in progress so the redirects do not end in a loop.Until the tab is closedYes

Audience measurement without cookies

We count the views of our public websites with Pirsch Analytics. Nothing is stored on your device and nothing is read from it: your browser requests the page from us, and our server passes on the details of that request. Details are in the "Audience measurement on our websites" section of the privacy notice.

If you do not want to be counted, switch the measurement off here for this browser. We remember that in a cookie that holds nothing but this decision; it is listed in the overview above. If your browser sends "Global Privacy Control" or "Do Not Track", we do not count your visits anyway.

Why there is no cookie banner

A consent banner is required where a website stores information on your device, or reads it from there, that is not necessary for the service — typically for advertising or to recognise you across websites. That does not happen here; our audience measurement, too, works without access to your device.

Showing you a banner anyway would mean asking for consent to something that does not require consent. We deliberately decided against it and are instead disclosing the basis for that decision here.

Should we introduce non-essential technologies in future, we will put a consent mechanism in place beforehand, and such technologies will only load once you have agreed.

Third-party services

Fonts and icons are served from our own servers; no content is loaded from external content delivery networks.

Signing in goes through ZITADEL, our identity provider. ZITADEL sets its own cookies on its own domain, not on ucando's; its privacy notice applies.

Payments are handled by Stripe. You are redirected to a page operated by Stripe, to which their own privacy notice applies.

Which other providers are involved in the processing is set out on the "Service providers" page. None of those services stores anything on your device while you use ucando.

How to control this

You can delete any of the listed items at any time through your browser settings. Because all of them are necessary for operation, doing so may mean you have to sign in again and that your personal settings are reset.

Session storage entries are deleted automatically as soon as you close the browser tab.