Cookie Policy
Last updated: September 25, 2026
The short version. Edgekeeper sets no third-party cookies of its own. What we store is one cookie that keeps you signed in, an anonymous id our own analytics use — written only if you allow it in the banner, and the control for changing your answer is in Section 5 — and a handful of browser-storage keys that remember your interface choices. The only third-party storage on the Service is Google's advertising, which is shown to free accounts and on our public articles, and never to paid subscribers. The complete list is below — all of it.
1. What these things are
A cookie is a small file a site asks your browser to keep and send back on later visits. Local storage and session storage do a similar job but are never sent to a server automatically — the page reads them in your browser. We use all three, and the table below labels which is which, because "we only use cookies for essential purposes" is a sentence that is often true and complete only because everything else was put in local storage instead.
First-party means set by edgekeeper.net. Third-party means set by another company whose code runs on the page — for us, that is Google's advertising and nothing else. We use no third-party analytics SDK: the product analytics described in Section 4 are our own, stored in our own database.
2. Everything we store, in full
| Name | What it does | Category | Lifetime | Type & party |
|---|---|---|---|---|
| sb-…-auth-token | Keeps you signed in and tells your account apart from everyone else’s. Without it the app cannot function at all. | Strictly necessary | Until you sign out or the session expires | Cookie · first-party |
| ek-recovery | Marks a session created by a password-reset link so it can only be used to set a new password, and nothing else, until you do. | Strictly necessary | Cleared the moment the new password is saved | Cookie (httpOnly) · first-party |
| ek_consent | Records your answer to the cookie banner — whether you allowed the one optional entry below — so we honour it and stop asking. | Strictly necessary | 180 days | Cookie · first-party |
| ek-anon | A random id with no name or email attached, so an anonymous page view can be joined to the account it later becomes. Only our own analytics read it, and it is written only if you allow it. | Analytics | Until you clear your browser storage | localStorage · first-party |
| ek-paywall-seen | Remembers that you have already been through the upgrade page’s introduction, so a second visit goes straight to the plans. | Preferences | Until you clear your browser storage | localStorage · first-party |
| ek-paywall-variant | Keeps the upgrade page’s layout consistent for you between visits while we compare two versions of it. | Preferences | Until you clear your browser storage | localStorage · first-party |
| ek-add-layout | Remembers whether you prefer the guided steps or the quick form when logging a trade. | Preferences | Until you clear your browser storage | localStorage · first-party |
| ek-onboarding-dismissed | Remembers that you dismissed the dashboard’s setup checklist, so it does not come back. | Preferences | Until you clear your browser storage | localStorage · first-party |
| ek-readiness-skipped | Remembers that you skipped today’s readiness check-in, so you are not asked again the same day. | Preferences | Holds one date; replaced the next day | localStorage · first-party |
| ek-setup-banner-dismissed-until | Hides the “finish setting up” banner for 24 hours after you dismiss it. | Preferences | 24 hours | localStorage · first-party |
| ek-risk-per-trade | Your own default risk-per-trade figure, kept in your browser so the position calculator and the import screen start where you left them. It is deliberately not stored on our servers. | Preferences | Until you clear your browser storage | localStorage · first-party |
| ek-paywall-exit-shown | Ensures the upgrade reminder on the upgrade page appears at most once per browsing session. | Preferences | Until the tab is closed | sessionStorage · first-party |
| Google advertising cookies, including __gads, __gpi and DoubleClick cookies | Serve, frequency-cap and measure the ads shown to free accounts and on our public articles. Set by Google’s ad script, not by us — we cannot read them. | Advertising | Set by Google, typically up to 13 months; see Section 5 for controls | Cookie · third-party (Google) |
That is the complete inventory. If we add a key, it is added to this table in the same change — this page is written from the code, not from a recollection of it.
3. What we do not do
- No third-party analytics, session-replay or heat-mapping SDK. None.
- No advertising or social pixels — no Meta pixel, no TikTok pixel, no LinkedIn or X tag.
- No cross-site tracking by us, and no sale or sharing of personal information as the CCPA/CPRA define those terms.
- No fonts loaded from a third party at page-view time: our typefaces are downloaded when the site is built and served from our own domain, so viewing a page sends no request — and no IP address — to Google Fonts.
- Nothing at all is stored by our /embed widget, which is the version of the drawdown calculator designed to run inside other people's pages. It renders no session, reads no cookie and writes nothing — that is what makes it safe to put in somebody else's page in the first place.
4. The one that is not strictly necessary
One entry in the table above is not needed to make the Service work, and we would rather name it than let it hide in a list. It is not written until you allow it. On your first visit a banner asks about it, switched off; nothing in this section is stored while that question is unanswered, or if you decline it.
ek-anon — first-party product analytics
A random id minted in your browser with no name or email attached. It lets us count that one visitor moved through the upgrade or cancellation flow rather than three separate people, and to join a visit to the account it becomes if you sign up. The events it labels are the ones described in the Privacy Policy §2: a screen name and a step, stored in our own database and never shared with an advertising network or any other third party.
5. Your controls
The banner, and changing your mind
The banner has two one-click options, side by side and the same size: allow the optional entry, or refuse it. There is no close button, because closing a box is not an answer either way — until you give one, nothing beyond the strictly necessary cookie is stored. Your answer is kept in ek_consent for 180 days and you are not asked again in that time, whichever way you answered. Refusing is remembered exactly as long as accepting.
Use the control below to see what you chose and change it. Switching it off does not only stop future writes: it deletes what had already been stored — the anonymous analytics id is erased from your browser.
Change this at any time. Switching it off also deletes what it had already stored.
Advertising
Ads are served by Google AdSense to free accounts and on our public articles. Paid Pro accounts are ad-free, which is the most direct control of all — no ad script loads on a Pro session, so no Google ad cookie is set. You can also opt out of personalized advertising at google.com/settings/ads, or across many networks at once at aboutads.info/choices. Visitors in the EEA, the UK and Switzerland are shown Google's own consent message before any ad personalization takes place and may decline it; you can read how Google uses information from sites that use its services.
Two separate controls, and we would rather say so than let you assume otherwise. Our banner governs the first-party entry in Section 4 and nothing else. Google's advertising cookies are set by Google's own script under Google's own consent message, shown in the regions that require one — so accepting or refusing ours does not change what Google does, and the links in the paragraph above are the controls for that half.
Your browser
Every browser can block or delete cookies and clear site storage, usually under Settings → Privacy. Clearing ours costs you nothing except the preferences in the table: you will be signed out, the interface choices reset to their defaults, and your risk-per-trade default is forgotten. Nothing in your journal lives in the browser — trades, rules and screenshots are all in your account, so clearing storage cannot lose them. Blocking the sign-in cookie specifically will stop the app working, which is what "strictly necessary" means in the table.
Sign out, or delete the account
Signing out clears the session cookie. Deleting your account (Settings → Danger zone) erases the data behind all of it — see Privacy Policy §9 for what survives deletion and why.
6. Changes and contact
We will update this page when what we store changes, and revise the date at the top. The Privacy Policy covers everything else we hold about you, including its own dated change history. Questions can be sent through the in-app Report / suggest form after signing in.