Email support@render402.xyz. Use the subject line and evidence checklist below. Never send a wallet private key, seed phrase, or unnecessary sensitive media.
1. Abuse or safety
Use the subject “Render402 Abuse Report” for non-consensual imagery, exploitation, threats, impersonation, deceptive content, privacy harm, illegal material, or other Content Policy concerns.
Include, when available:
- the relevant Render402 URL, order ID, or public wallet address;
- a concise description of the suspected violation;
- why you are affected or able to report it; and
- the smallest useful screenshot or evidence.
2. Copyright or other rights
Use the subject “Render402 Rights Notice.” A good-faith notice should identify:
- the protected work, person, mark, or other right;
- the specific output or activity at issue, with enough detail to locate it;
- your name, contact details, and relationship to the right;
- a statement that you believe the reported use is not authorized by the owner, an agent, or law;
- a statement that the information is accurate and that you are authorized to act; and
- your physical or electronic signature.
We may ask for clarification, notify the affected user where appropriate, restrict access, preserve evidence, or reject notices that do not identify material we can locate. This reporting route does not represent that Render402 has registered a statutory DMCA designated agent.
3. Payment or delivery
Use the subject “Render402 Payment.” Include the order ID, public payer address, transaction hash, current order status, and a short description. Do not pay a second time while the first settlement is unresolved. See the Payments & Refunds Policy.
4. Privacy request
Use the subject “Render402 Privacy.” State whether you seek access, correction, or deletion and identify the wallet or order involved. We may request a wallet signature to avoid disclosing data to the wrong person. See the Privacy Notice.
5. Security vulnerability
Use the subject “Render402 Security.” Do not access another user’s data, disrupt the service, perform denial-of-service testing, publish an unpatched vulnerability, or move digital assets that are not yours. Describe the affected endpoint, reproducible steps, impact, and a safe proof of concept.
6. What happens next
We triage reports based on severity, available evidence, and our ability to identify the order or content. We may restrict access while investigating, preserve relevant records, request more information, or take no action where a report cannot be verified. We do not promise a particular outcome or response time.
Good-faith reports are not treated as user violations. Knowingly false, fraudulent, or abusive notices may result in restricted access and may carry legal consequences.
Send a report
Email support@render402.xyz. Include “Render402” and the report type in the subject. Keep a copy of your message and any order or transaction reference.