Product and technical support
For account access, SDK setup, campaign behavior, delivery errors, or API questions, email [email protected].
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.
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.
For account access, SDK setup, campaign behavior, delivery errors, or API questions, email [email protected].
For a vulnerability or suspected credential exposure, email [email protected] and follow the safe-reporting guidance on the security page.
For access, deletion, retention, or subscriber-data questions, email [email protected] and identify the account or domain without attaching secret values.
For a factual correction, broken source, or unclear technical explanation, email [email protected] with the article URL and supporting evidence.
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.
A useful request identifies the affected surface and supplies reproducible evidence while keeping credentials and subscriber data out of email.
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.