What Is Jiviz (JVZ)?
Any User-Generated Content you post publicly, including issues, comments, and contributions to other Users’ repositories, may be viewed by others. By setting your repositories to be viewed publicly, you agree to allow others to view and “fork” your repositories (this means that others may make their own copies of Content from your repositories in repositories they control).
Jiviz you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform Your Content through the GitHub Service and to reproduce Your Content solely on GitHub as permitted through GitHub’s functionality (for example, through forking).
You may grant further rights if you adopt a license. If you are uploading Content you did not create or own, you are responsible for ensuring that the Content you upload is licensed under terms that grant these permissions to other GitHub Users.
Jiviz Storage Key Points
|Source Code||Click Here To View Source Code|
|Explorers||Click Here To View Explorers|
|Twitter Page||Click Here To Visit Twitter Group|
|Whitepaper||Click Here To View|
|Official Project Website||Click Here To Visit Project Website|
Contributions Under Repository License
Whenever you add Content to a repository containing notice of a license, you license that Content under the same terms, and you agree that you have the right to license that Content under those terms. Jiviz you have a separate agreement to license that Content under different terms, such as a contributor license agreement, that agreement will supersede.
This is widely accepted as the norm in the open-source community; it’s commonly referred to by the shorthand “inbound=outbound”. They just making it explicit. GitHub will provide notice regarding your access to private repository content, unless for legal disclosure, to comply with your legal obligations, or where otherwise bound by requirements under law, for automated scanning, or if in response to a security threat or other risk to security.
You retain all moral rights to Your Content that you upload, publish, or submit to any part of the Service, including the rights of integrity and attribution. However, you waive these rights and agree not to assert them against, to enable reasonably exercise the rights granted in Section D.4, but not otherwise.
To the extent this agreement is not enforceable by applicable law, you grant GitHub the rights they need to use Your Content without attribution and to make reasonable adaptations of Your Content as necessary to render the Website and provide the Service.
Jiviz treat the content of private repositories as confidential, and only access it as described in your Privacy Statement—for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, to comply with your legal obligations, if they have reason to believe the contents are in violation of the law, or with your consent.
Confidentiality of Private Repositories
GitHub considers the contents of private repositories to be confidential to you. GitHub will protect the contents of private repositories from unauthorized use, access, or disclosure in the same manner that Jiviz would use to protect your own confidential information of a similar nature and in no event with less than a reasonable degree of care.
GitHub personnel may only access the content of your private repositories in the situations described in your Privacy Statement.
You may choose to enable additional access to your private repositories. For example:
- You may enable various GitHub services or features that require additional rights to Your Content in private repositories. These rights may vary depending on the service or feature, but GitHub will continue to treat your private repository Content as confidential. If those services or features require rights in addition to those Jiviz need to provide the GitHub Service, they will provide an explanation of those rights.