Cookies on plauso.appLast changed 7 October 2026
Cookies
Plauso sets no tracking cookies. What is left is the ones needed to sign you in and connect your systems, and two short ones that get the page into the right language. Here is exactly what they are, what else is kept in your browser, and why none of it needs us to ask first.
DraftThis text has not been reviewed by a lawyer.
We wrote it ourselves, as plainly as we could, and it describes how Plauso works today. But no lawyer has read it, and we are not going to pretend otherwise. If you see something that does not match how the service actually works, we want to know: write to support@plauso.app.
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.
Seven of them belong to signing in and connecting systems. 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 are 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. kopplingar_oauth does the same as konto_oauth when you connect Fortnox or Spiris to your account, and gbp_oauth when you connect your Business Profile. admin_session is the sign-in for us who run Plauso. If you ask to sign in or connect a system, this is what it consists of. Without them there is nothing 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 are 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 |
| kopplingar_oauth | Keeps a connection you started to Fortnox or Spiris tied to your account, until you are back from there. | 10 minutes | No |
| gbp_oauth | Keeps a connection you started to your Business Profile tied to your account and this browser, until you are back from there. | 10 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 |
| plauso_inne | That you are signed in, so the header shows Go to account instead of Get started. Carries nothing about who you are. | 30 days | Yes |
| plauso_meny | Whether the account's side menu is wide or narrow, so it is drawn right straight away. | 365 days | 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
These are created by something you do in the service and are read only by the page. None of it reaches us by itself, only when you send the form it belongs to. So the same exemption applies as for the cookies above.
- 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.signup.v1: what you have filled in during sign-up, so a reload does not cost you everything. It lives in the tab, disappears when you close it, and is not used after an hour.
- plauso.svar.v1: existed before October 2026 and held the signature and contact route you typed in the reply assistant. If it is still in your browser, Plauso moves its contents to your AI reply settings the first time you open AI replies, and then removes it.
- 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.
- plauso.guide.…: whether the getting-started guide in your account is collapsed, and that its closing card has been shown. It lives in the tab and disappears when you close it.
- plauso-app-later: that you pressed Not now on the card about installing the app, so it stays out of the way for 30 days.
- plauso:applad: that the applause in the header has already played during the visit, so it plays once. It lives in the tab and disappears when you close it.
- plauso.erbjudande.…: which offers in the account's side menu you have closed, with one key per account. It stays until you clear your browser.
- plauso:affisch-pris: the latest price you saw for printed posters, so a change can be shown. It stays until you clear your browser.
- plauso:affisch-firad: that you have already been congratulated on your first poster order. It stays until you clear your browser.
- plauso:provet-sista:…: that the card about the trial's last day has already been shown, so it shows once. It stays until you clear your browser.
- plauso.kalender.vy: which view you last chose in the calendar (day, week, month or list). It stays until you clear your browser.
- plauso.dela.v1: the review you chose to share, on its way from the reviews to the Share page. It is removed as soon as the Share page has read it, and otherwise stays in the tab until you close it.
The app and notifications
When you open the Plauso app, or turn notifications on, a small script is registered in your browser, a so-called service worker. It shows the notifications and a page of its own when you have no connection. It stores nothing from the account: no pages, no customers, no images.
When you turn notifications on, your browser asks you first, and that answer is your consent. The browser then creates an address for the device with its push service, and we store that address together with two keys, so that notifications can be encrypted for your device alone. How to turn them off is further down.
Links, signs and websites
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.
The link in a text or email from you sets no cookie either. It carries a random code with no personal data in it, and all we note is that it was opened and when, so the customer is spared the reminder. Previews in messaging apps and email scanners are not counted.
Business websites hosted by Plauso set no cookies and measure no visits. The review button you can put on your own website sets none either; a press on it counts as a click on the short link, just like a scan.
Getting rid of them
You delete cookies and other storage 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.
You turn notifications off under Settings in your account, in your phone's or browser's settings, or by removing the app.
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.