Catch-Up for Confluence

Catch-Up terms

Last updated: 18 September 2026. Effective from Catch-Up's first Atlassian Marketplace availability.

Provider: Luiz Anton Perren (LuixBits), acting personally, Oberschönenbuch 31, 6438 Ibach, Switzerland. Contact: contact@luizperren.dev.

Agreement

Catch-Up is offered through the Atlassian Marketplace under Atlassian's standard end-user agreement, configured for this provider, together with the provider-specific terms on this page, the data-processing agreement and the privacy notice. Purchases, billing and evaluation licenses are handled by Atlassian.

The service

Catch-Up provides shared document updates and discussion within Confluence Cloud, with optional Azure DevOps and GitHub publishers. Installation requires an authorized Confluence administrator. Customers control membership, publication permissions and sources; publishers must have permission to share submitted content. Protect publisher signing keys and review recipients before enabling a publisher.

Confluence posts require source access. Repository publication shares approved metadata with feed members without checking individual repository membership. Content remains its rights holder's property; the provider processes it only to provide, secure and support the agreed service.

Product limits

Original documents stay in Confluence/Git. Catch-Up is not a backup: feed export is limited to 100 posts/1 MB, excludes private reading state and has no restore function. "Seen" is not acknowledgement. Post lifetime defaults to 60 days, then archive; administrators choose 1–3,650 days and archive or deletion. Archive retains data. See Data and retention.

Support and discontinuation

Support is provided per the support page: ordinary initial response target of three Swiss business days (Europe/Zurich), with Atlassian Marketplace response obligations taking precedence. Support continues while the app is offered, and existing paid service and support entitlements are honored even if new sales stop. For a planned discontinuation, the aim is at least 90 days' notice explaining customer and data options. Necessary security or legal action may happen sooner. This does not cancel purchased terms or restrict applicable refunds, remedies or mandatory rights.