mirror of
https://github.com/zulip/zulip.git
synced 2025-11-06 23:13:25 +00:00
docs: Document push notification redacting setting.
This commit is contained in:
@@ -75,8 +75,8 @@ forwarding service).
|
|||||||
|
|
||||||
## Security and privacy implications
|
## Security and privacy implications
|
||||||
|
|
||||||
We've designed this push notification bouncer service with security in
|
We've designed this push notification bouncer service with security
|
||||||
mind:
|
and privacy in mind:
|
||||||
|
|
||||||
* All of the network requests (both from Zulip servers to the Push
|
* All of the network requests (both from Zulip servers to the Push
|
||||||
Notification Service and from the Push Notification Service to the
|
Notification Service and from the Push Notification Service to the
|
||||||
@@ -85,10 +85,17 @@ mind:
|
|||||||
* The code for the push notification forwarding service is 100% open
|
* The code for the push notification forwarding service is 100% open
|
||||||
source and available as part of the
|
source and available as part of the
|
||||||
[Zulip server project on GitHub](https://github.com/zulip/zulip).
|
[Zulip server project on GitHub](https://github.com/zulip/zulip).
|
||||||
The service's logging is designed to protect the privacy of users of
|
The Push Notification Service is designed to avoid any message
|
||||||
Zulip servers that are using the forwarding service.
|
content being stored or logged, even in error cases.
|
||||||
* The push notification forwarding servers are professionally managed
|
* The push notification forwarding servers are professionally managed
|
||||||
by a small team.
|
by a small team of security experts.
|
||||||
|
* There's a `PUSH_NOTIFICATION_REDACT_CONTENT` setting available to
|
||||||
|
disable any message content being sent via the push notification
|
||||||
|
bouncer (i.e. message content will be replaced with
|
||||||
|
`***REDACTED***`). Note that this setting makes push notifications
|
||||||
|
significantly less usable. We plan to
|
||||||
|
[replace this feature with end-to-end encryption](https://github.com/zulip/zulip/issues/6954)
|
||||||
|
which would eliminate that usability tradeoff.
|
||||||
|
|
||||||
If you have any questions about the security model, contact
|
If you have any questions about the security model, contact
|
||||||
support@zulipchat.com.
|
support@zulipchat.com.
|
||||||
|
|||||||
Reference in New Issue
Block a user