The content and behavior rules for Media2URL uploads, public links, private links, embedded media, and automated usage.
Last updated: July 9, 2026
Media2URL is built for legitimate sharing: support screenshots, product images, PDFs, creator files, internal assets, and repeat upload workflows. The same upload flow can be abused if someone uses it to distribute illegal files, hide harmful links, or overwhelm the platform.
This policy describes the content and behavior that is not allowed. It applies to public links, private links, uploads, embeds, file replacements, and files that are no longer publicly visible but still stored in an account.
You may not use Media2URL for content that is illegal, exploitative, threatening, non-consensual, malicious, deceptive, or unsafe. Material involving child exploitation, non-consensual intimate imagery, trafficking, sexual coercion, terrorism, violent threats, stolen credentials, or malware can lead to immediate action.
Private links are not a shield for illegal files. A file can violate this policy even if only a small group receives the URL.
Do not use Media2URL to host malware, command-and-control payloads, phishing pages, credential kits, spam assets, evasive redirects, bot traffic, denial-of-service activity, vulnerability probes, or files designed to bypass another service's security rules.
Automated traffic must respect rate limits, plan limits, and normal product rules. Creating multiple accounts to avoid limits, hide abuse, or continue after suspension is not allowed.
Only upload files you have the right to store and share. If an image, video, audio clip, PDF, or dataset includes someone else's work or personal information, you are responsible for permission, consent, and lawful handling.
Media2URL may remove files when rights, consent, or safety concerns are credible enough to require action, even before a court or agency has made a final decision.
Policy enforcement may include warnings, link disabling, file removal, account suspension, upload-access revocation, billing cancellation, evidence preservation, and reports to relevant authorities. The response depends on severity, history, risk, and legal obligations.
Users can contact support if they believe enforcement was a mistake. Appeals should include the affected URL, account email, and a direct explanation of why the file or activity complies with the rules.
