Home Privacy
Privacy policy
Written in plain English, because a policy nobody can read is not a policy. Short version: your statement is parsed on your device, nothing is uploaded, there is no account, and in this release there is no analytics of any kind.
Your statement files
When you open a MetaTrader statement in the analyzer, the browser hands the file to page JavaScript through the standard File API. TapeSheet decodes it, parses it with the browser’s own DOMParser, and computes every metric locally. The file is never transmitted, copied to a server, or shared with a third party, because there is no code path that could do so.
You can verify this without trusting us. Open the analyzer, open your browser’s developer tools, select the Network tab, and load a statement: no requests appear. Stronger still, disconnect from the internet first — the analyzer keeps working, because the entire application arrived with the page.
Your journal and settings
Journal entries, tags, daily notes, prop-firm rule sets, your settings and your most recent parsed dataset are stored in IndexedDB, a storage area inside your own browser profile on your own device. We cannot read it, and neither can anyone else without access to your machine and browser profile.
Practical consequences, stated honestly:
- Clearing browsing data or “site data” for this site deletes your journal permanently.
- Private / incognito windows usually discard everything when the window closes.
- Some browsers evict site storage under disk pressure or after long periods of disuse.
- Your journal does not follow you to another browser, another profile, or another device.
- There is no cloud copy for us to restore, because we never had one.
Use Settings → Export in the analyzer to write a single JSON backup file, and keep it wherever you keep important files. Settings → Import reads it back on any machine. If storage is unavailable in your browser, TapeSheet displays a banner and keeps working for the session only.
Accounts, emails and broker credentials
There is no sign-up, so we hold no email address, no password and no profile. TapeSheet never asks for broker credentials, investor passwords, API keys or MetaTrader logins, and has no ability to connect to a trading account. The only input it ever reads is a report file you chose yourself.
Analytics
This release contains no analytics. Nothing is counted, and no request leaves your browser at all. The section below describes what will be counted when it is switched on, so it is on this page before it ships rather than after.
Two separate things count things here, and the difference matters, so both are described below in full. Neither one runs inside the analyzer at /app/.
1. Our own counter — no cookies, on every page
A short, fixed list of anonymous events: that a page was viewed, that a statement was dropped in, whether it parsed, which step failed if it did not, that a journal entry was created, that a backup was downloaded. There is no identifier of any kind in any of them — no account, no cookie, no login, no device id, and nothing that links one event to another or to you.
It is ours, not a third party's: about thirty lines that post to this domain. No outside company's code runs on this site to make it work, which is why it needs no cookie banner — there is nothing stored on your device to ask you about.
2. Google Analytics — cookies, and only on our articles
On our content pages — the guides, calculators, glossary and comparison pages — we also use Google Analytics, to see which articles people actually find useful. It sets cookies, and the data goes to Google. We are not going to pretend otherwise: that is the trade, and it is why you get asked.
It is never loaded on the analyzer at /app/. That is the page holding your trades, and no third-party code runs there at all — not Google's, not anyone's. It is also never loaded on a shared report at /r/, because those get embedded on other people's websites and tracking their visitors is not ours to do.
Nothing from Google loads until you accept. Not a script, not a cookie, not a request. If you ignore the banner, or decline it, your browser never contacts Google at all — most sites load the tracker immediately and merely withhold the cookie, and we thought that made the banner dishonest. If your browser sends Do Not Track we skip the question entirely and load nothing.
Neither counter ever receives your trades. Not a symbol, not a price, not a profit or loss, not a date, not a balance, not your account number, not your broker, and not the name of your file.
The one thing we record about a statement is a template fingerprint: a short hash of the section and column headings your broker's export uses, with every digit stripped out first. Two people at the same broker with completely different trading produce the identical fingerprint. It exists so we can tell which broker layouts fail to parse without ever seeing what is inside one.
Counting is done by a cookieless analytics provider, and the request goes to this domain and is passed on from our side — your browser never contacts them. To count a visit without a cookie, they derive a daily-rotating anonymous number from your IP address and browser version and then discard both; the IP is not stored and never reaches us in any log we keep. That is the whole mechanism, and it is why there is no consent banner: there is nothing stored on your device to ask you about.
We honour Do Not Track. If your browser sends it, nothing is counted. You can also switch counting off just for this browser, whatever your browser sends:
None of this changes the rule that matters: your statement is parsed in your browser and is never uploaded, whatever is being counted.
Advertising
TapeSheet is free and intends to stay free. The plan for paying for the domain and the maintenance is advertising on content pages — guides, calculators and explainers — and never inside your data.
- Today: no ad network is loaded anywhere on this site. The dashed boxes on guide pages are static placeholders that make no network requests.
- If ads are enabled later: they would appear only on content pages such as the export guides — never in the analyzer, dashboard, trade journal, trade drawer or prop-firm tracker.
- What that would mean for you: ad networks such as Google AdSense generally set cookies or read device identifiers to measure and target ads, and that would happen on content pages only. Those networks would be independent controllers of the data they collect, under their own policies.
- What would not change: your statement files and journal would remain on your device. Ad code would never run on the analyzer, so there is no ad-tech surface anywhere near your trading data.
When that day comes, this page is updated first, and the /ads.txt file at the site root — today a comment-only placeholder with no seller records — is filled in with the authorised sellers.
Hosting and server logs
The site is static files served from a CDN (Cloudflare Pages). Like any web host, the CDN processes the ordinary technical information every HTTP request carries — IP address, user agent, requested path, timestamp — to deliver pages and to mitigate abuse. We do not build profiles from it, and it never contains anything from your statement or journal, which are never sent over the network.
Children
TapeSheet is a tool for adults analysing their own trading records and is not directed at children under 13.
Your rights
Rights such as access, correction, deletion and portability normally apply to data a company holds about you. We hold none. Your data is on your device: deletion isSettings → Clear all data (or clearing site data in your browser), and portability is Settings → Export, which hands you the complete contents in a plain JSON file.
Changes
Material changes will be reflected here with a new “last updated” date. Anything that changes what leaves your device will also be announced on the home page.
Contact
Questions about this policy: hello@tapesheet.com, or see the contact page. See also theterms of use, the risk disclaimer, andhow this site makes money.