|
|
|
|
|
by franky47
2188 days ago
|
|
I agree that giving someone else your data is the issue. But as an alternative to self-hosting, I'm working on an end-to-end encrypted approach [1]. I can offer a service (much easier to setup and maintain than self-hosting), but I don't have the data (not in a useable/leakable way). https://chiffre.io |
|
Also, what does end-to-end encryption mean? HTTPS already does that, right? If there's some extra encryption on top, does it mean that the client will encrypt the analytics data before sending it?
That sounds interesting, but it feels like the whole purpose is to hide the data from your company. How can you make sure that you don't have access in any way to the data, if you also store the user accounts that have access to this data? If you wanted, what would stop you from logging in as that user and viewing his data?