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

Privacy policy #250

Open
JimKillock opened this issue Mar 27, 2019 · 4 comments
Open

Privacy policy #250

JimKillock opened this issue Mar 27, 2019 · 4 comments
Assignees

Comments

@JimKillock
Copy link
Member

A late but important addition: we need a specific privacy policy that describes how data is used on the site,

@JimKillock JimKillock changed the title Pivacy policy Privacy policy Mar 27, 2019
@JimKillock
Copy link
Member Author

@edjw I've mentioned this to Martha as something she should help with.

@dantheta
Copy link

If a modx resource is created under the same "feed" folder as the others, I can plumb it into the frontend as a CMS page. It just needs to have filetype XML and use the template BlockedContent1x3, similar to the about page (9747)

@edjw
Copy link

edjw commented May 30, 2019

@dantheta – This is in ModX now as resource 10312. I called it 'How Blocked uses data'.

@dantheta
Copy link

I've updated the footer link. The content in the ModX resource has been moved from banner_text to TextAreaOne (so that it appears in the right page region). Hope that's OK!

dantheta added a commit to dantheta/blocked-frontend-py that referenced this issue May 31, 2019
@dantheta dantheta reopened this May 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants