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

Introduce support for Privacy Policy #2145

fpietrosanti opened this issue Jan 3, 2018 · 2 comments

Introduce support for Privacy Policy #2145

fpietrosanti opened this issue Jan 3, 2018 · 2 comments


Copy link

Current behavior
Any website, especially those managing confidential information such as whistleblowing sites, must have a clearly documented privacy policy in order to comply with data protection law and regulations.

Expected behavior
This ticket is to introduce support for Privacy Policy in GlobaLeaks.
The software should provide the ability to:

  • Either up-load a pdf as a privacy policy document
  • Either to copy-paste in a textbox the privacy policy

The Privacy Policy must be visible from within the footer from #2144 only when juridical ownership information are defined #2143 .

The admin interface should provide a section to enable/display/configure the privacy policy.

The Privacy Policy document text support a variable to describe the ${DATARETENTION} configured value, that can be re-used within the policy document.

It should be possible to configure the Privacy Policy to be a warning that the whistleblower must accept before proceeding.

Copy link
Contributor Author

Also required for EAT project accordingly to the GDPR compliance requirement defined as per:
"Furthermore, the Policy should be published in all the pages of the Website with the
Whistleblowing Mailbox; usually a link to the Policy is published at the bottom of every page of
the Website."

@evilaliv3 evilaliv3 removed the X: EAT label Feb 7, 2023
Copy link

Deprecated by:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

2 participants