Acceptable Use Policy

What you may and may not send through HAMANI MAIL.

3. Acceptable use

You are responsible for what you send. In particular:

• Australian anti-spam law applies to you. Commercial electronic messages sent from your domain are governed by the Spam Act 2003 (Cth) — consent, accurate sender identification, and a working unsubscribe. The obligations, and what our system enforces technically on your behalf, are set out in docs/AU-LEGAL.md, which forms part of these terms. In short: you must send only to people who have consented, you must keep records of that consent, and you must honour every unsubscribe. We also enforce unsubscribe technically — a marketing send is refused outright if our one-click unsubscribe is not configured, so we never send non-compliant mail on your behalf.
• Do not send spam, phishing, malware, deceptive content, or anything unlawful.
• Do not use the service to harass, defraud or impersonate anyone.
• Do not attempt to circumvent our rate limits, warm-up limits, suppression list or reputation controls.
• Do not use the service to send mail on behalf of a third party whose sending you cannot vouch for.

Personal mailboxes on a HAMANI-owned domain

HAMANI may offer a personal mailbox on a domain HAMANI owns, rather than on a domain of your own. Where it does, these additional terms apply to that mailbox:

• The same anti-spam rules apply to you. A personal mailbox is not a loophole. Bulk or commercial messages sent from it are governed by the Spam Act 2003 (Cth) exactly as they are from a business mailbox, and docs/AU-LEGAL.md applies to you unchanged.
• Do not impersonate anyone. Do not choose or use an address, display name or signature that represents you as another person, as a business you do not represent, as a government agency, or as HAMANI itself.
• Reserved and restricted names. Addresses that suggest an official, administrative or security function — for example admin, postmaster, abuse, security, support, billing, noreply — and names that impersonate a brand, an institution or a public body, are reserved to HAMANI. We may refuse them, and we may reclaim one that was issued in error or obtained by misrepresentation, on notice.
• The address is a licence, not a possession. You do not own a HAMANI-owned domain and cannot transfer the address away, because the domain is not yours. If that matters to you, use a domain you own — which is the main product.
• One person, honestly. Signup requires a verified recovery email address before the mailbox is activated. Do not create accounts in bulk, automate signup, or create an account in someone else's name.

What happens if a personal account is abused. We may suspend that account's sending — where these terms are breached, or where its bounce or complaint behaviour threatens the shared sending reputation. When we do:

• Your mailbox and your data stay reachable. You can still sign in, read your mail, and get your data out. Suspending sending is not lockout, and the same rule that applies to an unpaid business invoice (§4) applies here.
• Suspension of sending is not deletion. Nothing is destroyed by a suspension.

A separation we have actually built, and its limit. Personal sending and business sending are counted against separate reputation aggregates with separate brakes, so abuse on the personal side stops the personal side and cannot stop a paying business customer from sending. That is real, and it is proven both ways by tests. Its limit is equally real and we are not going to bury it: Amazon SES measures its own account-wide reputation, and that is not separated by us. Bad enough behaviour anywhere on the platform can still cause AWS to throttle or suspend the underlying account, which is outside our control.

Why we enforce this hard

Every HAMANI customer shares sending reputation. One bad sender damages delivery for every honest one. So:

• We may throttle or suspend sending — immediately, with or without notice — where sending breaches these terms, or where bounce or complaint rates threaten the shared sending reputation. This is a deliberate design commitment.
• Suspension of sending is not lockout from your mailbox. See §4.

Limits that exist, so you are not surprised

These are real, currently-configured limits, not marketing numbers:

• A free sending tier includes 3,500 emails a month and up to 150 a day. Over either ceiling, a send is refused until the next period. Paid sending tiers raise the monthly volume — see our pricing page.
• New-domain warm-up. A newly verified domain is capped at 50 sends on its first day, growing over 30 days to 50,000 per day, after which it graduates. Over the ceiling, a send is refused with a clear warm-up error. This protects your domain's reputation and everyone else's. Plan launches around it.
• Per-key request rate limit, and a per-source-IP limit applied before authentication.
• Message size is capped (roughly a few megabytes of real payload once attachments are encoded), and a batch send has a maximum number of recipients per call.
• Amazon SES account limits apply underneath us — a sending rate and a daily quota. We surface throttling and never report a message as sent when the provider rejected it.