Origin matching
The subscription API accepts a browser request only when its Origin header exactly matches the HTTPS origin registered for the supplied site key.
PushNotifications.org encrypts subscription endpoints, browser keys, and private VAPID keys at rest; uses Google OpenID Connect only for account sign-in; hashes API tokens; and isolates records by registered website. Website owners must publish an exact verification file before installation can continue.
Sensitive push records are encrypted, Google handles sign-in only, API tokens are hashed, and private VAPID keys remain server-side. The browser receives only the VAPID public key and a non-secret site key.
State-changing account requests require a server-managed session and CSRF token. Responses apply a restrictive Content Security Policy, frame protection, MIME sniffing protection, a limited referrer policy, and secure-cookie behavior in production.
A Web Push subscription contains a delivery endpoint and encryption keys. These values are capabilities, not ordinary marketing identifiers, and should be handled as sensitive data.
The subscription API accepts a browser request only when its Origin header exactly matches the HTTPS origin registered for the supplied site key.
Each registered site receives an independent VAPID keypair. The public key can create subscriptions; the encrypted private key is used only by the delivery worker.
Subscription endpoints, authentication secrets, browser public keys, and VAPID private keys are encrypted before database storage. A hash supports endpoint deduplication without exposing the endpoint itself.
A permanent 404 or 410 response from a push service retires the affected subscriber record from future sends. Manual opt-out is also available from the authenticated dashboard.
Campaign creation is limited to authenticated account users or a bearer token associated with that account. The selected website must belong to the account. Notification titles and bodies have bounded lengths, and destinations must be public HTTPS URLs without credentials or custom ports.
The delivery worker excludes opted-out records, enforces the current plan allowance, and avoids another attempt to the same subscriber within a rolling 24-hour window. Those controls are not a substitute for advanced preferences, quiet hours, or audience segmentation, which are not presented as implemented features.
Send a concise report to [email protected] with the affected URL, reproducible steps, expected result, actual result, and a safe way to follow up. Do not include live private keys, access tokens, subscriber endpoints, or unrelated personal data.
For data-handling details, read the privacy policy. For implementation boundaries, use the Web Push API documentation, the secure implementation guide path, and the payload encryption guide.
Protocol references: RFC 8291 defines Web Push message encryption, and RFC 8292 defines VAPID application-server identification.