Thank you for your comment and sorry for the late response.
I will try to answer your questions.
PushStaq is hosted on Heroku servers based in the US. I find it the fastest way to push my code and deploy quickly.
PushStaq communication is secured with HTTPS by default at all times, this ensures secure client server communication when using the web app.
Messages that are sent through the web app to the server are plain text and visible by default, to allow developers easy use of the API to trigger notifications or connect to third party services such as IFTTT.
If you wish to have another layer of security and privacy and encrypt the messages so the server saves the data encrypted, you can enable the End-to-end encryption feature.
I wrote a blog post about secure communication and private messaging here - Secure and private messaging with End-to-end encryption | PushStaq Blog
If you enable End-to-end encryption in your channel it will also apply to Push notifications (the message is sent encrypted as push message and decrypted at the client),
Unlike other existing services that do not support this (Are messages/notifications encrypted? | Pushover Support) or Pushbullet which supports it partially (they don't encrypt links for example)
I should add that the Node-Red PushStaq node latest update includes support for End-to-end encryption as well, here is the Node-Red tutorial - Node-Red Push notifications with PushStaq | PushStaq Blog
It took time but I have added them to the website (which I am sure I will update from time to time), they also include GDPR and statements for EU/UK as well.
I want to thank you for your constructive criticism.
It would be nice if you would like to contact me if you have more questions or suggestions that I can improve PushStaq.
BTW PushStaq didn't and currently don't use Google analytics.