Cookie use
See the exact cookies, local storage keys, and third-party services used.
1. How CTHub currently handles consent
- 1a.The cookie banner currently records your choice in browser localStorage using the key
cth_cookie_consent_v1. That storage item is not itself a cookie. - 1b.Clicking Accept cookies or Reject non-essential currently hides the banner and stores that preference locally in your browser.
- 1c.At the time of writing, that choice does not switch CTHub features, analytics, maps, social login buttons, or security widgets on or off. Essential site cookies continue to work either way, and any third-party feature used on a page is not currently gated by the banner choice.
2. First-party cookies set by CTHub
| Cookie | What it does | When it appears | Typical duration | Essential |
|---|---|---|---|---|
| car-transporters-hub-session | Laravel session cookie used for signed-in sessions, flash messages, CSRF/session state, intended redirects, pending two-factor or passkey sign-in state, and other core request state needed to keep the site working. | On normal site use where a web session is created. | Configured for 120 minutes of inactivity. | Yes |
| XSRF-TOKEN | CSRF protection token used by Laravel and front-end requests so forms and AJAX actions can be verified as coming from your session. | When pages/forms need CSRF protection. | Usually tied to your session lifecycle. | Yes |
| remember_web_59ba36addc2b2 |
“Keep me signed in” recaller cookie used only if you tick the remember-me option on login. It helps restore your authenticated session between visits. | Only after choosing “Keep me signed in” when logging in. | Laravel default remember-me duration: 576,000 minutes (about 400 days), unless the app changes that later. | User-requested / login convenience |
| cthub_guest_dealership_views | Stores a JSON list of dealership IDs a guest has viewed so the guest-content gate can count unique dealership page views and decide when the viewing limit has been reached. | Only for signed-out visitors when the guest dealership gate is enabled. | 30 days. | Core site behaviour for that feature |
| cthub_toast | Short-lived plain-text toast payload used to show one-off notices after redirects such as sign-in, profile actions, donations, or social account flows. | Only after actions that queue a toast notification. | 1 minute. | Functional |
3. Similar browser storage CTHub uses
| Storage key | What it does | Cookie? |
|---|---|---|
| cth_cookie_consent_v1 | Stores whether you selected accepted, rejected, or have not yet answered the cookie banner. | No, localStorage |
| cth_theme_preference | Stores a guest user’s theme preference, such as light, dark, or system. | No, localStorage |
4. Third-party services that may place cookies
- 4a.Cloudflare Turnstile: the login and registration pages load Cloudflare Turnstile to help block automated abuse. If Turnstile is enabled, Cloudflare may set or read its own cookies or similar identifiers subject to Cloudflare’s policies.
- 4b.Google sign-in: if you choose “Continue with Google”, the sign-in flow moves onto Google pages, where Google may set or read cookies required for authentication, account selection, security, and abuse prevention.
- 4c.Facebook sign-in: if you choose “Continue with Facebook”, Facebook may set or read cookies on its own pages during login or account-linking.
- 4d.Discord sign-in: if you choose “Continue with Discord”, Discord may set or read cookies on its own pages during login or account-linking.
- 4e.Google Maps: pages that load interactive Google Maps use Google’s JavaScript Maps API and may cause Google to set or read cookies or similar identifiers when that map feature is used.
- 4f.External map/CDN assets: some map-related pages may also load assets from providers such as
unpkg.com, OpenStreetMap, or Esri. Those requests can expose technical request data such as IP address and browser details even where they do not set cookies.
5. Third-party services that are linked but not embedded by default
- 5a.CTHub includes outbound links and share links to services such as Facebook and other platforms. Those links do not place third-party cookies on CTHub just by being visible on the page.
- 5b.Once you click through to a third-party service, that provider can apply its own cookies and tracking rules under its own policies.
6. Analytics status
- 6a.The current front-end code refers to analytics in the banner text, but there is no active analytics loader in the audited code paths that reads your cookie choice and enables or disables an analytics script.
- 6b.In practical terms, the current accept/reject buttons are not toggling a live analytics integration on CTHub at this time.
7. More information
- 7a.For broader information about account data, profile data, uploaded content, and retention, see the Privacy Policy.
- 7b.For questions about this cookie use page or a privacy-related request, contact [email protected].
- 7c.Last updated: 6 April 2026.