Catch-Up for Confluence

Catch-Up: data and retention

What Catch-Up stores

Catch-Up uses Atlassian Forge storage for each installation. It stores:

Original Confluence pages, attachments and Git files stay in their source system. The app does not store a repository clone. Repository excerpts are off by default; an owner can explicitly approve a bounded excerpt. Text people add to posts, comments or update descriptions may itself contain personal or confidential data.

Display names are retrieved from Confluence when needed and are not saved in the app database. The browser remembers your last selected feed and a visit identifier; clearing browser storage removes these local shortcuts, not the reading state stored by the app. The installed app has no third-party analytics or AI service.

Who can read it

Feed membership controls access; audience labels only filter relevance. Confluence posts also require current access to their linked source. Repository publication shares the approved metadata with the reviewed feed audience; it does not check each reader's repository membership. Opening the repository link still requires source access. Review recipients before enabling a publisher.

Forge hosts the app and its storage. Optional publisher jobs run in your Azure DevOps or GitHub environment and send selected metadata to the app's signed endpoint. No separately operated Catch-Up application server is used. Support email is a separate channel; send only the information needed to resolve a request.

How long posts stay

An app administrator chooses Manage workspace → Post lifetime. The default is 60 days, then archive; the allowed setting is 1–3,650 days. The policy also applies to existing posts, measured from their original publication date.

Archive removes a post from the normal timeline while keeping its discussion and personal state. Delete permanently removes the post, its discussion and associated reading state through background cleanup. Once deletion starts, changing the policy cannot undo it. Original documents remain intact.

Archive retains storage. Post lifetime does not remove feed configuration, account records or the minimal source identities needed to prevent replay from recreating deleted posts. An expired license pauses automatic publication; configured lifetime maintenance continues.

Export, uninstall and requests

An authorized owner can export accessible feed posts and comments as JSON. The current limit is 100 posts and 1 MB. Private reading state is excluded, and there is no import/restore function. This is not a complete installation backup.

Uninstalling is separate from post deletion. Atlassian currently retains Forge hosted storage for 28 days after uninstall; reinstalling does not automatically restore it. Recovery needs your consent and a developer support request within 21 days of uninstall. Contact us promptly with your site and uninstall date; recovery is not guaranteed (Atlassian storage lifecycle).

For access, correction or deletion requests, contact contact@luizperren.dev and identify the relevant Confluence site. Do not include private document contents or credentials in the initial message. Post lifetime and account-data requests are separate processes. Account identifiers, private reading state and personal information people have written in shared content are handled through a verified, case-by-case procedure coordinated with your site's administrator. Automatic account-closure cleanup is not claimed by this release.

See the privacy notice and data-processing agreement for roles, retention and rights.