Email people expect to receive.

Orbance is designed for messages to people who have requested them or have another clearly documented, lawful relationship with the sender. Bought, rented, scraped and harvested lists are not accepted.

Consent evidence should identify the recipient, sender, source, wording, scope, time and later withdrawals. Double opt-in may be used where stronger evidence or list quality is needed.

Service messages and marketing messages serve different purposes. A password reset or requested account notice should not be used to hide a promotion.

If content advertises or promotes a product or service, Orbance applies marketing safeguards rather than relying only on a "transactional" label.

A sender must identify the authorising business and use a domain or address it is permitted to use. Domain verification is one control; it does not by itself create permission to contact a recipient or prove provider production approval.

Managed and customer domains may have different setup steps. Sending remains unavailable until the relevant identity, provider, application and runtime checks pass.

Marketing templates must retain a clear recipient-specific unsubscribe path. A recipient should not need to sign in, create an account, pay or provide unrelated information.

Orbance can record the withdrawal, suppress later marketing for the applicable business and keep the minimum evidence needed to honour that choice.

When provider sending is live, delivery, bounce, complaint, rejection and delay events can be used to reconcile message state and protect future sends. Known hard bounces and complaints should not be treated as ordinary retry targets.

Provider events do not replace the sender's consent records or Orbance's product-level suppression rules.

Each Orbance customer is accountable for its recipients, content and sender identity. Orbance may use tenant-scoped controls, evidence review, rate limits and suspension so one business's poor practice does not become normal platform behaviour.

New sending should begin with low, expected volume and increase only as consent quality, bounces, complaints and delivery behaviour remain healthy. Limits may be lower than a provider's maximum quota.

Orbance distinguishes configured infrastructure, verified identities, tested application controls and approved live sending. We do not describe those separate gates as complete when they are not.

Current availability is shown in the product. This page does not claim Amazon SES or another provider has granted production access.

Read the binding Anti-spam policy or report unexpected Orbance-delivered email to support@mail.orbance.com.au.