blitz.cloud cookie policy
Which cookies blitz.cloud sets, which of them need your consent, how long they last and how to change your choice.
This page lists the cookies and the browser storage blitz.cloud uses: on the website blitz.cloud, in the dashboard at dashboard.blitz.cloud and at sign-in on login.blitz.cloud. It is the short version of sections 3 and 4 of the privacy policy, which names the legal bases and the providers. If the two differ, the privacy policy applies.
What a cookie is
A cookie is a small text file a website stores in your browser. With it the site recognises the browser again, for example to keep you signed in. Local storage does a similar job for settings that stay on your device.
Your choice
Most cookies here are needed for blitz.cloud to work and are set without asking. Two kinds are only set if you agree in the consent dialog: the statistics cookies and the advertising cookies.
You can change or withdraw your choice at any time with effect for the future: on the website through "Cookie settings" in the footer, in the dashboard under Settings.
Cookies that need your consent
Statistics
We count visits to blitz.cloud and the dashboard with Matomo, which we run ourselves. The count works without cookies and without access to your device. Only if you allow statistics cookies in the consent dialog does Matomo also set the cookies _pk_id (13 months) and _pk_ses (30 minutes) to recognise returning visits. They are deleted when you withdraw your consent.
Advertising
On the free plan the dashboard shows one ad through Google AdSense. On Pro there is no ad. The blitz.cloud website includes Google's script so Google can review the site.
Third party vendors, including Google, use cookies to serve ads based on a user's prior visits to this website or other websites. Google and its partners only set or read such cookies and similar identifiers on blitz.cloud and in the dashboard if you agree in the consent dialog. Which providers these are, what they use the data for and how long they keep their cookies is listed in the consent dialog.
If you do not agree, we tell Google so. Google then shows, where it can, only non-personalised or limited ads and sets no advertising cookies for them. You can also turn off personalised advertising from Google in Google's Ads Settings, and from many other providers at www.aboutads.info and www.youronlinechoices.eu.
Cookies that are needed
These are technically necessary and are set without consent:
| Where | Name | What for | How long |
|---|---|---|---|
| dashboard.blitz.cloud | __Host-blitz_session (split across numbered cookies when needed) | Keeps you signed in | until you close the browser or sign out |
| dashboard.blitz.cloud | blitz_state, blitz_verifier, blitz_next | Secure the sign-in and remember where to go afterwards | 10 minutes |
| dashboard.blitz.cloud | gh_return | Remembers which page to return to when you connect GitHub | 30 minutes |
| dashboard.blitz.cloud | blitz_ref | Remembers the invite code when you arrive through another customer's invite link, until your account is created | 7 days |
| login.blitz.cloud | Cookies of the sign-in software Keycloak, such as AUTH_SESSION_ID, KEYCLOAK_IDENTITY, KEYCLOAK_SESSION | Sign-in and session | the session, at most as long as the sign-in |
| all addresses | Cookies of Cloudflare, whose network every request passes through | Protection from automated traffic | short, as stated by Cloudflare |
| blitz.cloud and every address under it | __lxG__consent__v2, __lxG__consent__v2_daisybit and __lxG__consent__v2_gdaisybit from Clickio, FCCDCF from Google, as cookies and in local storage | Store your choice in the consent dialog | 13 months |
Your choice in the consent dialog applies to every address under blitz.cloud. Our customers' apps run under those addresses too and can therefore read these cookies. They hold only your choice.
Browser storage
In your browser's local storage we also keep: your choice in the consent dialog, whether you want a light or dark look, an unsent draft in the wizard for new apps, small notes such as "this tip was already seen", whether you are signed in to the dashboard, and the code from an invite link. These entries stay on your device. Except for the invite code, which goes to us with sign-up, they are not sent to us, and you can delete them in your browser's settings.
Cookies in our customers' apps
The apps that customers run on blitz.cloud set their own cookies, and this page does not cover them. We do not measure these apps with Matomo and show no ads from us in them.
Questions
Write to hallo@blitzworks.io. More ways to reach us are on the contact page.