Cookies are small text files a website asks your browser to keep. Many modern apps — including KortexHQ — mostly use other kinds of browser storage instead. This page lists both, so you can see exactly what is kept on your device and why.
1. Summary
- KortexHQ's own code uses no advertising or marketing cookies and adds no advertising trackers.
- Every page loads its fonts from Google Fonts (fonts.googleapis.com and fonts.gstatic.com). Your browser connects to Google's servers to fetch them, which gives Google your IP address and browser details; KortexHQ does not set a cookie for this. See Google's privacy policy.
- KortexHQ uses browser storage (local storage, session storage and IndexedDB) to keep you signed in, save on-device work and remember small settings. These are needed for the features to work.
- The platform that hosts the published website adds a page-analytics script that sets a short-lived cookie, and an error/event script. Our network provider sets a bot-protection cookie.
- Because we don't use optional cookies in our own code, we don't show a cookie banner asking you to “accept all.”
2. Storage KortexHQ uses
| Name or pattern | Type | Purpose | When set · how long | Party |
|---|---|---|---|---|
sb-…-auth-token | Local storage | Keeps you signed in to your account | When you sign in · until you sign out or clear site data | First party (Lovable Cloud sign-in) |
kortexhq-local-preview, kortexhq-account-… | IndexedDB | Saves on-device projects, files, notes, styles and preferences | When you use the workspace · until you delete them or clear site data | First party |
kx-draft:…, kx-pending:…, kx-autosend:… | Session/local storage | Keeps an unsent message and an in-progress reply safe if the page reloads | When you write or send · cleared after it is saved | First party |
kx:village:req:… | Local storage | Reconnects you to a Prompt Village creation already in progress | When you start a creation · cleared when it finishes | First party |
kortex.village.returnHint.v1 | Local storage | Offers a “Continue your creation” link after you sign in (public tool name and time only) | When you sign in from a creation · up to 24 hours | First party |
kortex.village.motion.v1 | Local storage | Remembers whether you paused cover animations | When you press Pause or Play · until changed or cleared | First party |
kortex.files.layout, kortex.files.dir | Local storage | Remembers your Files view | When you change it · until changed or cleared | First party |
3. Storage added by hosting and network providers
| Name or pattern | Type | Purpose | When set · how long | Party |
|---|---|---|---|---|
session-id | Cookie (may also use browser storage) | Hosting page analytics: groups page views and performance measurements into one visit | On page load · about 30 minutes | Lovable (hosting), on our domain |
Hosting error/event script | Script; we have not confirmed it stores anything | Reports page errors and events to the hosting platform | On page load | Lovable (hosting) |
__cf_bm | Cookie, HttpOnly | Bot protection and traffic security | On page load · about 30 minutes | Cloudflare |
These are added by the platform, not by KortexHQ's code, so we can't switch them off for you from inside the app. We are confirming their exact settings with the provider and will update this table if they change.
4. Payment pages
If you start a checkout or open billing management, you go to a page hosted by Stripe, which sets its own cookies for fraud prevention and to run the payment. See Stripe's privacy policy at stripe.com/privacy.
5. How to clear or control storage
- Sign out from your workspace to remove the sign-in token from this browser.
- In Settings, you can delete preferences and all on-device data. This permanently erases on-device work that isn't saved anywhere else — it does not affect your account.
- Your browser's settings let you clear cookies and site data for kortexhq.com, block cookies, or use a private window. Clearing site data signs you out and permanently erases on-device work.
Questions: team@aimasterminds.com.