Privacy first
Arvexa does not routinely inspect customer content or require customers to identify themselves through a standard KYC process. Minimal technical metadata may still be generated or retained when reasonably necessary to operate and protect the service.
Clearly prohibited activity
Services may not be used for phishing, credential theft, malware distribution, botnet or command-and-control activity, denial-of-service attacks, unauthorized intrusion, fraudulent activity, child sexual abuse material, or other activity that is clearly unlawful under applicable law.
Spam and network abuse
Bulk unsolicited messaging, spoofing, reflection/amplification abuse, brute-force attacks and malicious scanning that materially harms third parties or upstream networks are not permitted.
Copyright and complaints
Arvexa does not proactively scan customer content for copyright issues. Properly supported infringement notices or repeat-abuse reports may be reviewed and handled according to applicable requirements.
Proportionate response
Where practical, Arvexa will contact the customer and request remediation before restricting a service. Immediate restriction may be used when there is an urgent security risk, ongoing attack, clearly illegal material or a valid legal requirement.
No conflict with privacy policy
The privacy policy limits unnecessary collection and retention. It does not prevent Arvexa from acting on credible abuse reports or protecting the service and other users.