Update Chayn 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.

---

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 💪

Fixes #1551

---

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

[Cli4d]

Hi @MattiSG,

Thank you for your contribution in updating the privacy policy. I have reviewed the changes, and everything looks good. However, I noticed that in the checked version, the two elements marked as insignificant do not seem to be excluded. I'm not sure why this is happening, as I have tried various methods to remove them, but they persist.

That said, these issues are minor, so I will approve the pull request and merge it to resume the tracking of this contractual document.