Privacy notice

This is the privacy notice for the Axelrod waitlist website, join.axelrod.coach: the short form that takes your email address (and, if you choose to say more, a couple of optional details) so we can tell you when early access opens. The notice also covers the Axelrod blog newsletter, a separate list with its own sign-up form on our blog and article pages, which takes your email address so we can email you when we publish a new piece. It also covers the basic, anonymous visit statistics we collect about the site. It explains what we collect, why, who else touches it, how long we keep it, and how you can ask us to change or delete it.

§1 Who runs the waitlist and the newsletter

The waitlist and the blog newsletter are run by the founders of Axelrod, reachable at support@axelrod.coach. They are individuals, and under India’s Digital Personal Data Protection Act, 2023 (DPDP Act) and the EU/UK GDPR they are the data fiduciary and controller of the data described in this notice.

They are two separate lists. Being on one does not put you on the other, and leaving one does not take you off the other (see §8).

The founders run Axelrod through LedgerLight Technologies LLP (incorporation in progress), a limited liability partnership being incorporated in India. When incorporation completes, the partnership will take over as data fiduciary and controller, and we will update this notice to say so. Nothing else about how your data is handled changes.

§2 What we collect

When you join the waitlist (step one, required):

Your email address.

If you choose to tell us more (step two, entirely optional, skipping it costs you nothing, your seat is already confirmed by then):

Whether you are already trading with a funded/prop firm, planning to, or neither.
The name of a prop firm, if you mention one.
Which trading platform you use (MT4, MT5, cTrader, DXtrade, Match-Trader, Tradovate, TradingView, or “other” with a short description).
Which markets or asset classes you trade: forex, futures, crypto, stocks, or indices.
Your X (Twitter) handle, if you want us to be able to reach you there.

When you subscribe to the blog newsletter (the form on our blog and article pages):

Your email address.
When you subscribed, and, if you leave, when you unsubscribed.
A record of which emails we have sent you, so we never send you the same piece twice.

Automatically, in the background (on both forms):

First-touch marketing attribution: which campaign, channel and page first brought you to the site, and the path you landed on. Your browser holds this in its session storage (not a cookie) and clears it when you close the tab. It is sent to us only if you submit a sign-up form. It is used only to learn which of our own links you followed, not to track you across other sites.
Which page or box you signed up from, an internal tag, not personal information on its own.
Your IP address, read to stop abuse of the sign-up, confirmation and unsubscribe forms (for sign-ups, a limit of 5 submissions per minute from the same address, and for the newsletter also 5 sign-ups per hour). Each counter sits in a separate table with no link to your email. A counter is cleared the next time the same IP address is checked after its window ends. Otherwise it is cleared once it is 2 days old, by the next request we check or by our daily clean-up, whichever comes first, so a counter can last up to 3 days. We keep more counters of the same kind. One limits the newsletter to about one email a day to an address; it is keyed on a scrambled form of the address (a keyed hash), so only we can tie it back to your address. Another counts clicks on newsletter links per IP address, so one reader cannot inflate a piece’s count. Another limits how often one unsubscribe link can be used; it is keyed on a scrambled form of the code in that link (a keyed hash), so only we can tie it back to your sign-up. Two more are site-wide totals that hold no IP address and no email address: newsletter sign-up attempts in each hour, and sign-up attempts each day (which caps our confirmation emails). When either total is full, the newsletter form asks you to try again later, your address is not stored, and no email is sent. Our hosting providers also keep standard access logs that include IP addresses, for periods they set (see §4).
Anonymous visit statistics. While you use this site, our analytics provider (PostHog, see §4) records the following, with no name, account or email address attached: which pages you view and whether you read a blog post to the end; the website you came from; if you land on an address that is not a page of this site, the first part of that address (at most two path segments, never anything after a question mark, and nothing at all if it contains an @ sign); the campaign tags in the link you arrived on, if any; your browser and operating system (with version numbers), device type, screen size and language setting; how far down a page you scroll, in steps of 25 percent, and which sections of a page you reach; how long a page stays open and in view; which of our buttons and links you click, and, for a link that takes you to another website, the name of that website only; where on a page you click, as a position on that page, which we add to other visitors’ clicks to see which parts of a page get used (a click heatmap), with the size of your browser window so that clicks on different screens line up; how far you get in the sign-up form, including when you see it and leave without finishing (we never record what you type in a field, and a click on a field counts only as one more position in the click heatmap, like any other click; nothing else about a field is recorded until you submit the form), and which field showed an error and what kind (for example, left empty or not a valid address), but never what you typed into any field; that a sign-up was submitted; and the name and version of the analytics software. We do not record what you type, text from the page, your mouse movements, or a recording of your screen, and we do not give you a profile; the random identifiers described in §4A last only until you close or reload the tab. Your IP address is received by PostHog’s servers when the page loads, as every website visit requires, but our PostHog project is set to discard it rather than store it, so we cannot see it or look you up by it. Our set-up also tells PostHog not to work out your location from it, so no location is derived.

