Privacy Protocol.
Last Verified Instance: May 6, 2026
The Core Mandate
Financial privacy is a fundamental human right. Our architecture is physically incapable of "seeing" your data because the extraction logic resides exclusively within your local runtime.
Local Extraction
Your statements are read directly into browser RAM. No packets containing your financial data are transmitted across the network card.
Wasm Isolation
The parsing engine runs in a sandboxed WebAssembly environment, isolated from other browser tabs and processes.
Zero-Persistence
We do not use local storage or cookies to cache your financial data. Once the tab is closed, the memory is purged.
Anonymized Telemetry
We only collect minimal technical metrics (e.g. success rates) to maintain the hub. No PII is ever ingested.
1. Node Operations
When you initialize a conversion protocol, the extraction happens locally on your computer's CPU. The file is triggered for download directly to your machine. At no point is the content of your bank statement uploaded to any server or cloud service.
2. Third-Party Interfaces
We use Vercel for hosting and generic, privacy-respecting analytics to monitor site performance. These partners do not have access to the files you convert on our site, as the conversion logic remains strictly within your local node.
3. Intelligence Updates
We may update this protocol occasionally to reflect new security standards. Any changes will be notated on this instance with an updated verification date.
Contact Support Line
For inquiries regarding our security whitepaper or privacy protocols.
nadimhamza41@gmail.com