Cookie Policy
kenn.pro keeps cookies to a minimum. We use them to sign you in and to keep you logged in across the network — not for advertising or third-party tracking.
What we use, and why
We don't use any advertising cookies, and we don't run third-party analytics or tracking pixels. The only cookies and local storage we set are these:
Strictly necessary — sign-in & sessions
Set by auth.kenn.pro on the .kenn.pro domain so a single sign-in works across every app on the network. These keep you logged in and run the login flow (the session cookie and the OIDC _session / _interaction cookies). They're essential — the service can't work without them — so they don't require consent. They're HttpOnly and expire automatically (within about 14 days of inactivity).
Device identifier (security)
A longer-lived cookie (kp_device, shared across .kenn.pro) gives each device a stable label. We use it solely for account security and session management — to show you the list of devices and sessions on your account, let you revoke them, and help us recognise your devices and spot suspicious sign-ins. It is not used for advertising, analytics, profiling or any kind of tracking, and it holds no personal profile — just an identifier.
Because it's used only to secure a service you've explicitly asked for (signing in), we treat it as a strictly-necessary security cookie. You can still clear it at any time (see below); doing so simply means your next sign-in is treated as a new device.
Local storage
During sign-in we briefly store the provider you chose (e.g. auth_provider) in your browser's local storage to complete the redirect. It's removed once you're signed in.
Cookies from sign-in providers
When you sign in with Google, Discord, GitHub, Steam or Patreon, that provider may set its own cookies on its own domain under its own policy. We don't control those — see the relevant provider's cookie policy.
Managing cookies
You can delete or block cookies in your browser settings at any time. Blocking the strictly-necessary sign-in cookies will stop you from logging in. Clearing the device-identifier cookie simply creates a new device entry next time. Signing out, or revoking a device from your profile, ends the related session.
Changes
If we change the cookies we use, we'll update the "updated" date above. See the Privacy Policy for how the related data is handled.
Questions? [email protected]