1. What FinCharya collects
Your sign-in identity. An email address or a mobile number, whichever you sign up with. If you sign in with Google, Microsoft or Apple, we receive the verified email address from that provider and nothing else about you (Apple may hand us a private relay address in place of your real one, if you choose that on Apple’s screen). If you set a password, only a scrambled form of it is stored — one that cannot be turned back into your password, and never the password itself. A display name is optional.
The portfolio data you bring. Everything you import or type in: holdings and fund folios, trades, fixed deposits and small-savings schemes, EPF/PPF/NPS balances, bank balances, bonds and debt instruments, US stocks, loans and credit-card debt, goals, tags and any notes you write. Where you tag a holding to a family member, that label is stored too.
Your broker connection, if you make one. Linking Zerodha stores only the details of the connection itself — a label, which broker, when it was last active and when it expires. The live session stays in the server’s working memory for as long as it lasts and is never written to disk. The connection can only read: it cannot place an order or move money, and FinCharya never sees your broker password, because you authorise it on Zerodha’s own screen.
Anonymous usage records. To learn where people get stuck signing up, FinCharya records a handful of simple events: a random identifier your browser makes up and keeps for itself, the name of the step reached (opening the landing page, opening pricing, starting the demo, and similar), whether you were signed in at the time, and a small non-identifying detail such as which button was pressed. No cookies are read for this, no device fingerprint is taken, no outside analytics service runs, and nothing about your holdings or who you are is attached. These records are deleted after 180 days.
Ordinary operational records. Server logs and counters needed to keep the service running and to find faults — when an update ran, whether a request failed. When something breaks, a technical error report goes to Sentry (section 4).
2. What FinCharya does not collect
- Your consolidated account statement never leaves your device. The PDF and the password that opens it are read entirely in your browser, by a PDF reader FinCharya serves itself. Two things travel out of it, and nothing else: while you are reviewing the import, the list of instrument identifiers (ISINs) is sent so each holding can be matched to a name and a price; and when you confirm, the rows you approved are saved — each instrument and how much of it you hold. The file, its password, your demat and folio numbers, and your name as printed on the statement all stay on your machine. Broker files are read the same way.
- Your inbox and messages. FinCharya never asks for email or SMS access and has no code that reads them. Consolidation comes from statements, not surveillance.
- Advertising. No ad networks, no marketing or tracking code from anyone else, no tracking pixels, no outside analytics service of any kind. The one outside service that receives anything from your browser for FinCharya’s own use is Sentry, which gets error reports when something breaks (section 4). It does not record what you look at or do in the app.
- Anything sold or shared. Your personal data is not sold, rented, licensed or shared for anyone else’s marketing. There is no data-broking arrangement, no lead-gen, and no fund house or broker paying to reach you.
3. Where your data lives
FinCharya keeps three separate databases, and only one of them is about you.
- Your data — everything in section 1 — sits in rows keyed to your account and can be read only through your signed-in session. This database is hosted by Turso, in Amazon Web Services’ Mumbai region (
ap-south-1). The primary database stays in India. There are two exceptions. FinCharya’s application server runs on Railway in Singapore: it handles your data while it answers your requests, and it keeps a working copy of this database on its disk. And the messages FinCharya sends you, including the optional Sunday digest, pass through an email service that stores them in the European Union. See section 4. - Market data — closing prices, fund values, index membership, corporate actions, exchange rates — is shared reference information drawn from public exchange and AMFI records. It describes investments, not people, and would be identical whether or not you existed. It sits on the application server, and FinCharya publishes it through Cloudflare’s storage.
- Operational data — a short-lived copy of recent prices, and records of when scheduled jobs ran. It is disposable: deleting it costs nothing but a little speed. It also sits on the application server. Error reports are the exception: they go to Sentry, in Germany. See section 4.
The three are kept physically apart with no links between them, so market data can be rebuilt or replaced without touching anything of yours.
4. Who else is involved
Turso (database hosting) — this is the one that holds your data itself, so it is listed first. Turso runs the database described in section 3: your identity, your portfolio and everything else in section 1. It is a processor acting on FinCharya’s instructions — it does not use your data for its own purposes, and nothing is shared with it beyond what FinCharya stores. The database sits in AWS Mumbai (ap-south-1). Traffic between FinCharya and it is encrypted on the way, and authorised by a key held only on FinCharya’s server that never reaches your browser. Deleting your account deletes the rows there, not just locally. Turso publishes its security and compliance details at trust.turso.tech.
Railway (application server) — Railway runs the server that answers the app’s requests, so your data passes through it, and its disk holds a working copy of the database described in section 3. That server is in Singapore, so your data is processed and copied outside India. Railway is a processor acting on FinCharya’s instructions and does not use your data for its own purposes.
Cloudflare (web hosting) — Cloudflare delivers the web app to your browser and stores the public market-data file. It sees your IP address and browser details as part of delivering the pages. It does not receive your portfolio.
Zerodha — only if you choose to link a broker. FinCharya uses Zerodha’s official read-only connection to read your holdings, positions and trades. Nothing is ever written back.
Brevo (email delivery) — operated by Sendinblue SAS, France. The emails FinCharya sends — the link that verifies your address, the password-reset link and the optional Sunday digest — go through Brevo over an encrypted connection. Your email address and the whole message pass through Brevo, and Brevo stores a copy as part of its delivery records. The Sunday digest names your holdings and states amounts, so those details reach Brevo too. Brevo says it stores this data in the European Union, so email content is processed and stored outside India. Brevo acts on FinCharya’s instructions and does not use the messages for its own purposes. If you would rather no holdings or amounts leave India, keep the digest switched off: the verification and password-reset emails carry none. If Brevo is down, FinCharya may send through a backup email service for a short time, on the same terms. When no email service is set up, no email is sent and no address is shared.
Sentry (error reporting) — operated by Functional Software, Inc., USA. When something breaks, in your browser or on the server, FinCharya sends Sentry a technical report: what failed, where in the code, the page or request path involved, and browser details. It also receives timing records for a sample of server requests, which show where the service is slow. Before a report leaves, FinCharya removes who you are, email addresses, the contents of requests, and the part of a web address that can carry a private link. No screen recording is ever made. FinCharya does not put holdings or amounts in these reports, but an error message can occasionally quote a value it was handling, and no filter catches every case. Sentry sees your IP address when your browser sends a report. Sentry stores reports in Frankfurt, Germany, and its contract also allows processing in the United States, so these reports are processed and stored outside India. Sentry acts on FinCharya’s instructions and does not use the reports for its own purposes.
Google, Microsoft or Apple — only if you sign in through them. They confirm your email address to us; we tell them nothing about your money.
Public market-data sources — the closing-price records published by NSE and BSE, AMFI, and public fund pages. These are read for investments in general, on a schedule, and carry no information about you.
There is no analytics vendor, no advertising partner, and no CRM in the list.
5. Your rights under the DPDP Act, 2023
India’s Digital Personal Data Protection Act, 2023 gives you the following rights, and FinCharya is built to honour them without you having to ask twice.
- Access and portability. Settings → Account → Download my data gives you everything held against your account, as one open file any tool can read.
- Correction. Anything you entered can be edited in the app. If something imported is wrong, correct or re-import it — imports replace rather than duplicate.
- Erasure. Settings → Account → Delete account. This signs you out immediately, invalidates every session issued to you on every device, and releases your email address and phone number so they are no longer associated with you. The remaining rows are erased in FinCharya’s routine purge shortly afterwards.
- Withdrawal of consent. Disconnect a linked broker at any time; the session ends there and then. Deleting your account withdraws consent entirely.
- Nomination. You may nominate someone to exercise these rights on your behalf in the event of death or incapacity. Write to the address below.
- Grievance redressal. Write to [email protected]. We aim to acknowledge within 72 hours and resolve within 30 days. If you are not satisfied, the Act lets you escalate to the Data Protection Board of India.
6. How long things are kept
| What | How long |
|---|---|
| Your portfolio and account data | While your account is open |
| Anonymous usage records | 180 days, then deleted automatically |
| Sign-in identifiers after deletion | Released immediately on deletion |
| Remaining rows after deletion | Erased in FinCharya’s routine purge |
| Copies in the hosting provider’s backups | Until those backups expire (see below) |
| Error reports at Sentry | Until Sentry’s retention period ends. They are not tied to your account, so deleting it does not remove them |
| Market and price data | Indefinitely — it isn’t personal data |
About backups. The hosted database (section 3) is backed up by Turso as part of running it. When you delete your account the live rows go immediately, but a copy can remain in those provider-side backups until they expire on their own schedule. Those backups are never opened to restore one deleted account; they exist only to bring the service back after a failure. So here “deleted” means deleted from the running system now, and from the backups shortly after — not erased everywhere this instant. We would rather say that plainly than promise a speed we cannot deliver.
7. Security, in plain terms
Your session is held in a sealed cookie that scripts on the page cannot read and that cannot be tampered with; passwords are stored only in a scrambled form that cannot be reversed; and signing out or deleting your account invalidates every session already issued to you, on every device. The Zerodha connection is read-only in how it is built, not merely in how it is presented — it is not capable of placing an order, whatever happens. The riskiest file in the whole product, your statement PDF, is never uploaded, so it cannot leak from a server that never had it.
The hosted database is reached over an encrypted connection using a key held only on FinCharya’s server; it is never exposed to your browser, and there is no route that lets a request reach the database directly. If FinCharya or its hosting provider suffers a breach affecting your data, we will notify you and the Data Protection Board of India as the DPDP Act requires.
No system is perfect, and we would rather say so than claim otherwise. If you find a problem, please write to the address above.
8. Children
FinCharya is meant for adults managing their own or their household’s money. It is not directed at children, and accounts should not be created for anyone under 18.
9. Changes to this policy
This policy carries a version — the date at the top. When you accept it, the version you accepted is recorded against your account, so a later change is a new consent rather than a silent edit. Material changes will be surfaced in the app, not buried here.