I'm thinking about adding JavaScript and CryptoJS to my personal website, airikr.me, despite stating the following on the privacy page:
Sending the IP address with end-to-end encryption to the server, is not planned as this requires JavaScript. airikr.me is a hobby project where the challenge is to never use JavaScript (except for Plausible).
The solution: if JavaScript is enabled, use CryptoJS instead of Halite.
Still thinking if this is needed, though. Well, E2EE should always be needed everywhere regarding personal data. But since it's "only" the IP address that will be encrypted... I don't know. But what I do know is that the IP address is personal data and should be encrypted with CryptoJS.
I'm conflicted 
Please, tell me if I need to add E2EE to my personal website for only storing the IP address with E2EE or not.
EDIT I removed the poll after knowing that you can't get the IP address with JavaScript.
This entry was edited (2 weeks ago)
Samuel
in reply to Airikr • • •what is not e2ee with https? Why would you need more? Also, why would you need that from the client side? You would have the client IP address on the server backend anyway.
What am I not getting here?
Airikr
in reply to Samuel • • •In order to keep high-standard privacy, personal data needs to be sent encrypted to the server and not be encrypted on the server side. What I know, HTTPS only transfers the data securely to the server.
Ah, didn't knew you can't get the IP address via JavaScript
My bad. I'll keep it as it is now then 
Samuel
in reply to Airikr • • •yes https transfer the data from the client/browser securely to the server where it can be read by the server backend. If that is your objective, to read the data from the server backend, then https is enough.
The server will be able to read the IP address regardless. However if you don't want to save that information on the server, that is up yo you. But your web server logs will probably save it as default. If you don't want that, you have to configure your web server
Samuel
in reply to Samuel • • •Airikr
in reply to Samuel • • •Now when I know how to add end-to-end encrypted data to my server on my web projects, I want to add this feature to so many of my projects as I can.
But since airikr.me only store the IP address upon interaction, I thought that encrypting it with E2EE would be a good thing. But since the IP address is only fetchable on server side, no need to add that feature
All other data that the visitors publish on airikr.me, will be public so no need for encryption for that.
Samuel
in reply to Airikr • • •great!
Though I would argue e2ee is probably not the term that is best suitable for this case.
Yes, the only two parties are the client and the server and thus encrypting the traffic would make sure no other parties can see the plaintext (and would make the communication e2ee).
However, almost always there are two (or more) clients that want to communicate and using a server in doing so when talking about e2ee. E2ee would mean the server can't see the plaintext, only the clients can.