SECURITY
No Abuse
Malware, phishing, DDoS, brute-force attacks, credential theft, and unauthorized scanning are strictly prohibited.
AUP
Acceptable Use Policy
This policy defines acceptable and prohibited use of Zmirf services, including hosting, reseller accounts, domain operations, and managed infrastructure.
Last updated: March 18, 2026
LEGAL
Lawful Content
Content or operations that violate criminal law, IP rights, privacy law, or sanctions regimes are not allowed.
OPERATIONS
Fair Resource Use
Service use must not degrade shared infrastructure or impact other customers through excessive or abusive consumption.
1. Prohibited Activities
- Spam campaigns, mail abuse, spoofing, and deceptive traffic generation.
- Hosting illegal content or tools intended for unauthorized intrusion.
- Operating services that bypass legal takedown obligations.
- Reselling services to users engaged in known fraudulent activity.
2. Enforcement Measures
- Immediate temporary restrictions may be applied for active threats.
- Accounts may be suspended or terminated for repeated or severe violations.
- Evidence may be preserved and disclosed where legally required.
- Customers must cooperate during incident response and abuse investigations.
Operational guidance for policy-compliant service use
Acceptable use rules protect service stability, legal compliance, and customer trust. Organizations should align internal processes with these requirements before onboarding users, launching campaigns, or integrating third-party tools that generate traffic or process sensitive data.
Most policy violations come from unclear ownership or unmanaged automation. Defining responsible roles for security, content moderation, and incident response lowers risk and helps teams react quickly if abnormal activity is detected across accounts or hosted workloads.
- Document who approves campaigns and high-volume traffic actions.
- Monitor suspicious behavior before abuse escalates.
- Maintain clear reporting paths for internal policy incidents.
- Review provider terms when adding third-party integrations.
FAQ
Acceptable use FAQ
What happens after an acceptable-use violation?
Depending on severity, actions can include warning, temporary restriction, suspension, or termination.
How can teams reduce violation risk?
Set clear ownership for content, campaigns, and security monitoring before launch.
Practical controls include approval flows for high-volume campaigns, abuse reporting procedures, and routine reviews of integrations that can impact traffic quality, security posture, or legal compliance obligations.
Can integrations trigger policy issues even if core content is lawful?
Yes. Third-party scripts, automations, or traffic tools can still create abuse or compliance risk.
Review integrations for behavior, data handling, and traffic patterns before production deployment, and keep monitoring active after launch to catch unexpected policy-impacting behavior early.