mirror of
https://github.com/privacyguides/privacyguides.org.git
synced 2024-12-20 21:34:34 -05:00
32 lines
1.8 KiB
Markdown
32 lines
1.8 KiB
Markdown
|
|
|
|
<!-- SCROLL TO BOTTOM TO AGREE!:
|
|
Please use a descriptive title for your PR, it will be included in our changelog!
|
|
|
|
Please share with us what you've changed.
|
|
If you are adding a software recommendation, give us a link to its website or
|
|
source code.
|
|
|
|
If you are making changes that you have a conflict of interest with, please
|
|
disclose this as well (this does not disqualify your PR by any means):
|
|
|
|
Conflict of interest contributions involve contributing about yourself,
|
|
family, friends, clients, employers, or your financial and other relationships.
|
|
Any external relationship can trigger a conflict of interest.
|
|
|
|
That someone has a conflict of interest is a description of a situation,
|
|
NOT a judgement about that person's opinions, integrity, or good faith.
|
|
|
|
If you have a conflict of interest, you MUST disclose who is paying you for
|
|
this contribution, who the client is (if for example, you are being paid by
|
|
an advertising agency), and any other relevant affiliations.
|
|
-->
|
|
|
|
<!-- Place an x in the boxes below, like: [x] -->
|
|
- [ ] Please check this box to confirm you have disclosed any relevant conflicts of interest in your post.
|
|
- [ ] Please check this box to confirm your agreement to publish your work under the [Creative Commons Attribution-NoDerivatives 4.0 International](https://github.com/privacyguides/privacyguides.org/blob/main/LICENSE) license, and to grant Privacy Guides a perpetual, worldwide, non-exclusive, transferable, royalty-free, irrevocable license with the right to sublicense such rights through multiple tiers of sublicensees, to reproduce, modify, display, perform and distribute your contribution as part of our project.
|
|
|
|
<!-- What's this? When you submit a PR, you keep the Copyright for the work you
|
|
are contributing. We need you to agree to the above terms in order for us to
|
|
publish this contribution to our website. -->
|