Cookie Policy

1. Overview#

KaiBuild uses cookies and similar technologies — browser local storage, and in future possibly pixels — to run the Service and, with your permission, to measure and improve it. This policy should be read with our Privacy Policy.

Section 5 lists every cookie and stored value we set ourselves, by name. It is not a category summary; it is the actual list, and we update it when the code changes.

This policy covers kaibuild.space and the app. A website built by one of our customers and published through us is theirs. If they add analytics or embeds to it, those are their choices and their cookie notice, not ours. See section 8.

2. How we ask#

We apply one rule everywhere, rather than a different standard depending on where you are: nothing optional loads until you say yes. Cookies strictly necessary to run the Service are set without asking, because without them the Service does not work. Everything else — analytics, anything measuring or marketing — defaults to off until you choose Accept all or save your own selection.

That is the stricter of the standards we could apply, and applying it to everyone is simpler than deciding, per visitor, which country's rule they get.

Refusing everything optional costs you nothing. There is no reduced version of the Service for people who decline, no repeated prompt, and no dark pattern that makes "reject" harder to find than "accept".

3. What that means where you are#

• India — we tell you what is being set and why, and ask before anything optional loads. You can change your answer at any time, as described in section 6.
• EEA and UK — non-essential cookies require prior consent, and ours are off until given. You can withdraw consent as easily as you gave it.
• United States — you get notice of every category and can opt out. Where an analytics or marketing technology could be treated as a "sale" or "share" under state law, opting out covers it, and we honour Global Privacy Control signals as an opt-out where those scripts are enabled.
• Everywhere else — the same rule in section 2. We do not have a weaker default for countries with no cookie statute.

4. Categories#

Strictly necessary#

Sign-in and session, the anonymous session that lets you try the builder before you have an account, security and bot challenges, and the record of your own cookie choice. Always on, because switching them off means switching the Service off.

Functional#

Preferences such as theme and locale, where they are stored rather than derived. Off until you opt in.

Analytics#

Usage measurement via Google Analytics 4 and PostHog when configured. Off until you accept; no analytics script loads before consent. The providers and cookie names are listed in section 5 when analytics is enabled.

Marketing#

Advertising and retargeting pixels. We run none. The category exists so that the banner is honest about what a future "accept all" would cover, not because there is something hiding behind it.

5. The cookies we actually set#

First-party, set by us. "HttpOnly" means page scripts cannot read it; "Lax" means it is not sent on cross-site subrequests.

Set by others, on our pages#

• Cloudflare — as our network and security layer, Cloudflare sets its own bot-management and challenge cookies (you may see names such as __cf_bm and cf_clearance). They exist to tell a browser from a script. They are short-lived, Cloudflare sets the duration, and they are strictly necessary: without them we cannot keep automated abuse off the Service. See the Turnstile Privacy Addendum and Cloudflare's Privacy Policy.
• Google — sign-in happens on Google's own pages, under Google's cookies and Google's policy. We are not setting them and cannot switch them off; not signing in is the only way to avoid them.
• Dodo Payments — checkout happens on their surface, under their cookies, for the length of the payment. We do not see them.

Vendors change their own cookie names and durations without asking us. Where this table differs from what your browser shows, the browser is right and we want to know — [email protected].

6. How to change or withdraw consent#

• Use the banner: Essential only, Accept all, or Customize to pick categories one at a time.
• Your choice is written to your browser's local storage under pkd_cookie_consent. It stays on your device — we do not hold a server-side record of it, which also means the choice is per-browser and per-device.
• To change your mind, clear that key or clear the site's data in your browser settings. The banner returns and nothing optional loads until you answer it again.
• Withdrawing is the same number of clicks as accepting. That is deliberate.
• You can also write to [email protected] and we will tell you what is set and help you clear it.

7. If you refuse#

Declining everything optional leaves the Service fully working, because nothing optional is running yet. Nothing is withheld, nothing is degraded, and you will not be asked again on that browser until you clear the stored choice.

Blocking strictly necessary cookies is different, and your browser or an extension can do it. If you block them: you cannot stay signed in, the builder cannot keep your guest session between page loads, a referral will not be credited to the partner who sent you, and Cloudflare may challenge you repeatedly. Nothing breaks maliciously — it simply cannot remember you from one request to the next.

8. Sites built with KaiBuild#

When you publish a site with us, the cookies on your site are your responsibility. We set no analytics or marketing cookie on a published site. If you add an embed, a tracking script, or a captcha using your own provider keys, you have introduced a third party to your visitors — and your own cookie notice needs to say so.

The DPA & Subprocessors page sets out what we hold on your behalf and what remains yours to decide.

9. Changes and contact#

When we add or remove a cookie, this page changes with the code, and the version and effective date at the top move with it. A new optional category never arrives switched on.

Questions: [email protected], addressed to Krushang Vachhiyat.