Skip to content

Legal

Cookie Policy

What cookies and similar technologies JobTackl uses, and how consent will work. This is a working draft prepared for legal review.

Working draft — pending final founder review before publication. This document is not yet final and should not be relied on as a published policy.

Today the JobTackl website sets no advertising or third-party analytics cookies, and there is nothing to consent to. This policy describes that honestly and sets out what will be added — and what consent will be required — as the platform develops.

1. What cookies are

Cookies are small files a website stores on your device. They can keep you signed in, remember preferences, or record how a site is used. Similar technologies — local storage, session storage and pixels — do comparable things and are covered by this policy.

2. What we use today

The current site is a pre-launch marketing site. It does not set advertising cookies, and it does not send behavioural data to any third-party analytics platform.

JobTackl uses cookie-free, first-party analytics stored in our Supabase project. It does not create a persistent visitor ID, advertising profile or cross-site record. The events contain no direct identifiers and are explained in the Privacy Policy.

NameTechnology and purposeDuration
jobtackl_analytics_opt_outLocal storage used only to remember that analytics have been turned off on this device. It is necessary to preserve the user's privacy choice.Until the user allows analytics again or clears the browser's site data

We have deliberately not deployed a consent banner, because no non-essential cookie or device storage is used. Presenting a consent choice where there is nothing non-essential to consent to would be misleading.

3. What will be added

As JobTackl launches, we expect to use the following categories. Each will be listed here with its specific cookies before it goes live.

CategoryPurposeConsent needed
Strictly necessarySigning in, keeping a session, security and fraud prevention, load balancingNo
FunctionalRemembering preferences such as your area or roleYes
AnalyticsCookie-free first-party events are used today. Consent will be requested before any future analytics tool stores or reads non-essential information on a deviceNo for the current cookie-free system; yes before non-essential storage
PaymentsCookies set by Stripe to process payments and detect fraudStrictly necessary for a payment; otherwise yes
MarketingMeasuring campaigns, if we ever run advertisingYes

Before any non-essential cookie, pixel, SDK or device-storage item is enabled, we will ask. Our required approach:

  • No non-essential cookies set before you make a choice
  • Rejecting made as easy as accepting — no dark patterns, no pre-ticked boxes
  • Granular control by category
  • A way to change your mind later, reachable from every page
  • A record of consent, as UK GDPR requires

5. Third-party cookies

No third-party cookie is currently set by the JobTackl website. Stripe is not embedded yet. When payment and authentication integrations are added, we will audit and name their cookies or similar technologies here before they go live. We do not permit advertising profiles or cross-site tracking on JobTackl.

6. Managing cookies in your browser

You can block or delete cookies in your browser settings, and most browsers let you refuse third-party cookies entirely. Blocking strictly necessary cookies will stop parts of the site working — you will not be able to stay signed in.

Guidance for each major browser is available from its own support site.

7. Changes to this policy

This policy will be updated whenever we add or remove a cookie. The categories and consent approach described above will be in place before any non-essential cookie is used. See the Privacy Policy for how the resulting data is handled.

To confirm before publication

These details are deliberately left out of the draft rather than guessed. They must be supplied and checked before this document goes live.

  • Independent PECR and UK data-protection review before marketplace trading begins
  • Repeat the cookie and SDK audit when authentication, Stripe and the mobile apps are integrated
  • Add a consent manager before enabling any non-essential cookie, pixel, SDK or device storage

Questions about this document: legal@jobtackl.com