Questions re: handling data erasure / user privacy concerns


I’m currently implementing a trigger to detect when user accounts are updated or closed, then update or delete user-personal data as appropriate within “my” Forge app’s boundaries, in accordance with

When a given Atlassian user account exercises Right to Be Forgotten, then the personal data reporting API will indicate that the account is closed, so that my app can erase its copy of their data. Does the same thing occur if an account is deactivated (e.g., they left the company they worked for), or if a given Atlassian customer uninstalls “my” app from their site? If not, then what does my app need to do to handle those scenarios?




bump @Atlassian-Staff