At a glance
| Control | Production v6 behavior | Boundary |
|---|---|---|
| Personal-data reporting | A weekly scheduled job sends each covered account ID and its latest recorded update time to Atlassian. | It does not export record content. |
| Key-value actor fields | A closed status replaces matching actor IDs with account-deleted. | The handler covers only fields named in its code. |
| Enterprise SQL actor fields | Matching catalogued fields become [deleted-user] through revision-checked writes. | A write conflict prevents successful completion of that lifecycle run. |
| App roles | The closed account leaves the app administrator list. Matching role-change attribution is also replaced. | Atlassian and Confluence account administration remain separate. |
| Governed evidence | Terms, versions, findings, baselines, and other non-actor evidence remain stored. | Preserving evidence does not decide its lawful retention period. |
| Retention contract | A backend helper blocks capture without a retention date. It prevents deletion during legal hold. | No production workflow calls this helper. The lifecycle plan is marked plan_only. |
How it works
- Send the request to privacy@teamkit.dev under the published privacy policy.
- Use the published policy to identify the rights and controller contact.
- The weekly Forge job reports covered account identifiers to Atlassian.
- Atlassian can return a closed status for an identifier.
- The app replaces matching actor references and removes matching app-role membership.
- Governed records and unrelated actor references remain unchanged.
- Review free text, page content, and uploaded files separately when the request covers them.
- Apply retention and legal-hold decisions outside this actor-replacement callback.
Example
A former reviewer’s Atlassian account closes. The app replaces that identifier in approval history and covered enterprise evidence. It also removes matching app-role membership. The approved meaning and evidence remain intact. Personal data written inside a definition or uploaded file is outside this actor-field process.
What this does not mean
The callback reports and replaces catalogued actor references. It does not search term text, finding text, Confluence content, or uploaded files for personal data.
It does not provide complete access, rectification, restriction, portability, or objection workflows. Retention evaluation and expired-object deletion remain backend contracts.
The privacy policy names DailyMind LTD as controller. Evidence preservation does not itself establish a lawful basis for retaining personal data.
Related questions
Next step
Send data-rights requests to privacy@teamkit.dev. Include the affected Atlassian account and the requested right.
View on Atlassian Marketplace