This PR updates the Privacy Policy text in order to match the updated copy/version in the main WRI website, as per task's description.
Notes:
I made a couple quick changes, unrequested, under review by the QA team:
I've noticed WRI's Privacy Policy often mentions other sections, which are linked to the respective section via hash tags. This was not working nor implemented at all in the GFW website; I took the liberty of implementing it (no animations, just making them work. If necessary, we can animate the scroll later on)
Verified that all links have rel="noopener noreferrer"
Some were missing it. noopener ends up being redundant in this context, but as standard practice I've added both anyways.
While going through the Privacy Policy, I noticed it was both pretty much unstyled but also extremely difficult to read. I took the liberty of adding a couple styling tweaks, very basic just to improve spacing and readability, mostly focused on:
Sized of the headers
Spacing of the sections
Spacing of the lists
This doesn't match the ToS, which are also majorly unstyled, waiting from input on the QA team as to whether:
Keep the changes
Possibly improve ToS spacing as well
Revert it (takes a couple minutes)
There are references to the cookie policy, including a link to open the settings, which works on the main WRI website but doesn't apply here. Waiting on input from the QA team on whether to:
Overview
This PR updates the Privacy Policy text in order to match the updated copy/version in the main WRI website, as per task's description.
Notes:
I made a couple quick changes, unrequested, under review by the QA team:
rel="noopener noreferrer"Some were missing it.
noopenerends up being redundant in this context, but as standard practice I've added both anyways.This doesn't match the ToS, which are also majorly unstyled, waiting from input on the QA team as to whether:
Relevant tickets
FLAG-1012