Skip to main content

Cookie policy

Version 1.1. Last updated 20 October 2026.

This policy explains every cookie and every piece of browser storage QuickISO uses. It is short because there is little to explain, and that is deliberate.

The public site sets no cookies

quickiso.app and its language versions set no cookies at all. They load no third party scripts, no third party fonts, no advertising pixels and no analytics product. There is no consent banner because there is nothing to consent to, and a banner asking permission for nothing would be theatre.

Visits are counted on our own server without a cookie. Each page load records the page address, its language, the message variant, the domain of the referring site and the campaign tag, together with a visitor identifier derived from the visiting address and a salt that exists only in memory and is replaced every day. The salt is never written down, so yesterday's identifiers cannot be linked to today's, and none of them can be turned back into an address.

The application sets five, all strictly necessary

Signing in requires cookies. These five are necessary to provide a service you asked for, which is the exception in article 400 of the Polish Electronic Communications Law, so they do not require consent. Refusing them means you cannot sign in.

CookieWhat it doesLifetimeSameSite
qi_sessionKeeps you signed in8 hoursLax
qi_preauthCarries a step that is not finished: between your password or Google and your two factor code, a registration through Google waiting for you to accept the terms, or a sign in while your account is scheduled for deletion15 minutesStrict
qi_inviteCarries an invitation between opening the link and accepting it1 hourStrict
qi_ssoTies a sign in through company single sign on or Google to the browser that started it, so that an answer arriving in another browser is refused10 minutesLax
qi_driveTies the connection of a workspace's Google Drive to the browser of the person who started it10 minutesStrict

qi_session and qi_sso are Lax because they must come back with a link from another site: the link in an email for the first, and the provider sending you back after you signed in there for the second. The others never need to.

All five:

  • are HttpOnly, so page scripts cannot read them;
  • are host-only, with no Domain attribute, so they are never sent to a subdomain;
  • carry the __Host- prefix and the Secure flag over https, which means a browser will refuse the cookie if either of those conditions is not met;
  • are set with Path=/ and expire on their own.

Signing out deletes the session cookie immediately.

Browser storage

The application stores your interface theme (light or dark) in your browser's local storage. It never leaves your device and reaches no server.

The small calculation your browser solves before an email sign up, described in the privacy policy, runs in the page's memory and stores nothing.

The mobile app

The QuickISO app for iPhone and Android uses no cookies. What it keeps on the phone, your sign in and any answer waiting to be sent, is described in section 3.6 of the privacy policy.

Third parties

None set cookies through QuickISO. Cloudflare sits in front of the service as a network provider; it may set a cookie of its own for security purposes on its own responsibility.

When you choose to sign in with Google, your browser goes to Google's own page, and any cookie it sets there is Google's, under its own policy. QuickISO's pages load nothing from Google.

Changes

A new cookie, or a change of purpose for an existing one, is published here before it is set.

Questions about this policy go to [email protected].

Version history

VersionDateWhat changed
1.019 September 2026First version
1.11 October 2026qi_sso and qi_drive added, which the application already set; qi_preauth also carries a registration through Google or Apple and a sign in during the deletion window; the mobile app and the sign in providers described; a contact address
1.1, revised20 October 2026Signing in with Apple removed from qi_preauth, qi_sso and the section on sign in providers, because QuickISO does not offer it