Security & Deliverability Protection

Sendzovo is designed to help protect your account, sending infrastructure, email credentials and sender reputation while keeping legitimate email flowing.

Security by design

Protection across your entire sending stack

Email infrastructure needs more than account authentication. Sendzovo combines application security, domain authentication, delivery controls and abuse prevention to help keep your sending environment reliable.

Account Protection

Protect your Sendzovo account with secure authentication and controlled access to your email infrastructure.

Credential Security

API credentials and SMTP credentials should be treated as sensitive access keys and used only where required.

Deliverability Protection

Suppressions, authentication and sending controls help reduce unwanted mail and protect sender reputation.

01 · Domain authentication

Authenticate your sending domains

Proper domain authentication helps receiving mail providers establish that your messages are authorized to use your domain.

SPF

SPF helps identify the servers authorized to send email on behalf of your domain.

DKIM

DKIM adds a cryptographic signature to outgoing messages so receiving systems can verify message authenticity.

DMARC

DMARC provides a policy framework that helps domains control how receiving systems handle authentication failures.

DNS Verification

Sendzovo can use DNS-based verification to confirm ownership and authorization of sending domains.

02 · Access control

Keep your sending credentials under control

API and SMTP credentials provide access to your sending infrastructure. They should be generated, stored and rotated carefully.

API Keys

Use dedicated API credentials for applications and integrations rather than exposing account passwords inside application code.

  • Use separate credentials where appropriate.
  • Keep credentials out of source control.
  • Rotate credentials when exposure is suspected.

SMTP Credentials

SMTP credentials should be stored securely and restricted to the systems that need to send email.

  • Do not expose SMTP passwords in client-side code.
  • Use environment variables or a secrets manager.
  • Rotate credentials when necessary.
03 · Deliverability protection

Protect sender reputation

Sending unwanted email can damage domain and infrastructure reputation. Sendzovo uses deliverability-focused controls to help customers maintain healthier sending practices.

Suppressions

Suppression controls help prevent messages from being repeatedly sent to addresses that should no longer receive mail.

Bounces

Bounce handling helps identify addresses that cannot successfully receive email.

Complaint Signals

Monitoring delivery and complaint signals can help identify sending patterns that may negatively affect reputation.

04 · Abuse prevention

Built to reduce abusive sending

Email platforms must protect both customers and the wider delivery ecosystem. Sendzovo uses controls designed to detect and limit potentially abusive activity.

Rate Controls

Sending limits can help prevent unexpected traffic spikes and reduce the impact of compromised credentials.

Abuse Monitoring

Sending activity can be monitored for unusual patterns and potentially abusive behavior.

Account Controls

Accounts and sending capabilities may be restricted when activity presents a significant abuse or deliverability risk.

05 · Infrastructure security

Security at the infrastructure layer

Sendzovo is built with security considerations across the application and infrastructure stack.

Encrypted Connections

HTTPS and encrypted transport should be used when communicating with Sendzovo services and APIs.

Secure Application Practices

Application components are developed with common security principles including controlled access, validation and secure credential handling.

Access Controls

Administrative and service access should be restricted according to operational requirements.

Monitoring

Operational monitoring helps identify service issues, abnormal activity and potential security events.

06 · Shared responsibility

Security is a shared responsibility

Sendzovo provides security and deliverability controls, but customers are also responsible for protecting their accounts and using the platform appropriately.

Protect Your Credentials

Never publish API keys, SMTP passwords or other sensitive credentials in frontend applications, public repositories or client-side code.


Secure Your Account

Use strong, unique authentication credentials and limit access to trusted team members and systems.


Send Responsible Email

Only send legitimate, permission-based email and respect recipient preferences and unsubscribe requests.


Monitor Your Sending

Review delivery activity, bounces and other signals regularly so unusual behavior can be identified quickly.

Security contact

Found a security issue?

If you believe you have discovered a security vulnerability affecting Sendzovo, please report it responsibly so our team can investigate and address the issue.

Contact Sendzovo