Acceptable Use Policy

September 5, 2026

1. Purpose

This Acceptable Use Policy ("AUP") defines permitted and prohibited uses of the Orathos Service operated by EVYNUM. It protects customers, infrastructure, third parties, and the integrity of backup and disaster recovery operations.

This AUP supplements the Terms of Service. Capitalized terms not defined here have the meanings given in the Terms.

2. Permitted use

You may use Orathos only for lawful business or organizational purposes and only to back up, store, monitor, and restore systems and data you own or are expressly authorized to manage.

Backup agents must be installed only on systems where you have written permission or a lawful right to deploy monitoring and backup software. You must respect licensing, employment, and contractual restrictions applicable to those systems.

3. Prohibited content and activities

You may not use the Service to back up, store, transmit, distribute, or restore content or engage in activities that:

• Violate applicable law or regulation, including export control, sanctions, privacy, or data protection laws.
• Infringe intellectual property, confidentiality, or privacy rights of any person or entity.
• Contain malware, ransomware tooling, exploit code, or instructions for unlawful access.
• Facilitate harassment, fraud, phishing, spam, or deceptive practices.
• Relate to illegal goods, services, or exploitation of minors.

4. Prohibited technical conduct

You may not attempt to probe, scan, attack, or compromise the Service, other tenants, EVYNUM infrastructure, or third-party systems. Prohibited conduct includes, without limitation:

• Circumventing authentication, tenant isolation, rate limits, or security controls.
• Reverse engineering or extracting source code except as expressly permitted by law.
• Introducing excessive load, denial-of-service traffic, or abusive API usage.
• Using the Service to stage attacks against third parties or to exfiltrate data without authorization.
• Sharing credentials, API tokens, or agent enrollment secrets outside your organization except as required for authorized administration.

5. Agent, API, and workspace rules

API tokens and agent enrollment credentials must be treated as confidential secrets. Automated access must remain within documented limits and intended use cases.

You are responsible for reviewing backup scope, retention, encryption settings, and user permissions within your workspace. Role-based access should follow least privilege.

If your workspace enables approval workflows or change controls, you must not bypass them.

6. Enforcement and reporting

We may investigate suspected violations and take action including warning, throttling, suspension, termination, or legal remedies, with or without notice where permitted by law.

Report abuse, unauthorized agent activity, or security concerns to support@orathos.com with relevant details. Do not conduct unsolicited vulnerability testing of production systems except as expressly authorized in our Security Policy.