Trust & Safety

Anti-Spam Policy

Sendzovo prohibits spam and requires customers to use email responsibly, maintain lawful recipient relationships and respond promptly to opt-outs, bounces and complaints.

Effective: September 8, 2026 Last updated: September 8, 2026

What Sendzovo is for

Our delivery service is primarily intended for automated application email such as verification messages, password resets, receipts, security notifications, account alerts and other legitimate service communications.

No unlawful unsolicited email

Customers must not send unlawful unsolicited bulk email. Where consent is legally required, customers must obtain valid permission and be able to demonstrate how recipients were obtained.

Sender identification

Customers must not misrepresent the sender or disguise the origin of email. Sender domains and addresses must be authorized and appropriately authenticated where required.

Opt-outs and suppression

Where an unsubscribe right applies, customers must provide a clear mechanism and honor valid requests promptly. Sendzovo may maintain suppression data for complaints, hard bounces, opt-outs and other risk events.

Bounces and complaints

Persistently high hard-bounce, spam-complaint or invalid-recipient rates may result in throttling, account review or suspension.

Prohibited list sources

Do not use addresses collected through automated scraping, directory harvesting, credential theft, breaches, deceptive practices or third-party list purchases without a lawful and verifiable basis for the intended communication.

Email verification does not create consent

A technically valid or deliverable email address is not evidence that the owner agreed to receive email. Verification is a deliverability and risk-assessment tool, not a consent-generation service.

Enforcement

We may restrict or suspend sending while investigating suspicious activity. Serious or repeated violations may result in termination.

Report spam or abuse

Contact abuse@sendzovo.com and include full message headers or a message ID where available.

Before publishing: verify that the enforcement, suppression, bounce and complaint handling described above accurately reflects your production systems and operational procedures.