You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please improve Rocket.Chat in a way that the content of the message isn't going through third parties (e.g Google, Apple etc) when push notification is enable.
For some of us this might be important as we may have rules which prohibit sending data to third parties.
I shared some thoughts about this issue with @Sing-Li
sing.li 3:21 PM
@kristjan.kullerkann: you are correct on all counts. Do I understand correctly that Rocket.Chat is using Google Cloud Messaging for Android and Apple Push Notification Service for IOS? yes
And there is also a possibility to use Rocket.Chat gateway which in the end uses also Google Could Messaging and/or Apple Push Notification Service? yes
Does this mean that messages them self are also going through Google/Apple? the content of the message (at least the first part) is the subject of the notification
Or this is not the case - GCM is just notifing the device to pull new messages? the content of the message (at least the first part) is the subject of the notification ... for your requirement - please open a new issue to have an option to _not send the actual message content
the content of the message (at least the first part) is the subject of the notification ... for your requirement - please open a new issue to have an option to not send the actual message content
The text was updated successfully, but these errors were encountered:
Just in case I will mention that when disabling Push notifications (by default through https://rocket.chat), then that it would take any effect you will have to restart RC. Until restart, push notifications are still sent.
Please improve Rocket.Chat in a way that the content of the message isn't going through third parties (e.g Google, Apple etc) when push notification is enable.
For some of us this might be important as we may have rules which prohibit sending data to third parties.
I shared some thoughts about this issue with @Sing-Li
The text was updated successfully, but these errors were encountered: