MT940 Toolkit
Security
How MT940 Toolkit limits access to banking data and what the practical boundaries of a browser-side app are.Local processing
The file stays in the browser
Reading, decoding, parsing, filtering, and exporting happen client-side. The tool does not require sending the MT940 file to our server.
Browser storage
File history and the active Pro document may be stored locally in IndexedDB or localStorage so the user can resume work without uploading again.
No file-content analytics
The product assumption is no analytics over bank document content. Future diagnostics should use technical metadata without sending statement content.
Pro access protection
- Pro access is checked through the EasyCart protection mechanism.
- The protected part of the app is loaded only after a positive access decision.
- Pro code is built as a separate chunk and obfuscated to make copying harder.
- Obfuscation is not the same as backend protection of business logic. It is an intentional friction layer in a frontend-first model.
Recommendations for users
Use a trusted device
Do not upload bank statements on public or shared computers because the document may remain in local browser storage.
Clear storage after work
In Pro, use the option to remove the active document from memory. File history can be cleared from the file intake screen.