Update Instagram 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 in the history file. To get that date, you can use the following method. In all cases where a date is to be obtained from the GitHub user interface, you can obtain the exact datetime by hovering your cursor over the date or using the developer tools to copy its datetime attribute.
  1. Find the date at which the problem was first encountered:
  • If there is one, find the first date at which an issue was opened claiming that the terms can not be tracked anymore.
  • If there is no issue, or if the version is wrong even though the terms can be extracted, find the first version with wrong data and obtain its date.
  • If the document can not be fetched anymore, find the latest snapshot.
  2. Find the most recent snapshot that is strictly anterior to this date from the snapshots database.
  3. Set the creation date of this snapshot as the validUntil date in the history file.

---

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 undefined, which enables graphical declaration of documents. You can load it on your local instance if you have one set up.

[varjas]

The selectors for this page are no longer semantic and may not be stable over time. I noticed this particular page does not display all of the policy information either, because many elements need to be clicked on to display the full details.

There is a link to a separate printable version of this policy here, that may be easier to parse and capture all details of the policy. However, it is not on the instagram.com domain and I'm not sure how this is usually handled, as Instagram is owned by Meta. Should this version be used in this scenario?

[Cli4d]

Hi @varjas

Thank you for making this contribution. I agree most of the selector options are not semantic and just generic alphanumeric ones. For now we can just use it for now as there is no better option
Regarding the click sections, I have looked at the generated version and it appears these sections appear linked to the markdown. The alternative link provided is a good one, however are we sure that updates appear simultaneously to both sites given the alternative link is not directly tied to their domain?

For a start I can merge this contribution and we can have a conversation regarding the best way of capturing all the content in the Privacy policy.

Thank you so much for making this contribution and I will proceed to merge it.

[MattiSG]

You can also have a look to how the PGA team tracks Instagram terms: https://github.com/OpenTermsArchive/pga-declarations/blob/main/declarations/Instagram.json 🙂