What we do not collect here: no password, no payment details, no trade or brokerage data, no phone number, and no recording of your screen, your mouse movements or what you type. We run no visit statistics on the page you reach through an unsubscribe or confirmation link. Pressing its button records only what the button does: a confirmation records when you confirmed and which version of this notice was in force, an unsubscribe records the date. Either one also adds one to a short-lived counter for the IP address it came from, and an unsubscribe also adds one to a counter for that link (both described above). If you reached the page from a link in a newsletter email, Resend records that click, as it does for any link in that email (see below).

Email opens and clicks: We record whether you open our emails and which links in them you click. Our email provider, Resend, does this for us, using a tiny image in the email and by sending the links in our emails through its own address first. We use it to see whether our emails are being read. Some mail apps load the image without you opening the email, so an open does not always mean you read it. The email that asks you to confirm a newsletter subscription is the exception: we send it from a separate address with this recording switched off, so whether you open it and what you click in it are not recorded. The newsletter emails and the waitlist emails are recorded. Unsubscribing from a list stops it for that list’s future emails. In the blog newsletter, each link then goes through our own redirect, which adds one to a count for that piece and keeps a rate-limit counter per IP address to stop abuse (described above); neither is linked to your email address.

§3 Why we collect it, and on what legal basis

We collect this to:

Hold your place on the waitlist, email you when early access opens, send a few update emails about Axelrod along the way, and, later, occasionally offer a free tool or resource we think is useful. All of this is covered by the same consent you gave by signing up, and every email lets you leave with one click (see §8). We also record whether each email is opened and which links are clicked, to see whether our emails are being read (see §2). This is covered by the same consent.
Understand, in aggregate, which marketing channels and pages are working, and roughly who is interested, so we build the right product for the right people, and so a person can reach out to you directly (for example on X) based on what you tell us in step two.
Keep the sign-up and unsubscribe forms and the newsletter’s links and emails from being abused by bots or scripts (the rate limits in §2).
If you subscribe to the newsletter, send you one email when we publish a new piece, and occasionally a note that early access to Axelrod has opened. Every one carries a one-click unsubscribe link (see §8). After you unsubscribe we keep only the bare record that you did, so that we never email you again (see §5). When you subscribe to the newsletter, whether for the first time or again after unsubscribing, we first email you a link to confirm, and nothing starts until you click it. We also record whether each newsletter email is opened and which links are clicked (not the confirmation email), to see whether our emails are being read (see §2). This is covered by the same consent.
Count visits and sign-ups in aggregate, see where visitors click on a page, and see which pages, sections, buttons and campaigns work and where visitors get stuck in the sign-up form, so that we can improve the site. We do not use these statistics to identify you, to build a profile of you, or to advertise to you.

Lawful basis:

Under India’s DPDP Act, 2023:
- Your consent, given by submitting the waitlist form or the newsletter form. You can withdraw it at any time (§7-§8).
- Anonymous visit statistics are collected without a lasting identifier and with your IP address discarded, so we do not treat them as personal data about an identifiable person.
Under the EU/UK GDPR, if you are signing up from the EU or UK:
- Email + step-two context, updates, and any resource offers (Article 6(1)(a)): your consent. That consent also covers recording whether you open our emails and which links you click, which the same rules treat as storing and reading information on your device. You can withdraw it by unsubscribing.
- Your newsletter subscription and the emails it brings (Article 6(1)(a)): your consent, given by submitting the blog form. The EU and UK rules on email marketing also need your consent, and the form is how you give it. That consent also covers recording whether you open our emails and which links you click, which the same rules treat as storing and reading information on your device. You can withdraw it by unsubscribing.
- Keeping your address on a do-not-email list after you unsubscribe (Article 6(1)(f)): our legitimate interest, and yours, in making sure we never email you again once you have asked us to stop. You can object to this and ask us to erase it (see §6).
- First-touch attribution and page tag (Article 6(1)(f)): our legitimate interest in understanding which marketing channels work, without identifying you beyond your waitlist or newsletter record.
- The rate limits (Article 6(1)(f)): our legitimate interest in keeping our public forms, links and mail from being abused.
- Anonymous visit statistics (Article 6(1)(f)): our legitimate interest in understanding how the site is used so we can improve it, using a set-up that does not store anything on your device, does not give you a lasting ID and does not keep your IP address. We do not ask for your consent for these statistics. If you would rather not be counted, you can turn on your browser’s privacy signal (Global Privacy Control or Do Not Track) or block requests to eu.i.posthog.com (see §4A); the site works the same without them.

§4 Who else processes this data on our behalf

We use a small number of service providers (“processors”) to run the waitlist and the newsletter. None of them may use your data for their own purposes; they process it only to provide their service to us.

Provider	What it does for us	Data it touches
Neon	What it does for usHosts the database where waitlist sign-ups, newsletter subscribers and rate-limit counters are stored.	Data it touchesEverything in §2.
Railway	What it does for usHosts the API server that receives the forms, writes to the database, and sends the newsletter.	Data it touchesEverything in §2, in transit. Our server writes request identifiers and error details to its logs, and Railway may keep standard platform logs that include IP addresses.
Resend	What it does for usSends the “you’re on the list” waitlist confirmation, the email asking you to confirm a newsletter subscription (new or returning), each new-piece newsletter email, and any later waitlist emails. Records whether each email is opened and which links are clicked, except the email asking you to confirm a newsletter subscription, which is sent with that recording switched off.	Data it touchesYour email address, the content of the email we send you, whether it was delivered, and, for every email except the one asking you to confirm a newsletter subscription, whether it was opened and which links in it were clicked, each tied to you as the recipient.
Vercel	What it does for usHosts and serves the waitlist website itself.	Data it touchesStandard hosting/access data (IP address, browser type) for whoever loads the page.
PostHog (EU Cloud, hosted in the European Union)	What it does for usCounts page views, clicks on our buttons, where on a page visitors click, scroll points, form steps and sign-up submissions on this site so we can see how it is used and which campaigns work.	Data it touchesPage address (without anything after a question mark; an address that is not a page of this site is shortened, or sent as “404”), the website you came from, campaign tags, browser, device type, operating system, screen size, the size of the browser window (sent with click positions only), language, time, the name and version of the analytics software, and the events listed in §2. It does not receive your email address, your optional step-two details, your X handle, or anything you type. It receives your IP address in transit, but our project discards it rather than storing it.

Our providers may store and process data outside India. Most of our providers, including Neon, Railway, Resend and Vercel, may process data in the United States. PostHog processes the data it receives for us on its EU Cloud, in the European Union. All of them rely on their own standard contractual terms (their published data processing agreements) to do this lawfully; we have not needed a bespoke agreement of our own for a waitlist at this scale.

§4A Cookies and storage on your device

Analytics: we do not use cookies for analytics, and our analytics tool does not write anything to your browser’s cookies, local storage or session storage. It reads some basic details from your browser, such as screen size, language and how far you have scrolled, and sends them with each visit. It holds random, temporary identifiers in the tab’s memory only: most stay the same while you move between pages of this site, one is new for each page you view, and all of them disappear when you close or reload the tab. If you visit twice, our statistics see two separate visits and cannot connect them to each other or to you.

Attribution: as described in §2, the first-touch campaign tags are held in your browser’s session storage (not a cookie) and cleared when you close the tab. This is separate from analytics and is sent to us only if you submit a sign-up form.

No advertising or cross-site tracking: we do not run advertising trackers or social media pixels on this site.

Your browser’s privacy signal: if your browser sends the Global Privacy Control or Do Not Track signal, visit statistics do not start on this site.

Blocking analytics anyway: most browsers and many content blockers can block requests to eu.i.posthog.com. The site works the same without them.

§5 How long we keep it

Waitlist: your email and any optional context: kept until 18 months after Axelrod launches, or until you unsubscribe, whichever comes first.
Marketing attribution and page tags: kept alongside your row for as long as that row exists, since they’re stored on the same record, not separately. On the newsletter, they are cleared when you unsubscribe.
Rate-limit counters: the counters that hold an IP address are not linked to your sign-up record. Each is cleared the next time the same IP address is checked after its window ends (one minute for the sign-up, confirmation and unsubscribe forms and for link clicks, one hour for the newsletter’s hourly sign-up limit), and otherwise once it is 2 days old, by the next request we check or by our daily clean-up, whichever comes first, so it can last up to 3 days. The per-address mail counter covers one day and is cleared the same way, so it can also last up to 3 days. The per-link unsubscribe counter covers one minute, is keyed on a scrambled form of the code in the link, which only we can tie back to your sign-up record, and is cleared the same way, so it can also last up to 3 days. The two site-wide totals, newsletter sign-up attempts per hour and per day (the daily one caps our confirmation emails), hold no IP address and no email address and are cleared the same way. Provider access logs follow each provider’s own schedule (see §4).
Open and click records (Resend): Open and click records are kept by Resend under its own retention schedule, which we have not been able to confirm as a fixed period. We use them to see, for each email, whether it was read and which links were clicked. Unsubscribing stops new records being made; the records already made follow Resend’s schedule.
Anonymous visit statistics (PostHog): kept for up to 7 years, which is the retention period of our PostHog plan. Because they are not linked to your email or any account, we cannot find or delete a single visitor’s records on request.
Newsletter subscription: your email address, when you subscribed, and the record of which emails we sent you are kept for as long as you stay subscribed.
Unconfirmed newsletter sign-ups: if you do not click the link in the confirm email, we delete your address, and everything we store with it, once it is 7 days old, at the latest at our next daily clean-up. Until you confirm, we send it nothing else.
After you unsubscribe from the newsletter: we keep your email address, when you first subscribed, and the date you unsubscribed, and nothing else, so that we never email you again. We keep that record for as long as we run the newsletter. If you would rather we erase it completely, write to us (§7) and we will. The only cost to you is that we then have nothing to stop the address being signed up again by whoever types it into the form.

