Bonterms Adoption Notes (Shared)
| Owner | Flowdence Legal and Product |
| Applies to app | All Flowdence Marketplace cloud apps |
| Review cadence | Quarterly and before legal publication changes |
Purpose
Section titled “Purpose”Define how Flowdence adopts the Atlassian-supported Bonterms standard end-user agreement and applies app-specific Provider-Specific Terms.
Policy
Section titled “Policy”- 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.
Why this model
Section titled “Why this model”- Reduces legal divergence between apps.
- Keeps customer review predictable.
- Supports app-specific risk treatment through addenda.
Per-app implementation steps
Section titled “Per-app implementation steps”- Confirm app listing legal mode is Bonterms-based in Marketplace configuration.
- Add or update app-specific Provider-Specific Terms using the Provider-Specific Terms Base Template.
- Link app-specific addendum and DPA documents using the Data Processing Addendum Base Template.
- Validate support, privacy, and security links in listing match published pages.
- Record legal revision in app decision log.
Version management
Section titled “Version management”- Bonterms baseline version used: Atlassian Marketplace Bonterms standard end-user agreement (current baseline in legal mode)
- Flowdence Provider-Specific Terms template version:
v1 - DPA baseline template version:
v1
Change control
Section titled “Change control”- Legal approves baseline changes.
- Product and engineering confirm operational commitments are achievable.
- Every app using updated legal text must update its decision log.