Cookies Policy

Cookies are small files that a website or third-party service can place on your browser or device. Similar storage and access technologies include local storage, pixels, scripts, tags, and other methods that store information on your device or access information already stored there.

UK rules apply to cookies and similar technologies even where the information is not personal data. Where the information is personal data, UK data protection law also applies.

Kindura does not set analytics, marketing, tracking pixel, CRM, or advertising cookies on ordinary page load. The website loads its own Next.js scripts, local stylesheet, local font file, and local brand assets from www.kindura.co.uk.

Kindura does not show a general cookie banner because optional technologies are not loaded on ordinary page views. The contact page instead asks for a just-in-time choice before the embedded Calendly booking calendar can load.

A preference centre is provided because Calendly may set third-party cookies or use similar technologies when the embedded calendar loads. The embed is blocked unless you allow the embedded booking category.

Kindura uses local browser storage named kindura_cookie_preferences_v1 to remember your cookie and embedded-booking choices. This is used only to respect your privacy preferences and is retained for up to 180 days unless you clear browser storage sooner.

This storage is treated as strictly necessary because it lets the website remember whether optional technologies should stay off or may be loaded.

The embedded booking category controls whether the Calendly calendar can load inside the Kindura contact page. If you do not allow this category, the iframe is not mounted and Calendly is not loaded by the Kindura page.

You can still use the external booking link. If you open Calendly in a new tab, you leave Kindura's website and Calendly's own cookies, privacy notice, and terms apply.

When Calendly is loaded, Calendly may also load resources or nested frames from its own service providers. Live testing on 22 May 2026 showed Calendly loading Stripe infrastructure frames after embedded booking consent.

A technical check on 22 May 2026 showed Calendly setting cookies such as _calendly_session and Cloudflare security cookies when its booking page was requested directly.

No production analytics provider is currently active on the website. Kindura has internal event hooks ready for future analytics, but those hooks do not fire unless the analytics category is allowed.

If analytics is enabled in the future, it must be used for aggregate website improvement only. Form names, email addresses, phone numbers, company names, free-text messages, passwords, access tokens, and sensitive system details must not be sent in analytics payloads.

Kindura does not currently use advertising cookies, retargeting tags, social media tracking pixels, heatmaps, session replay, HubSpot tracking, Meta Pixel, LinkedIn Insight Tag, Google Tag Manager, Google Analytics, Hotjar, Microsoft Clarity, or similar marketing technologies.

If these tools are introduced later, Kindura should update this policy and request valid consent before they load.

You can reopen the preference centre from this page, the contact page booking card, or the website footer. Rejecting non-essential choices keeps optional analytics and the embedded Calendly calendar switched off on Kindura pages.

You can also clear this website's local storage in your browser to reset your saved choice. Optional tools remain off until you choose to allow them again.

Third-party services may receive technical information when they are embedded, loaded, or opened from the website. At present, the main visible third-party booking service is Calendly where the booking calendar is enabled.

Kindura should review and update this policy before adding new third-party tracking, CRM, marketing automation, chat, video, analytics, heatmap, session replay, or advertising technologies.