Lionsa uses cookies that are necessary for secure account authentication. We do not currently use advertising, behavioural-tracking or optional analytics cookies.
1. About cookies
Cookies are small text records stored by a browser and returned with relevant web requests. They can keep a user signed in, protect a service, remember a requested setting or measure how a site is used. Similar technologies include browser session storage, which remains in one browser tab or session rather than being sent automatically with every request.
2. Our current use
Lionsa's account provider, Clerk, sets cookies when you sign in, sign up, restore or maintain an authenticated session. These cookies are necessary to provide the account and private search service you request, so they cannot be disabled through a Lionsa preference control.
Public marketing pages do not currently set Lionsa analytics or advertising cookies. For that reason, Lionsa does not currently display a consent banner that would offer choices which do not exist.
3. Necessary authentication and security cookies
| Cookie | Purpose | Typical duration |
|---|---|---|
__session | Provides a short-lived signed session token so Lionsa can recognise an authenticated request. | About 60 seconds, refreshed while the session remains active. |
__client and __client_uat | Allow Clerk to maintain and validate the signed-in browser session. | Controlled by the configured Clerk session and browser limits. |
__clerk_handshake | Temporarily completes a secure session refresh or authentication handshake. | Transient. |
_cfuvid | May be set by Clerk's traffic-security provider to distinguish legitimate requests and protect the service. | Determined by the security provider and browser. |
__clerk_db_jwt | Development-only cookie used to connect local testing with Clerk's development environment. | Development only; it is not part of the production cookie set. |
Exact cookie names or durations can change when Clerk improves its authentication or security service. We will update this notice if that materially changes how your information is used.
4. Similar browser storage
If a signed-out visitor starts a search and is then asked to sign in, Lionsa places the query and search mode in tab-scoped sessionStorage under lionsa.pending-search.v1. This lets the requested search resume after authentication without placing the query in a URL or sending it to Clerk.
The pending value is consumed and removed after sign-in, rejected after 15 minutes, and disappears when the browser clears that tab's session storage. Lionsa does not use local storage for advertising or cross-site tracking.
5. Consent and future changes
UK cookie rules allow storage that is strictly necessary to provide a service requested by the user without prior consent, although it must still be explained. If Lionsa later introduces optional analytics, personalisation, advertising or similar technologies, they must remain disabled until the required consent has been obtained. We would then add a clear preference control that makes rejecting optional cookies as easy as accepting them.
6. Your browser controls
You can inspect, block or delete cookies through your browser settings. Blocking necessary Clerk cookies will prevent sign-in and private account features from working. Disabling session storage may mean a search started before authentication cannot be resumed automatically, but you can enter it again after signing in.
7. Contact us
Questions about Lionsa's use of cookies or browser storage can be sent through the Contact Us page.