Check this yourself
We would rather show you how Sachfolio works than ask you to take our word for it. This page lists what we say about your privacy, how each statement will be tested, and how you can watch it yourself.
Privacy label
Four statements, each with the automated test that checks it before every release.
-
Your PDF
Your PDF and password stay on this device. Nothing is uploaded.
These tests open the invented sample statements, record every request the app makes, and fail if one carries the file name, the file's text or its hash. Two further tests make sure that check does catch a deliberate leak.
Checked by test:
requests after a file is picked do not depend on the file;choosing a file downloads no code;harness: the file name in a self-origin URL fails the test;harness: statement text in a header fails the testChecked automatically before every release goes live.
-
Your password
Your password is used only to open the file on this device. It isn't stored or sent.
These tests open an invented locked statement with a wrong and then the right password, an invented NSDL statement locked with a PAN-shaped password, as depository statements are, and an invented statement locked with a password the app made for a CAMS request. They fail if any of these passwords appears in any request address, header or body, or anywhere the browser keeps data for this site afterwards (local and session storage, cookies, IndexedDB, the offline cache).
Checked by test:
encrypted statement: prompt, wrong password kept, right password opens;the password and the statement are absent from browser storage after reading;NSDL statement: the PAN password opens it on the device and its mutual funds show;CAMS request: the password made here opens the PDF with no typing and is kept nowhereChecked automatically before every release goes live.
-
Network
The Sachfolio app runs entirely in your browser. It never sends your statement to us or to anyone else.
These tests fail if the page or its workers request anything from another site or open a WebSocket, and check that after the first visit nothing a statement needs is fetched from the network. The only other sites the app opens are the CAMS and KFintech request pages, in a new tab you start, with nothing added to the address and no Referer. Further tests make sure these checks do catch a deliberate off-site request, a new tab to another site, an address with something added and a Referer.
Checked by test:
landing loads only from its own origin;after the first visit, nothing a statement needs reaches the network;harness: an off-origin request fails the test;harness: a WebSocket fails the test;CAMS request: new tabs open only the registrars' request pages, with nothing added and no Referer;harness: a new tab to another site fails the test;harness: a registrar tab with something added to the address fails the test;harness: a registrar tab that sends a Referer fails the testChecked automatically before every release goes live.
-
Analytics
No analytics, trackers or third-party scripts.
These tests fail if any script, font, stylesheet or other request comes from a site other than Sachfolio's own. A further test makes sure that check does catch a deliberate off-site request.
Checked by test:
landing loads only from its own origin;harness: an off-origin request fails the testChecked automatically before every release goes live.
Run the self-test
Coming soon. A button here will list every request this tab made to other sites, and every request our policy blocked, so you can see the result without any tools. Until then, use the browser steps below, or open What leaves this device in the app after you open a statement.
It will also say what it can't see: some WebSocket traffic, browser extensions and other tabs.
Watch the network yourself
On a computer, with Chrome or Edge
- Open Sachfolio.
- Press F12 (on a Mac, Cmd + Option + I) to open the developer tools, then choose the Network tab.
- Tick Preserve log, and set the filter to All.
- Reload the page. Then choose your CAS PDF and open it as usual.
- Each row in the list is one request this tab made. To see where each one went, right-click a column heading and add Domain.
What this shows: every request this tab made, where it went and how big it was. You can check that none goes to another site, and that none made after you chose the file is large enough to carry your PDF.
What it can't show: requests made by browser extensions or by other tabs.
On a phone, with airplane mode
- Open Sachfolio once while you're online. After the page finishes loading, wait about half a minute while it saves itself on your device.
- Turn on airplane mode, and make sure Wi-Fi is off too.
- Choose your CAS PDF and open it.
What this shows: if your results appear, Sachfolio read your statement with no connection at all.
What it doesn't show: what happens after you reconnect. The network log above is the way to check that.
Our Content Security Policy, word for word
A Content Security Policy is a list of rules the browser enforces on our pages. This is ours, copied into this page from our build configuration when the page was built:
default-src 'none'; script-src 'self'; worker-src 'self'; style-src 'self'; font-src 'self'; img-src 'self'; connect-src 'self'; object-src 'none'; base-uri 'none'; form-action 'none'; frame-ancestors 'none'; require-trusted-types-for 'script'; trusted-types sachfolio
In plain words:
'self'means Sachfolio's own site. Scripts, styles, fonts and workers load only from there.connect-src 'self': the browser blocks the page from sending requests to any other site.form-action 'none': no form on our pages can be submitted anywhere.frame-ancestors 'none': no other site can show our pages inside its own.
The policy doesn't stop requests to our own site. That is what the privacy label tests above are for.
To compare, open the developer tools as described above, choose the first request in the Network tab, and find Content-Security-Policy under Response Headers.
What our host logs, and what we could be made to hand over
Sachfolio is hosted on Amazon Web Services: the site's files sit in a storage bucket in Mumbai (ap-south-1) and are served by Amazon CloudFront.
For each request to this site, our host logs the time, your IP address, the page or file requested, your browser's name, and the page that linked here if your browser sends it. These logs never hold your statement, its password or anything read from it, because none of that is ever sent (the tests above check this). We keep the logs in India for one year, locked against deletion, as Indian cyber-security rules (CERT-In) require for at least 180 days.
If an Indian authority lawfully asks, we could be made to hand these logs over. They show that a device visited this site, never what was in anyone's statement.
Build hashes and source
Every release is built twice from the same source, and the two builds must match file for file before it is published. The list of every published file with its SHA-256 fingerprint is kept with each release.
The source code will be published under its licence once the licence review is done, so anyone can rebuild a release and compare the fingerprints. Until then, this page says so rather than claim otherwise.
Accuracy and abstention report
Not published yet. It needs a set of real statements kept aside for testing, and we are still collecting them.
It will say, for a set of statements kept aside for testing, how many figures matched, how many didn't, and how often Sachfolio said it couldn't check something instead of guessing.
Our design rules
We design Sachfolio by these rules. They are based on the Central Consumer Protection Authority's 2023 guidelines on dark patterns, plus a few of our own. A written self-audit against them will be published with each release.
- No countdowns, “limited time” offers or fake urgency.
- No account, email, phone number or app install needed for any result, download or printout.
- No pre-ticked boxes, anywhere.
- No guilt-trip buttons: declining is always a plain choice.
- No sponsored content, affiliate links or fund placements.
- No nagging: we ask once, and no push notifications.
- No fear wording, risk scores or red and green for gains and losses.
- No fake progress bars or artificial delays.
- No network request to another site unless you turn it on, and we tell you first.
What Sachfolio never does
- To read your statement, asks only for its password, never a phone number, email, OTP or an account. For NSDL and CDSL statements that password is your PAN; it opens the file on your device and is never sent.
- Never calls you or messages you first, on WhatsApp or anywhere else.
- Never asks for your statement password over a call or a message.
- No ads, no trackers and no third-party scripts.
Reporting a security problem
If you find a way that Sachfolio could leak a statement, its password or anything read from it, or a way to change what this site serves, please email security@sachfolio.com. Say what you found and how to reproduce it.
- We aim to reply within 7 days and to fix serious problems first.
- We won't pursue anyone who reports in good faith, tests only against their own data, and gives us reasonable time to fix the problem before telling others.
- Please don't access other people's data, overload the site, or try to trick people.
There is no paid bug bounty.
Contact and grievance officer
Sachfolio is an independent product built and run in India. Its Grievance Officer answers questions, complaints and data requests at the address below.
- Questions, complaints or requests about your data: grievance@sachfolio.com
- Security reports: security@sachfolio.com (also in security.txt)
We aim to reply within 7 days. See also our terms of use and privacy notice.