Cookie Policy

Cookie Policy

Effective date: 18 July 2026 Applies to: salieno.com

This Cookie Policy explains how Salieno uses cookies on salieno.com. It is short because our cookie use is small.

The short version: Salieno uses exactly one cookie — a strictly necessary, first-party session cookie that keeps you signed in to your account. We do not use analytics, advertising, performance, or third-party tracking cookies of any kind, and we do not sell or share your browsing behaviour with anyone.

1. What cookies are

A cookie is a small text file that a website asks your browser to store on your device. On each later request to that site, your browser sends the cookie back, which lets the site recognise your browser — for example, to keep you signed in from one page to the next.

Cookies can be:

• First-party — set by the website you are visiting (here, salieno.com). This is the only kind we use.
• Third-party — set by a different domain (for example, an ad network or analytics provider embedded in a page). We use none of these.

They can also be session cookies (tied to your signed-in session) or persistent cookies (kept until they expire or you delete them). We describe exactly what we use below.

Related technologies — such as localStorage, sessionStorage, web beacons, and tracking pixels — are covered by the spirit of this policy too. Salieno does not use them to track you.

2. The one cookie we use

Salieno sets a single cookie on salieno.com. It is strictly necessary: it exists only to keep you securely signed in to your Salieno account.

| Cookie | Purpose | Type | Retention | Security flags | |---|---|---|---|---| | __Host-salieno_web | Keeps you signed in to your Salieno account across pages on salieno.com | First-party · strictly necessary · authentication | Up to 90 days (see below); removed the moment you sign out | HttpOnly, Secure, SameSite=Lax, Path=/, __Host- prefix |

What the cookie stores

The cookie contains only an opaque, randomly generated session identifier — a string of random characters with no meaning outside our systems. It does not contain your name, email address, password, payment details, or any other personal information.

Your actual session data is held server-side, on our own infrastructure, and is looked up using that identifier. As an additional safeguard, we store only a one-way (SHA-256) hash of the identifier on the server, so the raw cookie value cannot be reconstructed from our records — and a copy of our server data alone never reveals a usable cookie.

The cookie is protected by industry-standard flags:

• `HttpOnly` — it cannot be read by JavaScript in the browser, which defends it against cross-site scripting (XSS) theft.
• `Secure` — it is only ever sent over encrypted HTTPS connections.
• `SameSite=Lax` and the `__Host-` prefix — it is bound to salieno.com over HTTPS at the root path with no cross-domain scope, which hardens it against cross-site request forgery (CSRF) and cookie-injection attacks.

How long it lasts

The cookie is a session cookie in purpose but is stored persistently, so that you are not forced to sign in on every visit. It ends at whichever of these comes first:

• 90 days after you sign in — an absolute limit that is never extended by activity; or
• 14 days of inactivity — the idle window is reset each time you use your account, up to that 90-day ceiling; or
• immediately when you sign out, at which point the server-side session is destroyed.

When the limit is reached, you are simply asked to sign in again.

Why it is essential and cannot be turned off

This cookie is the mechanism that keeps you signed in. Without it, your browser has no way to prove — on the page after you log in — that it is the same browser that just authenticated.

Because it is strictly necessary to deliver a service you have actively requested (access to your account), it is not subject to consent under cookie and e-privacy rules, and there is no option to disable it while using signed-in features. If you block or delete it, you can still browse the public pages of salieno.com, but you will not be able to sign in, view your account, or manage your licence and subscription.

3. Cookies and trackers we do NOT use

To be completely clear, on salieno.com we do not use:

• Analytics cookies (usage or audience-measurement tracking).
• Advertising or marketing cookies, retargeting pixels, or ad-network identifiers.
• Third-party tracking cookies of any kind.
• Social-media cookies or embedded "like / share" trackers.
• Cross-site or profiling cookies that follow you between websites.

We do not build advertising profiles, and we do not sell or share your personal data with data brokers or advertisers. Because our only cookie is strictly necessary, salieno.com does not show a cookie-consent banner — there is nothing optional to consent to.

4. Third-party services and payments

Salieno relies on a small number of trusted service providers (sub-processors) to run the service — currently a payment processor (Stripe), a transactional email provider, and infrastructure monitoring. None of these set cookies on salieno.com.

Payments are the one place you may encounter another company's cookies, and that happens off salieno.com:

• When you start a checkout, we send you to Stripe's own hosted payment page on Stripe's domain. Stripe may set its own cookies there — to operate the payment flow and to help prevent fraud — under Stripe's own privacy and cookie policies, not this one. We never see or store your full card number.

If you follow a link from salieno.com to any other website, that site's own cookie policy governs your visit there.

5. Do Not Track

Because we do not track you across sites in the first place, there is nothing for a browser "Do Not Track" (DNT) or Global Privacy Control (GPC) signal to switch off. We honour the intent of these signals by simply not tracking.

6. Managing cookies in your browser

You are always in control of cookies at the browser level. Most browsers let you view, block, or delete cookies — usually under Settings → Privacy. Each major browser (Chrome, Firefox, Safari, and Edge) documents how to do this in its own help centre.

Please note the trade-off described above: because our only cookie is essential for sign-in, blocking or deleting it will sign you out and prevent you from signing back in. The public pages of salieno.com will still work.

7. Changes to this policy

We may update this Cookie Policy from time to time — for example, if we introduce a feature that requires a different cookie. When we do, we will revise the "Effective date" at the top and, for material changes, take reasonable steps to notify account holders. If we ever add a non-essential cookie, we will ask for your consent before setting it.

8. Governing law

This Cookie Policy is governed by the laws of [GOVERNING LAW — owner to set jurisdiction], without regard to its conflict-of-laws rules.

9. Contact

If you have any questions about this Cookie Policy or how Salieno uses cookies, please contact us:

• Email: [email protected]
• Website: https://salieno.com
• Registered address: [REGISTERED ADDRESS — owner to set]

We aim to respond to cookie and privacy enquiries promptly.