Contact PushNotifications.org for support

Choose the address that matches your question so it reaches the right review path. Do not send passwords, API tokens, VAPID private keys, complete subscription endpoints, or payment-card data by email.

Contact routes

Include the relevant page URL, account email or registered domain when appropriate, the expected result, and the smallest safe reproduction needed to understand the issue.

Product and technical support

For account access, SDK setup, campaign behavior, delivery errors, or API questions, email [email protected].

Security reports

For a vulnerability or suspected credential exposure, email [email protected] and follow the safe-reporting guidance on the security page.

Privacy requests

For access, deletion, retention, or subscriber-data questions, email [email protected] and identify the account or domain without attaching secret values.

Editorial corrections

For a factual correction, broken source, or unclear technical explanation, email [email protected] with the article URL and supporting evidence.

What to include

  • A concise subject that names the product area or page
  • The affected URL or registered domain
  • Browser and operating-system versions for Web Push problems
  • Reproducible steps, expected behavior, and actual behavior
  • A request identifier or bounded error message when available

What to remove

Redact authorization headers, session cookies, private keys, subscriber endpoints, browser authentication secrets, and unrelated personal data. A record ID or timestamp is normally safer than copying a confidential payload.

Route a request without exposing secrets

A useful request identifies the affected surface and supplies reproducible evidence while keeping credentials and subscriber data out of email.

Choose the route
The sender routes product problems to support, vulnerabilities to security, data-rights requests to privacy, and factual corrections to editorial review.
Name the affected record safely
An account email, registered domain, public page URL, timestamp, or request identifier locates the issue without revealing a token or endpoint.
Separate expected and actual behavior
A short reproduction explains what the user attempted, what the system returned, and what outcome was expected.
Keep evidence bounded
A redacted error message or screenshot should show only the relevant state. Remove cookies, authorization headers, keys, endpoints, and unrelated personal data.

Billing and legal questions

Use [email protected] for plan or checkout questions and [email protected] for terms-related notices. The pricing page lists current allowances, while the terms and privacy policy describe the governing service and data boundaries.