Given that Lettera edits files directly on disk, I believe it is the user’s responsibility to look after this. iCloud Drive does E2EE if you have ADP enabled, for instance, but that’s on you, not on the app.
A password at the app level doesn’t really make much sense. Lettera edits your files on disk, so anyone with access to the machine could just bypass Lettera altogether and open the files another way. It would give a feeling of security without the substance.
Same reasoning for document-level locking. There aren’t really open standards for per-file encryption (a password-protected zip is about the closest thing), and that’s something better left to the user’s own setup than baked into the editor.
Both local and iCloud encryption are handled by the standard macOS security layer, so your files get the same protection (FileVault on disk, Apple’s encryption in transit/at rest for iCloud) as anything else on your Mac.
this is great and makes total sense. I am still caught up in an App managing access to the data which is not the case here. I need to reset my thinking and keep in mind you have a clear separation of data from the app. It would be like TextEdit having to have a password. The password just becomes a nuisance in this case as you indicated. I should have thought this through a bit more, sorry for the interrupt.