The datproject [1] had an interesting approach to this. Distributed data stores that you control and are addressable via hashes, with client-side apps that wo

The datproject [1] had an interesting approach to this. Distributed data stores that you control and are addressable via hashes, with client-side apps that work 100% in browser just by pulling in the distributed copies of that data (via its hash) - no backend slurping it up. Of course, it is not impossible for the client-side app to send the data back up to the server. Even if encrypted somehow once decrypted in the client for display to humans then its hard to protect that plain-text data. There were also some other open questions like if my distributed data is distributed, how can I "take it back?" I dont think there is a mechanism for that yet - some sort of TTL might work there though, if you can somehow bake it into the data/hash itself to avoid bad clients from ignoring TTL values before deleting/archiving. 1 - https://datproject.org/ https://datproject.org/