FLINT MARKDOWN EXPORT · DPA DETAILS VERSION 2026-10-12
Data Processing Addendum
These completed Flint-specific details accompany the Bonterms Data Protection Addendum v2.0 (Attachment Version), including its Exhibits A and B. Read that standard together with these details for the complete DPA.
Key terms and incorporation
These DPA Details identify the processing performed for Flint Markdown Export. The Bonterms Data Protection Addendum v2.0 (Attachment Version), including Exhibits A and B, is incorporated by reference. The Provider-Specific Terms of the customer's end-user agreement incorporate both these completed details and that standard into the Main Agreement.
| Item | Flint-specific detail |
|---|---|
| Main Agreement | The Bonterms Standard End User Agreement v1.0 for Flint Markdown Export, including the applicable Marketplace Order and Provider-Specific Terms, entered into by Customer and Provider. |
| DPA effective date | The date the Customer enters into a Main Agreement that expressly incorporates this DPA. |
| Service | Flint Markdown Export for Confluence Cloud. |
| Provider / data importer | BlueConfetti, the Provider identified in the applicable Marketplace listing and Main Agreement. |
| Provider mailing address | 30448 W Aster Dr, Buckeye, Arizona 85396, United States of America. |
| Provider privacy contact | support@blueconfetti.net; security incidents: security@blueconfetti.net. |
| Provider activities and role | Providing the export service described below as processor, or subprocessor where Customer is itself a processor. |
| Customer / data exporter | The customer identified in the applicable Marketplace Order and Main Agreement. |
| Customer address and privacy contact | The customer's address in its Order and its designated privacy contact; until another contact is supplied, its designated site/Marketplace administrator. Customer can supply updated details to support@blueconfetti.net. |
| Customer activities and role | Managing and exporting its Confluence content; controller, or processor acting for its own controller, as applicable to the relevant data. |
| Subprocessor list | The list included below. |
| Designated EU governing law | Ireland, where the EU SCCs apply. |
| Designated EU member state | Ireland, where the EU SCCs apply. |
| Competent EU supervisory authority | Determined under Clause 13 of the EU SCCs for the relevant Customer and transfer. |
| Additional Terms | None. The service-specific facts and measures below supplement the standard without replacing its obligations. |
Processing description
Flint reads customer-selected Confluence pages and attachments, converts them into Markdown, resolves links and images, generates warnings and metadata, and prepares downloadable ZIPs. Customers choose scope, pages, presets and output options. Browser exports run in the requesting user's browser. Background and authenticated API exports execute on Atlassian Forge under the requester's Confluence permissions. Forge-hosted records support saved settings, activity history, asynchronous jobs, expiry and personal-data handling. Customer instructions include these selections and authorized support requests concerning the service.
Data subjects may include Confluence users, authors, editors, people mentioned in content, and any employees, customers, business contacts or other individuals whose information the Customer includes in selected pages, attachments or custom values.
Data may include account IDs and display names; names or contact information embedded in content; selected page and attachment bodies; page titles, identifiers, URLs, space names, labels, timestamps, versions and author/editor/mention metadata; user-supplied custom fields and profile values; and export/job/history metadata. Flint does not require users to provide Atlassian passwords or personal access tokens.
Customer-selected content may contain sensitive or special-category data. Flint does not solicit a particular sensitive-data category or automatically detect/classify arbitrary personal information in content. The same requester-permission checks, tenant isolation, temporary-artifact controls and retention limits apply. The Customer is responsible for its source permissions, lawful instructions and suitability assessment. No sector-specific certification is claimed.
Processing is initiated by the Customer's users or authenticated integrations, with scheduled maintenance of hosted records. Operations include reading, conversion, temporary storage, packaging, transmission to the requesting user and deletion. Data is used to provide the export workflow and authorized support, not advertising, sale of personal information, independent content analytics or AI-model training. Flint does not call an AI provider.
Retention, return and deletion
Background job and ZIP access expires one hour after job creation; platform object TTL and scheduled metadata cleanup apply. Export history expires after 90 days. Saved profiles persist until deleted. Users can delete their own profiles/history, and authorized administrators can explicitly manage all-users history. Customers return page content to themselves through export downloads; they retain control of copies they download or share.
The hourly privacy process inventories retained account IDs and handles Atlassian closed/updated-account responses for matching history, profiles and jobs/artifacts containing known author/editor/mention identities. It does not classify all personal information in prose, attachments or custom values. For additional app-held-data requests, the customer's authorized contact may contact support@blueconfetti.net. Customer source pages and Confluence attachments remain under the customer's administration.
Following termination, deletion/return is governed by Section 8 of the incorporated standard. Forge uninstall, recovery, soft-deletion and backup lifecycles also apply; logical expiry or an application delete is not a promise of immediate physical erasure from every platform backup. No app-specific independent backup service is configured. Support-provided customer content is restricted to the support purpose and removed when no longer needed for that purpose, subject to applicable legal retention requirements. Independently controlled support/business contact records are described in the privacy policy.
Locations and transfers
App-hosted export records and artifacts use Forge KVS and Forge Object Store. Supported storage residency follows the host Confluence location through Atlassian; compute may execute outside that storage realm. User-browser memory, downloaded files and support email do not inherit that storage-residency guarantee. Provider support is performed from the United States. The incorporated transfer provisions apply where relevant; BlueConfetti does not claim Data Privacy Framework certification.
Subprocessors
| Supplier | Processing purpose and data | Locations / further details |
|---|---|---|
| Atlassian, through the contracting entity and affiliates providing Forge under the Forge Terms | Hosting and operation of background processing, per-installation KVS records, temporary ZIP Object Store, queues and scheduled functions for customer-selected data. | Host-aligned supported storage locations; compute and operational processing may occur in other locations. Forge DPA, Forge residency, Atlassian subprocessors. |
| Google Workspace, through the contracting entity and affiliates providing the mail service | Only customer content voluntarily supplied in an authorized support request. No automated app export, page or ZIP transfer to Google is configured. | United States and other locations used to deliver Google Workspace under its Cloud DPA and subprocessor list. No support-email residency guarantee is offered. |
Customers should redact support examples and must not send credentials. The public GitHub issue tracker is for non-confidential reports; customer-selected export content is not sent there by Flint. This list does not present Atlassian's or Google's own suppliers as directly contracted BlueConfetti subprocessors.
Technical and organizational measures
- Tenant-specific Forge-hosted storage and functions; no configured external backend, Forge Remote, content analytics or AI integration.
- Confluence requests use the signed-in requester or authenticated requester's impersonated permissions. Worker and download paths check current access, including inlined pages. API access requires OAuth, custom scopes and administrator enablement; job ownership is checked.
- History and profiles are per-user, with explicit administrator all-users controls. License checks apply in both frontend and backend.
- Background ZIP availability is bounded; objects are not placed on a public CDN. Signed download URLs are credentials and downloaded copies cannot be retracted by later permission changes.
- Application code does not log content, credentials or signed URLs; failure logs are limited to error name, code and HTTP status. Atlassian operational records remain governed by its platform policies.
- Local automated conversion/backend tests, recorded two-account isolation checks and real exported-file validation support change review. This is not an independent certification or a guarantee covering every possible customer payload.
- Personnel processing support content must keep it confidential and restrict access to the support purpose. Any new person or subprocessor receiving access requires an appropriate authorization and contractual controls.
- Security and deletion requests go to the contacts above. Incident assessment, containment, customer notice, rights-request assistance, records and audit cooperation follow the incorporated standard. The incident-notification commitment begins upon awareness; it does not promise continuous staffed customer support.
Standard terms and attribution
Bonterms Data Protection Addendum v2.0 (Attachment Version), © 2026 Bonterms, Inc., is available under CC BY 4.0. Its substantive clauses are incorporated by reference without modification; these are BlueConfetti’s service-specific details. Bonterms is independent of BlueConfetti.