After a record is deleted, copies can remain in our providers’ backups for a short time, until those backups cycle out. They are not used.

§6 Your rights

If the DPDP Act, 2023 applies to you (India):

A summary of the personal data we hold about you and what we do with it.
The right to correct, complete, or update your data.
The right to erase your data once it is no longer needed, or once you withdraw consent.
The right to withdraw consent at any time, as easily as you gave it (one click, §8).
The right to name a nominee who can exercise these rights if you die or become unable to.
The right to complain to the Data Protection Board of India if you’re not satisfied with how we handle a request.
A named contact for questions about this processing: the founders, reachable at support@axelrod.coach (same as §1).

If the EU/UK GDPR applies to you: access, rectification, erasure, restriction or objection, data portability, withdrawal of consent, and the right to lodge a complaint with your local supervisory authority.

Rights requests under this section cover the data tied to your email address on the waitlist or the newsletter. Anonymous visit statistics carry no identifier we could use to find your records, so we cannot look them up, correct them or delete them for you individually. To object to being counted in them, block them in your browser or with a content blocker, as §4A describes.

These rights apply to the waitlist and the newsletter alike. If you ask us to erase your newsletter record after you have unsubscribed, we erase it in full, including the record of your unsubscribe, other than open and click records held by Resend, which follow Resend’s schedule (see §5).

§7 How to exercise these rights, or ask us anything

Email support@axelrod.coach. Tell us which email address you used, whether it was for the waitlist, the newsletter or both, and what you’d like us to do. We check both lists. We will respond within 30 days.

§8 Unsubscribe

Every email we send carries a one-click unsubscribe link, except the email that asks you to confirm a newsletter subscription. That one starts nothing on its own: if you ignore it, you are not subscribed and no posts follow. Click the link in any other email and you land on a confirmation page at join.axelrod.coach; confirming there removes you from the list that email came from straight away. You do not need to reply or write to us separately. Unsubscribing also stops any further open and click recording for that list.

Every email also carries a List-Unsubscribe header, so most mail apps (Gmail, Outlook, Apple Mail, and others) show their own built-in “Unsubscribe” button next to our name, which does exactly the same thing.

If you’d rather write to us directly, reply to any email, or write to support@axelrod.coach, and ask to be removed.

The waitlist and the newsletter each have their own unsubscribe link. The link in a newsletter email ends the newsletter only, and the link in a waitlist email ends the waitlist only. If you are on both and want out of both, use the link in one email from each, or write to us and we will remove you from both.

When you confirm a newsletter unsubscribe, we send you nothing more from the newsletter. The one exception is an email already on its way to you at that moment. Unlike the waitlist, where leaving deletes your entry, the newsletter keeps a bare do-not-email record of your address (see §5), because that record is what stops us mailing you again.

§9 Security

Your data travels to us over an encrypted connection (HTTPS/TLS). The sign-up forms are protected against automated abuse. We have not made any claim here beyond what is actually built; a fuller security statement belongs in the product-stage privacy policy, not this one. Only the founders can open the sign-up lists, through a login-protected database. When we download a list as a file, we keep that file only for as long as the task needs.

§10 Children

This waitlist and the newsletter are not directed at children, and we do not knowingly collect data from anyone under 18.

§11 Changes to this notice

We may update this notice as the waitlist or the newsletter changes, or as the partnership named in §1 completes incorporation (at which point §1 and §6 will name it directly). The version on this page is always the current one. If the newsletter ever sends you something of a different kind from what the form promises, we will update this notice before we do, and ask for your consent again where the law requires it.

§12 Effective date

2026-10-18.