blitz.cloudPricing
EnglishEN
Sign inPut your app onlineStart

blitz.cloud cookie policy

Which cookies blitz.cloud sets, what each one is for and how long it lasts. All of them are needed for the service to work, so there is nothing to consent to.

Updated

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.

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.

blitz.cloud only sets cookies it needs to work. The one thing we ask about is Google's quick sign-in on the website and the sign-in page (Google One Tap): Google's script only loads if you allow it in our small card, and you can turn it off again at the bottom of every page or under the sign-in form. The privacy policy says what Google learns then. We show no ads anywhere, and we count visits with Matomo, which we run ourselves, without cookies and without anything stored on your device.

Until 8 November 2026 the website showed ads through Google AdSense and asked for consent in Google's dialog. If you allowed it then, these may still be in your browser: Google's FCCDCF, Matomo's _pk_id and _pk_ses, and from the dashboard blitz_sk, blitz_from and blitz_consent. None of them is written or read anymore. Matomo and the dashboard delete theirs when they find them, and you can delete the rest in your browser's settings.

Cookies that are needed

These are technically necessary, so they are set without asking:

WhereNameWhat forHow long
dashboard.blitz.cloud__Host-blitz_session (split across numbered cookies when needed)Keeps you signed inuntil you close the browser or sign out
dashboard.blitz.cloudblitz_state, blitz_verifier, blitz_nextSecure the sign-in and remember where to go afterwards10 minutes
dashboard.blitz.cloudgh_returnRemembers which page to return to when you connect GitHub30 minutes
dashboard.blitz.cloudblitz_refRemembers the invite code when you arrive through another customer's invite link, until your account is created7 days
dashboard.blitz.cloudblitz_intentRemembers which store app or repository you came to deploy, or the plan you chose on the pricing page, until your account is set up7 days
dashboard.blitz.cloudblitz_signup_langRemembers the language of the page you signed up from, until your account is created7 days
dashboard.blitz.cloudblitz-langRemembers the language you chose in the dashboard1 year
blitz.cloud, login.blitz.cloudblitz_google_signinYour answer to whether Google may show its quick sign-in, set only when you answer1 year
login.blitz.cloud, dashboard.blitz.cloudblitz_last_signinRemembers how you signed in last time and with which email address, so the sign-in page can offer it first1 year
login.blitz.cloudCookies of the sign-in software Keycloak, such as AUTH_SESSION_ID, KEYCLOAK_IDENTITY, KEYCLOAK_SESSIONSign-in and sessionthe session, at most as long as the sign-in
all addressesCookies of Cloudflare, whose network every request passes throughProtection from automated trafficshort, as stated by Cloudflare

Browser storage

In your browser's local storage we also keep: 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. 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 in them.

Questions

Write to hallo@blitzworks.io. More ways to reach us are on the contact page.