Catch-Up for Confluence

Catch-Up data-processing agreement

Last updated: 18 September 2026. This agreement forms part of Catch-Up's terms and is accepted by the customer with the Marketplace order or installation.

Parties and instructions

Provider: Luiz Anton Perren (LuixBits), acting personally, Oberschönenbuch 31, 6438 Ibach, Switzerland. Customer: the organization identified in the Marketplace order or installation.

For workspace data, the customer determines the purposes of processing and the provider processes data on its documented instructions. If the customer is itself a processor, it must have authority to appoint the provider. Support and business records processed for the provider's own purposes are covered separately by the privacy notice.

Instructions comprise the agreed service, authorized settings and verified support requests. The provider may process data only to provide, secure and support that service, including instructed transfers, or as required by law. It will notify the customer of a conflicting legal requirement unless prohibited, and flag instructions it believes infringe applicable data-protection law. The customer is responsible for lawful collection, notices, access and publication instructions.

Processing inventory

Processing lasts through service provision and the applicable deletion period. It includes storing, displaying, updating, organizing, exporting and deleting data. Subjects are workspace users and people identified in submitted content.

Data and purposeLocation and retention
Account IDs, membership, grants and attribution: access and authorship Forge SQL. Current profile names are fetched without persistent caching. Kept while the installation uses them; removed with feed deletion/uninstall.
Posts, comments, revisions and selected source metadata: shared updates and discussion Forge SQL. Default 60-day archive; configurable 1–3,650-day archive/delete policy. Archive retains data.
Seen/saved/follow state, filters and reading position: private reading experience Forge SQL, with limited browser preferences. Post deletion removes associated state; verified account requests have a separate procedure.
Signing keys, checkpoints and work records: authenticated publication, deduplication and recovery Forge secret storage/SQL. Minimal technical records can outlast a post but not the installation; removed with it.
Approved support extracts and request evidence: instructed troubleshooting or privacy requests Operator-controlled files and, if necessary, Hostpoint mail, under the support retention policy.

Customer-selected text may contain sensitive data; the service does not require it. Original documents remain in Confluence/Git. Optional repository jobs run in the customer's own GitHub/Azure environment under its provider arrangements. Data and retention gives the product limits.

Protection, assistance and providers

The provider will restrict access to authorized people under confidentiality duties, maintain appropriate technical and organizational measures, and assist with verified rights requests, security obligations, impact assessments and regulator consultation, taking account of the processing and information available. It will notify the customer of a personal-data breach without undue delay and provide information as it becomes available.

Implemented controls include server-side authorization, Confluence source checks, signed repository requests with replay protection, encrypted signing-key storage, input validation and restrained logging. These controls are not a certification or a promise that every risk has been eliminated.

General authorization covers Atlassian (Forge hosting) and, where support requires customer data, Hostpoint (mail). Changes are announced on the support page at least 30 days in advance, with an opportunity to object by email on data-protection grounds; equivalent protection applies in provider contracts and the provider remains responsible for its subcontracted duties.

Forge persistent data follows eligible site residency, but compute and provider support can occur elsewhere (Forge residency limits). Swiss operator access and Hostpoint mail are separate.

Ending processing and review

At the customer's choice after service ends: deletion follows the disclosed platform periods (Forge removes hosted app data about 28 days after uninstall), and return is provided through the documented feed export (100 posts/1 MB, excluding private reading state) plus verified-request extracts. This agreement promises exactly these documented mechanisms, not an unlimited full-database return.

The provider will supply compliance information and allow proportionate audits or inspections, protecting other customers' data.

Drafting basis: GDPR Article 28, FDPIC outsourcing guidance, Forge DPA (which covers the developer–Atlassian relationship and does not replace this customer agreement).