feat: add privacy policy #3694
Merged
feat: add privacy policy #3694
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@xx13 @zvenigorodskaia if you have an idea of better placement - I'm happy to hear. |
asvae
force-pushed
the
feat/privacy-policy
branch
from
b1dcc5a to
d858d65
Compare
|
Maksim says it's ok. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #3601
I chose a very simple approach to privacy policy - just add links to headers.
There are ways to improve it (add consent banner etc), but other ui solutions don't do it. It will also be harmful for user experience.
Links lead to iubenda - a site where said policies for each tool used (analytics, cdn etc) are being regularly updated, so we won't need to follow these up on our own.