Privacy
The Analyst’s Path · last updated 3 November 2026
There’s nothing to register for here. What you do in the app stays in your own browser, on your own device, and we never get a copy of it. On our side we keep the newsletter list, if you join it, a record of what is done with that list, and the page-view counts our host makes, which name nobody. The adverts on the public pages and in the app bring their network’s own cookies, and the ads section below says what those are.
What the app keeps, in your browser
The app at app.consultantlearning.org stores what you do in it in your
browser’s own storage (IndexedDB and local storage): your progress through the modules
and their gates, your review cards and when each one is due, your quiz and drill answers, your
mock exam sittings, your decision journal, simulator portfolios, case drafts, where you stopped
reading and your preferences. None of it is sent to us, so we can’t see it and nobody
else can either.
That has a cost worth knowing. Clearing this site’s data in your browser deletes your progress for good, and a second browser or device starts empty. To move it, open Your data in the app, export everything as one file and import that file in the other browser. The same page deletes it all, if that’s what you want.
Loading a page is still a request to our host, Cloudflare, which sees what any web server sees: an IP address, a browser user-agent and the file asked for. Those go into Cloudflare’s own logs, and we keep no copy of them.
Progress saved before October 2026
Until October 2026, learners who registered had a copy of their progress on our server. When that ended, each one’s progress was saved as a file in the app’s own export format, with the list of addresses beside them, on our own computer, and the server, its database and the database’s backups are deleted in the same week, with the hosting project that held them. We keep those files until 30 April 2027 so anyone can ask for theirs, and we delete them then. Write to us from the address you used and we’ll send you yours. If we write to those addresses, it’s one mail about this change, sent through Resend or from our own mailbox, and none of them is added to the newsletter list.
The newsletter
The box at the end of a page asks for your email address so we can send a short mail when new pages go up. If you use it, we keep the address, the page you were reading and the dates you joined, confirmed and, if you go, left. We also note when we last sent you a confirmation link, so nobody can have a pile of them sent to one address.
Nothing goes out until you confirm. You get one mail with a link, and an address that never uses it gets nothing more, unless it is put in the box again. Once you’ve confirmed, the address is used for that one thing, the mail about new pages. Every mail carries a link to leave: it opens a page with one button, and pressing it takes you off. We don’t sell the list or share it, and we don’t add anyone to it who didn’t ask.
When you leave, your row stays in the list marked as left, with the date, so the address can’t be mailed again by mistake. An address that was never confirmed stays marked that way. Ask us and we’ll delete the row completely.
Beside the list we keep a record of what was done with it: each request to join with a valid address, each confirmation mail, confirmation and unsubscription, each weekly summary, and each time we open or download the list, with the time, the outcome and a SHA-256 hash of the address concerned. That hash is not a secret: anyone who already has an address can work it out and find that address’s entries. From 13 May 2027 an entry made for a request (a request to join, a press of the button on the page a mail’s link opens, a look at the list) also holds the IP address the request came from, because rule 8(3) of India’s Digital Personal Data Protection Rules, 2025 asks for logs of processing from that date. Each entry is deleted after one year, and that includes the entries about an address whose row we have deleted on request.
The list sits in a Cloudflare database. Resend sends the confirmation mail, so it gets your address and that mail. Once a week a short summary of who joined and who left comes to our own mailbox. If we ever send the newsletter through a mailing service, that service will get the list, and we’ll name it on this page before the first mail goes out.
As soon as you click into the box, Cloudflare’s Turnstile runs in your browser to tell a person from a script. It reads signals such as your IP address and your browser’s details, and Cloudflare’s Turnstile privacy addendum covers what it does with them. To stop one connection from adding address after address, the form also keeps a one-way hash of your connection’s address for one minute in Cloudflare’s cache. That hash never goes into the list.
Analytics
The only analytics here is our host’s own (the host is named under “Who else sees anything”). It counts page views on both sites, and it may time how quickly a page loads. It sets no cookie. To tell one visitor from another it may work out a value from the request itself, which is thrown away within a day, so it can’t follow you from one day to the next or on to another site. What we see is totals, such as which pages were read and from which countries, so nothing it records is tied to a person. There’s no session recorder and no heatmap.
What we never collect
- Your name. Nothing here asks for it.
- Card numbers or any other payment details. There is no paid plan, so none of it ever reaches us.
- Real portfolio or brokerage data. The simulator isn’t connected to any brokerage and has no way to be.
- Your own AI provider keys. If you give the app a key of your own, it stays in your browser and talks to that provider directly. It’s never sent to us.
- Behavioural advertising data. See below.
Ads
The adverts pay for the hosting. Since 26 October 2026 the ones on the public pages come from an ad network, Adsterra, and from November 2026 the app carries Adsterra’s adverts too; Google’s will join them on the public pages once Google approves the site and we switch them on. In the app there are adverts on four index screens (The Path, the Dashboard, the Library list and the Practice home): a banner under the screen’s heading, a native advert at the end and, on a wide screen, a tall banner beside the content. There is one more at the end of a lesson, after its last section, in the module page and in the Reader. Nothing plays before a module opens.
There are never adverts beside a quiz, a drill, a case, a review, a mastery gate or anything timed or graded, and never on onboarding or the Your data page. That is a rule enforced in the code, not a preference.
On the public pages at consultantlearning.org the adverts sit on the concept pages,
the module pages, the glossary, the guides and the ratio calculator. Your browser keeps what the
app stores (your progress, review cards, journal, preferences and any service key you save) with
the app’s own site, app.consultantlearning.org, and a script on
consultantlearning.org can’t read any of it. In the app each advert is loaded
in a frame of its own on the app’s address, and the advert itself then shows in a frame of
Adsterra’s. Because those first frames are on the app’s address, Adsterra’s
code there runs where the app keeps what you do. We pass it none of that, and while a key you
saved for an outside service is still in the app, no advert loads there at all.
What is serving right now: Adsterra, on the public pages and in the app
- What loads. Adsterra’s scripts, from addresses Adsterra chooses and
changes from time to time (
bauval.orgis one as this page is written), on the reading pages and in the app as above, and nothing on the home page, the public site’s index pages or this page. A reading page carries a native advert and display banners in set places in and beside the text, each labelled “Advertisements” once something is in it; a slot nothing fills closes, and so does one in the app. We don’t run Adsterra’s page-behind-the-page format (a “popunder”), its notification panel (the Social Bar) or any Adsterra link in the text. - What Adsterra can see. Your IP address, the address of the page the advert sits on, and what its code reads from your browser: the user-agent, language, time zone, screen size, whether it has touch, and the checks ad networks run to tell a real browser from a bot. It sets a cookie or a local-storage identifier for frequency capping and fraud detection. Adsterra chooses the advert from the page and the country it is read from, and what else its code does on its own side is governed by Adsterra’s privacy policy (AD MARKET LIMITED, Cyprus).
- What we never pass to Adsterra. Your progress, your answers, your scores,
your journal, your simulator portfolio, your notes, your newsletter address, or anything
else you have typed into this product. The public pages show none of it, and in the app we
send it nothing (what its code could reach there is said above). One leftover is dealt with
first: a browser that used the
app at
consultantlearning.orgbefore 15 October 2026, when the app moved toapp.consultantlearning.org, may still hold an old token at this address, where nothing can use it; the page removes that token before any Adsterra script loads, so no network script can read it. A browser the app had marked as holding a saved service key here gets no Adsterra advert at all. - Who gets a request. A browser whose language and time zone leave it outside the EEA, the UK and Switzerland gets the adverts without being asked: neither may place it in those places, and at least one of the two has to say where it is. A browser whose language or time zone places it in those places, or that gives neither, is asked first, and nothing is requested from Adsterra until you allow it (the section on the EEA, the UK and Switzerland below). A browser set up to look as if it were elsewhere, through a VPN or a changed time zone, is read as where it says it is.
What will serve once Google AdSense is approved
We have built the integration and we intend to switch it on. When we do, this is exactly what changes, worth reading now rather than being surprised later:
- What loads. Google’s script from
pagead2.googlesyndication.com, on our public pages only, never inside the app, and the rest of Google’s ad code, which it fetches from addresses Google chooses. It shows banners in the same set places on the reading pages, each labelled “Advertisements”, and now and then a full-screen advert as you move from one public page to another (never on a link into the app), which you can close at once. Each advert renders inside a Google frame, from addresses such asgoogleads.g.doubleclick.netortpc.googlesyndication.com. - What Google can see. Your IP address, your browser’s user-agent, the address of the page the advert sits on, and a cookie or local-storage identifier it sets in your browser for frequency capping and fraud detection.
- What we never pass to Google. Your progress, your answers, your scores,
your journal, your simulator portfolio, your notes, your newsletter address, or anything
else you have typed into this product. The public pages Google’s script runs on show
none of it, and each advert sits in a Google frame that can’t read the page around it.
The script itself runs on those pages, which is why they are a separate site: your browser
keeps what the app stores (your progress, review cards, journal and preferences) with the
app’s site,
app.consultantlearning.org, and a script onconsultantlearning.orgcan’t read any of it. - Adverts are never personalised. Every request we make is flagged non-personalised, for everybody, in every country. Adverts are chosen from the page they sit on, not from a profile of you.
- Google’s cookies, and how to opt out. Third-party vendors, including Google, use cookies to serve ads based on a user’s prior visits to this website or other websites. Google’s use of advertising cookies enables it and its partners to serve ads to you based on your visits to this site and other sites on the internet. Our requests ask for non-personalised adverts only, and you can also opt out of personalised advertising from Google in Ads Settings, and out of other vendors’ use of cookies for personalised advertising at www.aboutads.info (in Europe, www.youronlinechoices.eu).
That last one is deliberate and it costs us money. India’s Digital Personal Data Protection Act prohibits targeted advertising directed at anyone under 18, and this product doesn’t ask your age, so we can’t know that any particular reader is an adult, and we treat everyone as though they might not be. There’s no setting anywhere that turns personalised advertising on, and nothing is personalised for anyone.
Cookies, in full
We set no cookies of our own. Not one. The complete list of what is stored in your browser is:
| Name | Kind | What it is for |
|---|---|---|
ap.*, ap-* and assistant.* (local storage, session storage) and the analysts-path database (IndexedDB) | Ours, first-party, in the app | Your progress, review cards, journal, mock exam sittings and preferences, whether you’ve been through onboarding, and counts of how often a service key you saved has been used. The public pages store nothing of their own apart from your answer about adverts (below); they also look for the old token described in the ads section and remove it. Never sent to an advertiser. |
| Cache Storage and a service worker | Ours, first-party, in the app | Copies of the app’s own files (its pages, its code, the course’s text and the engine that runs Python exercises), so the app opens quickly and works offline. Nothing about you. |
ap.ads.consent | Ours, first-party, on the public pages and in the app separately | One boolean and a date: your answer about adverts, if you were asked (see the next section), and when you gave it. A year later you are asked again. Nothing else. |
| Cloudflare Turnstile | Third-party, on the public pages, only once you click into the newsletter box | Whatever the bot check needs in your browser to run. Cloudflare’s Turnstile privacy addendum, linked in the newsletter section, covers it. |
| Adsterra’s cookies and identifiers | Third-party, on the public pages and in the app; in the EEA, the UK and Switzerland only after you allow adverts | Frequency capping and invalid-traffic detection. Set by Adsterra’s code and used only by Adsterra; see its privacy policy, linked above. |
| Google advertising cookies | Third-party, on the public pages only: only once AdSense is live, and only with consent where consent is required | Frequency capping, click measurement and invalid-traffic detection. Set by Google’s code and used only by Google. |
| Google’s consent record | Third-party, on the public pages only: only once AdSense is live, in the EEA, the UK and Switzerland | Your answer to Google’s consent message, so it doesn’t ask again on every page. Set by Google’s code and used only by Google. |
If you are in the EEA, the UK or Switzerland
While your browser’s language or its time zone places it there, as a browser in those places normally does, or it gives neither, nothing is requested from Adsterra until you say yes. On the public pages a small bar at the foot of the page asks you; in the app a notice does. “Allow adverts” lets Adsterra’s adverts load, with the cookies and identifiers described above. “No thanks” means none load and no Adsterra cookie is set, and everything else works the same. Your answer is kept in your browser, on each site separately, and after a year you are asked again. You can change it at any time: “Advert choices” at the foot of any public page that carries adverts, or “Change my answer” on Your data in the app. Once Google’s adverts are live, Google’s own consent message (a consent tool Google has certified) asks you before any Google advert loads there.
No paid plan
There is no paid plan, and we hold no payment or card details of anyone. The adverts pay for the hosting. Nothing about what you study goes to advertisers.
Who else sees anything
- Cloudflare, our host. It serves both sites and counts their page views, keeps the newsletter list, runs the bot check and forwards mail sent to our address. The provider that serves this site and the public pages is Cloudflare.
- Resend, which sends the newsletter’s confirmation mails, our weekly summary of the list and, if we send it that way, the mail about the change of October 2026 to the people who had registered. It receives the address and the message.
- Google, once AdSense is live, for the adverts on our public pages (see the ads section). Our own mailbox is with Google too, so the weekly summary of the list, any mail you send us and any mail we send from it sits there.
- Adsterra (AD MARKET LIMITED, Cyprus), which serves the adverts on our public pages and in the app, to readers in the EEA, the UK and Switzerland only once they allow it (see the ads section).
- Nobody else. We don’t sell, rent or trade personal data, and apart from Adsterra, and Google’s AdSense once it is live, we have no advertising or data-broker relationships.
- We would disclose data if a court with jurisdiction over us ordered it, and we would tell you unless legally barred from doing so.
How long we keep it
- What the app keeps: in your browser, for as long as you keep it there. We hold no copy.
- The newsletter list: until you ask us to delete your row. Leaving marks it as left and stops every mail at once.
- The one-way hash behind the form’s one-a-minute limit: one minute.
- Confirmation links: they work for 7 days. They’re checked by their own signature, so nothing extra is stored for them.
- Progress files saved from the old server, and the list of addresses beside them: until 30 April 2027.
- The record of what was done with the newsletter list (its time, outcome, a SHA-256 hash of the address and, from 13 May 2027, the request’s IP address): one year, then deleted, including the entries about an address whose row we deleted on request. Rule 8(3) of India’s Digital Personal Data Protection Rules, 2025 asks for logs of processing to be kept for at least one year, for the purposes the Rules list, from that date.
- Page requests (IP address, browser user-agent, the address requested): only in Cloudflare’s own logs, for as long as Cloudflare keeps them. We keep no copy.
Your choices
- Back up or move your progress: Your data in the app, then Export. A JSON file you own, with no request needed.
- Delete your progress: Your data in the app, then the button that deletes everything. It’s gone from that browser at once.
- Leave the newsletter: the link in any mail from us, or write to us.
- Have your newsletter row deleted completely, or an address corrected: write to us.
- Get your progress file from before October 2026: write to us from the address you used.
If you are in the EU or UK, these are your GDPR rights to access, rectification, erasure, portability and objection; the lawful bases we rely on are your consent (the newsletter) and legitimate interest (keeping the site secure). If you are in India, this is how we meet the Digital Personal Data Protection Act’s access, correction and erasure duties. Either way, one email is the whole process.
Security
There is little personal data on our side to protect: we hold no passwords (the old server and its backups are deleted with the hosting project), and the only list we hold is the newsletter’s. Its links are signed, so nobody can forge one. The list can be read in two places only: on a page behind Cloudflare Access, which we have set to let in nobody but us, and in the weekly summary of who joined and who left, which comes to our own mailbox. The bot check and the one-a-minute limit keep scripts from filling it. What the app keeps is as safe as your browser and your device are. We don’t claim to be unbreakable; we do claim to have taken these specific measures.
Children
This isn’t aimed at children. The newsletter is for people aged 18 or over, which is where India’s Digital Personal Data Protection Act, 2023 draws the line between a child and an adult, and we don’t knowingly keep a child’s address. If you think someone under 18 has joined it, tell us and we’ll remove the address.
We also don’t ask anyone’s age, which means we can’t rule out that a reader is a student under 18. Rather than guess, we assume it: advertising is non-personalised for every reader, everywhere, which is what India’s Digital Personal Data Protection Act requires for children and what we apply to everybody. No behavioural profile is built for anyone, at any age, in any country.
Who is responsible for your data
The data fiduciary for everything on this page (the controller, in the GDPR’s terms) is the operator of consultantlearning.org. The person who answers for it, and for any question about how your data is handled, is reached at hello@consultantlearning.org.
Grievances
To raise a grievance about your data, such as a request we haven’t met or something you think we got wrong, write to that address with “Grievance” in the subject line. We acknowledge it within 3 working days and answer it in full within one month, inside the 90 days that India’s Digital Personal Data Protection Rules, 2025 allow.
If you aren’t satisfied with our answer
- In India, you can complain to the Data Protection Board of India under the Digital Personal Data Protection Act, 2023. The Act asks you to use our grievance route first (section 13(3)).
- In the EU or the EEA, you can complain to the data protection authority of the country where you live or work, or where you think the problem happened (GDPR, Article 77). The European Data Protection Board lists them. In the UK, it’s the Information Commissioner’s Office.
If your data is breached
If a breach affects your personal data, we’ll tell you, and the Data Protection Board of India as the Act requires (section 8(6)), and the authority concerned where the GDPR applies.
Data outside India
Some of the providers named above process data outside India: the machines Cloudflare runs, and the mail services. The Act allows this unless the Government restricts transfers to a country (section 16).
Changes
If this policy changes in a way that affects you, we’ll say so on the site before it takes effect, and by mail to the newsletter list when the change is about the list. The date at the top is always current.
Contact
Write to the address on the contact page about anything on this page, and see Grievances above for a complaint about your data. There is no form and no ticket queue, and we answer.