Acceptable Use Policy

1. Prohibited Content

You may not host, store, or distribute:

• Malware, viruses, trojans, rootkits, or exploit kits
• Phishing pages or credential harvesting sites
• Child sexual abuse material (CSAM) — reported to authorities immediately
• Pirated software, media, or copyrighted material you do not own
• Content that incites violence or terrorism
• Personal data collected without consent

2. Prohibited Network Activities

You may not use DigitalAura infrastructure to:

• DDoS attacks — launching, amplifying, or participating in denial-of-service attacks against any target
• Port scanning — scanning or probing other networks, servers, or DigitalAura infrastructure for vulnerabilities
• Spam — sending unsolicited bulk email, operating open mail relays, or running email campaigns that violate CAN-SPAM or equivalent laws
• Brute-force attacks — automated password guessing against any service, including other DigitalAura customers
• Traffic interception — ARP spoofing, DNS hijacking, man-in-the-middle attacks, or packet sniffing
• Tor exit nodes — operating Tor exit nodes or open proxies without prior written approval
• IP spoofing — sending network traffic with forged source addresses

3. Infrastructure Abuse

• Cryptocurrency mining — mining any cryptocurrency is prohibited unless you have explicit written permission from DigitalAura. This applies to all mining software regardless of the algorithm or currency.
• Resource abuse — running workloads designed to consume maximum CPU, RAM, bandwidth, or disk I/O beyond what your plan provides, or in a way that degrades other customers.
• Security bypass — attempting to access Proxmox management interfaces, storage networks (Ceph), internal APIs, or other customers' Nods. Our firewall rules block this by default — attempting to circumvent them is a violation.
• Billing fraud — creating multiple accounts to exploit free trials, using stolen payment methods, or disputing legitimate charges.

4. Automated Enforcement

DigitalAura uses automated systems to protect our infrastructure and all customers. The following actions trigger automatic Nod suspension:

When a Nod is auto-suspended, you will receive an email explaining the reason. Your data is preserved — the Nod is stopped, not deleted. You can appeal via a support ticket.

5. Consequences

6. Your Responsibility

You are responsible for securing your Nods. If your Nod is compromised and used to launch attacks, you are held responsible — even if the attack was not intentional. We strongly recommend:

• Always use SSH keys (password authentication is disabled by default)
• Keep your operating system and packages updated
• Do not disable the UFW firewall or fail2ban that we configure
• Monitor your Nod for unauthorized access
• Use strong, unique passwords for all services running on your Nod

7. Reporting Abuse

To report abuse originating from a DigitalAura server, email abuse@digitalaura.app with:

• The IP address involved
• Timestamps (with timezone) of the abuse
• Logs, packet captures, or other evidence
• Your contact information

We respond to all abuse reports within 24 hours. Our upstream infrastructure providers require this response time, and we take it seriously.

8. Email / SMTP Policy

Outbound SMTP (port 25) is blocked on all DigitalAura Nods by default. This prevents compromised Nods from being used for spam. If you need to send email from your Nod:

• Recommended: Use the DigitalAura transactional email API (included in your plan) or a third-party service like Postmark, SendGrid, or Brevo. These use port 587 (submission), which is not blocked.
• Port 25 unblock: Open a support ticket explaining your use case. We review manually and may approve for legitimate mail servers with proper SPF/DKIM/DMARC configuration.

9. Changes to This Policy

We may update this policy from time to time. Material changes will be announced via email to all registered users at least 14 days before they take effect. Continued use of the services after the effective date constitutes acceptance.