Use public pages, proof/status routes, labeled demos, and visible contact paths for normal review.
Acceptable use.
Use Mullusi public pages normally: read product information, review status, try public demos, and contact Mullusi through visible mailboxes. Do not disrupt the site, attack reserved routes, or treat reserved product services as open access.
These rules apply to the public pages. Using the product will need separate written approval and product terms.
Allowed, blocked, and what access does not grant
Do not attack delivery, test reserved services, bypass controls, or treat reserved surfaces as open access.
When sharing Mullusi content, keep its Available, Not yet or Planned labels.
Visiting the website does not grant API, dashboard, operator, pilot or product access.
Use boundaries
Allowed
Read public pages, use public demos as labeled, review status or proof pages, and contact Mullusi through visible mailboxes.
Not allowed
Do not attempt unauthorized access, disrupt delivery, bypass security controls, probe reserved services, or present demo output as product evidence.
Status accuracy
Do not remove or alter status labels when presenting Mullusi public content elsewhere. If a route is marked Not yet or Planned, keep that label.
Contact responsibly
Do not send harmful payloads, credential material, spam, or unrelated bulk mail through public contact routes.
Future product use
If written approval to use the product is published, more rules may apply. Until then, visiting the website does not authorize product use.
- No unauthorized external side effects.
- No use to hide, automate, or route prohibited actions.
- No attempts to bypass review, approval, budget, record, or status checks.
- No use against systems or data you do not own or have authority to test.
Violation reports: Send public-surface abuse or conduct reports to support@mullusi.com.
Route record (for auditors)
Acceptable-use route state: Published. Runtime conduct terms: AwaitingEvidence until separate written approval.