Acceptable use & anti-spam

Updated 26 October 2026 · Pilot policy version 1

The current Moonemail pilot is for expected transactional email: for example an account-verification code requested during signup, a password reset requested by the account holder, or a receipt for a completed purchase. Newsletters, promotions, bulk outreach and marketing campaigns are not permitted in this pilot.

Sending requirements

• Use only sender domains you control and have verified. Identify the business responsible for the message accurately and provide valid contact details.
• Send only to recipients who expect the particular message. Keep records of the user action, transaction or permission that justifies sending.
• Do not use bought, rented, scraped or harvested recipient lists, or send messages asking strangers for marketing consent.
• Do not send phishing, impersonation, scams, malware, harassment or unlawful content; evade suspensions, suppressions or quotas; or expose another person’s credentials.
• Protect API keys, limit agent permissions and review automation. You remain responsible for messages submitted by your integrations and agents.

Transactional is about the content

A subject line or API label does not determine whether an email is commercial. Adding an offer or promotion to a receipt or service notice can change its legal treatment. Do not include promotional material in pilot messages.

For commercial email, Australian spam rules generally require consent, accurate sender identification and a usable unsubscribe facility. An unsubscribe must work for at least 30 days, require no login or extra personal information, and be honoured within five working days. See the ACMA’s guidance. These requirements do not make marketing use available in the current pilot.

Suppression and recipient requests

Our event pipeline adds hard bounces and complaints to a team suppression list. New send requests are checked against that list. Customers must also act on direct recipient requests and maintain their own consent and suppression records. Do not remove a suppression simply to retry unwanted mail. Suppression is not a substitute for consent, nor does it recall emails already accepted for delivery.

Report a problem

Send abuse reports to al@halyard.studio. Include the sender, approximate time and message ID or relevant headers if available. Redact unrelated personal information and never include passwords or API keys. We review reports, investigate the relevant account and can restrict sending to contain abuse.

We may pause affected sending where reasonably necessary to prevent harm, comply with law or investigate a credible violation. We will explain the reason and provide a route to resolve or challenge it where safe and lawful. See pilot terms.