This policy explains what keynodex.com and the Keynodex Memory app (memory.keynodex.com) store on your device, why, and how you control it. It describes the site as it actually works today; if the code and this page disagree, the code is the bug.
1.0 The short version
1.1 In most places you are not tracked for analytics or advertising unless you turn those categories on. Both start off. Where the law allows it (today, the United States), product analytics and error reports start on behind a clear notice with a one-tap way to turn them off. Advertising never starts on. Section 5.9 explains the rule.
1.2 Your theme, language and cookie choices are stored on your device so the site works and remembers your preferences. Those are always on because the site cannot function without them.
1.3 You can change or withdraw your choices at any time from the cookie banner, the settings link in the footer, or your browser.
1.4 We do not sell your personal data, and we do not use advertising cookies for anyone unless you grant targeting consent.
2.0 What cookies and similar storage are
2.1 Cookies are small files a site asks your browser to keep. Local storage and session storage are similar: the browser holds small pieces of data for the site.
2.2 "Session storage" lives only in the current tab and is erased when the tab closes. "Local storage" and cookies can survive between visits until they expire or you delete them.
3.0 Strictly necessary storage (always on)
3.1 This storage is required to deliver the site and your privacy choices. It is not used to profile you.
| Key | Type | Purpose |
|---|---|---|
knx-consent-v2 |
localStorage | Records whether you accepted or rejected non-essential cookies |
knx-consent-prefs-v1 |
localStorage | Records your granular performance / functional / targeting choices |
| language cookie | cookie, SameSite=Strict |
Remembers the language you selected |
| sidebar state | cookie | Remembers whether the docs sidebar is open |
| Cloudflare Turnstile | cookie / challenge | Security check for forms, stopping bots and spam |
3.2 Keynodex Memory app (memory.keynodex.com). The app needs these to sign you in and keep you signed in.
| Key | Type | Purpose |
|---|---|---|
km_session |
cookie, HttpOnly, Secure, 24 hours |
Keeps you signed in to the Memory app |
km_google_oauth_state |
cookie, HttpOnly, Secure, 10 minutes |
Protects the Google sign-in step from forged requests; cleared when sign-in finishes |
act-reloads |
sessionStorage | Counts how often the setup checklist refreshed itself in this tab, so it stops after a few tries |
4.0 Functional storage (always on)
4.1 Functional storage powers site features you can see. It is not used for advertising or analytics.
| Key | Type | Purpose |
|---|---|---|
keynodex-theme |
localStorage | Remembers light or dark mode |
kx-rep-panel |
localStorage | Remembers whether the side panel of the chat on keynodex.com/rep is open or closed |
kx-kept-chat |
sessionStorage | Keeps your chat with the Rep on keynodex.com/rep in this tab, so it is still there when you come back to the page. Removed when you choose "New chat" and when the tab's session ends (normally when you close the tab). A chat whose last message is more than 24 hours old is not shown again and is removed the next time you open the page |
5.0 Analytics
5.1 Analytics is off by default. Google Analytics 4, Google Tag Manager and the session activity sent to Rep (5.2 and 5.3) never load or fire until you grant performance consent (the "Performance (Analytics)" switch in the cookie settings). PostHog analytics and error reports (5.7 and 5.8) follow the region rule in 5.9.
5.2 Google Analytics 4, via Google Tag Manager. Google Tag Manager loads in consent-denied mode and Google's Consent Mode keeps analytics storage denied until you grant performance consent.
5.3 Session activity sent to PingRep. When performance consent is granted,
keynodex.com sends page views, dwell time, CTA click events and a periodic
session heartbeat to PingRep's tracking API at api.pingrep.com. PingRep is our
infrastructure provider and processes this as a service provider to produce
aggregate performance metrics for keynodex.com.
| Key | Type | Purpose |
|---|---|---|
kn_tracking_session_id |
sessionStorage | Random session identifier for the current visit; not linked to you across sessions |
kn_tracking_session_meta |
sessionStorage | Session creation and last-seen timestamps |
5.4 The session identifier lives in session storage only. It is erased when the tab closes, when consent is withdrawn, and when the session is idle for 30 minutes or older than 4 hours. We keep no cross-session identifier for keynodex.com visitors.
5.5 The session activity payload is minimized to the page path, the referring host, UTM campaign parameters and the session identifier. It does not include your screen size, timezone, connection type, touch support or device fingerprint.
5.6 Withdrawing performance consent removes the session keys, stops all tracking in the open tab, and returns Google Consent Mode to denied.
5.7 PostHog, product analytics. When analytics is allowed (5.9),
PostHog's US cloud, hosted in the United States, receives a small set of
events: a page was viewed (the page path, campaign parameters from the link,
such as utm_source, and the host of the site that sent you, on the first page
of a visit), a call to action was clicked, the contact form was sent or was
rejected (with a reason code such as which field failed, never what you typed),
the waitlist was joined, and clicks on links and buttons (the kind of element
and where it sits on the page, with its text and link query removed). Each event
also carries a random visit identifier and your browser, operating system and
device type. We do not send what you type into forms or the text of pages, and
we do not record sessions. Our PostHog project discards IP addresses on arrival
and we switch off its location lookup, so neither is stored with an event.
Session replay, heatmaps, surveys and feature flags are off. PostHog keeps
events for 12 months.
| Key | Type | Purpose |
|---|---|---|
ph_<project key>_posthog |
sessionStorage | PostHog's random visit and session identifiers; erased when the tab closes, so there is no cross-visit identifier |
5.8 PostHog, error reports. PostHog receives a report when something breaks. From your browser, this happens only when analytics is allowed (5.9): the error message, the stack (which part of our code failed), the page path without any query, your browser and operating system, and the version of our site. From our own server, it happens whatever you choose, because the report is about our server failing, for example when a form could not be sent. Before a report leaves, we remove cookies, headers, request content, query strings, IP addresses and user identifiers, and we replace email addresses and phone-like numbers in messages. Error reports go to the same PostHog project as analytics, in its US region, and are kept for 12 months.
5.9 The region rule. Whether PostHog analytics and error reports in your browser start on or wait for your yes depends on where you appear to be.
- Notice regions (today: the United States). They run unless you turn them off. A notice at the bottom of the page says so and offers "Turn off" and "Your privacy choices". You are treated as in a notice region only when your country, read from your IP address by our host, and your browser's time zone agree.
- Everywhere else, and whenever we cannot tell. Nothing optional runs until you choose Accept. This includes the EU, the UK and Canada.
- Global Privacy Control. If your browser sends it, you are always treated under the opt-in rule.
- Session replay and advertising tags are opt-in everywhere.
We read your country once per page load to apply this rule. Our site does not store it.
5.10 You can turn analytics off at any time from the notice, the banner or the cookie settings. PostHog and in-browser error reports stop at once, and your choice is kept for up to 6 months (section 8.0).
5.11 Sign-up source in the Memory app. When you open certain pages of the Memory app before you have an account, the app may store how you arrived, so it can record your sign-up source when you sign up (Privacy Policy 4.2.4). It sets this cookie only when your country, read from your IP address by Cloudflare, is the United States and your browser does not send Global Privacy Control. Everywhere else, and whenever we cannot tell your country, it sets nothing. The cookie holds short labels only, never a full web address, search terms, your email address or your IP address, and it is cleared when you sign up.
| Key | Type | Purpose |
|---|---|---|
km_ft |
cookie, HttpOnly, Secure, up to 30 days |
Remembers how you first arrived until you sign up |
6.0 Advertising — only with your consent
6.1 Advertising and personalization tags are off by default and stay off until you grant targeting consent.
6.2 Advertising tags are configured inside Google Tag Manager (for example,
Meta). Google Consent Mode holds ad_storage, ad_personalization and
ad_user_data at denied until targeting consent is granted.
6.3 If your browser sends a Global Privacy Control (GPC) signal, targeting is forced off and cannot be turned on while GPC is active. Analytics remains off unless you explicitly enable it yourself.
7.0 Managing your choices
7.1 Cookie banner. On your first visit, choose "Accept", "Reject" or "Manage". Rejecting turns off everything optional. In a notice region (5.9) you see a short notice instead, with "Turn off" and "Your privacy choices".
7.2 Cookie settings. Reopen the settings any time from the footer ("Your privacy choices") or the link in the banner, and change individual categories.
7.3 Browser controls. You can delete or block cookies in your browser. Blocking strictly necessary storage may break parts of the site, such as remembering your privacy choices.
7.4 Do Not Track. Browser Do Not Track signals are not standardized. We honor Global Privacy Control, which is the standard signal with legal weight in the places we operate.
8.0 How long your choices last
8.1 Your consent choice is kept for up to 6 months. After that the record expires: the tracker is torn down, Google Consent Mode returns to denied, and the banner asks you again.
9.0 Service providers involved
| Provider | Role | Data |
|---|---|---|
| Google (Tag Manager, Analytics, ads tags) | Analytics and advertising tags, loaded only with consent | Page usage, ad interactions |
| PingRep (api.pingrep.com) | Tracking ingest for aggregate performance metrics, only with performance consent | Session id, page path, referring host, UTM parameters |
| Cloudflare (Turnstile) | Form security | Challenge and security signals |
| PostHog (US cloud) | Product analytics and error reports. Analytics and browser error reports when analytics is allowed; server error reports always | Page path, campaign parameters, referring host, click events, random visit id, browser, operating system, device type; for errors, the error message, stack trace and site version; no IP address, cookies or user id |
| Vercel | Hosting | Request logs needed to serve the site; its request header also tells us your country for the region rule (5.9) |
9.1 A current list of the processors the site uses, with what each one handles, is maintained in the Privacy Policy.
10.0 Changes to this policy
10.1 When we change how storage works, we update this page and its date. If the change is material, the banner will ask for your choice again.
11.0 Contact
11.1 Questions about this policy: [email protected] 11.2 Data protection requests (access, deletion, correction): [email protected]. Requests submitted to [email protected] are acknowledged within 3 business days and processed within 30 calendar days.