Skip to main content
KungoraKungora

Cookie Policy

Version 1.0.0, in force from 8 October 2026

The public site (kungora.com), the newsrooms of Kungora, their feeds and the widgets set no cookies at all and read none.

When you sign in to the dashboard (app.kungora.com)

NamePurposeLifetimeWhen
__Host-better-auth.session_tokenKeeps you signed in.7 days (renewed while in use)When you are signed in
__Host-better-auth.session_data*Short-lived signed copy of your session to avoid a database lookup on every request.5 minutesOnly when you use the function
__Host-better-auth.dont_rememberEnds your session when the browser closes if you did not choose "remember me".Browser sessionWhen you are signed in
__Host-better-auth.two_factorRemembers that your password was accepted while you complete two-factor sign-in.10 minutesWhen you are signed in
__Host-better-auth.trust_deviceSkips the two-factor step on this device, only when you tick "trust this device".30 daysOnly when you use the function
__Host-better-auth.better-auth-passkeyHolds the one-time challenge while you register or use a passkey.5 minutesWhen you are signed in
__Host-pcLets you manage your email subscriptions after opening a link from one of our emails.1 hourOnly when you use the function

In our staff console (our own staff only)

NamePurposeLifetimeWhen
__Host-staff.session_tokenKeeps you signed in.8 hoursWhen you are signed in
__Host-staff.session_data*Short-lived signed copy of your session to avoid a database lookup on every request.5 minutesOnly when you use the function
__Host-staff.dont_rememberEnds your session when the browser closes if you did not choose "remember me".Browser sessionWhen you are signed in
__Host-staff.two_factorRemembers that your password was accepted while you complete two-factor sign-in.10 minutesWhen you are signed in
__Host-staff.trust_deviceSkips the two-factor step on this device, only when you tick "trust this device".30 daysOnly when you use the function
__Host-staff.better-auth-passkeyHolds the one-time challenge while you register or use a passkey.5 minutesWhen you are signed in

All cookies are first-party, HTTP-only and sent over encrypted connections. A name marked with * can be split into several cookies with a number at the end when the value is large.

1. Summary

Kungora uses no cookies for statistics, marketing or tracking. The public website kungora.com and all newsrooms, on our domain or on organisations’ own domains, set no cookies at all. Cookies are used only when you sign in, and then only those necessary for the service to work. That is why we show no box asking you to consent to cookies.

2. What cookies are

A cookie is a small text file that a website saves in your browser. Under Chapter 9, section 28 of the Swedish Electronic Communications Act (2022:482), information may be stored in or read from your device only with your consent, except where it is necessary to provide a service you have explicitly requested. The same rules apply to similar techniques, for example local storage in the browser.

3. Public pages without cookies

3.1 No cookies and no local storage

Our public pages, newsrooms, feeds and widgets set no cookies and store nothing in the browser’s local storage.

3.2 Statistics without cookies

We count visits without storing anything in your browser and without storing your IP address. How this works is described in clause 3.2 of the Privacy Policy. If your browser signals that you do not want to be tracked (Do Not Track or Global Privacy Control), no statistics are sent at all.

3.3 Protection against bots

Forms on public pages, for example for following a newsroom or reporting content, are protected by a check computed in your browser. The check stores no cookies.

4. Cookies when you are signed in

4.1 Which services set cookies

Cookies are set only by the sign-in service and the account for organisations and journalists, by the page where you manage your email preferences and by our staff tools. All of them are necessary for you to sign in and stay signed in, or to protect the sign-in.

4.2 List

The list of each cookie, its purpose and how long it is kept is shown on this page. It is generated automatically from the same source the service uses, and an automated test stops any change that would set a cookie missing from the list.

5. Content from other websites

5.1 Embedded players

Organisations can embed video and audio from YouTube, Vimeo, Dailymotion and SoundCloud in their publications. When a page with such a player is shown, nothing is loaded from the provider, not even a preview image. Instead we show our own panel with a play button and a note that the player is fetched from the provider only when you play it (on the media page of a video, the panel can carry a preview image that we host ourselves). Only when you click the button is the player loaded from the provider, which may then receive your IP address and store or read information in your browser under its own terms. If you do not click, nothing is sent to the provider. We use the options that collect the least data: YouTube is shown in privacy-enhanced mode and Vimeo with a do-not-track request. Without JavaScript the panel is a link that opens the provider’s own page, where the provider’s rules apply. The providers are themselves responsible for their processing.

The preview of a draft, which a signed-in author or anyone who has been given a preview link sees, loads the player at once, without a click.

5.2 Links

If you follow a link to another website, that website’s cookie rules apply.

6. Email

Emails from the service may contain a small image that shows whether the email is opened, and links that go through us so that we can count clicks. These are not cookies, but the technique is similar. For followers and subscribers we report only totals. Organisations can see opens and clicks per recipient for their own contacts, and the email footer then says so. You can avoid this by not showing images in the email.

7. How to manage cookies

You can delete cookies and block them in your browser settings. If you block the sign-in cookies, you cannot sign in.

8. Changes

If we ever want to use cookies that are not necessary, we will first ask for your consent, with equally clear buttons to accept and decline, and update this policy.

9. Contact

Send questions about cookies to dpo@kungora.com.

SHA-256 of the text: 80f04a72fcf1c3f24e039af98c1f9f9252e82cac83919bba3996800850224361

Version 1.0.0 as JSON