Cookie Notice

The marketing site sets none at all. The applications set a handful, each of them needed to sign you in or to remember something you chose — named here, one by one.

In effect from

1. This website sets no cookies

The marketing site you are reading — the one at truckzly.com — sets no cookies, runs no analytics and loads no third-party script. There is no consent banner because there is nothing to consent to, and we do not know who visits.

2. The cookies the applications set

The cookies that do exist live in the products: accounts.truckzly.com, where you sign in, and logistics.truckzly.com, the application itself. Every one of them is either strictly necessary to run the service or a preference you set yourself. Under the ePrivacy rules — in Romania, Law 506/2004 — neither kind requires consent, which is why the products have no banner either. This is the complete list.

  • sb-<project>-auth-token — the session. Written when you sign in, and it is the thing that keeps you signed in. It is scoped to .truckzly.com rather than to a single host, which is what lets one sign-in cover both applications. It lasts until you sign out or it expires.
  • sb-<project>-auth-token-code-verifier — written when a sign-in leaves the application and comes back, such as confirming an email address or following a password-reset link, so the last step can prove it is the same browser. Gone when the flow ends.
  • NEXT_LOCALE — the language you chose. Written only when you pick one from the language switcher. Kept for a year, on the application where you set it.
  • sidebar_state — whether you left the sidebar open or collapsed. Kept for a week.
  • layout_variant, layout_collapsible — the same thing for the other two layout choices the application offers. Kept for a year.

3. The bot check on the sign-in screens

The sign-in, sign-up and password-reset screens run Cloudflare Turnstile, a bot check. It does not set a cookie on our domain. What it does do is send Cloudflare enough about the request to judge it: your IP address, your browser's user agent and TLS fingerprint, and the identifier of our site. Cloudflare states that it cannot identify an individual from those signals, and that they are used to tell a bot from a person rather than for advertising. The marketing site does not run it at all.

4. Things in your browser that are not cookies

The applications use your browser's local storage for a few preferences — the theme you chose, whether the orders screen opens as a list or a timeline, which map style you last looked at. They stay on your device, and clearing your browsing data removes them.

5. What we never set

No analytics cookie, on the website or in the products. No advertising, remarketing or conversion cookie. No profiling, and no fingerprinting in place of a cookie. We do not sell or share personal data for advertising, and we do not buy audience data about you.

6. Blocking or clearing them

Every browser lets you clear cookies and refuse new ones, usually under privacy or site settings. On the marketing site this changes nothing, because there is nothing there to block.

In the applications, blocking cookies stops them working. The session cookie is how the product knows who you are, so refusing it means you cannot sign in, and clearing it signs you out. Clearing the preference cookies is harmless: the application returns to its defaults.

Signing out is the tidy way to remove the session cookie. It clears it across every subdomain at once, rather than leaving a copy behind on one of them.

7. Who is responsible, and who to ask

Truckzly Solutions SRL, a company registered in Romania, VAT number RO52281367, is responsible for the storage described here. The date at the top shows the version in force.

The wider picture — what personal data we hold, why, who else sees it, and what you can ask us to do about it — is in our Privacy Notice. Questions about either go to contact@truckzly.com.