1. In short

Gnorium uses seven cookies: one that keeps you signed in, two that carry a registration for a day at most, two that carry a sign-in with Google for a few minutes, one that remembers whether you collapsed the sidebar, and one that tells Gnorium your browser's time zone when you filter by date or time. It also keeps a few display settings in your browser's local storage. There are no analytics, advertising or tracking cookies, and nothing is shared with advertisers.

Because every cookie Gnorium sets is either strictly necessary for something you ask for—filtering by your own days and hours is one—or remembers a setting you chose yourself, Gnorium doesn't show a cookie consent banner.

2. What cookies and local storage are

A cookie is a small piece of text a website asks your browser to keep and send back with later requests. Local storage is similar, but it stays in your browser: it isn't sent to the website with each request, and only the website's own pages can read it.

3. Cookies

• auth_token keeps you signed in. It is set when you sign in or register, and removed when you sign out; signing out also ends the session on our side, so a copy of the cookie no longer signs anyone in. It holds a signed token naming your account and your sign-in session by random identifiers (never your email address, username or role) and when your sign-in ends. Your browser's scripts can't read it, it is sent only over HTTPS, only to gnorium.com itself (never to another gnorium.com address), and it isn't sent with a form another website submits to Gnorium. Normally it lasts until you close your browser, and at most 24 hours. If you tick “Remember me”, and after you register or sign in with Google, it lasts 30 days.
• registration_email is set when you start registering with an email address, and removed when your account is created. It holds, encrypted so that only Gnorium can read it, the address the verification link went to, so the page can say where and send another. It is sent only to Gnorium's sign-in pages.
• registration_proof is set when you open the verification link, and removed when your account is created. It holds a random value proving you opened the link, which lets you choose your username and password, once, for 15 minutes. It is sent only to Gnorium's sign-in pages.
• oauth_flow is set when you choose “Continue with Google”, and removed when Google sends you back. It holds, encrypted so that only Gnorium can read it, a random value that proves the sign-in coming back from Google is the one you started, and a second one that Gnorium shows Google to finish it. It is sent only to Gnorium's sign-in pages.
• pending_signup is set the first time you continue with Google, while you choose a username, and removed when your account is created. It holds, encrypted so that only Gnorium can read it, what Google told us about you (your Google account identifier, email address, name, and whether Google verified the address). It is sent only to Gnorium's sign-in pages.
• gnorium-sidebar-collapsed remembers whether you collapsed the sidebar, so that pages open the way you left them. It is set only when you collapse or expand the sidebar.
• tz holds only your browser's time-zone name, such as America/New_York—nothing else. It is set only when you filter a list by date or time—when you pick a range of days or hours, or open a link that carries one—never when you simply read a page, so that “Today” and “Last 7 days” mean your own days. That makes it strictly necessary for a feature you asked for. It lasts a year. It isn't tracking: it can't tell you apart from anyone else in your time zone, it isn't used to follow you or count visitors, and Gnorium doesn't store it. Pages show dates and times in your own time zone without it, in your browser.

All seven cookies are first-party: they are set by gnorium.com and sent only to gnorium.com.

4. Local storage

Gnorium's pages keep these settings in your browser's local storage. They are never sent to Gnorium, and they stay until you clear your browser's site data.

5. Other websites

To display pages, your browser also loads code libraries from two content delivery networks, cdnjs (run by Cloudflare) and jsDelivr. They receive the usual information your browser sends with any request, such as your IP address, as the Privacy Policy explains. Gnorium sets no cookies for them. Links to other websites lead to sites with their own cookie policies.

6. Your choices

You can block or delete cookies and local storage in your browser's settings. If you block the auth_token cookie, you can still read Gnorium, but you can't sign in. If you block the tz cookie, date filters count days in UTC rather than your own. If you clear local storage, Gnorium forgets your display settings and goes back to its defaults.

Nothing in this policy limits rights you have under the mandatory law of the country you live in.

7. Changes and contact

If Gnorium starts using a cookie that isn't listed here, we will update this page and its date before we do, and ask for your consent first wherever the law requires it. For questions, write to info@gnorium.com. The Privacy Policy explains how we handle personal data generally.