The current page showing data residency can be confusing (see screenshot) and cause unnecessary concern for customers. In the screenshot the location is 'Europe PINNED' but the AWS region includes 'US East...'.
 
It's not explicitly obvious as to why there is an aws-region outside of the requested location.

As I understand it, the in-scope data is pinned to Europe but the out-of-scope data results in the US AWS region appearing. Explaining this distinction would help to remove any concerns/confusion/negative conversations and also reduce the number support incidents requesting clarification.
 
It would be great for the user interface to separate the in-scope and out-of-scope data, so that: * It is possible to see that the in-scope data is pinned to the requested location along with the associated aws regions for that location.

• It is possible to see that the out-of-scope data resides in <location> along with the associated aws regions for that location

Include a direct link to https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/#Managedataresidency-In-scopeproductdata to explain In-scope data would also be helpful.