Anti-Spam Policy

Why this is enforced hardest

Sender reputation attaches to an IP range, not to an account. A single customer working an acquired list can push every other site sharing that range into junk folders for weeks, and the affected parties can do nothing to accelerate recovery. That asymmetry is why the response here is faster than anywhere else in these documents.

1. The consent standard

The Privacy and Electronic Communications Regulations, read with UK data protection law, require consent before marketing mail reaches an individual. Consent is an affirmative act. A pre-ticked box is not one. Neither is an address surrendered to enter a competition, nor one collected from a published directory.

The single exception covers existing purchasers, contacted about comparable products, who were given a means of refusal when the address was taken and in every message since. It is materially narrower than most senders believe.

For any address held, you must be able to evidence when consent was given and by what mechanism. Absent that evidence, the list is unusable here.

2. Acquired lists

Purchased and rented lists are refused without exception. So are addresses harvested from websites, directories or social platforms, and so is a list inherited with an acquired business unless the original consent covers your intended use.

Re-permissioning a doubtful list by mailing it to ask is not remediation. That message is the breach.

3. Message requirements

• accurate sender identity — no forged headers, no misleading from-address;
• a subject line describing the actual contents;
• a functioning unsubscribe, honoured on receipt and within three working days at the outside;
• a postal address, and the registered company behind any trading name.

Unsubscribes are permanent. Reinstating an address because a different form was completed or a new list was created restarts the breach.

4. Volume ceilings

Shared and reseller plans apply hourly sending limits sized for transactional traffic — order confirmations, password resets, form notifications — rather than campaigns.

Bulk sending belongs with a provider whose product is deliverability and which reports on it. Routing a list through shared hosting damages your own delivery rates before it becomes an issue for anyone else.

5. Relaying

No open relays, and no sending on behalf of third parties whose consent practices you cannot personally evidence. Resellers carry their customers' compliance as far as we are concerned, because the account is the unit we can act against.

6. Response to an outbound run

Outbound traffic is monitored by pattern rather than content. When a run is detected, sending is stopped first and discussed second. An hour of deliberation is the difference between one customer receiving a warning and an entire range requiring delisting.

• Compromise. The usual cause — a hijacked form or leaked credential rather than a decision. Sending is suspended, the origin is shared with you, and it is restored once closed.
• Deliberate. Account terminated, with no refund for the unexpired term.

Where an account causes a range to be blocklisted, delisting effort and the cost of migrating other customers to clean addresses may be charged to it.

7. Reporting spam

File it through report abuse with full headers. Headers are what make a report traceable to an account; a forwarded body alone usually is not.

8. Our own sending

Service, billing and security messages are part of operating the account and arrive regardless. Promotional mail is opt-in, and unsubscribing from it never affects operational mail. Detail sits in the privacy policy.

9. Contracting entity

HostingAlly operates as a trading name of Fairdeal Renovations Limited, a company registered in England and Wales under Company No. 15026869. Registered office: The Workspace Basildon, 7 High Pavement, Basildon, England, SS14 1EA. Questions to info@hostingally.com.