Cookies notice
Cookies, device storage and the choices available to you when using Kontxs.
Version 2026-10-1. Published .
About this notice
This notice explains cookies and similar technologies used by Kontxs Limited across the Kontxs website and web app. It also explains how these differ from storage in our phone apps. Read it alongside our Privacy notice, which covers the personal information we process, our providers and your rights.
- The public website does not use advertising or tracking cookies.
- The public website counts visits with cookie-free analytics, which stores nothing on your device.
- If you apply for early access after following an advert or campaign link, we record which one from the link’s address, not from a cookie.
- The web app uses cookies from Clerk, our sign-in provider, to support secure access to your account.
- The web app stores a light or dark appearance choice locally when you use its theme control.
What cookies and similar technologies are
A cookie is a small piece of data a website asks your browser to store. The browser can send it back on later requests, for example so a service can recognise that you have signed in. Some cookies last for a browser session; others have an expiry date and may remain after you close the browser.
Local storage is another way to keep small values in your browser. Unlike a cookie, it is not automatically sent with each request and has no automatic expiry. Secure storage on a phone is a different mechanism used to protect information such as a sign-in token. These technologies have different purposes; they are not all used for advertising or tracking.
A first-party cookie is set for the site you are visiting. A third-party cookie is set for another site. A service provider can also supply technology that sets cookies on our own domain. The provider’s involvement alone does not make a cookie an advertising cookie.
Where we use cookies and storage
| Where | Technology and purpose | How long it remains |
|---|---|---|
| Public website · kontxs.com | No cookies are used for ordinary browsing of the public website. Visit counting, performance measurement, campaign links and early-access abuse checks are explained below. | No website browsing cookie to retain. |
| Web app · app.kontxs.com | Clerk authentication cookies support sign-in, recognise your session and keep access to your account secure. | Depends on the cookie, your sign-in session and browser. Session tokens are short-lived and refreshed while you are signed in; other authentication cookies can remain longer. |
| Web app appearance | The theme value in local storage records light or dark when you use the appearance control. It is not an advertising identifier. | No automatic expiry. It remains until overwritten or removed, or until your browser clears site storage. |
| Phone apps | Our Privacy notice describes sign-in tokens held in secure device storage rather than browser cookies. | See the phone-app storage information in the Privacy notice. |
Sign-in cookies
Authentication cookies are necessary for the web app’s sign-in features. Clerk uses a session cookie on the app’s domain and authentication cookies on its sign-in service’s domain. These support access to your account; we do not use them to advertise to you or track you across other companies’ websites.
Clerk’s documented authentication cookies include the following. The cookies present in your browser depend on the sign-in flow and whether you have an active session.
| Cookie | Purpose |
|---|---|
| __session | Holds the short-lived sign-in token used to authenticate requests to the web app. Clerk refreshes the token while your session is active. |
| __client | Allows Clerk’s authentication service to recognise the browser and manage its sign-in sessions, including issuing fresh session tokens. |
The lifetime of a session token is different from how long you remain signed in. Your browser’s site-data settings show cookie domains and stored expiry dates. Clerk explains its authentication cookies and session refresh in its authentication documentation.
Visit counts, performance and abuse prevention
We count visits to the public website with Vercel Web Analytics. It sets no cookies and stores nothing on your device. Vercel recognises a returning visitor within a day from a one-way hash of the request, which it discards after 24 hours, and we see only totals: pages viewed, the referring website, country, browser, operating system, device type and any campaign tags in the page’s address. More information is in Vercel’s Web Analytics privacy information. The web app does not use it.
We use Vercel Speed Insights to measure technical performance, such as page-load timings and device or browser information. This is performance measurement, rather than advertising or a profile of your activity across other websites. More information is in our Privacy notice and Vercel’s Speed Insights privacy information.
The early-access form uses Vercel BotID to check browser signals for automated abuse. It performs a browser challenge and checks the response on the server. This supports abuse detection; it is not an advertising tool. Our Privacy notice explains the information processed for this purpose.
Server-side request logs and rate-limit records are separate from cookies or local storage on your device. Clearing browser data does not delete those server-side records. Our privacy notice explains how we handle personal information.
Advertising and external services
We do not use advertising, cross-site tracking or social media cookies, and we do not place advertising pixels or tags on our website. We do not embed social media tracking widgets. Videos on the public website use our own video player rather than an embedded social media player.
When we advertise, our links can carry campaign tags in their address (such as utm_source or utm_campaign), and the advertising platform may add its own click reference (such as gclid from Google or fbclid from Meta). Our website reads nothing from your device to do this. If you apply for early access from a page reached through such a link, the form sends those values from the page’s address with your application, so we can measure which advertising brings applications. Our Privacy notice explains how we hold them.
If you follow a link to another website, or choose to sign in through a provider such as Apple or Google, that provider may use its own cookies or storage on its service. Its notices and controls apply there. Our Sub-processor list explains the providers we use to process information for Kontxs.
Managing cookies and browser storage
You can use your browser’s privacy or site-data settings to inspect, block or remove cookies and local storage. Look for settings called “Cookies”, “Site data” or “Website data”. To remove stored information for Kontxs, select the relevant website, app and authentication-service domains shown there.
- Blocking authentication cookies can prevent sign-in or stop the web app from working correctly.
- Removing authentication cookies can sign you out. Use the app’s sign-out control when you want to end your session.
- Removing the web app’s local storage clears its stored appearance value.
- Clearing site data affects that browser or device. It does not close your account or delete records held in Kontxs.
There is no advertising-cookie preference panel on Kontxs because we do not use advertising cookies. Before introducing non-essential cookies or similar technologies, we will update the relevant notices and obtain consent where required.
Changes and questions
We will update this notice when our use of cookies or similar technologies changes. The version and publication date at the top identify the current notice.
For questions about this notice or information stored on your device when using Kontxs, contact privacy@kontxs.com.