Cookie Policy

EdgeFlow stores a small number of cookies and similar items (browser storage, “localStorage”) on your device. This page lists each one and explains how to control them, in line with the EU ePrivacy Directive, Belgian law and CCPA/CPRA disclosure principles. EdgeFlow uses no advertising cookies, no session recording and no cross-site tracking.

1. Strictly necessary

Needed for what you ask the service to do. Set without asking, as EU law allows.

• ee_token — your login session (JWT). localStorage. The login inside it expires after 30 days; it is removed when you log out.
• ee_account_id — remembers which trading account is currently active. localStorage.
• af_token — your login to the affiliate portal, only if you are an affiliate. localStorage.
• cookie_consent_v1 — remembers your cookie choice so we don't ask again. localStorage. Kept until you change your choice (button below) or clear your browser's site data. If you reject, this is the only thing we write: it is the record of your rejection, and without it we would have to ask you again on every page.
• locale — the language you picked, only once you pick one. Cookie. Lifetime: 12 months.
• Stripe cookies (during checkout) — fraud prevention, set by Stripe. See Stripe's cookie policy.

2. Remembered choices in the app

These keep the app the way you left it. They are stored in your browser as you use EdgeFlow, without asking, and they stay on your device: our server never reads them. You can remove all of them at any time by clearing your browser's site data for https://youredgeflow.com.

• ee_onboarding_done, ee_user_prefs, ee_dismissed, flowguide-…, flow_last_greeting, ef_weekly_reminder — which introductions, tips and reminders you have already seen or closed, and your display preferences. localStorage.
• edgeflow.learn.…, edgeflow.flow.open — which explanations and panels you opened or closed. localStorage.
• edgeengine_account_balance / display_mode / risk_per_r — how you want results shown (unit display, risk sizing). localStorage.
• edgeflow-trade-prefill — your most recent Add-Trade values, for faster entry. localStorage.
• edgeflow.edgeBuilder.tradeModes, ee_discovery_journey::… — which trades Edge Builder counts, and where you are in Edge Discovery. localStorage.
• edgeflow.edgeBuilder.frozenPlans.v1 — the plans you froze in Edge Builder. localStorage.
• tradingcircle_accounts / tradingcircle_active_account — an older copy of your trading-account list and selection. localStorage.
• pendingCheckout — remembers the plan you selected if you were mid-checkout. Cleared after checkout.

2a. Partner referral

When you arrive through a partner's link, we remember which partner sent you, so they are credited and you get their discount. In the EU, the EEA, the UK and Switzerland we store this only if you allow partner-referral cookies in the banner; elsewhere it is stored without asking. If you say no, nothing is stored, and a partner code you type at checkout still counts. The banner asks again only when you arrive through a partner link.

• ef_ref — the partner code, as a first-party cookie for 60 days. Set by our server after it checked that the partner is active. Read at sign-up and checkout. A code you type at checkout counts instead. Landing on another active partner's link replaces it.
• ef_referral_code, ef_referral_click_… — the same code in localStorage, sent with your sign-up or checkout, and a note that the click was already counted. Cleared when you start a checkout; landing on another partner link replaces it.

3. Analytics

We count every visit, so we can see how many people reach the site and which pages they read. Your answer to the banner does not decide whether we count. It decides how.

If you have not accepted analytics

That covers both rejecting and simply not answering. We count the visit without writing anything to your device: no cookie, no browser storage, no identifier of any kind. There is nothing left behind for us — or for anyone else — to recognise you by on your next visit.

Our analytics tool, PostHog, receives which page was opened, where the link came from, and — as every web server does — the IP address your browser connects from. We send nothing alongside it that points to you: no cookie, no number stored on your device, and no link to your EdgeFlow account, even while you are logged in. PostHog receives that address on its own servers in the European Union and we use it for nothing but the count. EdgeFlow itself never sees or stores your IP address for analytics, and because nothing is kept on your device, a visit on another day cannot be joined to this one. Legal basis: our legitimate interest in knowing how many people use the site (Art. 6(1)(f) GDPR). No consent is required for this under the ePrivacy rules, because nothing is read from or written to your device.

If you accept analytics

Then PostHog also stores the items below, which is what lets us see a visit as one journey instead of as unconnected pages, and lets us link what you do to your EdgeFlow account when you are logged in.

• PostHog (ph_*, cookie and localStorage) — product analytics. Records which features you use (for example: logging a trade, opening Edge Discovery, reaching the pricing page) so we can see where the product helps and where people get stuck. Set only after you accept. Withdrawing your consent removes these items immediately and puts you back to the count described above. We do not record the content of your trades, notes or journal entries.

Either way

• Error reports — when part of the interface fails, we record the error message and the page it happened on (via PostHog) so we can fix it. This happens whether or not you accepted; without your consent it is stored against nothing, exactly like the count above. Nothing from your trades or notes.
• Where you came from — if you arrive through a link we placed in an advertisement or a post, that link carries labels we wrote ourselves (which platform, which campaign) and, on a paid advertisement, an identifier the advertising platform adds to the link. Both travel with the events described above and, if you join the waiting list, are stored with your entry so we know which advertisement brought you. They are read out of the address of the page you arrived on and are not written to your device.

We do not use Google Analytics and we use no advertising trackers.

4. Managing consent

The first time you visit, a banner asks you to accept or reject analytics. Rejecting it does not affect your ability to sign in, use EdgeFlow or pay, and it does not stop the cookieless count described in section 3 — it stops anything being stored on your device. To change your choice later, use this button: it forgets your choice, removes what analytics stored, and shows the banner again.

You can also clear your browser's site data for https://youredgeflow.com, or block cookies directly in your browser. Note this may break parts of EdgeFlow (e.g. login won't persist).

5. Third-party embedded services

• Stripe — during checkout. Strictly necessary for payment fraud prevention.
• PostHog — product analytics, EU-hosted. Runs on every visit; it stores something on your device only once you accept analytics (section 3).

6. Changes

We will update this page when we add or remove cookies. The effective date at the top reflects the latest version.

7. Contact

Questions: privacy@youredgeflow.com.