Cookie policy
Last updated:
1. Essential cookies
These are needed to run the site and are set without asking for consent.
- Session cookie (better-auth.session_token): keeps you logged in.
- locale: remembers the language you chose. Kept for one year.
- consent: remembers your cookie choice. Kept for 12 months.
- campaign_code: if you arrive on the website package page from a link with a discount code (e.g. ?code=SPLET25), we remember the code for 30 days so that it is applied on the order summary automatically. It holds only the code, nothing about you.
Feedback form: nothing from Damper (usedamper.com), our feedback provider, is loaded until you click "Suggest a feature". Then its form loads and keeps your identity (the email you enter, or your account when you are logged in) in your browser's local storage so that your suggestions and votes stay together. You asked for the form, so no separate consent is needed.
2. Analytics and advertising cookies
We don't run analytics or advertising tools on password-reset and set-password pages.
signup_pending: set for 10 minutes right after you create an account, only if you allow advertising cookies, so the next page can report the sign-up to our ad partners once. It contains no identifier and is removed when read.
attribution: on your first visit we note the website you came from (only its host name, for example google.com, never the full address), the first page of ours you opened, and when; if you arrive from a link with campaign parameters (utm_source, utm_medium, utm_campaign, utm_content, utm_term, gclid, gbraid, wbraid, fbclid, oppref), we keep those too. They stay in a first-party cookie for 30 days and are attached to an order if you place one. This lets us see which sources and campaigns lead to orders. We set it only after you allow analytics or advertising cookies, and store click identifiers (gclid, gbraid, wbraid, fbclid, oppref) in a cookie only with advertising cookies. Campaign tags and click IDs saved on an order come from the page address. No cookie is used for this.
Google tag (Google Ads): not loaded, and no Google cookies are set, until you allow advertising cookies. It receives the address of the page you are on. If you reject, it never loads.
If you accept, Google may set cookies (such as _ga and _gcl_*) and use the data for measuring and personalising ads.
If you accept and came from one of our Google ads, our server also reports your purchase to Google with the email address of your account as a SHA-256 hash, so that Google can match it to the ad click.
If you accept advertising cookies and came from one of our ChatGPT ads, our server reports your purchase to OpenAI with the ad click identifier, so that OpenAI can match it to the ad click.
PostHog (product analytics, EU cloud): before you choose, and if you reject, it runs without cookies and without storing anything in your browser. It sends events (page views, clicks, searches and the steps of sign-up and checkout) with technical data such as your browser information. PostHog uses your IP address to create a visitor identifier that changes every day, and doesn't store the IP address, so we cannot follow you from one day to the next. You can object at any time by writing to us. If your browser sends a Global Privacy Control or Do Not Track signal, your browser doesn't send these events.
If you accept, PostHog stores a random identifier and some session data in a first-party cookie and in local storage of your browser: the cookie ph_<project key>_posthog and the local storage entries ph_<project key>_posthog (and its …__flags) and __ph_opt_in_out_<project key>. The cookie lasts up to one year. Then we can recognise you on later visits and, when you are logged in, link your activity to your account. If you reject or withdraw your choice, these items are deleted.
3. Support chat
The chat button is ours. Nothing from our chat provider Hal (chatwithhal.com) is loaded, stored or contacted until you click it, so you can browse the site without any of it. You asked for the chat, so no separate consent is needed.
When you click it, we load the chat widget from api.chatwithhal.com. It sets no cookies. It stores a random visitor ID (hal_visitor_…) and whether the chat is open (hal_widget_open_…) in your browser's local storage so that your conversation continues, and it talks to Hal's servers. If you are logged in, we also tell the chat who you are (name, email address, user ID, language), using a signature our server creates so that nobody else can claim to be you, and we keep your user ID in local storage (hal_identified_user) so that the chat is disconnected from your account when you log out.
Once you have used the chat, the widget loads on your later visits to show your conversation. Delete the site data in your browser settings to remove these items.
4. Changing your choice
Use the cookie settings link in the footer to change your choice at any time. You can also delete cookies in your browser settings.