> ## Documentation Index
> Fetch the complete documentation index at: https://notifizz.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Platform support & privacy

> What web push looks like on macOS, Windows, Android, Safari and iOS — and how the end-to-end encryption keeps payloads private.

# Platform support & privacy

## TL;DR

* **Chrome, Edge, Firefox** — full support on desktop and Android: title, body, banner image, click action.
* **Safari (macOS)** — text only: no banner image, no action buttons.
* **iOS / iPadOS** — web push exists **only for installed PWAs** (Add to Home Screen, iOS ≥ 16.4). A regular Safari tab cannot receive one.
* **Truncation is real.** macOS shows about one line of body, Windows about two. Front-load your message; the composer previews each platform.
* **End-to-end encrypted.** Push services (Google, Mozilla, Apple) relay ciphertext they cannot read.

## Per-platform behaviour

| Platform               | Body shown | Banner image | Notes                                               |
| ---------------------- | ---------- | ------------ | --------------------------------------------------- |
| Windows (Chrome/Edge)  | \~2 lines  | Yes          | Toast in the notification center, stays in the feed |
| macOS (Chrome/Firefox) | \~1 line   | Preview only | Banner top-right, disappears to Notification Center |
| macOS (Safari)         | \~1 line   | No           | Text-only rendering                                 |
| Android (Chrome)       | Expandable | Yes          | Rich expanded view on pull-down                     |
| iOS / iPadOS           | \~2 lines  | No           | **Installed PWA only** (iOS ≥ 16.4)                 |

Write for the worst case: a **title under 48 characters** with the point in the first words, and a **single-sentence body under 120 characters**. The composer enforces these budgets with live counters and an OS-real preview for each platform.

## Privacy

Web push is one of the most privacy-preserving channels there is:

* **Payloads are end-to-end encrypted** (RFC 8291). The message is encrypted with keys that exist only in the recipient's browser and the Notifizz backend; Google's, Mozilla's and Apple's push services see ciphertext.
* **Notifizz stores no message content in the clear at rest** beyond what you see in your own delivery history, and never stores the subscription's cryptographic keys unencrypted.
* **Subscriptions are anonymous capability URLs.** They identify a browser's push mailbox, not a person; Notifizz links them to the same user id you already use for the Notification Center — no new personal data is collected.
* **Deletion is honoured end to end.** Erasing a recipient (GDPR) removes their subscriptions immediately.

## FAQ

<AccordionGroup>
  <Accordion title="Why does my push look different on macOS and Windows?">
    Each OS renders notifications with its own layout and truncation rules — that's outside anyone's control. The composer's platform switcher shows the exact rendering per OS before you ship.
  </Accordion>

  <Accordion title="Can iPhone users receive web pushes?">
    Only if your product is installed as a PWA (Add to Home Screen) on iOS 16.4 or later. For a regular mobile web audience, treat web push as a desktop/Android channel and keep email or the Notification Center as the fallback for iOS.
  </Accordion>

  <Accordion title="Does Notifizz read my notification content?">
    Notifizz composes and encrypts the payload server-side to deliver it — the content is yours and appears only in your dashboard's delivery history. The transport (browser push services) never sees it in the clear.
  </Accordion>
</AccordionGroup>