MuseMVP Acceptable Use And Community Rules

Effective Date: March 11, 2026

These rules explain what kinds of behavior are expected when you use MuseMVP. They apply to public pages, account features, documentation, uploads, API-related surfaces, support interactions, and any community or collaboration features we make available now or later.

1. Core Expectations

You must use MuseMVP in a lawful, respectful, and security-conscious manner. You are expected to protect your account, respect the rights of others, and avoid conduct that harms users, operators, or infrastructure.

2. Allowed Use

You may use the service to:

explore the public site, docs, and legal materials;
register for an account and use the signed-in product features made available to you;
upload lawful content you are authorized to use;
access APIs, API Keys, or developer surfaces in accordance with the product design and any published limits;
contact support, submit feedback, and report bugs or security issues in good faith.

3. Prohibited Conduct

3.1 Illegal Or Harmful Content

You must not create, upload, transmit, or distribute content that:

violates law or regulation;
infringes intellectual property, privacy, publicity, or other rights;
promotes violence, exploitation, abuse, harassment, discrimination, or illegal trade;
contains malware, malicious code, phishing schemes, or deceptive content.

3.2 Security Abuse

You must not:

attempt to bypass authentication, authorization, rate limits, or access controls;
scan, probe, or test the service for vulnerabilities without authorization;
use stolen credentials, session tokens, API keys, or other secrets;
interfere with service stability, background jobs, storage, logging, or network operations.

3.3 Platform Misuse

You must not:

use automation in a way that creates unreasonable load, spam, or service degradation;
impersonate another person or misrepresent your affiliation;
use uploads, docs, APIs, or admin surfaces to distribute junk data, unsolicited promotions, or fraudulent workflows;
attempt to extract non-public data, model behavior, internal prompts, source assets, or customer information without authorization;
use the service to support activities that are clearly inconsistent with the intended product purpose or that create legal or operational risk for MuseMVP.

4. Account And Team Responsibility

You are responsible for activity performed through your account, team, integrations, and credentials. If you invite collaborators or expose API access, you must manage permissions carefully and revoke access when no longer needed.

5. Content Review And Enforcement

We may review reports, investigate suspicious behavior, remove content, limit features, rotate credentials, suspend access, or terminate accounts when necessary to enforce these rules, protect the service, or comply with law. We are not obligated to monitor every action, file, or API request proactively.

6. Reporting

If you discover abuse, policy violations, or security problems, contact us at . Please provide enough detail for us to investigate responsibly.

7. Appeals

If you believe an enforcement action was taken in error, you may contact us at and provide the relevant account, timeline, and supporting information. We will review the request within a reasonable period, but submission of an appeal does not guarantee reinstatement.

8. Updates

We may update these rules when the product, threat model, infrastructure, or legal requirements change. The latest version will be posted on this page with an updated effective date.

9. Contact

Questions about acceptable use or enforcement can be sent to:

Email:

Community Guidelines