ApprovalFlow Terms of Use


Owner	Flowdence Legal and Product
Applies to app	ApprovalFlow for Confluence
Review cadence	Quarterly and before publication

1. Legal framework

Default legal base for cloud listings: Bonterms standard end-user agreement.
App-level customization: Provider-Specific Terms only.
Data processing terms: linked DPA where required.

2. Service description

ApprovalFlow provides soft, version-aware content approval workflows for Confluence Cloud. The app enables space-scoped workflow definitions, per-page-version approval tracking, approver notifications via comments, and audit trail visibility across spaces.

3. Customer responsibilities

Maintain valid Atlassian and Marketplace licensing.
Configure approvers and workflows according to internal organizational policy.
Ensure users act with appropriate organizational authorization.
Review approval outcomes before relying on them for compliance or operational decisions.

4. Acceptable use

Customers must not use ApprovalFlow for unlawful activity or in violation of Atlassian terms.

5. Dependencies and platform requirements

ApprovalFlow requires an active Confluence Cloud subscription.
App functionality depends on Atlassian Cloud platform availability.
ApprovalFlow does not connect to any external third-party endpoints.

6. Availability and support

Support model and response targets are described in the ApprovalFlow support policy.
Support contact: support@flowdence.io or Flowdence Support

7. Data and privacy

Privacy commitments are described in the Flowdence privacy policy and the ApprovalFlow data handling disclosure.

8. Product-specific terms

ApprovalFlow is a soft workflow and audit tool for Confluence. It records approval state, page version context, approver decisions, and workflow audit events, but it does not prevent users from viewing Confluence pages during review or replace Confluence permissions. Customers are responsible for configuring workflow steps, assigning approvers, reviewing stale version states, and deciding how ApprovalFlow records map to internal compliance obligations.

ApprovalFlow does not require customer-supplied external credentials and does not declare external data egress. Support requests should avoid sharing full page body content unless specifically requested through an approved support channel.

9. Liability and warranty

To the maximum extent permitted by applicable law:

The services are 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 the app and associated services is limited to the fees paid by the customer for the affected app in the 12 months preceding the event giving rise to the claim.
Neither party is 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 (including liability for fraud, willful misconduct, or death/personal injury caused by negligence where required by law).

10. 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, the parties submit to the exclusive jurisdiction of the courts of Victoria, Australia, and the Commonwealth courts sitting in Victoria.

11. Termination

Usage rights end when subscription or license terminates.

12. Contact

support@flowdence.io

13. Shared baseline policies

This app-specific policy is read together with the shared Flowdence baseline: