Email Deliverability & Anti-Abuse Policy

BEEVELOPE

EMAIL DELIVERABILITY & ANTI-ABUSE POLICY

Effective Date: 5 September 2026

1. Purpose

This Email Deliverability & Anti-Abuse Policy (”Policy”) establishes the standards governing responsible use of the BEEVELOPE Platform for sending email communications and protects:

(a) Recipients;

(b) Customers and Users;

(d) domain and IP reputation;

(e) email deliverability; and

(f) the integrity and security of the Platform.

2. Scope

This Policy applies to all email communications sent through BEEVELOPE, including:

* marketing campaigns;

* automated campaigns;

* bulk communications;

* API-based sending;

* CRM-integrated campaigns; and

* other email functionality provided through the Platform.

This Policy supplements the Terms of Use and Email Marketing Compliance & Acceptable Use Policy.

3. Responsible Sending

Customers shall use BEEVELOPE responsibly and shall:

(a) send communications only to appropriately obtained and lawfully usable recipients;

(b) maintain reasonably accurate and current contact lists;

(d) promptly remove or suppress invalid addresses;

(e) monitor delivery failures and complaints;

(f) protect their Accounts and sending credentials; and

(g) comply with applicable email marketing and anti-spam laws.

4. Prohibited Activities

BEEVELOPE shall not be used for:

(a) unlawful spam or unsolicited bulk email;

(b) phishing or credential harvesting;

(d) fraudulent or deceptive campaigns;

(e) impersonation or spoofing;

(f) unlawful harvesting or scraping of email addresses;

(g) repeated emailing of recipients after valid opt-out;

(h) circumventing suppression mechanisms;

(i) campaigns designed to evade spam filters or abuse detection;

(j) activities intended to damage the reputation of BEEVELOPE or third-party email infrastructure; or

(k) any activity prohibited under the Terms of Use or Email Marketing Compliance & Acceptable Use Policy.

5. Marketing Lists

Customers are responsible for the quality and lawful source of their contact lists.

Customers should not use:

(a) unlawfully purchased lists;

(b) scraped or harvested lists;

(d) lists containing recipients who have opted out or should otherwise be suppressed.

The fact that an email address is publicly available does not, by itself, establish permission to send marketing communications.

6. Unsubscribe and Suppression

Customers must honour valid unsubscribe and opt-out requests.

BEEVELOPE may maintain or support suppression mechanisms designed to prevent further communications to recipients who have:

(a) unsubscribed;

(b) complained;

(d) otherwise been identified as requiring suppression.

Customers shall not knowingly circumvent such mechanisms.

7. Bounces and List Quality

Customers are expected to monitor delivery failures.

BEEVELOPE may take reasonable measures where an Account demonstrates:

(a) excessive hard bounces;

(b) persistent soft bounces;

(d) unusually high complaint rates; or

(e) other indicators of materially poor list quality.

Such measures may include sending restrictions, additional verification or suspension.

8. Spam Complaints

BEEVELOPE may monitor spam complaints and other recipient feedback to identify potentially abusive or non-compliant sending activity.

Where complaint levels indicate a material risk, the Company may:

(a) request information from the Customer;

(b) require corrective measures;

(d) suspend campaigns or Accounts; or

(e) take other proportionate measures.

9. Domain and Email Authentication

Where applicable and technically supported, Customers should use appropriate email authentication mechanisms, including:

(a) SPF;

(b) DKIM; and

Customers are responsible for maintaining accurate DNS and domain configurations where those configurations are under their control.

BEEVELOPE may require domain verification or authentication before permitting certain sending functionality.

10. Sending Volume and Reputation

Customers shall not engage in sending practices that materially threaten:

(a) BEEVELOPE’s IP or domain reputation;

(b) Customer-specific sending reputation;

(d) third-party mailbox-provider relationships; or

(e) the availability or integrity of the Platform.

