Data Egress

All of the scanning of your data happens within the confines of Atlassian's infrastructure. That is also where the list of findings is stored. In an ideal world, there would be a technical guarantee that no data ever leaves your instance. However, we understand the importance of being able to integrate with third party system or to notify stakeholders about any findings and potential issues. So, we've chosen a balanced approach.

PII Protection allows for limited egress permissions. This means that while your data is securely within your Atlassian Cloud instance, there is still a defined pathway for it to leave, allowing you to receive notifications and build integrations. Namely, we allow connections to Automation for Jira so that you can create custom integrations that cater to your specific needs and preferences.

Domain	Description
automation.atlassian.com	Allows PII Protection to trigger Automation for Jira/Confluence webhooks.
api.media.atlassian.com	Allows PII Protection to read attachments.

As you can see, we are only allowing connections to the Atlassian Cloud infrastructure and not to anywhere else. This is a deliberate choice to ensure that you can trust PII Protection with your data. It also means that, for any data to leave your instance you would need to make a deliberate choice to trigger an Automation webhook.

If you have any further questions or concerns about data egress or any other aspect of our app, don't hesitate to reach out to us. We're always here to help!