Acceptable
Use Policy.
This Acceptable Use Policy outlines the guidelines and standards of conduct required when uploading code, writing annotations, or reviewing preview builds.
This Acceptable Use Policy ("Policy") sets forth the standards of conduct for all users of the Claron platform and Service. This Policy is incorporated into and made part of our Terms of Service.
Any violation of this Policy may result in the immediate suspension or termination of your account, without refund.
2.1 Illegal and Harmful Activities
Users shall not use Claron to violate any local or international regulations, commit financial fraud, facilitate modern slavery/trafficking, distribute CSAM, create deepfakes/non-consensual imagery, or promote self-harm.
Consequence: Immediate termination and potential law enforcement notification.
2.2 Security and System Abuse
Users are strictly prohibited from attempting to compromise Claron's infrastructure, bypass authentication, probe vulnerabilities, or reverse-engineer services. Specifically:
- No unauthorized vulnerability scanning, DDoS, or brute-force operations.
- No cryptocurrency mining or CPU/GPU exploitation daemons.
- No deployment of proxies, exit nodes, VPNs, or reverse tunnels.
- No sandbox escape operations targeting the hypervisor or control plane.
- No adversarial prompt injection payloads designed to manipulate AI assistants.
Consequence: Immediate suspension and potential legal action.
2.3 Spam and Abuse
Bulk message spamming, metric inflation, multi-accounting to bypass usage limits, stalking, doxxing, or cyberbullying other team members is strictly prohibited.
2.4 Intellectual Property & Malware
Uploading copyrighted assets without rights, violating open-source license attribution terms, executing trojans/ransomware, or distributing keystroke loggers is banned.
2.5 Commercial Misuse & Evasion
You may not scrape content at commercial scale, build competitive products, resell platform credentials, or manipulate coupon codes fraudulently.
3.1 General Content Requirements
All content uploaded to Claron must comply with the following standards:
- Legal Compliance: Must not facilitate illegal activity or violence.
- Respectful Communication: Free of hate speech, bullying, defamation, or graphic media.
- Authenticity: Free of identity misrepresentation or fraudulent statements.
3.2 User-Generated Content
Bug reports, annotations, and comments should be accurate, honest, and focus solely on legitimate technical issues while avoiding offensive language.
4.1 Monitoring and Enforcement Path
We use anomaly detection, security logs, and customer reports to verify compliance. Enforcement stages include:
- First Offense: Account warning and content removal.
- Second Offense: Temporary account suspension (7 to 30 days).
- Severe Offense: Permanent account termination and forfeiture of prepaid fees.
4.2 Appeal Process
Suspended users can submit a written appeal to legal@claron.dev detailing remediation efforts. We will respond within 10 business days.
If you suspect a user has violated this Policy, report the details (including description, links, and screenshots) to:
Email: abuse@claron.dev (or support@claron.dev)
6.1 Source Code Sanitization
Users are solely responsible for ensuring no unencrypted credentials, database passwords, or private SSH keys are uploaded inside code packages or source maps.
6.2 Third-Party Privacy & Open Source
Do not process protected personal data (GDPR, CCPA) without safeguards. You must preserve open-source license attribution notices and respect copyleft requirements.
7.1 Disclaimer
Claron is not liable for user-generated content, third-party access, or local law enforcement actions.
7.2 Sanctions & Export Compliance
By using the Service, you represent that you are not located in a comprehensively sanctioned country (including Cuba, Iran, North Korea, Syria, or Russian-controlled regions of Ukraine) or listed on any governmental restricted parties list.
We reserve the right to modify this Policy. Material changes will be communicated via email or dashboard notifications 30 days prior to taking effect.
For questions, contact support@claron.dev.
