<h1>ntfy.sh | PUT/POST push notifications to your phone</h1>
<h1>Send push notifications to your phone or desktop via PUT/POST</h1>
<p>
<b>ntfy</b> (pronounce: <i>notify</i>) is a simple HTTP-based <ahref="https://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern">pub-sub</a> notification service.
It allows you to send notifications to your phone or desktop via scripts from any computer,
...
...
@@ -83,8 +95,8 @@
<h2id="subscribe"class="anchor">Subscribe to a topic</h2>
<p>
You can create and subscribe to a topic either in this web UI, or in your own app by subscribing to an
<ahref="https://developer.mozilla.org/en-US/docs/Web/API/EventSource">EventSource</a>, a JSON feed, or raw feed.
You can create and subscribe to a topic either <ahref="docs/subscribe/phone/">using your phone</a>,
in <ahref="docs/subscribe/web/">this web UI</a>, or in your own app by <ahref="docs/subscribe/api/">subscribing via the API</a>.
</p>
<divid="subscribeBox">
...
...
@@ -160,18 +172,6 @@
And another one with a smiley face 😀
</code>
<h2id="privacy"class="anchor">Privacy policy</h2>
<p>
Neither the server nor the app record any personal information, or share any of the messages and topics with
any outside service. All data is exclusively used to make the service function properly. The one exception
is the Firebase Cloud Messaging (FCM) service, which is required to provide instant Android notifications (see
FAQ for details).
</p>
<p>
The web server does not log or otherwise store request paths, remote IP addresses or even topics or messages,
aside from a short on-disk cache (for {{.CacheDuration}}) to support service restarts.
</p>
<centerid="ironicCenterTagDontFreakOut"><i>Made with ❤️ by <ahref="https://heckel.io">Philipp C. Heckel</a></i></center>