Update npm Public Registry Privacy Policy

[OTA-Bot]

🔎 Inspect this declaration update suggestion

Bots should take care of checking the formatting and the validity of the declaration. As a human reviewer, you should check:

• Selectors are:
  • stable: as much as possible, the CSS selectors are meaningful and specific (e.g. .tos-content rather than .ab23 .cK_drop > div).
  • simple: the CSS selectors do not have unnecessary specificity (e.g. if there is an ID, do not add a class or a tag).
• Generated version is:
  • relevant: it is not just a series of links, for example.
  • readable: it is complete and not mangled.
  • clean: it does not contain navigation links, unnecessary images, or extra content.
• validUntil date is correctly input:
  • Check the latest versions
  • Find the first occurence of the problematic change
  • Note the creation date of this issue (inspect x days ago with developer tools and copy datetime)
  • Find the latest snapshot from the list of snapshots strictly anterior to this date
  • Copy the creation date of this snapshot (inspect x days ago with developer tools and copy datetime)
  • Replace the to-be-determined date in history file directly from GitHub or check out branch update_npm_public_registry_privacy_policy and do so on your local

---

Thanks to your work and attention, Open Terms Archive will ensure that high quality data is available for all reusers, enabling them to do their part in shifting the balance of power towards end users and regulators instead of spending time collecting and cleaning documents 💪

---

This update suggestion has been created through the Contribution Tool, which enables graphical declaration of documents. You can load it on your local instance if you have one set up.

[MattiSG]

Please make sure that the content is complete before asking for a review 😉 the date is “to be determined”