Privacy Policy
Last updated: October 21, 2026 · what changed
1. Introduction & scope
Edgekeeper ("Edgekeeper", "we", "us", "our") is a trading journal and discipline-tracking service for traders, operated by an individual owner and available at edgekeeper.net (the "Service"). This Privacy Policy explains what information we collect when you visit or use the Service, how we use and protect it, who we share it with, and the rights and controls available to you. It applies to visitors, free-tier users, and Pro subscribers alike. By creating an account or using the Service, you acknowledge the practices described in this policy. If you do not agree with it, please do not use the Service.
2. Information we collect
We collect only what is needed to operate, secure, bill for, and improve the Service:
- Account data — your email address, an optional display name, an optional username, and a password. Your password is never visible to us or stored in readable form; it is hashed and managed by our authentication provider. If you answer the optional questions shown after sign-up (which markets you trade, your experience, whether you trade a prop account, your goal), those answers are stored on your authentication profile and are used to order the instrument list and tailor what the app suggests first. Stored alongside them is a record of what you agreed to at sign-up and when: that you confirmed you are 18 or older and accepted the Terms and this policy, and whether you asked for the optional product email described in Section 3. We keep the date because a consent we cannot evidence is not one we should be acting on.
- Journal data — the trades, notes, setups, tags, moods, written trading rules, daily check-ins, missed-trade entries, imported broker CSV files and prop-firm account rules you enter or import into Edgekeeper, together with any chart screenshots you upload. Screenshots are held in a private storage bucket and are only ever served to your own signed-in session through short-lived signed links. This data belongs to you; we store and process it solely to operate the Service for you.
- Payment data — if you subscribe to Pro, payment is handled entirely by Whop, our payment processor. Your full card number never touches our servers. We retain only what Whop reports back to us, such as your subscription status, billing period dates, trial dates, and any promotion code you redeemed.
- Alert settings — if you switch on alerts or digests, we store your preferences, your quiet hours and your time zone. Alerts and digests are delivered by email only, and you can switch any of them off at any time from Settings.
- Edgekeeper Education (the course) — your lesson progress, your answers and scores on checks and tests, your study-plan answers, the date and version of the course terms you accepted, and your course plan. To apply the course's fair-use limits we keep a short log each time a lesson video link is issued: which lesson, when, and a random id for the browser (not a fingerprint and not your IP address). Each video shows your account's email faintly on screen while you watch; that mark is drawn in your browser and not stored.
- Usage & product analytics — we record first-party product events: which screens of the upgrade, cancellation, onboarding or public-tool flows were viewed and which options were selected, along with answers you choose to give in the cancellation and deletion surveys. Events from visitors who are not signed in are recorded against a random browser-generated id (see the storage table below) and no account. These events are stored in our own database, are used only to improve the product, and are never shared with advertising networks or any other third party.
- Technical logs & abuse counters — standard server logs (such as request timestamps, IP addresses, and error traces) generated by our hosting provider, used to keep the Service running, diagnose problems, and prevent abuse. We also keep short-lived rate-limiting counters in our own database so that a single visitor cannot flood a public endpoint; those counters are keyed to a hashed form of the IP address and are pruned on a schedule (see Section 8).
- Cookies & browser storage — the complete inventory is below. Everything Edgekeeper itself sets is first-party; the only third-party storage on the Service comes from Google's advertising, described in Section 5. Exactly one entry in that table is not needed to make the Service work — the anonymous analytics id — and it is not written unless you allow it in the banner shown on your first visit; until you answer, and if you decline, it is not stored at all. You can change that answer at any time, and switching it off also deletes what it had already stored. The same inventory, with lifetimes and the controls available to you, is set out at length in our Cookie Policy.
| Name | What it does | Category | Lifetime | Party |
|---|---|---|---|---|
| sb-…-auth-token or sb-ek-auth | Keeps you signed in. Without it the app cannot tell your account from anyone else’s. Once the course has its own address, one cookie (sb-ek-auth) signs you in on edgekeeper.net and education.edgekeeper.net together. | Strictly necessary | Until you sign out or the session expires | First-party (cookie) |
| ek-recovery | Marks a session that was created by a password-reset link, so it can only be used to set a new password. | Strictly necessary | Cleared the moment the new password is saved | First-party (cookie, httpOnly) |
| ek_consent | Records your answer to the cookie banner, so we know what we may store and do not ask you again. | Strictly necessary | 180 days | First-party (cookie) |
| eke-dev | Course only: a random id for this browser, so the course can apply its limit of two devices playing videos at once. | Strictly necessary | 400 days | First-party (cookie, httpOnly) |
| eke_sample_pass | Course only: carries a pass of lesson 1.1’s check, taken before you had an account, into the account you then create. | Strictly necessary | 30 days | First-party (cookie, httpOnly) |
| eke-mode, eke-volume, eke-resume:…, eke-gym-fluency, eke-welcome-strip, ek-tour:… | Course and tour preferences kept in this browser only: light or dark, video volume, where you stopped in each lesson, your Chart Gym speed, a dismissed welcome note, and whether you finished the guided tour. | Preferences | Until you clear your browser storage | First-party (localStorage) |
| 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 set if you allow it. | Analytics | Until you clear your browser storage | First-party (localStorage) |
| ek-paywall-seen, ek-paywall-variant, ek-add-layout, ek-onboarding-dismissed, ek-readiness-skipped, ek-setup-banner-dismissed-until, ek-risk-per-trade | Remember interface choices: which layout you prefer, what you have already seen or dismissed, and your own risk-per-trade default. | Preferences | Until you clear your browser storage | First-party (localStorage) |
| ek-paywall-exit-shown | Ensures the upgrade reminder on the upgrade page is shown at most once per browsing session. | Preferences | Until the tab is closed | First-party (sessionStorage) |
| Google advertising cookies, including __gads, __gpi and DoubleClick cookies | Serve, cap and measure the ads shown to free accounts and on our public articles. Set by Google’s ad script, not by us. | Advertising | Set by Google; see Section 5 for controls | Third-party (Google) |
3. How we use information
We use the information described above to:
- provide, maintain, and secure the Service, including authentication and enforcement of plan limits;
- process subscriptions, trials, discounts, pauses, and cancellations through Whop;
- send service (transactional) email you would expect from a paid product — password resets, email-change confirmations, a reminder before a free trial ends, a written confirmation when you cancel, and a notice if a payment fails. These are not marketing, they are part of running your account, and they are not covered by the marketing opt-out below;
- send a short onboarding and product email sequence — a welcome and a few messages about getting started and the features you have not opened yet. These are promotional in nature, and they are sent only to accounts that asked for them: the box on the sign-up form is optional and starts unticked, leaving it alone means we send you none of this, and accounts created before that box existed are not enrolled either. That box controls this sequence and nothing else: your plan, your data and the service email above are the same either way. Every message carries a one-click unsubscribe link, and unsubscribing stops them immediately. Paid subscribers are never sent the one message in it that is about Pro;
- deliver the alerts and digests you switch on yourself (a daily brief, a weekly review, a prop-rule breach alert) by email. Nothing is sent until you save alert preferences — the settings you save are the opt-in — and you can switch them off at any time;
- run the optional AI features when you ask for them: the written weekly review (which sends that week's already-computed figures) and the AI CSV rescue (which sends part of the broker file you uploaded, so a file our own parser could not read can still be imported). Both are opt-in, both are described in Section 6, and neither runs on its own;
- understand, in aggregate, how features like the upgrade, cancellation and public-tool flows are used, so we can improve them;
- respond to bug reports and feature suggestions you submit;
- detect, prevent, and address fraud, abuse, and violations of our Terms of Service (for example, attempts to circumvent free-tier limits or trial eligibility).
We do not sell your personal data, we do not share your journal data with other users, and we never use your journal data for advertising or to train any AI model.
4. Legal bases for processing
Where the EU/UK General Data Protection Regulation (GDPR) or similar laws apply, we process your information on the following bases: performance of a contract (providing the Service you signed up for, including billing); legitimate interests (securing the Service, preventing abuse — including the trial-abuse record described in Section 9 — and improving the product through first-party analytics, balanced against your rights); consent (optional alert channels, marketing email, and personalized advertising for visitors in regions where consent is required — see Section 5); and legal obligation (retaining billing records where the law requires it).
5. Advertising
Free-tier accounts may be shown advertisements, as may our public articles. Paid Pro accounts are ad-free.
Our advertising is served by Google AdSense. Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or other websites. Google's use of advertising cookies (such as the DoubleClick cookie) enables it and its partners to serve ads to you based on your visits to this site and/or other sites on the Internet.
You can opt out of personalized advertising:
- via Google's Ads Settings at www.google.com/settings/ads; or
- for many participating ad networks at once, at www.aboutads.info/choices.
Visitors in the European Economic Area, the United Kingdom, and Switzerland are shown a consent message before any ad personalization takes place, and may decline personalized ads entirely. You can read more about how Google uses information from sites that use its services.
If Edgekeeper ever includes affiliate offers or sponsored promotions, they will always be clearly labeled as such, and we may earn a commission if you take up such an offer.
6. Service providers (subprocessors)
Edgekeeper is built on a small number of established providers, each of which processes data only as needed to perform its role and under its own privacy and security commitments. This is the complete list of places your data can go:
| Provider | What it does for us | What it receives |
|---|---|---|
| Supabase | Database, sign-in, and private storage for chart screenshots. | Your account details, everything in your journal, and any screenshots you upload. |
| Whop | Payments, subscriptions, trials, and the billing page. | Your email address and card details (entered on Whop, never held by us) plus your subscription history. |
| Vercel | Application hosting, content delivery, and server logs. | Ordinary request data, including your IP address and browser user-agent. |
| Cloudflare (R2) | Private storage and delivery of the course’s lesson videos. | Ordinary request data, including your IP address, when your browser plays a lesson video through a personal link we issued. |
| Resend | Delivery of the emails described in Section 3. | Your email address and the contents of the message being sent to you. |
| Google AdSense | Advertising on free accounts and public articles (Section 5). | Ad cookie identifiers, your IP address, and the page being viewed. Never your journal. |
| OpenRouter, and the model providers it routes to (Z.ai’s GLM, with Anthropic’s Claude as the backup) | The optional AI features: the written weekly review, the weekly Coach, reading a screenshot of your trade history into trades, and the AI rescue for a broker CSV our own parser could not read. | Only when you use those features. For the weekly review: that week’s already-computed figures — no individual trades, no names, no email address. For the Coach: the same kind of computed figures and patterns, plus the trading profile and answers you type into it. For screenshot capture: the screenshots you choose to upload. For the CSV rescue: part of the contents of the file you uploaded (the header row and a bounded sample of data rows), which is the only way a file can be read at all. We do not use your data to train any model; every request asks OpenRouter to route only to providers that do not collect or keep prompts, and is processed under OpenRouter's own privacy terms. If you never use either feature, nothing is ever sent. |
| Brokers you connect (MetaTrader via our Bridge EA, cTrader, OANDA, Alpaca, Interactive Brokers) | Only if you connect one (a Pro feature): your trades, deposits, withdrawals and balance flow FROM that platform TO us, into your Inbox to confirm. | We send the platform nothing but the request for your own history, with the access you granted. Tokens are encrypted at rest, never shown to your browser, and erased the moment you disconnect or delete your account. We never place, change or cancel an order. |
| Edgekeeper itself (first-party analytics) | The product analytics described in Section 2 — we run our own rather than embedding a third-party analytics SDK. | A page or step name and the anonymous browser id. It stays in our database; there is no analytics vendor to share it with. |
Fonts are not a third party here. The three typefaces the Service uses are downloaded once 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.
7. When we share information
We do not sell or rent your personal data. We share information only in these limited circumstances:
- Service providers — as described in Section 6, to the extent needed for them to perform their function.
- Legal compliance & protection — if we believe in good faith that disclosure is required by law, regulation, legal process, or an enforceable governmental request; or where necessary to investigate or prevent fraud or abuse, to enforce our Terms of Service, or to protect the rights, property, or safety of Edgekeeper, our users, or the public.
- Business transfers — if Edgekeeper is involved in a merger, acquisition, financing, or sale of assets, your information may be transferred as part of that transaction; this policy will continue to apply to it, and we will notify you of any material change in ownership or use of your personal data.
8. Data retention
We keep your account and journal data for as long as your account is active. When you delete your account (Section 9), everything in the first three rows below is erased immediately. The rows after those either outlive an account deliberately or were never tied to one in the first place, and each is listed here so there are no surprises.
| What | How long we keep it |
|---|---|
| Account, journal, rules, check-ins and screenshots | While your account exists. Erased from our database and our storage bucket when you delete the account. |
| Screenshots uploaded for capture (reading trade history into trades) | 180 days, then deleted automatically. A copy attached to a trade you confirmed stays with that trade. |
| Broker connection tokens and Bridge EA keys | Until you disconnect or delete your account, when they are erased at once. If a Pro plan ends, the connection pauses and its token is erased 30 days later unless Pro resumes. |
| Product analytics events tied to your account | Deleted with your account. Events recorded before you signed up carry no account link and stay in aggregate. |
| Alert preferences | Until you change or disconnect them, and deleted with your account. |
| Course progress, answers, study plan and course plan | Until you delete your course data or your account. A canceled or refunded plan keeps your progress for 24 months in case you come back. |
| Course video-link log (lesson, time, random browser id) | Read for the last 30 days only; deleted with your course data or your account. |
| Course terms acceptances (which terms, which version, when) | Three years, as the auto-renewal laws ask; they hold no email or IP and lose their link to you when your account is deleted. |
| Billing and tax records | Held by Whop for the period tax law requires, typically several years, independently of your Edgekeeper account. |
| Deletion-survey record | Kept after the account is gone: the reason you chose, your optional comment, and the plan you were on. It is what tells us why people leave. It does not keep your email address — only a one-way hash of it, so two answers can be told apart without the record being readable or contactable. |
| Trial-abuse record (see Section 9) | Kept indefinitely, and it is a one-way hash of an email address rather than the address itself. |
| Rate-limiting counters | Keyed to a hashed form of the IP address, never the address itself, and pruned on a schedule once the window they count has passed. |
| Server logs | Retained only for the short period our hosting provider keeps them. |
9. Deletion, export & your controls
Delete your account yourself — no support ticket needed
You can delete one product's data or your whole account at any time, from either product's Settings. Deleting your journal erases your journal data and keeps your account and course; deleting your course data erases your course progress and plan and keeps your account and journal; ticking the box to close your whole account does all of the following. Deletion is immediate and irreversible: all of your trades, setups, prop accounts, rules, check-ins, screenshots, alert preferences, reports, and cancellation-survey answers are erased from our database and storage, any active subscription or trial is canceled at the same moment so no further billing can occur, and your login is removed. Two narrow records survive, and they are named below. No refunds are issued for unused subscription time.
Export your data first
You can export your full trade history to CSV from within the app at any time, and we recommend doing so before deleting your account, since deleted data cannot be recovered.
Records that deliberately survive deletion
We think it is better to name these than to let you discover them:
- The trial ledger. Our free trial is once per person. When a trial starts we store a salted, one-way hash of the email address — never the address itself — in a table with no link to your account, so it survives deletion by design. It cannot be reversed into an email address, cannot be used to contact anyone, and exists only so that deleting an account and signing up again does not hand out an unlimited supply of free trials. The legal basis is our legitimate interest in preventing abuse of a paid product.
- The deletion-survey record. If you tell us why you are leaving, that answer is kept after the account is gone — otherwise the answer would be deleted along with the reason it was given. It records the reason, your optional comment and the plan you were on; your email address is not kept, only a salted one-way hash of it, computed separately from the trial-ledger hash above so the two cannot be matched to each other. See Section 8.
- Course terms acceptances. If you bought a course plan, the record of which terms you accepted, in which version and when, is kept for three years because auto-renewal laws require proof of consent. It holds no email address or IP and is unlinked from you when your account is deleted. The legal basis is our legal obligation.
If you would like the trial-ledger or survey record removed, or you object to this processing, contact us as described in Section 14 and we will deal with it.
Other controls
You can correct your profile information in Settings, switch alerts and their channels on or off at any time, unsubscribe from the product email sequence with one click from any of those emails, cancel or pause your subscription in-app without contacting anyone, and manage advertising personalization as described in Section 5.
10. Your privacy rights
Depending on where you live, you may have specific legal rights over your personal data, including the right to access, correct, export (data portability), restrict, object to processing of, or delete it. Under the GDPR (EU/UK) these rights apply broadly; under the California Consumer Privacy Act (CCPA/CPRA) you additionally have the right to know what personal information we collect and the right not to be discriminated against for exercising your rights. We do not sell or share your personal information as those terms are defined under the CCPA. Most rights can be exercised directly through the in-app tools described in Section 9; for anything else, contact us as described in Section 14 and we will respond within the timeframe required by applicable law.
11. Security
We take reasonable technical and organizational measures to protect your information, including encryption of data in transit (TLS), database row-level security so that your records are only ever readable by your own authenticated account, a private storage bucket for screenshots that serves them only through short-lived signed links, hashed password storage, and payment handling that keeps card data entirely within Whop's infrastructure. No method of transmission or storage is completely secure, and we cannot guarantee absolute security; if we learn of a breach affecting your personal data, we will notify you as required by applicable law.
12. International data transfers
Our service providers store and process data primarily in the United States. If you use the Service from outside the United States, you understand that your information will be transferred to and processed in jurisdictions that may have different data-protection laws than your own. Our providers rely on recognized transfer safeguards (such as standard contractual clauses) where required.
13. Children & changes to this policy
Edgekeeper is not directed at, and may not be used by, anyone under the age of 18. Creating an account requires you to confirm that you are 18 or older, and that confirmation is recorded with the account (Section 2). We do not knowingly collect personal information from minors; if we learn that we have, we will delete it.
We may update this policy from time to time as the Service evolves or the law changes. When we do, we will revise the "Last updated" date at the top of this page and add a line to the change history at the foot, so you can see what actually changed rather than having to re-read the whole document. Your continued use of the Service after an update constitutes acceptance of the revised policy.
14. Contact
Questions about this policy, or a request about your data, can be sent to us through the in-app Report / suggest form after signing in. We read every submission. If you have already deleted your account and cannot sign in, a dedicated contact address is being set up and will be published here; until then, send the request from the email address the account used and we will act on it.
15. What changed
Both of our legal pages promise that material changes will be surfaced rather than quietly swapped in. This is where that promise is kept.
| Date | What changed |
|---|---|
| October 21, 2026 | Added broker connections (Pro): the platforms you connect, what flows from them and how their tokens are kept (Sections 6 and 8). Section 6 now also names the weekly Coach and screenshot capture among the optional AI features, and Section 8 gives the 180-day limit on capture screenshots. |
| October 20, 2026 | The optional AI features now run on Z.ai's GLM model through OpenRouter, with Anthropic's Claude as the backup if the first does not answer; DeepSeek is no longer used. Every request asks OpenRouter to use only providers that do not collect or keep prompts (Section 6). What is sent is unchanged. |
| October 19, 2026 | Payments are now processed by Whop instead of Stripe. Whop replaces Stripe as the payment provider in Sections 2, 3, 6, 8 and 11; what it receives is unchanged. |
| October 13, 2026 | Telegram is no longer offered as an alert channel; alerts and digests are delivered by email only, and Telegram was removed from the provider list in Section 6. Added Edgekeeper Education: what the course collects (Section 2), Cloudflare as the private store for lesson videos (Section 6), course retention rows (Section 8), deleting one product's data without closing the account, and the course terms record that survives deletion (Section 9); the course's cookies and browser storage were added to Section 2 and the Cookie Policy. |
| September 25, 2026 | Accuracy revision. Added the full cookie and browser-storage inventory (Section 2), turned the provider list into a complete subprocessor table (Section 6) — which now names the AI provider used by the optional weekly write-up and CSV rescue, the Telegram alert channel, and our screenshot storage — split email into service mail versus the product sequence you can unsubscribe from (Section 3, replacing a line that said we send no promotional email at all), detailed retention row by row (Section 8), named the two records that survive account deletion (Section 9), and started this change history. The one non-essential storage in Section 2, the anonymous analytics id, also stopped being automatic on this date: it is now written only if you allow it in the cookie banner, and the Cookie Policy carries a control for changing that answer later. On the same date the deletion-survey record stopped keeping the email address of a closed account — it now holds a one-way hash instead, and the addresses recorded before this change were erased. The product email sequence in Section 3 also became opt-in on this date: it is sent only to accounts that ticked the optional box on the sign-up form, which starts unticked, and it is no longer sent to anyone who signed up before that box existed. |
| July 13, 2026 | Full rewrite into the current 14-section structure: collection categories, GDPR legal bases, the advertising disclosures Google requires, the provider list, retention, self-serve deletion and export, and CCPA/CPRA rights. |