Frequently asked questions
Is my data really safe? Where does the PDF go?
It stays in your browser tab. There is no backend server — no PHP, no Node, no API. The page is plain static HTML hosted on GitHub Pages. When you select a file, the browser hands the bytes to a Python interpreter (Pyodide) running inside the tab's WebAssembly sandbox. We read it, compute the plan, and render the result. The PDF, password, and plan never leave your device.
Verify it yourself: open DevTools → Network tab → upload your file → click Compute. You'll see fetches to GitHub's CDN for the runtime + the static NAV file, and zero outbound requests carrying your data.
How accurate is the plan?
The arithmetic is exact for the lots in your CAS. What's not exact is the NAV you'll transact at — Indian MFs publish closing NAV after market hours, so any order you place today gets today's EOD NAV (declared tonight ~9 PM IST), not the NAV in the plan (which is yesterday's). Mid-cap funds typically move ±1–2% intraday. The default 1.5% safety buffer is sized to absorb this so booked LTCG stays inside the exemption.
Always spot-check the unit counts on your AMC portal before placing orders.
I don't see my fund in the recommendations. Why?
A few reasons it might be excluded:
- Held < 1 year — not eligible for LTCG yet. Wait it out.
- ELSS in 3-yr lock-in or solution-oriented fund in 5-yr lock-in.
- NAV not on the AMFI feed — newly launched or suspended scheme.
- Smaller gain-per-unit — the algorithm prefers high gain/unit lots so it can hit the budget while moving fewer units.
The Warnings section in your report lists every excluded scheme with the reason.
What about NSDL / CDSL demat-only CAS?
This browser build handles CAMS, KFintech, and MF Central PDFs (the broadest coverage). NSDL/CDSL demat-only CAS needs an additional 50 MB SQLite ISIN database that won't fit in the browser bundle — for those, use the CLI.
Why is the first load so slow?
The browser downloads a Python runtime (~10 MB), a slim ISIN database (~3 MB), and today's AMFI NAV snapshot (~2 MB) — about 15 MB total, all from GitHub's CDN. Your browser caches them, so the next time you open this page it's instant. No Python or pip is installed on your operating system.
How does the safety buffer trade off against unused exemption?
A 1.5% buffer on a ₹1.25 L budget = ₹1,875 of exemption held back. If NAV moves < 1.5% adversely between plan time and execution, your booked LTCG stays inside the exemption (zero tax). If NAV moves favourably you "leave" up to ₹1,875 on the table — you can claw that back tomorrow with a small top-up redemption against the now-known NAV. Pick 0% for max exemption + small overshoot risk; 2% for extra conservatism.
I found a bug / want to add a broker. How do I contribute?
Open an issue or PR on
GitHub.
For broker tax-P&L formats other than Zerodha, the column mapping lives in
web/index.html → HEADER_MAP. Adding a new broker is usually one
dict entry. See CONTRIBUTING.md for the dev setup.