Slobal
Legal

Cookie policy

Effective 24 September 2026 · Last updated 6 November 2026 · Slobal, Ireland

slobal.com sets two cookies when you sign in, plus a third one for ten minutes while you sign in with another provider, two more when you open AgnCred, and keeps two preference keys in your browser storage. Every one of them is strictly necessary: it keeps you signed in, keeps the service secure, or remembers the theme and navigation state you chose. There is no cookie banner because there is nothing optional to ask about: no analytics, advertising or tracking cookies run on this site, and none are planned.

Key facts
Cookies set
Five: hmsly_id and hmsly_rt when you sign in, hmsly_pkce during a provider sign-in, and agncred_session and agncred_csrf when you open AgnCred
Browser storage keys
Two: slobal-theme and nav.*
Set on public pages before sign-in
Nothing
Analytics or tracking cookies
None
Consent banner
None needed and none shown: every entry is strictly necessary
CookiePurposeTypeExpiry
hmsly_id Keeps you signed in to your Slobal account and workspace. Strictly necessary, first party, HttpOnly, SameSite Lax, Secure Lasts up to 30 days, or until you sign out
hmsly_rt Renews your sign-in when the short session in hmsly_id ends, so you do not have to sign in again. Only slobal.com itself reads it. Strictly necessary, first party, HttpOnly, SameSite Lax, Secure Lasts up to 30 days, or until you sign out
hmsly_pkce Protects a sign-in with Google, Facebook, Apple, Microsoft or GitHub. It holds a one-time check value and nothing about you. Strictly necessary, first party, HttpOnly, SameSite Lax, Secure 10 minutes, set only during that sign-in
agncred_session Keeps you signed in to AgnCred under /agncred on this site. It identifies your AgnCred session and nothing else. Strictly necessary, first party, HttpOnly, SameSite Lax, Secure, path /agncred Lasts up to 24 hours, or until you sign out
agncred_csrf Protects AgnCred forms against cross-site request forgery. The AgnCred page reads it and sends it back with each change you make, so a request from another site cannot act as you. Strictly necessary, first party, readable by the AgnCred page, SameSite Lax, Secure, path /agncred Lasts up to 24 hours, with agncred_session

hmsly_id and hmsly_rt are set only once you sign in, and agncred_session and agncred_csrf only once you open AgnCred. They carry no tracking payload: they identify a session, not your behaviour on the site. Because they are strictly necessary for a feature you asked for, signing in, the GDPR and the ePrivacy Regulation do not require consent for them.

Browser storage keys

KeyPurposeTypeLifetime
slobal-theme Remembers the light or dark theme you chose. Strictly necessary preference, first party, localStorage Stays until you clear it
nav.* Remembers which navigation groups you opened or closed. Strictly necessary preference, first party, localStorage Stays until you clear it

These keys never leave your browser. We do not read them on our servers and no third party can read them. They are set only after you choose a theme or open or close a navigation group on the signed-in pages. The public pages set nothing before you sign in.

Why there is no consent banner

Consent is needed only for storage that is not strictly necessary. Every entry above is strictly necessary for a feature you asked for: the sign-in cookies keep you signed in and secure, the two AgnCred cookies keep you signed in to AgnCred and protect its forms, and the two preference keys keep the theme and navigation state you chose. Nothing else is stored, so there is nothing optional to ask about and no banner is shown.

What we do not set

Managing cookies

You can block or delete any of the cookies above in your browser's settings at any time. Deleting hmsly_id or hmsly_rt signs you out of this site, and with that out of AgnCred, because AgnCred under /agncred relies on your slobal.com sign-in. Deleting agncred_session or agncred_csrf signs you out of AgnCred only. Nothing else on this site is affected. You can clear the two storage keys in the same place, under site data. The theme and navigation state then return to their defaults.

This page states our cookie use plainly. For the full account of what Slobal collects and why, see the privacy policy. For what we store and where, see security. Our processors are listed at sub-processors.

Changes

When this policy changes, the date at the top changes with it. If we ever introduce a cookie beyond those described here that is not strictly necessary, this page is updated first and a consent banner is added before it is set.