Local file encryption
Plenty of services call themselves secure and still upload your file to a server to encrypt it there. With Loclavis the processing happens in your browser. This page explains exactly what that means and where the boundary runs.
What local means
Your file is read from disk into the browser's memory, encrypted there section by section, and written back out as a file. There is no network connection between those steps. The password is turned into a key in the browser and then overwritten, as far as JavaScript allows.
What does happen online
The website itself has to be loaded, and every host records technically necessary access data while doing so. If you buy Plus, payment runs through Stripe, and the licence check later asks about the subscription status. None of that touches your files. The details are in the privacy statement.
Why we do not word it more strongly
A sentence like \u201cLoclavis processes no data at all\u201d would be false the moment somebody buys something, or even just loads the page. So we separate the file processing, which is entirely local, from operating the website, which happens online like it does for every website.
How to check it yourself
Open your browser's developer tools, switch to the network tab and protect a file. You will see the requests for the page itself and then nothing more. No upload, no request to a third party. The same check runs automatically in our test suite on every run.
What local does not protect against
If your device is already compromised, no web application helps. Malware watching you type the password sees it regardless of where the encryption happens. Local processing reduces the risk of your data sitting somewhere else. It does not replace basic device hygiene.