# Updates coming to Marketplace Agreements, Policies and Procedures

**URL:** <https://community.developer.atlassian.com/t/updates-coming-to-marketplace-agreements-policies-and-procedures/24890>\
**Category:** General Discussion\
**Tags:** gdpr, terms\
**Created:** [November 5, 2018, 8:49pm UTC](https://community.developer.atlassian.com/t/updates-coming-to-marketplace-agreements-policies-and-procedures/24890 "2018-11-05T20:49:55Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![akassab](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/akassab/32/40412_2.png) [@akassab](https://community.developer.atlassian.com/u/akassab)\
**Post date:** [November 13, 2018, 11:40am UTC](https://community.developer.atlassian.com/t/updates-coming-to-marketplace-agreements-policies-and-procedures/24890/16 "2018-11-13T11:40:04Z")

</div>

@michal.nykiel - Yes. If you are storing username and user key today then you are storing not safe to store identifiers and will need to indicate Yes.

If user references are the **only** thing you store and you plan to remove username and user key after you’ve migrated your data store to accountID then I’d recommend indicating yes to represent accurately that you are storing not safe to store identifiers, prioritizing the migration to accountID and deletion of username and user key from your data store OVER implementing the personal data reporting API and then once your data store **only** contains accountID updating the field to say “No”.

---

_[View the full topic](https://community.developer.atlassian.com/t/updates-coming-to-marketplace-agreements-policies-and-procedures/24890)._