Business Continuity and Incident Response Summary
Flowdence maintains business continuity, disaster recovery, and incident response processes for its Marketplace apps and supporting systems.
Continuity approach
Section titled “Continuity approach”- Flowdence apps are designed around platform-managed services such as Atlassian Forge where possible.
- Product runbooks distinguish Flowdence app failures from Atlassian platform issues and customer-configured upstream service issues.
- Support and customer communication paths are maintained so customers can raise incidents even when an app feature is impaired.
- Continuity plans are reviewed and tested at least annually through tabletop exercises.
Incident response approach
Section titled “Incident response approach”Flowdence incident response covers:
- Evidence preservation.
- Severity classification.
- Containment and recovery.
- Customer impact assessment.
- Atlassian and customer notification where required.
- Post-incident corrective actions.
Notification commitments
Section titled “Notification commitments”When a Flowdence Marketplace app has a security incident or critical vulnerability that requires disclosure under Atlassian Marketplace policy, contract, or applicable law, Flowdence will notify Atlassian and affected customers using the appropriate communication path.
Customer-configured upstreams
Section titled “Customer-configured upstreams”Some Flowdence apps connect to customer-configured upstream systems such as Grafana Cloud, MuleSoft, or Boomi. Flowdence documents those integrations separately from Flowdence-controlled infrastructure and will help customers distinguish app issues from upstream platform issues during support and incident handling.