# iOS/Android Push Notifications on Self-Hosted Discourse (Docker)

**URL:** https://meta.discourse.org/t/ios-android-push-notifications-on-self-hosted-discourse-docker/394149
**Category:** Support
**Tags:** notifications, push-notifications, ios
**Created:** [January 23, 2026, 1:37am UTC](https://meta.discourse.org/t/ios-android-push-notifications-on-self-hosted-discourse-docker/394149 "2026-01-23T01:37:05Z")
**Posts on this page:** 1
**Showing post:** 15

<div class="post-metadata">

### Author: ![featheredtoast](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/featheredtoast/32/116994_2.png) [@featheredtoast](https://meta.discourse.org/u/featheredtoast)
#### Post date: [April 3, 2026, 10:21pm UTC](https://meta.discourse.org/t/ios-android-push-notifications-on-self-hosted-discourse-docker/394149/15 "2026-04-03T22:21:00Z")

</div>

It’s to prevent the odd case where you don’t want push notifications to go out to logged out devices. You’re on a device with push notifications turned on, but you’re done, so you log out.

Then someone later then sends you a sensitive message over PM. A push notification goes out to all registered devices. The device in which you logged out is still technically registered so it still receives the full preview of your notification. Oops.

I played it safe on its initial push by just wiping all keys which is obviously overkill and annoying. Perhaps we should start associating the push notification subscriptions to a specific user session or somehow confirm that the expected user is still logged in instead?

---

_[View the full topic](https://meta.discourse.org/t/ios-android-push-notifications-on-self-hosted-discourse-docker/394149)._