In the end you would build your compiler directly in assembler, so no compiling would be needed.
But if you run your compiler on compromised hardware it would still be possible to insert a backdoor in your programs without you knowing.
To mitigate this vector you would be required to build your own chips… with self developed and assembled machines all the way down starting at growing your own silicon crystals.
Shredding might not work the way you expect on a SD card.
The memory cells in a SD Card can only handle a limited amount of write operations. A SD card typically has more cells than needed, so the controller can switch through different cells to improve the overall lifetime of the card. Which means you can’t be sure which cells gets rewritten when shredding, so the data you want to be gone, could still be readable.
If you want to secure your data, use strong encryption. Because what you gonna do, if you can’t destroy or get rid of the SD card?
No, CryptPad uses OpenOffice for some document types, but is its own thing.
The realy nice feature is, all data is stored encrypted and is only decrypted locally in your browser. So not even the server admin can access your files.
I don’t know how MacOS time machine works exactly, but if it constantly writes on the SD card you should consider changing to an external SSD or HDD. The best backup isn’t helpful if your backup medium dies.