Hi @ademoss and @JuliaWester - We want to provide a bit more context for you to explain where we’re coming from re: helping you define data types. Hopefully this clarifies things a bit.
We designed the new tab to provide answers to the questions our customers most commonly want to understand about their apps.
One almost universal concern we hear from our customers is about what apps are doing with their data - for example, is it being sent outside of the Atlassian apps and infrastructure they’ve already evaluated for further processing and/or storage?
This concern is broader than just what you might think of as “personal data” - for instance, a company might use Confluence to store financial data, roadmap plans, legal advice or other information that may be extremely sensitive, even if it doesn’t include any personally identifiable information.
That’s why we use a broad definition for “End-User Data” that encompasses any data, content or information of an end user that is accessed, collected or otherwise processed by you or your app rather than a narrower or more limited definition that would still leave our customers with questions about what might be happening with their data.
@ademoss - we’d love to be able to give you and other partners specific and personalized guidance. The problem is not that Atlassian can’t be bothered to do so, it’s that as a matter of legal ethics our lawyers can’t offer legal advice about how you should interpret the defined terms that come from the contracts you’ve signed with Atlassian.
Fortunately, from the example in your post it sounds like you have already arrived at an understanding of “End-User Data,” but we’d be happy to hear any feedback if there’s something specific in the definition that still seems ambiguous.
Understanding that this definition is quite broad, we also give you the opportunity in the questionnaire to specifically list the End-User Data types that your app processes and/or stores, so you can give customers the full visibility that they often request, and share in detail your interpretation of “End-User Data.”