Most actual poisoning techniques don’t actually work that well. When I end up with a PDF, I usually strip out the existing text layer, apply a denoiser and a few other preprocessing steps to correct common errors, then a layout / reading order detector, and finally OCR the different blocs. This is against the most common poisoning techniques, and one of the most efficient, called : someone printed a document, forgot about it for 3 years, then scanned it slightly tilted (and dirty, crumpled, …), and the scanner decided to apply its crappy OCR.

Using screenshots of the PDF also avoid any kind of font face poisoning, and anti copy protection.

If you really, really need to protect your PDF, please consider accessibility first, then what would work imho is to use the scripting features of pdf to actually render your content on the fly. That would probably mess up most of the “automatic” processes.

I went the /e/os way and quickly turned back. Not to dismiss the effort of the maintainers, but it really felt like a frontend on lineage os meant to sell alternative cloud services. I did not find convincing arguments over a bare lineage os and the pretty much forced /e/ cloud was a total turn off.

I went the “real” security / privacy way and switched to grapheneos. Very happy overall, already went thought with 2 major os updates, no issues whatsoever. Only issue would be if you want Google pay (won’t work on graphene). You’d need a pixel phone if that’s in your budget. The pixel phones are great at photos, but pretty “meh” otherwise

I’ve not used it for quite a bit, but look at Thunderbird (a mozilla project iirc), it might do what you want as far as email is concerned. However do note that Microsoft is really closing things down in outlook/office these days, they really don’t like people using a “real” Linux (they want people to use windows with all their crap and start menu ads, and just have a small Linux VM they call the wsl )

It is also a huge deal because since (at least in France) the government forced ISPs to log DNS queries, a lot of browsers (and latest android and iOSversion’s) have now migrated to DNS over https or TLS DNS, which means that the only clear text DNS query they can intercept is the one to fetch your secure DNS service address. Now, having a trusted CA installed in browsers means that they can also spoof the identity of this secure name service, and regain a bit of control.

They invested a lot in surveillance technology (for both good and bad reasons), and https, DNS and encrypted messaging / phone calls means this was all for nothing.

And yes, by being authorized as a trusted CA, you can effectively spoof pretty much anything by setting a proxy. Some tools even leverage this for app analysis. Look up mitmproxy for example, or squid. A lot of companies already do this to inspect inbound / outbound traffic.