Networthy HQ

Privacy

Networthy HQ is built so your financial data stays yours. This page describes, in plain terms, what we do and don't do with it.

Where your data lives

Everything you enter or import — parsed holdings, manual entries, expenses — is stored in a database on the server that runs Networthy HQ, scoped to your account. It is not sold, shared, or sent to third-party analytics or advertising services.

Your statements

When you upload an NSDL CAS or CAMS statement, it is decrypted and parsed in memory on the server. The password (your PAN) is used only to open the PDF and is never stored. We keep the parsed figures; we do not keep the PDF.

The one thing that leaves the machine

To show live prices, Networthy HQ fetches quotes from public market data — Yahoo Finance for stocks, crypto and FX, and AMFI's public bulk feed for mutual-fund NAVs. In doing so the only information that ever leaves the server is a public symbol: a stock ticker (e.g. E2E), a currency pair, or a coin symbol. We never send your units, values, holding sizes, PAN, or identity. Mutual-fund NAVs are looked up locally from a downloaded file, so nothing about those holdings is sent at all. Every such request is best-effort: if it fails, the app simply falls back to your statement values.

Accounts & sign-in

Sign-in uses your email and a one-time code — no passwords to store or leak. We keep your email address to identify your account and send login codes. Sessions are held server-side; the cookie in your browser is just a random token.

Cookies — there's one

Networthy HQ sets a single cookie, named session, and only once you sign in. It holds a random token and nothing else — not your email, not an identifier, nothing readable. The session itself lives on the server; the cookie is just the key that points at it. It's marked HttpOnly (scripts can't read it), Secure (sent over HTTPS only), and SameSite=Lax. It lasts 30 days, and signing out deletes it.

There are no advertising cookies, no pixels, and no fonts or libraries loaded from someone else's server. Nothing you enter is ever shared with anyone.

On networthyhq.com the public pages — the landing page, the free calculators, and these policy pages — do load Google Analytics, so we can see how many people find them and which ones are useful. It sets its own cookies. Two limits on it, both deliberate:

If you'd rather not be counted even on the public pages, any browser-level blocker stops it, and nothing on the site breaks without it.

Your browser also remembers one preference locally — whether you chose the light or dark theme — using localStorage, not a cookie. It never reaches the server.

When you report a bug

Report a bug sends what you type to the maintainer — by email, and it's kept on the server so a mail failure can't lose it. What goes with it is only what you wrote, plus your account email if you're signed in, so a reply can reach you. The page you were on is deliberately not attached: a signed-in URL names which asset classes you hold, and that's the same reason analytics never runs once you sign in.

Because that message does leave the machine, the form asks you not to paste amounts, account numbers or statement contents into it — describing the shape of a problem is both enough to fix it and none of anyone else's business.

Usage & adoption

So we can understand how Networthy HQ is used, the operator sees basic account and usage metadata — how many people have signed up, when accounts sign in, and which features have been used. This is computed on the same server and is never shared with anyone. It deliberately excludes your financial values: adoption is measured in counts, never in your holdings or amounts.

Your control

You can delete individual entries, clear your snapshots, or remove imported data at any time from within the app.

You can also take everything with you or erase all of it yourself, from Your data — no email, no waiting on us. The export is the raw contents of your tables as JSON, or one CSV per table in a zip; it's the same data the app reads, not a summary. Deletion is immediate and permanent: there is no backup we could restore you from, which is the flip side of not keeping copies of your data.

Get started