Cookies · zutpralik

1.We do not use cookies

zutpralik sets no cookies at all — not on this marketing site, and not inside the application. There is no session cookie, no preference cookie and no cookie of any other kind written by us.

There are also no analytics, no tracking pixels, no advertising tags, no session recording, no A/B testing tools and no third-party scripts. Nothing on these pages phones home to a marketing platform, because nothing on these pages comes from one.

2.What we do store in your browser

To keep you logged in, the application stores a small amount of data in your browser’s localStorage. Unlike a cookie, this is never transmitted automatically with every request — the application reads it and attaches the session token only to the API calls it makes on your behalf.

Key	What it holds	Why
`zutpralik.token`	Your session token	Strictly necessary: without it the API cannot authenticate a single request and you would be logged out on every page load.
`zutpralik.user`	Your own name, e-mail and role	Strictly necessary: lets the interface render the right navigation immediately, without a round trip.
`zutpralik.originalSession` `zutpralik.impersonator` `zutpralik.impersonationScope`	Only present for a platform administrator during a “view as user” session	Strictly necessary for that feature: shows the warning banner and provides a reliable way back to the administrator’s own account. Every such session is also written to an audit log.

That is the complete list. All of it is written by the application itself, is readable only by this site, and is removed when you log out or clear your browser storage. Nothing here is used to profile you, and none of it is shared with anyone.

3.Why there is no consent banner

Under Article 5(3) of the ePrivacy Directive — and the national laws implementing it — consent is required before storing information on a user’s device or accessing information already stored there, except where the storage is strictly necessary to provide a service the user has explicitly requested.

Everything listed in section 2 falls squarely inside that exemption: it exists only to keep you logged into the application you asked to log into. We store nothing for analytics, nothing for advertising and nothing for measurement. So there is nothing to ask you to consent to.

If we ever introduce analytics or any non-essential storage, we will ask for your consent before setting it, offer a genuine refusal, and update this page first.

4.Third parties in the request path

Traffic to zutpralik.click passes through Cloudflare, which acts as our CDN and terminates TLS. Cloudflare is the only third party in the path between your browser and our server. We do not use Cloudflare Web Analytics or any other analytics product, and we run no Cloudflare feature that profiles visitors for marketing purposes.

If a CDN-level security or bot-protection mechanism ever needs to set a strictly necessary cookie to keep the service available, that is exempt from consent for the same reason as the storage above — and we would list it in section 2 rather than leave you to find it in your developer tools.

What Cloudflare does with data in transit, and the transfer safeguards that apply, are described in the Privacy Policy.

5.Your control, and how to reach us

You can clear the stored session at any time by logging out, or by clearing site data for zutpralik.click in your browser settings. Doing so simply logs you out; nothing else is affected, because nothing else is stored.

Questions about this page, or a discrepancy between what it says and what you observe in your browser? Tell us at [[CONTACT_EMAIL]] — we would want to know.