Storage is content-addressed through IPFS; the client checks every hash; any node can serve ciphertext; disk or S3 sits underneath.

It is why a server cannot alter data and why any server will do.

Underneath Peergos is a content addressed store, provided by IPFS. Every block of data is named by its hash. Its fingerprint.

Ask for a hash, get the block. Any Peergos node can serve it, if you are allowed to have it.

The client checks the hash of every block it reads or writes. A server that changes a byte is caught at once.

What is in a block? Ciphertext. The store holds sealed blobs. It never holds a plain file.

Where the blobs sit does not matter. A local disk, or any S3 compatible bucket, with no loss of privacy.

Check yourself. What does the client do with every block it reads?