Skip to content
Flowdence Flowdence Docs

BoomiSight Provider-Specific Terms Addendum

Last updated: 2026-06-02 Owner: BoomiSight Legal and Product Applies to app: BoomiSight for Confluence Review cadence: Quarterly and before publication Status: Publication-ready for Marketplace submission

This addendum supplements Flowdence provider-specific base terms for BoomiSight.

1. Service-specific scope

Section titled “1. Service-specific scope”

BoomiSight presents cached and refreshed Boomi snapshots inside Confluence modules.

The app does not guarantee real-time Boomi state at every render; freshness depends on refresh execution and Boomi API response behavior.

2. Customer configuration obligations

Section titled “2. Customer configuration obligations”

Customers are responsible for:

  • Providing and rotating the Boomi API token used by BoomiSight.
  • Ensuring credentials are authorized for required Boomi resources.
  • Reviewing displayed data before using it for operational decisions.

3. Data handling constraints

Section titled “3. Data handling constraints”

BoomiSight stores operational snapshots and credentials required for functionality as described in the BoomiSight Data Handling Disclosure.

4. Support boundaries

Section titled “4. Support boundaries”

Support does not include remediation of customer-owned Boomi platform outages or permissions misconfiguration unrelated to BoomiSight code behavior.

5. Security event handling

Section titled “5. Security event handling”

Security events are managed under the BoomiSight Security Policy and Flowdence internal incident-response procedures.

Security contact: [email protected]

6. Service limits and fair use

Section titled “6. Service limits and fair use”
  • High-frequency refresh requests may be rate-limited by upstream services.
  • BoomiSight may use cached data, reduced feature availability, or retry behavior when upstream services throttle or return transient errors.
Section titled “7. Additional legal clauses”

In addition to base provider-specific terms:

  • BoomiSight output depends on upstream Boomi API availability, customer permissions, and data freshness windows.
  • Cache-first rendering and stale fallback are resilience features and do not constitute a guarantee of real-time accuracy.
  • Customers remain responsible for validating critical operational decisions against source systems when required by internal policy.
Section titled “Related policies”

Related BoomiSight policies: