This policy is part of the Terms of Service and applies to everyone who uses cadshot, including the keyless demo. It exists to keep the Service lawful, secure and available for all customers. Examples below are illustrative, not exhaustive.
1. Content you submit
You must not submit, or direct the Service to fetch, files that:
- are unlawful, or whose possession, processing or distribution is unlawful, in the European Union, in Poland or where you are located;
- you do not have the right to use, including files that infringe someone else's intellectual property rights or trade secrets, or that you hold in breach of a confidentiality obligation;
- contain special categories of personal data or data about criminal convictions, unless we have agreed to this in writing;
- contain malware or are deliberately crafted to harm the Service.
2. Export-controlled and classified data
Unless we have agreed in writing beforehand, you must not submit data that is subject to export control or similar restrictions, including technical data controlled under the US International Traffic in Arms Regulations (ITAR) or Export Administration Regulations (EAR), items listed under the EU dual-use regulation, or national military lists, and you must not submit classified information. The standard Service does not provide the access restrictions such data requires. If you need this, contact [CONTACT EMAIL] about the self-hosted licence, which runs on your own infrastructure.
You must not use the Service if you are subject to EU, UN or other applicable sanctions, or on behalf of anyone who is.
3. Security of the Service
You must not:
- attempt to attack, exploit, crash or escape the renderer or its sandbox, for example with malformed, decompression-bomb or deliberately pathological files intended to exhaust memory or CPU;
- probe, scan or test the vulnerability of the Service, or bypass authentication, quotas or other controls, without our prior written permission;
- access or try to access another customer's data, cached outputs or account;
- interfere with or disrupt the Service or the networks and systems it depends on.
Good-faith security research is welcome: if you believe you have found a vulnerability, report it to [CONTACT EMAIL] and give us reasonable time to fix it before disclosing it. [DECISION: publish a vulnerability disclosure policy / security.txt.]
4. URL fetching
The url= parameter is for fetching model files that you are entitled to access from public http(s) locations. You must not use it to:
- reach, scan or probe internal, private, loopback, link-local or cloud-metadata addresses, or to get around the checks that block them (for example through redirects, DNS rebinding or encoded addresses);
- send requests to third-party systems in order to attack, scan or load them, or to hide the origin of such requests;
- fetch content from a site in breach of that site's terms or access controls.
5. Fair use and rate limits
You must respect the documented limits on input size, triangle count, output size and render time, and the rate limits signalled by the API (HTTP 429 with a Retry-After header). In particular you must not:
- create multiple free accounts, or rotate keys, addresses or identities, to get around the free allowance, the demo limit or rate limits;
- use the keyless demo endpoint from your own product or in automated workflows; it is for trying the Service on our website;
- generate load that is unreasonable for your plan without agreeing it with us first.
6. Reselling and competing services
You may build the Service into your own products and workflows and show the resulting images to your users. Without a written agreement with us you must not resell, sublicense or white-label the Service as a rendering or conversion API in its own right, share or sell API keys to third parties, or use the Service to build or benchmark a competing service for publication. [DECISION: confirm scope of the reselling and benchmarking restrictions.]
7. Enforcement
If we reasonably believe this policy is being breached we may throttle requests, block specific requests or sources, revoke keys, or suspend or terminate the account as set out in the Terms of Service. Where practical, and where the law allows, we will contact you first and give you a chance to fix the problem. We may report unlawful activity to the competent authorities and cooperate with them as the law requires.
We do not monitor the content of files as a matter of routine: input files are deleted when the render ends and logs do not contain file contents or file names.
8. Reporting abuse
To report misuse of the Service, or content you believe is unlawful, write to [CONTACT EMAIL] with enough detail for us to investigate.