VersionSelectData deletion and retention
Contact support@fogsea.top. A Jira administrator should identify the intended site and installation or environment, the requested data scope, and whether the app should remain in use. Do not send credentials, full catalog exports, or work item bodies. We verify administrative authority before an irreversible operation.
Specify the data scope
State whether the request covers the saved API token, current catalog entries, old manual-catalog records, all app-hosted data, or separately supplied support material. Jira field values and external API data are managed separately.
Controls available to administrators
- Use Delete token in API settings, then revoke the credential at its source.
- Create, edit, reorder, and remove active manual catalog entries in app settings.
- Manage active API catalog data in the customer-selected backend service.
- Manage Jira field values and Jira history using Jira administration.
- Manage downloaded JSON exports under the customer's retention policy.
Removing an active entry does not rewrite Jira field values. Changing the API URL or switching sources retains the other mode's saved configuration.
Manual-catalog cleanup boundary
Manual catalog saves use immutable internal rows. When a later save replaces a row or snapshot, an older row can remain in Forge storage without being referenced by the active catalog. A bounded daily background process removes eligible internal manual-catalog rows, indexes, and expired save sessions after they have remained unchanged and unreferenced for at least 24 hours.
The process protects the current catalog, recent records, and valid drafts and rechecks active references before deletion. It runs without an administrator action and does not pause configuration saves. Automatic cleanup does not delete Jira field values or history, API credentials, caches, logs, external API records, exports, or support correspondence. It is not a way to restore an older revision or evidence that every category of customer data has been erased.
Forge storage lifecycle
For a complete end to app processing, an authorized administrator may uninstall the app. Atlassian Forge handles soft deletion and later retention or removal under its hosted-storage lifecycle. This is not immediate erasure or a selective deletion mechanism.
Separate responsibilities
The Jira administrator manages field values and Jira history. The external API operator manages its records and request logs. The customer manages exports. Material separately sent to the support mailbox is a separate support record.
A deletion response should identify what was deleted, what remains, why anything is retained, and the next action or platform deadline. This guide does not replace applicable legal rights or deadlines.