Acceptable Use Policy

1. Permitted use

Use your allocated hostnames for lawful services you own, operate or are authorised to administer: personal servers, legitimate websites, development environments, business applications and approved remote access. Follow the agreed scope of internal hosting/proxy/support services.

Keep software and credentials secure, respect applicable law and third-party rights, and respond to proportionate requests about a service you operate.

2. Prohibited sexual content

Pornographic content and services primarily intended to distribute or facilitate pornography are prohibited by service policy, including material that may otherwise be lawful. Any sexual exploitation of children, non-consensual intimate imagery or unlawful sexual material is prohibited.

Lawful medical, educational, safeguarding or support content is not pornography merely because it discusses sexual health. Decisions should consider the actual purpose and context. Do not send copies of illegal imagery when making a report.

3. Piracy and unlawful services

Do not host, link through this service to, distribute or facilitate unauthorised copyrighted material, cracked software, stolen credentials, illicit streaming or other infringement. Do not use the service for unlawful sales, fraud or criminal activity.

Legitimate open-source downloads, authorised media distribution and lawful peer-to-peer software are not prohibited solely because they use a particular protocol. The prohibition concerns unauthorised or unlawful use.

4. Security, abuse and resource use

Malware, phishing, botnet control, credential theft, spam, denial-of-service activity, harassment, threats and attacks on systems without authorisation are prohibited. Do not scan or access private networks through the proxy, impersonate the operator, collect credentials, or evade account, IP or hostname restrictions.

Do not disclose tokens, create automated accounts to bypass quotas, misuse the update endpoint as a relay, or impose disproportionate load. Service limits and rate limits apply. Proxy traffic is allowed only for approved internal customers and fixed validated origins.

5. Reports and enforcement

Report concerns to technology@kai-young.co.uk with the hostname, a concise description and relevant times. Engineers review reports; the application does not automatically classify content or determine whether a person has committed an offence.

Proportionate enforcement may include a warning, temporary suspension, account/IP/domain restrictions, removal of service DNS records or termination. The Misuse and Enforcement Policy explains review, appeals and limitations.

Misuse and Enforcement Policy

1. Report and review

Send concerns to technology@kai-young.co.uk or open an abuse conversation from your workspace. Include the relevant hostname, incident description and time; provide links or identifiers rather than copies of illegal material. For copyright claims, describe your rights and the alleged infringement location.

An authorised engineer reviews the report, the applicable policy, the service relationship and available information. Additional proportionate details may be requested. A moderation action is a service decision, not a declaration of criminal guilt.

2. Available restrictions

An account ban prevents portal access and update-token use. A source IP or IP-range ban prevents protected requests from that connection; it also blocks origin-address updates and withdraws existing allocations pointing to a banned origin. Shared IPs and ranges may affect uninvolved customers, so engineers must review scope and collateral effects.

A domain/hostname ban covers the named domain and its descendants within this service, prevents new allocations and stops updates/forwarding for affected names. It does not alter third-party domains or remove content from the wider internet. Engineers cannot ban engineer accounts through the customer UI.

Reasons and changes are recorded for review. The UI rejects IP bans covering the engineer’s current connection and restricts overly broad ranges. Suspending or pausing a record is separate from a policy ban; the scope of each action should be explained.

3. DNS and proxy effects

Protected requests are blocked immediately after an active ban is recorded. Proxy routes are removed on the next successful routing sync. The maintenance task attempts to remove affected DNS records using the configured DNS provider and checks that each provider record still matches the allocated hostname before deletion.

DNS withdrawal is not instantaneous: the task must run, the provider must respond, and caches may retain old answers until their TTL expires. Customer-hosted content and existing network connections may remain outside our control. The application records provider failures and retries on the next maintenance run. Revoking a ban does not automatically restore deleted DNS; an authorised client must send a successful new update.

4. Notice and appeals

Where practical and lawful, explain the restriction and the policy basis to the affected customer. Urgent action may precede notice where necessary to protect systems, rights or safety. Avoid disclosing a reporter’s unnecessary personal information.

Customers can appeal by emailing technology@kai-young.co.uk, including the affected account or hostname and why the decision should change. Banned customers can still read public help/policies and use the email link. An engineer reviews the appeal and communicates the outcome where possible; no fixed response-time guarantee is offered.

5. Records and legal requirements

Preserve relevant records only as necessary for the decision, a dispute or a valid legal requirement; apply the privacy retention schedule and review active bans periodically. Do not store unnecessary criminal allegations or sensitive material.

We may cooperate with lawful requests from competent authorities and take action required by law. Whether to disclose information must be assessed case by case; a report or automated ban does not automatically send information to authorities.