Cookie Policy

This page lists every cookie Digital Edge Lab (“DEL,” “we,” “us”) sets on thedigitaledgelab.com, what each one is for, and how long it lasts. It sits alongside our Privacy Notice, which covers everything else we do with your data.

The short version: we only set cookies that are strictly necessary to sign you in and keep you signed in. We do not use advertising cookies, and our analytics are cookieless.

1. What a cookie is

A cookie is a small text file a website asks your browser to store, and sends back on later visits. Cookies are how a site remembers that the person loading this page is the same person who signed in a minute ago — HTTP on its own has no memory. Related technologies such as localStorage and sessionStorage store data in your browser in a similar way, and we treat them under this policy too.

2. The cookies we actually set

All of the following are strictly necessary. They are first-party (set by thedigitaledgelab.com, not a third party), and they exist only to make signing in work.

Authentication

• Session token (authjs.session-token, or __Secure-authjs.session-token over HTTPS) — proves you are signed in, so you are not asked for your password on every page. It is a signed token, marked HttpOnly so page scripts cannot read it, and it expires after 30 days, or when you sign out.
• CSRF token (authjs.csrf-token) — a security cookie that lets us verify a sign-in or sign-out request genuinely came from our own form, rather than from another site acting in your name. Expires when you close your browser.
• Callback URL (authjs.callback-url) — remembers which page to return you to after you sign in. Expires when you close your browser.

Preferences

• Small amounts of browser storage may be used to remember interface choices — for example a collapsed section or a chosen tab. This never leaves your browser and is not used to identify you.

You can see all of these for yourself: open your browser’s developer tools on this site and look under Application → Cookies. If you find one that is not on this list, please tell us — that would be a mistake we want to fix.

3. Analytics — and why it sets no cookies

We use Vercel Web Analytics and Vercel Speed Insights to see which pages are visited and how quickly they load. Both are designed to work without cookies and without tracking individuals across sites. They do not build a profile of you, and they do not follow you anywhere else on the internet.

What that gives us is aggregate and blunt: page view counts, referrers, rough country, and load times. It is enough to know which lessons people read. It is not enough to know who you are.

4. What we do not use

• No advertising or retargeting cookies. We do not currently run Meta, Google, or TikTok pixels on this site. If that changes, this page will be updated before any such tag goes live, and we will ask for your consent where the law requires it.
• No selling of data. We do not sell personal information, and we do not share it with data brokers.
• No cross-site tracking. Nothing we set is designed to follow you to other websites.

5. Third-party services and their own cookies

Some parts of the Service hand you off to another company, and once you are on their page, their cookie policy applies, not ours:

• Stripe — when you check out, payment happens on Stripe’s own hosted checkout. Stripe sets its own cookies there, including for fraud prevention. We do not load Stripe’s scripts on our own pages.
• Google — if you choose “Sign in with Google,” Google sets cookies on its sign-in page as part of authenticating you.
• Whop — used to verify purchases and memberships made through our Whop store; sign-in happens on Whop’s domain.
• Discord — if you link your Discord account for community access, Discord handles that authorisation on its own site.
• YouTube / TradingView — where a lesson embeds a video or chart, that provider may set cookies when the embed loads.

Links to a partner, such as a prop firm referral link, may carry an attribution parameter so the partner can credit the referral. Which of our links do that, and what we earn from them, is set out in our Affiliate Disclosure.

6. Your choices

Every browser lets you view, block, and delete cookies — usually under Settings → Privacy. You can also browse in a private or incognito window, which discards cookies when you close it.

The one trade-off worth knowing: the cookies in section 2 are what keep you signed in. Block them and the Service will still load, but you will not be able to stay logged in, so the Academy, the Edge Engine, your journal and any PRO features will be out of reach. Because those cookies are strictly necessary and we run no advertising tags, there is no consent banner to click through here.

7. Changes to this policy

If we add a cookie, we will list it here and update the date at the top of this page. If we ever add anything beyond the strictly necessary — an advertising pixel, for instance — we will say so plainly and obtain consent where it is required.

8. Contact

Questions about cookies, or think something here is wrong? Email privacy@digitaledgelab.com. See also our Privacy Notice and Terms of Service.