add Terms of Use & Privacy Policy legal pages #6
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
Alexandra-Haynes
changed the title
|
In the Privacy Policy, there's a typo at the beginning of the line: TIf you have any questions or concerns about our Privacy Policy, please contact us at info@codeforhawaii.org. |
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.
Added two pages: terms-of-use & privacy-policy, with the necessary content, and a Back Home button.
The links for these pages are located in the footer.
These two pages were not present on the former (currently active) website, so I did some research and put this together.
As I am not a legal expert, the content might need to be reviewed and customized if we have specific requirements and it is always recommended to seek legal advice to ensure compliance with the laws applicable to HI jurisdiction. But till then, I think that these policies cover us.
The pages look like this:
and they are responsive.
Also, made mirror modifications to the Footer component, just style-related.