Acceptable Use Policy

• You must own the 3D content you upload, or otherwise have the rights to store and process it.
• Do not upload content that infringes anyone's intellectual property.
• Do not upload content that is unlawful where you are, or where the service operates.
• Do not upload malware, exploit payloads, or files crafted to attack the parsers or the machines that run them.

• Do not attempt to circumvent size limits, upload quotas, or rate limits, including by creating additional accounts or anonymous sessions to do so.
• Do not use the service as general-purpose file storage or as a content-delivery network for files you are not processing.
• Do not submit work at a volume or shape intended to exhaust the processing queue or degrade the service for other customers.
• Automated use is fine within your plan's limits. Automated use designed to evade them is not.

• Do not probe, scan, or attempt to gain access to accounts, assets, jobs, or infrastructure that are not yours. Security research is welcome — report it rather than exploiting it.
• Do not resell or redistribute access to the service unless we have agreed to it in writing.
• Do not share account credentials with people outside your organisation.

Where use breaches this policy we may cancel jobs in progress, suspend processing, or suspend the account. We aim to contact you first where the situation allows it, and to act immediately where it does not — for example an active attack or a legal obligation.

A suspended account keeps its stored assets, and their retention windows keep running — suspension stops you starting new work, it does not delete what you already have. If the window would lapse during a suspension we lift the block on downloads so you can retrieve your files before they expire.

To appeal, reply to the notice or email support@meshcrunch.com. We aim to respond within five working days. Termination for a first-time, non-malicious breach is a last resort.

Email support@meshcrunch.com with what you have observed. Security vulnerabilities should go to the address on the Security page instead.