Some details in this document are not published yet.
- registered address not published yet
- email address not published yet
They are marked in the text below wherever they appear. Everything else in this document is final as drafted and pending legal review.
This is a short policy, and it is short because there is genuinely very little to describe. We would rather publish four honest paragraphs than borrow somebody else's ten pages describing trackers we do not run.
01Who this is from
KeelSG is operated by NICKTUNG, a sole proprietorship registered in Singapore under UEN 53267689X, at registered address not published yet.
Questions about anything in this policy: email address not published yet
02The short version
- The public pages of keelsg.com set no cookies at all.
- Signing in to the CRM sets session cookies, and nothing else.
- We use no analytics, no advertising and no tracking cookies anywhere.
- We do not use
localStorageorsessionStorage. - There is no cookie banner, because there is nothing to consent to on the public site.
The rest of this document explains each of those.
03Reading the public website sets no cookies
Every page you can reach without signing in sets nothing in your browser. That includes the homepage, the product pages, the integrations page, the security page, the pricing page and the implementation page.
This is not an accident of configuration. The request handler that runs in front of every page recognises the public pages and returns them before it ever creates an authentication client, so there is no code path on those pages that could write a cookie.
Two consequences worth stating:
- You can read everything about the product, including the price, without us putting anything on your device.
- There is no cookie consent banner on this site. Not because we are ignoring the question, but because there is nothing on the public site to ask you about. A banner asking permission for cookies that are never set would be theatre.
04Signing in sets session cookies
When you sign in to the KeelSG CRM, the authentication library sets a small number of cookies. Their names begin with sb-, and a long session token may be split across more than one cookie for size reasons.
| What they do | Why they are needed |
|---|---|
| Hold your signed-in session | Without this, you would have to enter your password on every single page |
| Allow the session to be refreshed | Keeps you signed in during normal work, and lets the session expire cleanly afterwards |
These cookies are set by Supabase Auth, the authentication service the product uses. They are strictly necessary for the product to function. There is no version of a CRM where you are signed in and there is no session cookie.
We do not set any other cookie in the product. No preference cookies, no analytics cookies, no advertising identifiers.
05What we do not use, named specifically
Because "we may use analytics providers" is the sentence that lets a policy describe anything later, here is the specific list of things that are not present anywhere in the KeelSG website or product:
- Google Analytics, Google Tag Manager and Google Ads tags
- Google reCAPTCHA or any other bot-detection service
- Meta or Facebook pixels
- LinkedIn Insight Tag
- Microsoft Clarity
- Hotjar
- Mixpanel, Amplitude, Segment, PostHog and Plausible
- Vercel Analytics and Speed Insights
- Any advertising, retargeting or cross-site tracking network
We do not load fonts from a third-party font service either. The typefaces are served from our own site. Visiting a page does not quietly tell a font provider that you were here, which is a thing most sites do without realising.
We hold no advertising relationship with anyone, so there is nobody for us to share browsing behaviour with even if we collected it.
06Server logs are not cookies, but you should know about them
Our hosting provider keeps standard web server records so the site can be served and protected from abuse. These typically include an IP address, the page requested, a timestamp and a browser user agent string.
They are not cookies, nothing is written to your device, and we do not build profiles from them or join them to anything else. We mention them because a cookie policy that says "we collect nothing" while a server quietly logs requests would be misleading, and every website has server logs.
07Turning cookies off
Every browser lets you block or delete cookies, usually under settings named Privacy, Security or Site data.
- On the public pages, blocking cookies changes nothing, because nothing is set.
- In the CRM, blocking cookies will stop you signing in. The session cookie is how the product knows who you are. This is not something we can work around, and it is not a dark pattern. It is how sessions work.
08Changes to this policy
If we ever add a cookie, or engage an analytics or bot-protection provider, we will update this policy before it goes live, name the provider specifically, and say what it does. If a change means we need your consent, we will ask for it properly rather than assuming it.
We will not quietly widen this policy with a vague phrase in order to cover something added later.
09Contact
email address not published yet
NICKTUNG
Sole proprietorship registered in Singapore, UEN 53267689X
registered address not published yet
This document is published as drafted and is pending review by a qualified Singapore lawyer. Where something is not built, it says so rather than describing it.