Merged into document 152 by user 6

<p> <strong>1. Repositories.</strong> Data that you upload to Bitbucket Cloud are stored in “repositories.” You designate whether the repositories are public (meaning that anyone coming to the Bitbucket website can view them) or private (meaning that access to those repositories will be limited to those who have permission to access the repositories). For each public repository that you maintain, you must indicate the license under which you are making the contents of the repository available to others, as well as the license under which you will accept contributions to your repository.</p> <p> <strong>2. Storage Rules.</strong> The Bitbucket Cloud documentation sets forth pre-defined storage limits on Your Data in Bitbucket Cloud. We enforce those parameters to ensure that you do not use Bitbucket Cloud in a way that consumes a disproportionate amount of system resources (CPU’s, memory, disk space, bandwidth, etc.) or that would adversely impact the performance or operation of Bitbucket Cloud for other Bitbucket Cloud users. Similarly, since Bitbucket Cloud is designed to be used as a source code repository, we reserve the right to remove any other content (such as music or video), particularly if the content is consuming a disproportionate amount of storage. Please note that, since we do not maintain access to your repositories, any removal of Your Data under Section 5.5 (Removals and Suspension) of the Agreement means removal of the entire repository in which the offending data resides, not just the offending portions.</p> <p> <strong>3. Accessing Repositories.</strong> If you are accessing code in someone else’s repository, you should carefully read all the licenses applicable to that repository before using or contributing any code. YOU ACKNOWLEDGE THAT ALL CODE MADE AVAILABLE THROUGH BITBUCKET CLOUD IS THE RESPONSIBILITY OF THE ACCOUNT OWNER CONTROLLING THE PARTICULAR REPOSITORY. WE ARE NOT THE LICENSOR OF ANY THIRD PARTY CODE MADE AVAILABLE THROUGH BITBUCKET CLOUD AND TAKE NO RESPONSIBILITY FOR SUCH CODE.</p> <p> <strong>4. Granting Permissions. </strong>Be careful about granting permissions to your repositories. Once you grant such permissions, we will not be able to prevent those users from taking the actions allowed under those permissions, even if you don’t approve of those actions. Be especially careful about granting administrative access to your repositories, as some of those actions may be irreversible. For example, if you grant someone permission that allows them to move content in your repository to another account, we will not be able to reach into that other user’s account without their permission to recover the data, as we are not in a position to arbitrate disputes among our users. In that case, your only recourse may be requesting a takedown under our policy regarding Reporting Copyright and Trademark Violations or pursuing legal action against the other user directly.</p>

On 2020-12-14 15:54:55 UTC, michielbdejong Staff wrote:

Moving from service_id 293 to 576 due to service merge

On 2020-12-14 15:56:18 UTC, michielbdejong Staff wrote:

Merged this document into document 152