The core principle
PulsePigeon is for mail that recipients asked for or expect: transactional messages tied to a user relationship, and marketing messages sent with consent. Everything in this policy follows from that principle.
If you cannot show that a recipient consented to your mail, or that the message is a transactional response to something they did, do not send it through PulsePigeon.
Consent and permission
You may only send to recipients who fall into one of these categories:
- they explicitly opted in to receive your mail (for example, a confirmed newsletter signup or a checkbox that was not pre-checked);
- they have an active account, order, subscription, or comparable relationship with you, and the message is relevant to that relationship;
- the message is a direct transactional response to an action they took (a password reset, receipt, security alert, or shipping notice).
You must keep records of consent and be able to produce them on request. Consent obtained by a third party, or bundled into unrelated terms, does not qualify.
Prohibited recipient sources
Never permitted. The following are grounds for immediate suspension regardless of message content.
- Purchased, rented, leased, or otherwise acquired third-party lists.
- Scraped, harvested, or appended email addresses.
- Addresses obtained without clear, specific consent.
- Cold outreach and prospecting to recipients who have no prior relationship with you.
- Re-mailing to addresses that have unsubscribed, bounced, or complained.
Prohibited content and conduct
You may not use PulsePigeon to send or facilitate:
- spam, chain letters, pyramid or multi-level-marketing schemes, or “get rich quick” offers;
- phishing, spoofing, credential harvesting, or messages that misrepresent the sender, domain, or origin;
- malware, ransomware, or links to malicious, deceptive, or fraudulent sites;
- content that is unlawful, defamatory, harassing, hateful, or that infringes intellectual property or privacy rights;
- regulated content that you are not licensed or permitted to send (for example, certain financial, gambling, pharmaceutical, or adult content), or content targeting minors;
- attempts to evade filtering, obscure links or sender identity, or manipulate engagement metrics.
Technical and deliverability requirements
To protect shared sending reputation, you must:
- authenticate your sending domains with SPF, DKIM, and a DMARC policy, and keep DNS accurate;
- include a working one-click unsubscribe and honor opt-outs within the timeframe required by law;
- maintain list hygiene: promptly suppress hard bounces and complaints, and remove disengaged recipients;
- respect sending limits, warm-up schedules, and throttles, and not attempt to circumvent them by splitting volume across accounts;
- keep complaint and bounce rates within accepted thresholds. Sustained high rates may result in throttling or suspension.
Monitoring and enforcement
We operate automated and manual controls, including pre-send content scanning, bounce and complaint monitoring, blocklist monitoring, and vetting. We may inspect metadata and, where necessary to investigate abuse, message content.
Depending on severity, we may warn you, throttle or pause sending, require remediation, or suspend or terminate your account. For active, ongoing abuse or a legal or reputational emergency, we may act immediately and provide notice afterward. We will act proportionately and, where practicable, give you an opportunity to cure.
Appeals
If your sending is suspended and you believe it was in error, you may appeal to [email protected]. We review appeals promptly and will explain the basis for a decision where we can do so without compromising an investigation.
Reporting abuse
To report mail you believe violates this policy, contact [email protected] with the message headers and, where possible, the full message. We investigate every credible report.