Cookie Policy
Enough browser storage to keep you signed in and remember your theme, plus Google Analytics and our Meta and X advertising pixels on the website if — and only if — you accept them. No session replay, and nothing at all in the CLI.
The short version
Local Keep AI uses the minimum browser storage required to keep you signed in, remember your interface preferences, and protect the account system from abuse. On the website we also use Google Analytics to understand how the site is used, and two advertising pixels — the Meta (Facebook) Pixel and the X (Twitter) tag — to measure whether our ads actually work, and only if you agree to them. All three are off until you accept the banner, you can decline and keep using everything, and declining changes nothing about how the product works. Both advertising pixels set an advertising cookie and can be used to show you our ads again elsewhere, which is why they sit behind the same consent as everything else. Nothing on this site is sold to a data broker, and there is no tracking of any kind inside the app or the CLI.
This page is about the web app
Cookies are a browser mechanism. The local-keep-ai-cli tool you install with pip does not use them — it stores an authentication token in a local configuration file on your own machine, and that token never travels through a browser. The iOS and Android apps use the platform's secure storage rather than cookies. Everything below applies to localkeep.ai in a browser.
Strictly necessary storage
These cannot be turned off without breaking the product, because they are what makes a signed-in session possible:
•
Session and authentication — a token that proves you are signed in, so you are not asked to reauthenticate on every page. Set when you sign in with Google or Apple; cleared when you sign out.
•
Sign-in flow state — short-lived values used during the OAuth handshake to match the response to the request you started. These expire within minutes of completing sign-in.
•
Security tokens — values used to prevent cross-site request forgery on actions that change your account or billing.
Preference storage
These remember how you like the interface. They live in your browser's local storage rather than being transmitted with every request, and losing them costs you nothing but a reset to defaults:
•
Theme — whether you chose light or dark. Stored locally under a single key; the default is dark.
•
Selected model — the model you last picked, so the chat does not reset your choice on reload.
•
Interface state — small things like whether the sidebar is collapsed.
Third parties we do allow
Two categories of third party can set storage on our domain, and both are functional rather than commercial:
•
Identity providers — Google and Apple, during sign-in only. They are the ones authenticating you; their own privacy policies govern what they do on their side.
•
Payment providers — PayPal, Apple Pay, and Google Pay, during checkout only. They handle payment credentials so that Local Keep AI never receives or stores your card details.
Beyond that: Google Analytics on the website only, and only with your consent — page views, which features are opened, your plan tier, and an account identifier so repeat visits are not double-counted. Alongside it, and behind the same consent, the Meta Pixel and the X tag record that you visited so we can tell which ads brought people here and show our ads to visitors again on those platforms. No session replay tool recording what you type, no embedded social buttons phoning home, and none of it in the CLI or the desktop app.
Controlling cookies yourself
Every major browser lets you view, block, and delete cookies and local storage per site, usually under privacy or site settings. Clearing Local Keep AI's storage signs you out and resets your theme and model preferences to defaults — nothing else is lost, and your account, conversations, and billing are unaffected. Blocking cookies for localkeep.ai entirely will prevent you from staying signed in, which means the web app cannot work. The CLI will continue to work regardless, since it does not depend on the browser.
Do Not Track
If you decline the banner, there is nothing to honour: no advertising pixel is loaded at all, and nothing follows you off this site. If you accept, the Meta Pixel and the X tag are cross-site by design — that is what lets us show our ads to people who have visited before — so declining the banner, not the Do Not Track header, is the control that actually stops it. Both are withheld entirely until you choose, and you can change your mind by clearing this site's storage.
Changes and contact
If we ever add a category of storage beyond what is described here, we will update this page and the revision date below before it ships. Questions about cookies, storage, or anything else on this page: info@localkeep.ai. For the fuller picture of what Local Keep AI collects and how to delete it, see our Privacy Policy.
Last updated: August 23, 2026