MuleSight Terms of Use
| Owner | Flowdence Legal and Product |
| Applies to app | MuleSight for Confluence |
| Review cadence | Quarterly and before Marketplace submission |
Legal structure
Section titled “Legal structure”MuleSight terms are based on:
- Bonterms standard end-user agreement selected in Marketplace.
- Flowdence provider-specific base terms.
- MuleSight provider-specific addendum.
In case of conflict, MuleSight app-specific addendum terms control for MuleSight-specific behavior.
1. Service description
Section titled “1. Service description”MuleSight provides Confluence-native views of MuleSoft operational and API security snapshots, including caching and refresh features.
2. Customer responsibilities
Section titled “2. Customer responsibilities”- Maintain valid Atlassian and app licensing.
- Provide valid MuleSoft connected app credentials with required MuleSoft permissions.
- Use the app in compliance with Atlassian terms and applicable law.
3. Acceptable use
Section titled “3. Acceptable use”Customers must not use MuleSight to perform unauthorized access, unlawful processing, or misuse of third-party credentials.
4. Dependencies
Section titled “4. Dependencies”MuleSight functionality depends on:
- Atlassian Forge platform availability.
- MuleSoft Anypoint API availability and customer credential permissions.
5. Availability and support
Section titled “5. Availability and support”Support commitments are defined in the MuleSight support policy.
6. Privacy and security
Section titled “6. Privacy and security”Privacy and security commitments are documented in the Flowdence privacy policy, MuleSight security policy, and MuleSight data handling disclosure.
7. Product-specific terms
Section titled “7. Product-specific terms”MuleSight is a Confluence visibility layer for MuleSoft data. It depends on customer-supplied Connected App credentials, required Anypoint OAuth scopes, MuleSoft API availability, and cached snapshot freshness. MuleSight may show cached or partial data when upstream calls fail, timeout, or return authorization errors; diagnostics and freshness indicators are part of the service and should be reviewed before relying on a view for operational decisions.
Customers are responsible for configuring credential scope, controlling access to Confluence pages that display MuleSoft data, and validating critical operational or security decisions against source systems where internal policy requires it.
8. Liability and warranty
Section titled “8. Liability and warranty”To the maximum extent permitted by applicable law:
- MuleSight is provided on an “as is” and “as available” basis.
- Except for non-excludable statutory rights (including rights under the Australian Consumer Law), Flowdence disclaims implied warranties, including merchantability, fitness for a particular purpose, and non-infringement.
- Flowdence’s aggregate liability for claims arising out of or related to MuleSight is limited to the fees paid by the customer for MuleSight in the 12 months preceding the event giving rise to the claim.
- Flowdence is not liable for indirect, incidental, special, consequential, or punitive damages, including loss of profits, goodwill, or business opportunity.
- Nothing in these terms excludes or limits liability that cannot be excluded under applicable law.
9. Governing law and jurisdiction
Section titled “9. Governing law and jurisdiction”These terms are governed by the laws of the State of Victoria, Australia, excluding conflict-of-law rules. Subject to mandatory rights under applicable law, disputes are submitted to the exclusive jurisdiction of the courts of Victoria, Australia, and Commonwealth courts sitting in Victoria.
10. Contact
Section titled “10. Contact”- Legal contact:
support@flowdence.io - Support contact: support@flowdence.io or Flowdence Support Portal
11. Shared baseline policies
Section titled “11. Shared baseline policies”This app-specific policy is read together with the shared Flowdence baseline: