OUR COMMUNICATION STANDARDS
Anti-Spam Policy
People should feel confident about the messages they receive. Our policy explains how to send responsibly, protect your customers and help keep our network trusted.
Permission comes first
Send marketing only to people who knowingly agreed to hear from you.
Every choice matters
Identify yourself clearly and make leaving a mailing list straightforward.
Protect the whole network
Keep accounts secure, respond to concerns and stop abusive sending promptly.
Our commitment and purpose
Nabtech Digitalnet Limited, referred to here as Nabtech, we, us or our, does not allow spam to be sent, hosted or supported through our services. Unwanted messages waste people's time, expose them to fraud and can make genuine business email harder to deliver. Protecting that trust is part of operating a responsible hosting network.
This policy sets the conditions for using our services to communicate with others. It applies alongside our Terms of Service, including their acceptable use requirements. A breach may lead to restrictions, suspension or termination. Our aim is to stop harm, establish what happened and determine whether the service can continue safely.
Customers must also follow the laws and receiving-provider rules that apply to their activities and recipients. Meeting this policy does not, by itself, establish compliance with every requirement in every country.
Who and what this policy covers
These rules apply to customers, account users, resellers and anyone authorised to operate a service on their behalf. They cover mailboxes, websites, applications, scripts, hosting accounts, virtual servers, dedicated servers and other Nabtech resources used to send or support messages.
Using another provider to send a campaign does not permit you to use a Nabtech-hosted website as the destination for spam, collect addresses abusively or conceal the campaign's origin. Equally, hiring an agency, affiliate or contractor does not remove your responsibility for the activity you authorise.
Where Nabtech only registers a domain and does not host the relevant website or mail system, our technical ability to investigate or restrict that external service may be limited. Reports should identify the activity accurately so they can be assessed through the appropriate service and process.
What we consider spam
Spam includes unsolicited promotional messages, repeated unwanted contact and messaging designed to deceive or overwhelm people. A message can be abusive even when sent to a small number of recipients. A large mailing is not automatically spam when it has proper permission and follows the rules.
- Promotions sent without the recipient's clear agreement to hear from that sender.
- Further marketing after a person has withdrawn permission.
- Phishing, impersonation, fraudulent offers, malicious attachments or deceptive links.
- Mail bombing, subscription bombing, abusive automated replies or attempts to flood an inbox.
- Unwelcome advertising through contact forms, forums, comments, chat or other public spaces.
- Tools, services or hosted pages intended to harvest addresses, distribute spam or evade anti-abuse controls.
A published email address, a social media follow or a previous enquiry is not, on its own, permission to add someone to ongoing marketing.
Permission and subscription records
Marketing subscribers must knowingly agree to receive the type of messages you intend to send. Explain who is sending them, their purpose and the expected frequency before the person subscribes. Avoid preselected boxes, hidden wording or making unrelated promotional consent appear necessary to complete a normal purchase.
Our mailing-list requirement is double opt-in. After an individual requests a subscription, send a limited confirmation message with a unique confirmation link, an explanation of the list and access to your privacy information. Do not start marketing until the person confirms. Protect the form against repeated submissions to someone else's address.
Keep records sufficient to demonstrate consent, including the address, confirmation time, confirmation IP address and subscription source. Retain the wording presented at signup where possible. Protect these records and provide relevant evidence when we investigate. Importing contacts into new software must not erase their permission history or previous opt-out choices.
Building and acquiring mailing lists
Do not use purchased, rented, scraped, harvested or partner-shared contact lists with our services. Claims that a list is verified or available for marketing do not demonstrate that each person agreed to receive your messages. Do not send an unsolicited campaign asking people to opt in as a way of working around this rule.
A genuine business acquisition requires separate care. Before using an inherited list, establish that the original permission remains valid for the new operator and intended purpose. Explain the ownership change, offer a simple way to leave and obtain confirmation again where necessary. If you cannot establish a valid basis, do not use that list for marketing through our services.
Permission is specific. Agreement to receive one organisation's newsletter does not automatically cover unrelated brands, changed subjects or a substantially different mailing frequency.
Clear messages and easy unsubscribe
Use an honest sender name, accurate addressing information and a subject that reflects the message. Your identity and a working contact route must be clear. Commercial and mailing-list messages must include the sender's valid postal address. Do not imitate another business or disguise a new promotion as an existing conversation.
Every marketing or subscription email must have a visible, working way to unsubscribe. Leaving must not require payment, a login or unnecessary personal information. Process requests promptly, within our maximum of five business days, and sooner whenever a receiving provider or applicable law sets a shorter requirement. Keep suppression records so a later import does not add the person back.
Where receiving providers require one-click unsubscribe, configure the appropriate message headers as well as the visible link. An unsubscribe page alone may not satisfy that technical requirement. Test the process and make sure security filters do not prevent legitimate requests from reaching it.
Service messages and marketing
Order receipts, requested password resets, security notices and necessary account updates have a different purpose from newsletters and promotional offers. Send these messages only when they relate to an actual request, transaction, account or service relationship, and keep their content appropriate to that purpose.
Do not label a promotion as a service notice to avoid consent or unsubscribe requirements. A person's decision to stop marketing does not automatically prevent necessary communication about an existing service, but it must be respected for promotional mail. Keep the two purposes separate in your systems wherever practical.
Automated notifications need abuse controls too. Limit repeated triggers, verify input appropriately and prevent forms or account tools from being used to send unwanted messages to other people. Calling a message transactional does not make deceptive or excessive sending acceptable.
Keeping lists accurate and respectful
Maintain your lists while they are in use. Suppress addresses that produce permanent delivery failures, honour complaints and investigate unusual changes in delivery or engagement. A permanent failure should not remain in an automatic retry cycle.
Repeated temporary failures, stale records and unexpectedly high complaint levels are reasons to pause and check the campaign. Review whether people still reasonably expect the messages, whether your signup process is working and whether an import included the wrong contacts. Do not continue simply because the software allows another attempt.
Keep suppression information across systems you control so that unsubscribe requests, complaints and invalid-address records survive a migration. Limit access to subscriber information and avoid exposing recipients to one another through unnecessary public address lists. Your own privacy notice should explain how you handle this information.
Authentication, limits and delivery
Configure the authentication needed for your sending service and recipients, including SPF, DKIM and DMARC where applicable. Use accurate DNS and secure mail connections. If you manage a server, keep its mail software maintained and prevent it from operating as an unauthorised open relay.
Follow the sending limits for your plan, any restrictions communicated by us and the rules of receiving networks. There is no single volume allowance in this policy that applies to every service. Ask about suitability before planning a large campaign. Ordinary hosting or mailbox access should not be assumed to include unrestricted bulk delivery.
Do not rotate accounts, domains or IP addresses to bypass a restriction or continue a rejected campaign. Authentication helps establish identity; it does not replace consent or guarantee inbox placement. Receiving providers make their own delivery decisions, and we may restrict sending to protect network stability and reputation.
Account security and reseller responsibilities
Use strong credentials, enable available additional authentication and protect mailbox passwords, application keys and administrative access. Keep websites, plugins and scripts updated, remove unused access and restrict contact forms so they cannot act as unrestricted mail senders.
If you suspect an account or website is sending without your permission, stop the affected activity and notify us promptly. Preserve useful logs, change exposed credentials, remove malicious code and repair the entry point. A compromise may still require temporary restrictions while the source is contained.
Resellers must make these requirements clear to their customers and respond to abuse affecting the accounts they manage. You remain responsible for the users, contractors and affiliates you authorise. Investigating the person who caused a problem does not justify leaving harmful sending active.
Reporting suspected spam
Report suspected misuse through our abuse reporting page or by emailing [email protected]. Customers can also open a support ticket about their own account. Include enough information for us to identify the activity without sending passwords, payment details or unrelated personal information.
- The original message with its complete headers, preferably attached as an email file.
- The date and time received, including the time zone if known.
- Relevant domains, sending IP addresses, message identifiers and links.
- A brief explanation of why the message was unexpected, including any earlier unsubscribe request.
A screenshot can help explain the problem, but usually cannot show the full route of an email. Do not open suspicious attachments or follow unsafe links to collect evidence. We may need additional information, and privacy or security considerations can limit the details we share about another customer's account.
Investigation and enforcement
We may review relevant complaints, technical logs, message samples, account activity and permission records to assess suspected abuse. A report is a reason to investigate, while immediate protective action may be necessary before every fact is known.
Depending on the risk, we may pause a campaign, restrict outgoing mail, disable an affected application or suspend a service. Serious, deliberate or repeated abuse may result in account termination. We may act without advance notice where necessary to contain ongoing harm or meet an applicable requirement. Notification and an opportunity to resolve the issue will depend on the circumstances.
Respond to our spam-related enquiries within 72 hours. Where an active incident requires faster containment, follow the deadline stated in our notice. Failure to cooperate, misleading evidence or attempts to evade restrictions may lead to further action. We handle any disclosure of relevant information in accordance with applicable law and our Privacy Policy.
Putting things right and requesting review
To request restoration, explain what caused the incident, what you have stopped and how you have addressed the cause. We may ask for permission records, corrected list practices, security remediation or evidence that an unsafe application has been repaired. A promise to avoid further complaints may not be enough.
Restoration depends on the service being safe to operate and is not guaranteed. We may require additional controls or a different service appropriate to the intended workload. External providers control their own blocklists and delivery restrictions, so restoring an account does not ensure immediate delivery everywhere.
If you believe we have linked an incident to the wrong account or misunderstood the evidence, reply through the relevant ticket and explain the discrepancy. Restrictions may remain during review. Refund eligibility and any charges for responding to abuse are governed by the applicable agreed Terms of Service and law.
Related terms and policy changes
Read this policy with our Terms of Service, Privacy Policy and the conditions for your particular service. The Terms address contractual matters such as charges, suspension, termination and refunds. The Privacy Policy explains how we handle personal information.
We may revise these requirements as our services, abuse risks and applicable obligations change. Changes take effect as stated in the update and subject to any notice required by our Terms of Service or applicable law. Nothing in this policy overrides rights that cannot lawfully be excluded.
For clarification about how a requirement applies to your account, use our contact page or the existing support conversation about the matter.
This policy forms part of the conditions for using our services. Read it alongside the terms that apply to your account and service.