Hello,
We have recently started using amplitude for tracking our Web and mobile platforms.
An issue we encountered when implementing the client-side libraries is that it's not possible to encrypt fields before sending the events to Amplitude.
This means that all data we push to Amplitude from client-side libraries is available to the user. We wish to restrict this by using encryption as some fields we want available in Amplitude we consider private fields.
The idea is to have an encryption key set-up that we use to encrypt the data. That way the user cannot see the data we sent. Then when Amplitude receives the events, amplitude decrypts the data before saving it to the platform.
I understand it's also possible to use the server-side HTTP api, but that requires much more effort for implementation