Trust & Safety

Acceptable Use Policy

Sendzovo is built for legitimate application and business email. These guidelines help protect recipients, customers and the reliability of the email infrastructure we provide.

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

Use Sendzovo responsibly

You may use Sendzovo only for lawful purposes and in a manner that respects recipient rights, network rules and reasonable email deliverability standards.

Prohibited practices

Sendzovo may not be used for activities that abuse recipients, infrastructure or sending systems. Prohibited uses include:

Spam and unsolicited bulk email

Unlawful unsolicited bulk email, spam or other communications sent without an appropriate lawful basis or permission.

Improper recipient lists

Purchased, rented, scraped, harvested or otherwise unlawfully obtained recipient lists.

Fraud and phishing

Phishing, credential theft, impersonation, fraud or deceptive sender identities.

Malicious content

Malware, malicious attachments, harmful links or other content intended to compromise users or systems.

Suppression bypassing

Repeatedly sending to recipients who have opted out or to addresses that are known to be suppressed.

Control evasion

Attempts to bypass bounce, complaint, authentication, rate-limit, review or suspension controls.

Transactional email

Transactional email should arise from a legitimate relationship, user action, account event, purchase, security event, service notification or other lawful application workflow.

Marketing communications

If a feature permits marketing email, customers must comply with all applicable consent, identification and unsubscribe requirements. Sendzovo may impose stricter limits or require proof of consent.

Email verification

Verification may be used only where the customer has a lawful purpose and legal basis to process the addresses. Verification may not be used to facilitate spam, list harvesting, harassment or unlawful profiling.

Authentication and sender identity

Customers must use domains and sender identities they are authorized to control and maintain required SPF, DKIM, DMARC or other authentication settings where applicable.

Bounces and complaints

Customers must maintain reasonable list hygiene and stop sending where required by hard-bounce, complaint, unsubscribe or suppression signals. Excessive bounce or complaint rates may trigger limits or suspension.

Protecting the service

We may rate-limit, investigate, suspend or terminate accounts, domains or API keys where necessary to protect recipients, infrastructure or service reputation.