Data, retention, and deletion¶
Service Quality Review stores the program configuration, review criteria, selection and assignment history, human assessments, cited evidence, optional AI suggestions, calibration, findings, and released coaching needed for the review workflow.
The app runs on Atlassian Forge with hosted storage. Optional AI uses Forge LLMs. The runtime has no separate Magnascale-hosted application backend or external analytics service. Support correspondence is handled separately through Magnascale's support channels.
Current permissions apply to retained content¶
Stored evidence and derived content do not bypass current Jira/JSM access. The app withholds affected content when source access cannot be verified, or when a stored excerpt no longer matches an edited or deleted source.
Numeric report rows and completed-results CSV follow current issue visibility and exclude private notes, quotations, and AI text. See Results and exports.
History and temporary data¶
Customer history is kept until your organization deletes it or uninstalls the app. Period closure, reopening, inactivity, and licence lapse do not expire that history. Current Jira and app permissions still govern access; privacy redaction and deletion take precedence.
Temporary data has separate deadlines. There is no customer retention editor or legal-hold guarantee. The table describes policy bounds, not an exact physical-deletion deadline. Background cleanup is bounded and can wait while related work remains active.
| Information | Retention |
|---|---|
| Drafts, submitted reviews, revisions, cited evidence, and period/selection history | Until customer deletion or uninstall. |
| Calibration, findings, coaching, audit history, published criteria, and program settings | Until customer deletion or uninstall. |
| Unused AI evidence and suggestions | Up to 30 days; content accepted into customer history follows that history. |
| Operation replay receipts | Up to 30 days. |
| In-app Updates and read state | Up to 365 days; shorter producer deadlines can apply. |
| AI/worker control and proof records | Producer deadlines and safe-retry requirements. Active work is protected; cumulative allowance records remain to enforce caps. |
| Content-free deletion receipts | 30 days. |
| Program-closure safety marker | An opaque program identifier and completion time remain indefinitely after program deletion to block late writes; no account association or review content is retained in that marker. |
Expired temporary information is withheld when checked for access. Previously downloaded or delivered content cannot be recalled.
Delete a program or site app data¶
Program managers can delete their program from its settings. Jira or app administrators can delete a program or erase all app data for the site from App settings → Access. Managers can also delete review periods that have not started reviews.
- Export authorized completed results you need before deleting.
- Select the intended program or site scope.
- Preview the deletion and inspect its record counts.
- Read and confirm the permanent-deletion statement.
- Use Check deletion status to follow cleanup. If it reports a failure, use Retry cleanup.
Accepted deletion hides the affected data immediately; physical cleanup continues in the background. The app cannot restore it. Deleting app data does not delete the original Jira requests, created corrective Jira work, or copies of exports held elsewhere. Atlassian platform backups follow Atlassian's own lifecycle.
Closed Atlassian accounts¶
When Atlassian reports a stored account as closed, the app redacts the account's identity in place within 30 days of learning of the closure. Affected program review content is temporarily hidden during processing; unrelated programs remain available.
History retains scores and counts under a Former user replacement identifier. Notes, quotations, and other free text about that person on reviews of their work are removed, and calibration results they participated in are removed. Names mentioned in free text about other people are not automatically searched. A replacement label does not guarantee anonymity in the wider context.
For a privacy request, contact privacy@magnascale.com.
Licence expiry and uninstalling¶
Licence expiry does not erase records: authorized reading and completed-results export continue under the normal retention and access rules. New work pauses. Renewal does not automatically replay work that failed while unlicensed.
Export needed outcomes before uninstalling. A reinstall starts a new installation and does not automatically restore old data. Contact support within 21 days of uninstalling if you need help requesting recovery through Atlassian. Recovery depends on Atlassian and is not guaranteed. See Atlassian's hosted-storage lifecycle.
Residency and policy information¶
Supported Forge storage residency follows the host product's pinning and migration. This does not fix the location of every AI inference, invocation, log, or support interaction. See Availability and policies for policy context and contact details.