Rechtliches

Unternehmen — Acceptable use
CloudNexs, Inc.

CloudNexs legal documents describe how the company operates its products and services.

Acceptable Use Policy

Effective date: August 18, 2026

This Acceptable Use Policy (“AUP”) applies to CloudNexs websites, applications, products, services, APIs, infrastructure, and other digital services that expressly link to this policy.

The purpose of this AUP is to protect CloudNexs users, third parties, and infrastructure while allowing legitimate use of CloudNexs software and tools.

1. Lawful Use

You may use CloudNexs only for lawful purposes.

You must not use a Service to:

violate applicable law;
facilitate illegal activity;
violate court orders or legal restrictions;
infringe intellectual property rights;
violate privacy or data-protection rights;
deceive, defraud, threaten, harass, or unlawfully harm another person.

2. Authorized Content and Files

You may submit, upload, process, test, analyze, or otherwise use only content that you are legally authorized to use.

You must not submit:

stolen content;
leaked confidential materials;
copyrighted content without necessary rights;
applications or software you are not authorized to test;
private data obtained unlawfully;
content that violates third-party contractual or legal rights.

CloudNexs may request evidence of authorization when necessary to investigate abuse or comply with law.

3. Malware and Harmful Code

You must not use CloudNexs to create, distribute, host, process, test for malicious deployment, or facilitate:

malware;
ransomware;
spyware;
credential-stealing software;
botnets;
destructive payloads;
unauthorized surveillance tools;
malicious exploits;
phishing infrastructure;
data theft;
cryptojacking;
tools primarily intended to compromise systems without authorization.

Legitimate security research or authorized testing may be permitted only when the relevant CloudNexs product supports that use and the user has lawful authorization.

4. Unauthorized Access

You must not:

access another user's account;
access another user's files, reports, projects, or data;
bypass authentication;
bypass authorization;
exploit a vulnerability to obtain unauthorized access;
attempt privilege escalation;
interfere with account isolation;
obtain secrets, credentials, tokens, or keys without authorization.

If you discover a potential security issue, report it responsibly instead of exploiting it.

5. Platform Abuse

You must not intentionally interfere with the normal operation of CloudNexs.

Prohibited activity includes:

denial-of-service activity;
excessive automated traffic intended to disrupt service;
intentionally overloading systems;
bypassing quotas;
evading rate limits;
creating accounts to evade restrictions;
circumventing technical controls;
manipulating billing or credit systems;
interfering with workers, queues, storage, databases, reports, or infrastructure;
probing internal systems beyond authorized product functionality.

6. Fraud, Deception, and Misrepresentation

You must not use CloudNexs to:

commit fraud;
impersonate CloudNexs;
impersonate another user or organization;
falsify ownership or authorization;
misrepresent a CloudNexs output;
alter a report to falsely claim a result produced by CloudNexs;
claim a CloudNexs report is a government certification, legal certification, security guarantee, store guarantee, or regulatory approval when it is not;
deceive clients or third parties about the meaning of product results.

7. Sensitive Data

Do not submit unnecessary sensitive information.

If a supported workflow requires sensitive information, you are responsible for ensuring that:

you have the legal right to process it;
the relevant CloudNexs product permits it;
you comply with applicable legal and contractual obligations;
you apply appropriate security practices before submission.

Sensitive information may include:

passwords;
authentication secrets;
tokens;
private keys;
financial account information;
medical information;
government identifiers;
precise confidential business data;
other legally protected personal data.

CloudNexs may prohibit particular categories of sensitive information in product-specific rules.

8. Privacy and Personal Data

You must not use CloudNexs to unlawfully collect, disclose, monitor, sell, profile, or exploit personal data.

You are responsible for obtaining any notices, permissions, consents, or lawful basis required for personal data you submit to or process through a CloudNexs Service.

9. Intellectual Property

You must not use CloudNexs to infringe:

copyright;
trademark;
patent;
trade-secret;
licensing;
other proprietary rights.

CloudNexs may restrict or remove content when required by law or when credible evidence of infringement is provided.

10. Automated Use and APIs

Automated access must follow:

documented API behavior;
authentication requirements;
rate limits;
quotas;
product-specific rules.

You must not:

use undocumented methods to bypass intended controls;
generate abusive request volumes;
rotate credentials or accounts to evade limits;
use automation to interfere with other users;
scrape protected or private information.

11. Resource and Usage Limits

CloudNexs may enforce limits involving:

request rates;
file sizes;
processing time;
stored data;
retained artifacts;
job concurrency;
API usage;
account usage;
credits;
product-specific capacity.

Limits may be used to preserve reliability, security, fair access, and cost control.

Attempts to evade these limits may result in restriction or suspension.

12. Security Review

To protect the Services, CloudNexs may use automated or manual controls to:

inspect technical metadata;
scan submitted files where appropriate;
identify malware or suspicious behavior;
detect abuse;
block malicious requests;
preserve evidence of security events;
restrict unsafe activity.

Security review does not mean CloudNexs guarantees that all malicious or prohibited activity will be detected.

13. Product Outputs and Reports

CloudNexs outputs must not be used to make false or misleading claims.

Unless CloudNexs expressly states otherwise, a report, score, check, or automated result does not constitute:

government approval;
regulatory certification;
guaranteed security;
guaranteed app-store approval;
guaranteed compliance;
guaranteed commercial performance.

Users remain responsible for how they interpret and use outputs.

14. Attempts to Evade Enforcement

You must not attempt to avoid enforcement by:

creating replacement accounts;
changing identifiers;
using alternate payment instruments;
hiding malicious activity;
redistributing prohibited workloads across accounts;
using another person or organization to continue prohibited activity.

15. Enforcement

CloudNexs may take proportionate action when it reasonably believes this AUP has been violated.

Actions may include:

warning the user;
blocking a request;
blocking a file;
stopping a job;
restricting a feature;
enforcing additional verification;
reducing or suspending access;
suspending or terminating an account;
removing stored content;
preserving relevant logs;
refusing service;
denying a refund where permitted by the Refund Policy and law;
reporting serious unlawful activity where required by law.

CloudNexs may take immediate action without advance notice where necessary to protect users, infrastructure, third parties, or legal compliance.

16. Reporting Abuse

Suspected abuse, security concerns, or unauthorized activity may be reported to:

support@cloudnexs.com

Include enough information for CloudNexs to identify and investigate the issue.

17. Changes to This Policy

CloudNexs may update this Acceptable Use Policy as its products, threat environment, infrastructure, and legal obligations evolve.

Material changes will be reflected by updating the effective date and by additional notice where required by applicable law.

18. Contact

CloudNexs, Inc.