Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update policies for better GDPR compliance #80

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Conversation

tomtom5152
Copy link
Member

@tomtom5152 tomtom5152 commented May 28, 2018

Provide a Monzo inspired privacy and cookie policy to brings is more in line with GDPR.

Required some reworking of the footer to add the links and make it still look decent.

Privacy has a reading ease score of 61.8, cookies 67, SU's privacy policy comes in at 42.9 (higher is easier to read).

Request for comments and proof reading please.

Also updates versions of things to the latest stable version.

Hugo 0.41 includes new privacy tools to help with GDPR compliance.
Update the footer to reflect these changes.

Update the TOC to support lots of sub headings.
@tomtom5152
Copy link
Member Author

Travis will fail until documents are marked as not draft, will wait for proofreading before doing that to prevent accidental merging.

@tomtom5152
Copy link
Member Author

Looks like I actually did this once upon a time, care to review @FreneticScribbler?

@FreneticScribbler
Copy link
Member

Yeah can do at some point :D

Copy link
Member

@FreneticScribbler FreneticScribbler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other than that minor phrasing point looks pretty damn good to me.

It's not quite as reader friendly as the Hire T&Cs but its still way better than most. Would it be worth having separate client and member facing policies?

@tomtom5152
Copy link
Member Author

This was done a lot earlier and I've had a lot more practice at this type of writing since then. I also think I wasn't quite as brutal with outright rewriting it back then, tring to fit it into the existing document. Full GDPR is another issue entirely though, the website was never non compliant.

@FreneticScribbler
Copy link
Member

Might be worth you reviewing it yourself if you have time then?

"never non compliant" ?

Also yeah, that RIGS GDPR thing didn't get done did it?

FreneticScribbler added a commit that referenced this pull request Jun 18, 2020
This supersedes and closes #80. It's better than what we had before, even if it does want reworking again.

# Conflicts:
#	Gemfile.lock
#	layouts/partials/footer.html
@davidtaylorhq davidtaylorhq removed their request for review January 12, 2023 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants