This Cookie Policy explains the small text files (and similar local-storage entries) that truckdoc.net places on your device, why we use them, how long they last, and how you can control them. It supplements our Privacy Policy, which describes how we handle personal data more generally under KVKK and GDPR.
1. What are cookies
Cookies are small text files that a website asks your browser to store. On every subsequent visit, your browser sends them back so the site can recognise the same device — keeping you signed in, remembering your preferences, or measuring how the site is used. Some cookies live only until you close the browser (session cookies); others persist for a fixed period (persistent cookies). Where it is more appropriate, we use the browser's localStorage instead of a cookie; for transparency we list those entries in the same inventory below.
2. How we use cookies
We group cookies into two categories: strictly necessary and analytics. Strictly necessary cookies are always set, because the site cannot function without them — they keep you signed in, defend against CSRF, and remember the consent decision you make in the banner. Analytics cookies, and any marketing cookies we may add in the future, are set only after you grant the corresponding consent.
You can change your decision at any time using the Cookie settings link in the site footer. Withdrawing consent stops further data collection from that moment onward; it does not retroactively undo measurements that were collected while consent was active.
3. Cookies we use
The table below is the authoritative inventory of every cookie or local-storage entry the site sets. If you find one in your browser that is not listed here, please report it to privacy@truckdoc.net so we can update this page.
| Name | Purpose | Category | Duration | Third-party | Legal basis |
|---|---|---|---|---|---|
__Host-session | Authenticates the signed-in user. | Strictly necessary | 7 days (sliding) | — | Strictly necessary |
__Host-csrf | Protects form submissions against cross-site request forgery. | Strictly necessary | Session | — | Strictly necessary |
tdc_consent | Stores your cookie preferences so we can honour them on every page. | Strictly necessary | 12 months | — | Strictly necessary |
_ga, _ga_* | Google Analytics 4 — measures aggregate site usage so we can improve the product. | Analytics | Up to 2 years | Google LLC | Consent |
Note on tdc_consent: this entry is stored in your browser's localStorage rather than a cookie. We list it here because it serves the same purpose — recording a small piece of state on your device — and GDPR and KVKK treat it the same way. Storing the consent record itself does not require consent (it is the mechanism by which consent is recorded), so it falls under strictly necessary.
4. Managing cookies
You have two complementary controls. The first is the Cookie settings link in the footer of every page: it reopens the consent banner and lets you grant or withdraw analytics consent on the spot. The second is your browser, which can block or delete cookies for any site individually — see the help pages for Chrome, Firefox, Safari, and Edge.
A warning: blocking strictly necessary cookies will break sign-in, checkout, and form submissions. The site will appear to load, but you will not be able to stay signed in or place an order. If you only want to opt out of measurement, use the Cookie settings link instead — it removes analytics cookies without touching the ones the site needs to operate.
You can also signal your preference at the browser level using Global Privacy Control (GPC) or the older Do Not Track header. We treat a clear GPC signal as a withdrawal of analytics consent for that browser.
5. Changes
The “Last updated” date at the top of this page reflects the most recent change to this Cookie Policy. When we add a new cookie or change the purpose or duration of an existing one, we update the inventory above and reset the consent banner so you can review the change before it takes effect.
6. Contact
Questions about cookies or this policy? Email privacy@truckdoc.net, or read our Privacy Policy for the broader picture of how we handle personal data.