This Acceptable Use Policy ("AUP") governs your use of the runQC platform operated by Syntaxa LLC ("Company"). This AUP is incorporated by reference into the runQC Terms of Service. Capitalized terms not defined herein have the meanings given in the Terms of Service.
1. Purpose
This AUP establishes the boundaries of acceptable conduct when using the Service to protect the integrity of the platform, the security of all customers, and the interests of the broader community. Violation of this AUP may result in suspension or termination of your Account.
2. Prohibited Activities
2.1 Unauthorized Testing
You may not use the Service to:
- Test, probe, scan, or interact with any endpoint, system, or service that you do not own or have explicit written authorization to test
- Conduct penetration testing, vulnerability scanning, or security assessments against third-party systems without authorization
- Impersonate another person or entity when interacting with target systems
2.2 Harmful or Abusive Use
You may not use the Service to:
- Generate, transmit, or facilitate the creation of content that is illegal, harmful, threatening, abusive, harassing, defamatory, or obscene
- Attempt to elicit illegal content, child sexual abuse material, or content promoting violence against specific individuals or groups from any target agent
- Develop, test, or deploy AI agents intended to deceive, defraud, or manipulate users
- Facilitate spam, phishing, or social engineering attacks
- Engage in or facilitate any activity that violates applicable law
2.3 Platform Abuse
You may not:
- Circumvent, disable, or interfere with any security, rate-limiting, authentication, or billing feature of the Service
- Create multiple free-tier Accounts to circumvent usage limits or credit caps
- Share, transfer, or sell Account credentials or API Keys to unauthorized persons
- Use automated scripts or bots to create Accounts or manipulate the Service, except through the documented API
- Attempt to access other customers' data, Accounts, or Journals
- Intentionally overload, crash, or degrade the performance of the Service
- Exploit bugs, errors, or vulnerabilities in the Service for unauthorized purposes (responsible disclosure to [email protected] is encouraged)
2.4 Intellectual Property Violations
You may not:
- Use the Service to infringe, misappropriate, or violate any third party's intellectual property rights
- Copy, reproduce, or distribute any part of the Service's source code, documentation, or proprietary materials
- Reverse engineer, decompile, or disassemble the Service or any component thereof
- Use the Service to develop a product or service that competes with runQC
2.5 Network and Infrastructure Abuse
You may not:
- Attempt to probe, scan, or test the vulnerability of the Service infrastructure
- Attempt to breach or circumvent authentication, encryption, or security measures
- Introduce malware, viruses, worms, trojan horses, or other malicious code
- Use the Service as a proxy or relay for unauthorized network traffic
- Attempt to access AWS, MongoDB, or other infrastructure components directly outside of documented interfaces
2.6 LLM Provider Abuse
You may not:
- Use the Service to violate the acceptable use policies or terms of service of any LLM Provider (OpenAI, Anthropic, or others)
- Attempt to extract, reconstruct, or reverse-engineer the training data, model weights, or internal workings of any LLM used by the Service
- Submit prompts designed to circumvent safety filters or alignment measures of LLM Providers
- Use the Service to generate content that violates LLM Provider policies
2.7 Data Misuse
You may not:
- Use the Service to collect, harvest, or store personal data of third parties without proper legal basis
- Process data subject to specific regulatory requirements (HIPAA, PCI-DSS, ITAR, EAR) through the Service without Company's prior written consent and appropriate contractual safeguards
- Use Test Results or Journal data for purposes other than your internal quality assurance and product improvement
3. Resource Limits
3.1 Technical Limits
The Service enforces the following technical limits, which vary by Subscription Plan:
| Resource | Limit Type | Purpose |
| API request rate | Per-plan | Prevent service degradation |
| Concurrent runs | Per-plan | Fair resource allocation |
| Monthly credits | Per-plan | Usage management |
| Daily cost cap | Per-plan | Cost protection |
| SSE connections | Per-tenant | Connection management |
| Run budget | Per-run. Where Customer does not specify a per-run limit, the platform applies a default of $0.20 for Runs submitted through the API and $0.50 for trial Runs and Runs triggered from repository configuration. Every Run is additionally capped at the per-run budget ceiling of Customer's Subscription Plan, and at a platform-level per-run LLM cost cap of $5.00 | Cost containment |
3.2 Fair Use
Even within technical limits, Company reserves the right to throttle or restrict usage that: (a) creates an unreasonable burden on infrastructure; (b) adversely affects other customers' experience; or (c) indicates abusive or exploitative usage patterns.
4. Reporting and Enforcement
4.1 Reporting Violations
If you become aware of a violation of this AUP, please report it to [email protected] with relevant details.
4.2 Security Vulnerabilities
If you discover a security vulnerability in the Service, please report it responsibly to [email protected]. Do not publicly disclose vulnerabilities until Company has had a reasonable opportunity to address them.
4.3 Enforcement Actions
Company may take the following actions in response to AUP violations, at its sole discretion:
- Warning: Written notice of the violation with a request to cease the prohibited activity
- Throttling: Temporary reduction of service capacity
- Suspension: Temporary suspension of Account access
- Termination: Permanent termination of the Account
- Legal Action: Pursuit of legal remedies, including injunctive relief and damages
The severity of enforcement action will be proportionate to the nature, severity, and recurrence of the violation. Company may take immediate action without prior notice for violations that pose a risk to the security, integrity, or availability of the Service.
4.4 No Liability for Enforcement
Company shall not be liable for any damages resulting from enforcement actions taken in good faith under this AUP, including any loss of data or access.
5. Modifications
Company reserves the right to modify this AUP at any time. Material changes will be communicated via email or in-Service notification at least fifteen (15) days before taking effect. Continued use of the Service after changes take effect constitutes acceptance.
6. Contact
For questions about this AUP, contact:
This Acceptable Use Policy was last updated on September 9, 2026.