BEEVELOPE may apply reasonable sending limits, rate limits or volume controls based on factors including:

* Account history;

* sending patterns;

* reputation;

* complaint rates;

* bounce rates;

* security risk; and

* infrastructure capacity.

11. Monitoring and Abuse Detection

BEEVELOPE may use automated and manual systems to identify potential abuse, including monitoring for:

(a) unusual sending patterns;

(b) sudden increases in volume;

(d) spam complaints;

(e) suspicious content or links;

(f) phishing indicators;

(g) compromised Accounts;

(h) abnormal authentication activity; and

(i) other security or deliverability risks.

Such monitoring shall be undertaken in accordance with the Privacy Policy and Applicable Laws.

12. Account Compromise

Customers must promptly notify BEEVELOPE if they suspect:

(a) unauthorised access to an Account;

(b) compromised credentials;

(d) unauthorised campaigns; or

(e) other activity that may result in abuse.

BEEVELOPE may temporarily restrict sending activity to contain suspected compromise.

13. Suspension and Enforcement

Where BEEVELOPE reasonably believes that an Account presents a material spam, abuse, security, legal or deliverability risk, it may take proportionate measures, including:

(a) warning the Customer;

(b) requiring corrective action;

(d) pausing a campaign;

(e) requiring verification;

(f) temporarily suspending sending;

(g) suspending the Account; or

(h) terminating the Services in accordance with the Terms of Use.

Where there is an immediate and serious risk, the Company may take protective action without prior notice to the extent reasonably necessary.

14. No Guarantee of Deliverability

BEEVELOPE does not guarantee that any email will:

(a) reach the Recipient’s inbox;

(b) avoid spam or junk folders;

(d) be delivered within a particular timeframe; or

(e) achieve any particular open, click or engagement rate.

Deliverability may depend upon factors outside BEEVELOPE’s reasonable control, including Recipient behaviour, mailbox-provider filtering, domain reputation, content, authentication and third-party infrastructure.

15. Customer Responsibility

The Customer remains responsible for:

(a) its recipient lists;

(b) obtaining appropriate permission or lawful basis;

(d) sender identification;

(e) unsubscribe compliance;

(f) list hygiene;

(g) domain configuration where applicable; and

(h) compliance with Applicable Laws.

Use of BEEVELOPE does not transfer these responsibilities to the Company.

16. Cooperation

Where reasonably necessary to investigate suspected abuse or material deliverability risks, BEEVELOPE may request information from the Customer concerning:

(a) the source of a recipient list;

(b) consent or permission;

(d) sending practices;

(e) domain ownership;

(f) suspected compromise; or

(g) other relevant circumstances.

Customers shall reasonably cooperate with such requests.

17. Third-Party Mailbox Providers

BEEVELOPE may implement reasonable measures to comply with applicable requirements or standards imposed by third-party email and mailbox providers.

Changes in mailbox-provider policies or filtering practices may affect deliverability and may require BEEVELOPE to modify its sending controls.

18. Relationship with Other Policies

This Policy shall be read together with:

1. Terms of Use;

2. Privacy Policy;

3. Email Marketing Compliance & Acceptable Use Policy;

4. Data Processing Agreement; and

5. other applicable policies of BEEVELOPE.

In the event of a conflict concerning email marketing compliance, the Email Marketing Compliance & Acceptable Use Policy shall govern the relevant compliance requirement, while this Policy shall govern matters relating specifically to deliverability, sending reputation and anti-abuse controls.

19. Changes to the Policy

BEEVELOPE may update this Policy to reflect:

(a) changes in email-industry standards;

(b) mailbox-provider requirements;

(d) new abuse patterns;

(e) security developments;

(f) regulatory requirements; or

(g) changes to the Platform.

The updated version shall indicate the applicable “Last Updated” date.

20. Effective Date

This Policy shall become effective on the Effective Date stated above and shall remain in effect until amended or replaced.