Cookie Policy
Last Updated: June 20261. What are cookies
Cookies are small text files placed on your device by a website when you visit it. They let a site remember information about your visit — for example, whether you are logged in — so you do not have to re-enter it on every page. Cookies set by the site you are visiting are called first-party cookies. Cookies set by other organisations (payment processors, analytics providers) are third-party cookies.
2. Cookies we use
ConstructDash uses a minimal set of cookies, all of which are strictly necessary for the site to function. We do not use advertising cookies, cross-site tracking, or third-party analytics cookies.
Strictly necessary — authentication (Clerk)
When you sign in, Clerk sets the following cookies to maintain your session. These cookies are required for the service to work and cannot be disabled while you are logged in. Unauthenticated visitors to public pages (/insights, /about, /contact) receive none of these cookies.
| Name | Purpose | Duration | Party |
|---|---|---|---|
__session | Signed session JWT — proves you are authenticated to the server on each request | ~1 hour (auto-refreshed while active) | First-party (.constructdash.com) |
__client_uat | Numeric timestamp Clerk reads client-side to detect whether an active session exists without decoding the full JWT | Persistent — verify in DevTools | First-party |
__clerk_handshake | Short-lived token created during the server-side auth handshake; deleted automatically once the handshake completes | Seconds to minutes (self-deleting) | First-party |
__clerk_redirect_count | Counter that prevents infinite auth redirect loops | Session | First-party |
Analytics
We use Vercel Analytics to measure aggregate site usage. Vercel Analytics is cookieless by design — it uses a server-side ephemeral identifier derived from a hashed IP address and User-Agent, discarded after 24 hours. No persistent analytics cookie is set on your device.
Marketing
We do not use advertising cookies, retargeting pixels, or cross-site tracking of any kind. No marketing cookies are set.
3. Conditional cookies (not yet active)
The following cookies are not currently set on this site but may be activated as the platform develops. This policy will be updated before they go live.
Bot protection — Cloudflare Turnstile
If we add a Turnstile widget to forms (sign-in, contact), Cloudflare may set cf_clearance — a strictly necessary security cookie confirming that a bot challenge was passed. This would be a third-party cookie set by challenges.cloudflare.com with a duration of approximately 30 minutes to 24 hours.
Payment processing — Stripe.js
Stripe is integrated server-side for payment processing. If we add a client-side Stripe.js checkout flow, Stripe would set three strictly necessary cookies during the checkout session: __stripe_mid (1 year), __stripe_sid (30 minutes), and m (2 years). These would be third-party cookies from stripe.com and would only appear on pages where a checkout form is loaded.
Advertising (AdSense)
We do not currently use Google AdSense or any advertising network. If advertising is enabled in the future, a cookie consent banner will be added and activated before any advertising cookies are set.
4. How to control cookies
You can manage or delete cookies through your browser settings. The following links cover the most common browsers:
Chrome: Settings → Privacy and security → Cookies and other site data. Firefox: Settings → Privacy & Security → Cookies and Site Data. Safari: Settings → Privacy → Manage Website Data. Edge: Settings → Cookies and site permissions.
You can also opt out of Vercel Analytics data collection by enabling the Do Not Track browser signal — Vercel Analytics respects it.
5. Changes to this policy
We will update this Cookie Policy before activating any new cookie categories. For material changes, active users will be notified by email. The "Last Updated" date at the top of this page reflects the most recent revision.
6. Contact
For questions about this Cookie Policy, contact: hello@constructdash.com