Cookies

JandaSec treats cookies and browser storage seriously. We minimise them. We do not use cookies for advertising, behavioural profiling, login, personalisation or visitor analytics on this website.

The site is static-first. There is no visitor account system and no marketing database built from website activity. There is no intentional cookie regime for tracking individuals around the site.

That does not mean every third-party security control operates without any browser mechanism of its own. Accuracy matters more than a “cookie-free” badge.

Why there is no cookie banner

JandaSec does not use a cookie consent banner because we do not use storage or access technologies that require prior consent.

We do not use advertising cookies, behavioural profiling, cross-site tracking, personalisation cookies or analytics cookies.

Cloudflare Turnstile is used only to protect the contact form from automated abuse. Any browser mechanisms required for that security purpose are used only for the security function and are not used by JandaSec for advertising, profiling or behavioural tracking.

JandaSec uses Cloudflare Web Analytics to produce aggregate information about website use and performance. It is not used to identify or profile individual visitors. You can turn aggregate analytics off at any time using the control on this page.

If you turn analytics off, we store one small preference in your browser so that we can remember and honour that choice. It is not used for tracking and is not sent to JandaSec as analytics data.

If we introduce technology in future that requires consent, we will introduce an appropriate consent mechanism before using it.

Visitor analytics

JandaSec uses Cloudflare Web Analytics to produce aggregate information about how the website is used and how it performs, with a view to improving the site.

Cloudflare Web Analytics is implemented using a lightweight JavaScript beacon. It does not require cookies. Its sole JandaSec purpose is aggregate statistical understanding of website use and performance. JandaSec does not use it to identify or profile individual visitors, for advertising, or combined with other data to make decisions about visitors.

The analytics available to JandaSec include aggregate information such as:

• Visits and page views
• Pages and paths visited
• Referring websites
• Approximate visitor country
• Device type
• Browser and operating system
• Page-load performance and Core Web Vitals

This information is used to understand which parts of the website are useful, identify technical or performance problems and improve the site.

JandaSec does not use Google Analytics, Google Tag Manager, advertising pixels or behavioural marketing technology.

Cloudflare states that its Web Analytics service does not collect or use visitors’ personal data and does not track individual users across its customers’ websites.

JandaSec’s website remains hosted and protected through AWS. Cloudflare Web Analytics is a separate measurement service; introducing contact-form protection has not changed the analytics implementation. The website is not routed through Cloudflare.

You can object to this aggregate analytics use at any time. When you turn it off, the Cloudflare Web Analytics beacon is not loaded and no analytics RUM request is sent from this browser.

Contact-form protection

The Contact page uses Cloudflare Turnstile to help distinguish genuine visitors from automated or bot traffic and to reduce automated abuse of the contact form.

Turnstile verification happens before a message is accepted. JandaSec does not use Turnstile for advertising or behavioural profiling.

Cloudflare states that Turnstile does not access, store or transmit the visitor’s form entries or communications. Turnstile necessarily processes limited technical and security information needed to perform the verification.

A distinction matters here. JandaSec does not set advertising, analytics or personalisation cookies on jandasec.com. Separately, Turnstile’s challenge runs in a Cloudflare-controlled browser context (challenges.cloudflare.com) and may use browser mechanisms there to complete bot and security verification.

At the time of the most recent review (20 October 2026), browser developer tools on the live Contact page showed:

• No cookies associated with jandasec.com
• No Local Storage entries for jandasec.com
• No Session Storage entries for jandasec.com
• No cf_clearance cookie on jandasec.com (the current Turnstile widget is configured without pre-clearance; Cloudflare’s documented default is a one-time verification token rather than a clearance cookie)
• The Turnstile script and challenge resources loading from challenges.cloudflare.com

Cross-origin storage inside Cloudflare’s challenge iframe is not readable from JandaSec’s own page JavaScript. Where Turnstile uses cookies or other browser storage in that Cloudflare context, it is for security verification associated with the contact form — not for JandaSec advertising or behavioural profiling.

How the site has been checked

JandaSec periodically checks the production site using browser developer tools and external cookie-detection services, including CookieChecker and CookieServe. Results are reviewed when the site or its supporting services change.

Browser inspection of https://jandasec.com/ and https://jandasec.com/contact on 20 October 2026 found no first-party cookies for jandasec.com, and no Local Storage or Session Storage unless a visitor has used the analytics preference control on this page (in which case only jandasec_analytics_optout is stored). The Contact page loads Cloudflare Turnstile from challenges.cloudflare.com for form protection, as described above.

CookieChecker scans of https://jandasec.com/ and https://jandasec.com/contact on the same date each reported zero cookies detected before consent across the categories it classifies. External scanners and browser extensions can still report differently depending on whether they load third-party challenge widgets, interact with them, or attribute cross-origin security cookies to the scanned site. Point-in-time results are not a permanent guarantee.

You can also inspect this yourself using your browser’s developer tools and review the Cookies, Local Storage and Session Storage associated with jandasec.com and, on the Contact page, any storage under Cloudflare’s challenge origin.

Infrastructure and technical data

Infrastructure providers may process limited technical request information required to deliver, secure and operate the website and contact service.

This is separate from JandaSec’s visitor analytics and is not used by JandaSec for advertising or behavioural profiling.

Third-party embedded content

The homepage includes a YouTube video using YouTube’s privacy-enhanced embedding mode.

When third-party embedded content is loaded or played, that provider may process technical information or use browser storage under its own terms. JandaSec does not control the internal operation of third-party players.

A direct Watch on YouTube link is provided as an alternative to using the embedded player.

External websites

Links to external websites take you to services operated by third parties. Their privacy, cookie and tracking practices are governed by their own policies.

JandaSec does not receive advertising or behavioural-tracking data from those sites merely because a visitor follows an external link.

External links that open in a new browser tab or window are configured using rel="noopener noreferrer". This prevents the destination site from gaining control of the originating JandaSec browser tab and avoids sending the referring page URL to that destination.

This is one of the browser-security and privacy controls used across the site. External websites remain responsible for their own privacy, cookie and tracking practices.

Wider privacy information

For information about how JandaSec handles personal information more generally, including contact-form enquiries, see Privacy and Security.

Last reviewed: 20 October 2026