Cookies on plauso.appLast changed 16 September 2026
Cookies
Plauso sets no tracking cookies. What is left is the ones needed to sign you in, and two short ones that get the page into the right language. Here is exactly what they are, and why each of them may exist without us asking.
DraftThis text will be reviewed by a lawyer before launch.
We wrote it ourselves, as plainly as we could, and it describes how Plauso actually works today. But it has not been read by a lawyer, and we are not going to pretend otherwise. The review happens before the service launches for real.
Short version
We do not measure you, do not advertise at you, and share nothing about your visit with anyone. There is no analytics, no ad pixel and no tracking network on this site.
So you get no consent banner. Showing a toggle where you can “decline” cookies that are required to sign in would be a fake choice, and we are not doing that. This page is the notice instead.
Why they need no consent
Swedish and EU rules require your consent before anything is stored on your device — except when the storage is needed to deliver a service you have expressly asked for. That is the only ground we rely on, so here is every row of the table below, one by one.
Five of them are the sign-in. konto_session keeps you signed in. konto_kod ties the code we email to the browser that asked for it, so a forwarded email cannot sign anyone else in. konto_oauth holds a sign-in you started with Google or BankID together with this browser until you come back from there — without it there is no way to tell that the same browser is the one returning. konto_oauth_klar carries an identity that has already been proven, for the minutes it takes you to type your email address, and after BankID it carries a hash of your personal identity number, never the number. admin_session is the same thing for us who run Plauso. If you ask to sign in, this is what a sign-in consists of — without them there is no sign-in left to consent to.
The last two are about language. plauso_sprak is your own choice and exists only so we stop asking. plauso_land carries the country code our server already read from your request on to the page, so the language question can be asked once in the browser; it lives for twelve hours and holds two letters. It says nothing about what you looked at, does not follow you to any other site, and never leaves plauso.app. We count it as part of showing you the page in a language you read — but it is the cookie closest to the line, and we would rather say so than hide it.
The cookies that exist
| Cookie | What it does | How long | Readable by page scripts? |
|---|---|---|---|
| konto_session | Keeps you signed in to your account. | 30 days | No |
| konto_kod | Ties the login code to the browser that asked for it, so a forwarded email cannot sign anyone in. | 15 minutes | No |
| konto_oauth | Holds a sign-in you started with Google or BankID together with this browser, until you come back from there. | 10 minutes | No |
| konto_oauth_klar | An identity Google or BankID has already proven, while we ask for your email address. It never carries your personal identity number. | 15 minutes | No |
| plauso_sprak | Your language choice, so we stop asking. | 180 days | Yes |
| plauso_land | The country code our server read, so we can offer the right language. | 12 hours | Yes |
| admin_session | Sign-in for us who run Plauso. Never set for a visitor. | 14 days | No |
Stored in the browser, but not cookies
- plauso:name — the business name you type on the home page, so it carries over to sign-up. It lives in the tab and disappears when you close it.
- plauso:gbp:… — the ticks in the Google profile guide inside your account, so you can see where you got to. It stays in your browser until you clear it, and never reaches us.
- plauso.review.… — that you have already been asked whether you want to leave a review of Plauso, with one key per account so a shared computer asks the right person. It stays in your browser until you clear it.
- plauso.celebrated — which milestones in your account you have already been congratulated on, so the same card does not turn up again. It lives in the tab and disappears when you close it.
- plauso.celebrated.session — that a congratulation has already been shown during this visit, so several milestones at once do not become several cards in a row. It lives in the tab and disappears when you close it.
The short link and the QR code
When someone scans your sign, no cookie is set at all. The visitor is sent on to your profile and we only count the clicks for that day and channel. No IP address is stored, and we do not tell the platform where the click came from.
Getting rid of them
You delete cookies in your browser settings, and these pages need none to be read. Block all cookies, though, and signing in stops working: the code we email belongs together with the cookie that says which browser asked for it.
If this changes
If we ever want to measure visits, we will ask first — for real, with a choice you can decline without anything breaking. Until then, nothing is here beyond what is already written.