Terms and Conditions and Privacy Policy

Terms and Conditions for using Dou.Git. Please read them and are subject to change.

• Terms
• Privacy

Terms

Effective date: July 10, 2020

Definitions

Short version: We use these basic terms throughout the agreement, and they have specific meanings. You should know what we mean when we use each of the terms. There's not going to be a test on it, but it's still useful information.

An "Account" represents your legal relationship with Dou.Git. A “User Account” represents an individual User’s authorization to log in to and use the Service and serves as a User’s identity on Dou.Git. “Organizations” are shared workspaces that may be associated with a single entity or with one or more Users where multiple Users can collaborate across many projects at once. A User Account can be a member of any number of Organizations. The “Agreement” refers, collectively, to all the terms, conditions, notices contained or referenced in this document (the “Terms of Service” or the "Terms") and all other operating rules, policies (including the Dou.Git Privacy Statement) and procedures that we may publish from time to time on the Website. "Beta Previews" mean software, services, or features identified as alpha, beta, preview, early access, or evaluation, or words or phrases with similar meanings. “Content” refers to content featured or displayed through the Website, including without limitation code, text, data, articles, images, photographs, graphics, software, applications, packages, designs, features, and other materials that are available on the Website or otherwise available through the Service. "Content" also includes Services. “User-Generated Content” is Content, written or otherwise, created or uploaded by our Users. "Your Content" is Content that you create or own. “Dou.Git,” “We,” and “Us” refer to Dou.Git and/or Dou.Bet, a platform or suite of web apps, as well as our affiliates, directors, subsidiaries, contractors, licensors, officers, agents, and employees. The “Service” refers to the applications, software, products, and services provided by Dou.Git, including any Beta Previews. “The User,” “You,” and “Your” refer to the individual person, company, or organization that has visited or is using the Website or Service; that accesses or uses any part of the Account; or that directs the use of the Account in the performance of its functions. A User must be at least 13 years of age. Special terms may apply for business or government Accounts (See Section B(5): Additional Terms). The “Website” refers to Dou.Git’s website located at Dou.Git.com, and all content, services, and products provided by Dou.Git at or through the Website. It also refers to Dou.Git-owned subdomains of Dou.Git.com, such as education.Dou.Git.com and pages.Dou.Git.com. These Terms also govern Dou.Git’s conference websites, such as Dou.Gituniverse.com, and product websites, such as atom.io. Occasionally, websites owned by Dou.Git may provide different or additional terms of service. If those additional terms conflict with this Agreement, the more specific terms apply to the relevant page or service.

Account Terms

Short version: User Accounts and Organizations have different administrative controls; a human must create your Account; you must be 13 or over; you must provide a valid email address; and you may not have more than one free Account. You alone are responsible for your Account and anything that happens while you are signed in to or using your Account. You are responsible for keeping your Account secure.

1. Account Controls Users. Subject to these Terms, you retain ultimate administrative control over your User Account and the Content within it.

Organizations. The "owner" of an Organization that was created under these Terms has ultimate administrative control over that Organization and the Content within it. Within the Service, an owner can manage User access to the Organization’s data and projects. An Organization may have multiple owners, but there must be at least one User Account designated as an owner of an Organization. If you are the owner of an Organization under these Terms, we consider you responsible for the actions that are performed on or through that Organization.

2. Required Information You must provide a valid email address in order to complete the signup process. Any other information requested, such as your real name, is optional, unless you are accepting these terms on behalf of a legal entity (in which case we need more information about the legal entity) or if you opt for a paid Account, in which case additional information will be necessary for billing purposes.

3. Account Requirements We have a few simple rules for User Accounts on Dou.Git's Service.

You must be a human to create an Account. Accounts registered by "bots" or other automated methods are not permitted. We do permit machine accounts: A machine account is an Account set up by an individual human who accepts the Terms on behalf of the Account, provides a valid email address, and is responsible for its actions. A machine account is used exclusively for performing automated tasks. Multiple users may direct the actions of a machine account, but the owner of the Account is ultimately responsible for the machine's actions. You may maintain no more than one free machine account in addition to your free User Account. One person or legal entity may maintain no more than one free Account (if you choose to control a machine account as well, that's fine, but it can only be used for running a machine). You must be age 13 or older. While we are thrilled to see brilliant young coders get excited by learning to program, we must comply with United States law. Dou.Git does not target our Service to children under 13, and we do not permit any Users under 13 on our Service. If we learn of any User under the age of 13, we will terminate that User’s Account immediately. If you are a resident of a country outside the United States, your country’s minimum age may be older; in such a case, you are responsible for complying with your country’s laws. Your login may only be used by one person — i.e., a single login may not be shared by multiple people. A paid Organization may only provide access to as many User Accounts as your subscription allows. You may not use Dou.Git in violation of export control or sanctions laws of the United States or any other applicable jurisdiction. You may not use Dou.Git if you are or are working on behalf of a Specially Designated National (SDN) or a person subject to similar blocking or denied party prohibitions administered by a U.S. government agency. Dou.Git may allow persons in certain sanctioned countries or territories to access certain Dou.Git services pursuant to U.S. government authorizations. For more information, please see our Export Controls policy. 4. User Account Security You are responsible for keeping your Account secure while you use our Service. We offer tools such as two-factor authentication to help you maintain your Account's security, but the content of your Account and its security are up to you.

You are responsible for all content posted and activity that occurs under your Account (even when content is posted by others who have Accounts under your Account). You are responsible for maintaining the security of your Account and password. Dou.Git cannot and will not be liable for any loss or damage from your failure to comply with this security obligation. You will promptly notify Dou.Git if you become aware of any unauthorized use of, or access to, our Service through your Account, including any unauthorized use of your password or Account. 5. Additional Terms In some situations, third parties' terms may apply to your use of Dou.Git. For example, you may be a member of an organization on Dou.Git with its own terms or license agreements; you may download an application that integrates with Dou.Git; or you may use Dou.Git to authenticate to another service. Please be aware that while these Terms are our full agreement with you, other parties' terms govern their relationships with you.

If you are a government User or otherwise accessing or using any Dou.Git Service in a government capacity, this Government Amendment to Dou.Git Terms of Service applies to you, and you agree to its provisions.

If you have signed up for Dou.Git Enterprise Cloud, the Enterprise Cloud Addendum applies to you, and you agree to its provisions.

Acceptable Use

Short version: Dou.Git hosts a wide variety of collaborative projects from all over the world, and that collaboration only works when our users are able to work together in good faith. While using the service, you must follow the terms of this section, which include some restrictions on content you can post, conduct on the service, and other limitations. In short, be excellent to each other.

Your use of the Website and Service must not violate any applicable laws, including copyright or trademark laws, export control or sanctions laws, or other laws in your jurisdiction. You are responsible for making sure that your use of the Service is in compliance with laws and any applicable regulations.

You agree that you will not under any circumstances violate our Acceptable Use Policies or Community Guidelines.

User-Generated Content

Short version: You own content you create, but you allow us certain rights to it, so that we can display and share the content you post. You still have control over your content, and responsibility for it, and the rights you grant us are limited to those we need to provide the service. We have the right to remove content or close Accounts if we need to.

1. Responsibility for User-Generated Content You may create or upload User-Generated Content while using the Service. You are solely responsible for the content of, and for any harm resulting from, any User-Generated Content that you post, upload, link to or otherwise make available via the Service, regardless of the form of that Content. We are not responsible for any public display or misuse of your User-Generated Content.

2. Dou.Git May Remove Content We do not pre-screen User-Generated Content, but we have the right (though not the obligation) to refuse or remove any User-Generated Content that, in our sole discretion, violates any Dou.Git terms or policies.

3. Ownership of Content, Right to Post, and License Grants You retain ownership of and responsibility for Your Content. If you're posting anything you did not create yourself or do not own the rights to, you agree that you are responsible for any Content you post; that you will only submit Content that you have the right to post; and that you will fully comply with any third party licenses relating to Content you post.

Because you retain ownership of and responsibility for Your Content, we need you to grant us — and other Dou.Git Users — certain legal permissions, listed in Sections D.4 — D.7. These license grants apply to Your Content. If you upload Content that already comes with a license granting Dou.Git the permissions we need to run our Service, no additional license is required. You understand that you will not receive any payment for any of the rights granted in Sections D.4 — D.7. The licenses you grant to us will end when you remove Your Content from our servers, unless other Users have forked it.

4. License Grant to Us We need the legal right to do things like host Your Content, publish it, and share it. You grant us and our legal successors the right to store, parse, and display Your Content, and make incidental copies as necessary to render the Website and provide the Service. This includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video.

This license does not grant Dou.Git the right to sell Your Content or otherwise distribute or use it outside of our provision of the Service.

5. License Grant to Other Users 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).

If you set your pages and repositories to be viewed publicly, you grant each User of Dou.Git a nonexclusive, worldwide license to use, display, and perform Your Content through the Dou.Git Service and to reproduce Your Content solely on Dou.Git as permitted through Dou.Git'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 Dou.Git Users.

6. Contributions Under Repository License Whenever you make a contribution to a repository containing notice of a license, you license your contribution under the same terms, and you agree that you have the right to license your contribution under those terms. If you have a separate agreement to license your contributions under different terms, such as a contributor license agreement, that agreement will supersede.

Isn't this just how it works already? Yep. This is widely accepted as the norm in the open-source community; it's commonly referred to by the shorthand "inbound=outbound". We're just making it explicit.

7. Moral Rights 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 us, to enable us to 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 Dou.Git the rights we 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.

Private Repositories

Short version: You may have access to private repositories. We treat the content of private repositories as confidential, and we only access it for support reasons, with your consent, or if required to for security reasons.

1. Control of Private Repositories Some Accounts may have private repositories, which allow the User to control access to Content.

2. Confidentiality of Private Repositories Dou.Git considers the contents of private repositories to be confidential to you. Dou.Git will protect the contents of private repositories from unauthorized use, access, or disclosure in the same manner that we would use to protect our own confidential information of a similar nature and in no event with less than a reasonable degree of care.

3. Access Dou.Git personnel may only access the content of your private repositories in the following situations:

With your consent and knowledge, for support reasons. If Dou.Git accesses a private repository for support reasons, we will only do so with the owner’s consent and knowledge. When access is required for security reasons, including when access is required to maintain ongoing confidentiality, integrity, availability and resilience of Dou.Git's systems and Service. You may choose to enable additional access to your private repositories. For example:

You may enable various Dou.Git services or features that require additional rights to Your Content in private repositories. These rights may vary depending on the service or feature, but Dou.Git will continue to treat your private repository Content as confidential. If those services or features require rights in addition to those we need to provide the Dou.Git Service, we will provide an explanation of those rights. 4. Exclusions If we have reason to believe the contents of a private repository are in violation of the law or of these Terms, we have the right to access, review, and remove them. Additionally, we may be compelled by law to disclose the contents of your private repositories.

Copyright Infringement and DMCA Policy

If you believe that content on our website violates your copyright, please contact us in accordance with our Digital Millennium Copyright Act Policy. If you are a copyright owner and you believe that content on Dou.Git violates your rights, please contact us via our convenient DMCA form or by emailing copyright@Dou.Git.com. There may be legal consequences for sending a false or frivolous takedown notice. Before sending a takedown request, you must consider legal uses such as fair use and licensed uses.

We will terminate the Accounts of repeat infringers of this policy.

Intellectual Property Notice

Short version: We own the service and all of our content. In order for you to use our content, we give you certain rights to it, but you may only use our content in the way we have allowed.

1. Dou.Git's Rights to Content Dou.Git and our licensors, vendors, agents, and/or our content providers retain ownership of all intellectual property rights of any kind related to the Website and Service. We reserve all rights that are not expressly granted to you under this Agreement or by law. The look and feel of the Website and Service is copyright © Dou.Git, Inc. All rights reserved. You may not duplicate, copy, or reuse any portion of the HTML/CSS, Javascript, or visual design elements or concepts without express written permission from Dou.Git.

2. Dou.Git Trademarks and Logos If you’d like to use Dou.Git’s trademarks, you must follow all of our trademark guidelines, including but not limited to all logos that look like: https://git.dou.bet/Dou.Git.png.

3. License to Dou.Git Policies This Agreement is licensed under this Creative Commons Zero license. For details, see our site-policy repository.

API Terms

Short version: You agree to these Terms of Service, plus this Section H, when using any of Dou.Git's APIs (Application Provider Interface), including use of the API through a third party product that accesses Dou.Git.

Abuse or excessively frequent requests to Dou.Git via the API may result in the temporary or permanent suspension of your Account's access to the API. Dou.Git, in our sole discretion, will determine abuse or excessive usage of the API. We will make a reasonable attempt to warn you via email prior to suspension.

You may not share API tokens to exceed Dou.Git's rate limitations.

You may not use the API to download data or Content from Dou.Git for spamming purposes, including for the purposes of selling Dou.Git users' personal information, such as to recruiters, headhunters, and job boards.

All use of the Dou.Git API is subject to these Terms of Service and the Dou.Git Privacy Statement.

Dou.Git may offer subscription-based access to our API for those Users who require high-throughput access or access that would result in resale of Dou.Git's Service.

Privacy Policy

What information Dou.Git collects

"User Personal Information" is any information about one of our Users which could, alone or together with other information, personally identify them or otherwise be reasonably linked or connected with them. Information such as a username and password, an email address, a real name, an Internet protocol (IP) address, and a photograph are examples of “User Personal Information.”

User Personal Information does not include aggregated, non-personally identifying information that does not identify a User or cannot otherwise be reasonably linked or connected with them. We may use such aggregated, non-personally identifying information for research purposes and to operate, analyze, improve, and optimize our Website and Service.

Information users provide directly to Dou.Git

Registration Information

We require some basic information at the time of account creation. When you create your own username and password, we ask you for a valid email address.

Profile Information

You may choose to give us more information for your Account profile, such as your full name, an avatar which may include a photograph, your biography, your location, your company, and a URL to a third-party website. This information may include User Personal Information. Please note that your profile information may be visible to other Users of our Service.

Information Dou.Git automatically collects from your use of the Service

Transactional Information

If you have a paid Account with us, sell an application listed on Dou.Git Marketplace, or raise funds through the Dou.Git Sponsors Program, we automatically collect certain information about your transactions on the Service, such as the date, time, and amount charged.

Usage Information

If you're accessing our Service or Website, we automatically collect the same basic information that most services collect, subject, where necessary, to your consent. This includes information about how you use the Service, such as the pages you view, the referring site, your IP address and session information, and the date and time of each request. This is information we collect from every visitor to the Website, whether they have an Account or not. This information may include User Personal information.

Cookies and Similar Technologies Information

As further described below, and subject, where applicable, to your consent, we automatically collect information from cookies and similar technologies (such as cookie ID and settings) to keep you logged in, to remember your preferences, and to identify you and your device.

Device Information

We may collect certain information about your device, such as its IP address, browser or client application information, language preference, operating system and application version, device type and ID, and device model and manufacturer. This information may include User Personal information.

Information we collect from third parties

Dou.Git may collect User Personal Information from third parties. But none that they are aware of at this moment in time.

What information Dou.Git does not collect

We do not intentionally collect “Sensitive Personal Information”, such as personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person’s sex life or sexual orientation. If you choose to store any Sensitive Personal Information on our servers, you are responsible for complying with any regulatory controls regarding that data.

If you are a child under the age of 13, you may not have an Account on Dou.Git. Dou.Git does not knowingly collect information from or direct any of our content specifically to children under 13. If we learn or have reason to suspect that you are a User who is under the age of 13, we will have to close your Account. We don't want to discourage you from learning to code, but those are the rules. Please see our Terms of Service for information about Account termination. Different countries may have different minimum age limits, and if you are below the minimum age for providing consent for data collection in your country, you may not have an Account on Dou.Git.

We do not intentionally collect User Personal Information that is stored in your repositories or other free-form content inputs. Any personal information within a user's repository is the responsibility of the repository owner.

How Dou.Git uses your information

• We may use your information for the following purposes:
• We use your Registration Information to create your account, and to provide you the Service.
• We use your Payment Information to provide you with the Paid Account service, the Marketplace service, the Sponsors Program, or any other Dou.Git paid service you request.
• We use your User Personal Information, specifically your username, to identify you on Dou.Git.
• We use your Profile Information to fill out your Account profile and to share that profile with other users if you ask us to.
• We use your email address to communicate with you, if you've said that's okay, and only for the reasons you’ve said that’s okay. Please see our section on email communication for more information.
• We use User Personal Information to respond to support requests.
• We use User Personal Information and other data to make recommendations for you, such as to suggest projects you may want to follow or contribute to. We learn from your public behavior on Dou.Git—such as the projects you star—to determine your coding interests, and we recommend similar projects. These recommendations are automated decisions, but they have no legal impact on your rights.
• We may use User Personal Information to invite you to take part in surveys, beta programs, or other research projects, subject, where necessary, to your consent .
• We use Usage Information and Device Information to better understand how our Users use Dou.Git and to improve our Website and Service.
• We may use your User Personal Information if it is necessary for security purposes or to investigate possible fraud or attempts to harm Dou.Git or our Users.
• We may use your User Personal Information to comply with our legal obligations, protect our intellectual property, and enforce our Terms of Service.
• We limit our use of your User Personal Information to the purposes listed in this Privacy Statement. If we need to use your User Personal Information for other purposes, we will ask your permission first. You can always see what information we have, how we're using it, and what permissions you have given us in your user profile.

Our legal bases for processing information

To the extent that our processing of your User Personal Information is subject to certain international laws (including, but not limited to, the European Union's General Data Protection Regulation (GDPR)), Dou.Git is required to notify you about the legal basis on which we process User Personal Information. Dou.Git processes User Personal Information on the following legal bases:

Contract Performance: Dou.Git does not guarantee uptime. But, it is approximately 96.38% over the last 3 years historically speaking. Consent: We rely on your consent to use your User Personal Information under the following circumstances: when you fill out the information in your user profile; when you decide to participate in a Dou.Git training, research project, beta program, or survey; and for marketing purposes, where applicable. All of this User Personal Information is entirely optional, and you have the ability to access, modify, and delete it at any time. While you are not able to delete your email address entirely, you can make it private. You may withdraw your consent at any time. Legitimate Interests: Generally, the remainder of the processing of User Personal Information we perform is necessary for the purposes of our legitimate interest, for example, for legal compliance purposes, security purposes, or to maintain ongoing confidentiality, integrity, availability, and resilience of Dou.Git’s systems, Website, and Service.

How we share the information we collect

Dou.Git only collects information on the user to make the site more user friendly. It will never be sold or mishandled in a mischievous or malicious manner.

Other important information

Repository contents

Dou.Git personnel do not access private repositories unless required to for security purposes, to assist the repository owner with a support matter, to maintain the integrity of the Service, or to comply with our legal obligations. However, while we do not generally search for content in your repositories, we may scan our servers and content to detect certain tokens or security signatures, known active malware, or other content known to violate our Terms, such as violent extremist or terrorist content or child exploitation imagery, based on algorithmic fingerprinting techniques. Our Terms of Service provides more details.

If your repository is public, anyone may view its contents. If you include private, confidential or Sensitive Personal Information, such as email addresses or passwords, in your public repository, that information may be indexed by search engines or used by third parties.

Please see more about User Personal Information in public repositories.

Public information on Dou.Git

Many of Dou.Git services and features are public-facing. If your content is public-facing, third parties may access and use it in compliance with our Terms of Service, such as by viewing your profile or repositories or pulling data via our API. We do not sell that content; it is yours. However, we do allow third parties, such as research organizations or archives, to compile public-facing Dou.Git information. Other third parties, such as data brokers, have been known to scrape Dou.Git and compile data as well.

Your User Personal Information associated with your content could be gathered by third parties in these compilations of Dou.Git data. If you do not want your User Personal Information to appear in third parties’ compilations of Dou.Git data, please do not make your User Personal Information publicly available and be sure to configure your email address to be private in your user profile and in your git commit settings. We currently set Users' email address to private by default, but legacy Dou.Git Users may need to update their settings.

If you would like to compile Dou.Git data, you must comply with our Terms of Service regarding scraping and privacy, and you may only use any public-facing User Personal Information you gather for the purpose for which our user authorized it. For example, where a Dou.Git user has made an email address public-facing for the purpose of identification and attribution, do not use that email address for commercial advertising. We expect you to reasonably secure any User Personal Information you have gathered from Dou.Git, and to respond promptly to complaints, removal requests, and "do not contact" requests from Dou.Git or Dou.Git users.

Similarly, projects on Dou.Git may include publicly available User Personal Information collected as part of the collaborative process. If you have a complaint about any User Personal Information on Dou.Git, please see our section on resolving complaints.

Organizations

You may indicate, through your actions on Dou.Git, that you are willing to share your User Personal Information. If you collaborate on or become a member of an Organization, then its Account owners may receive your User Personal Information. When you accept an invitation to an Organization, you will be notified of the types of information owners may be able to see (for more information, see About Organization Membership). If you accept an invitation to an Organization with a verified domain, then the owners of that Organization will be able to see your full email address(es) within that Organization's verified domain(s).

Please note, Dou.Git may share your username, Usage Information, and Device Information with the owner of the Organization you are a member of, to the extent that your User Personal Information is provided only to investigate or respond to a security incident that affects or compromises the security of that particular Organization.

If you collaborate on or become a member of an Account that has agreed to the Corporate Terms of Service and a Data Protection Addendum (DPA) to this Privacy Statement, then that DPA governs in the event of any conflicts between this Privacy Statement and the DPA with respect to your activity in the Account.

Please contact the Account owners for more information about how they might process your User Personal Information in their Organization and the ways for you to access, update, alter, or delete the User Personal Information stored in the Account.

How you can access and control the information we collect

If you're already a Dou.Git user, you may access, update, alter, or delete your basic user profile information by editing your user profile or contacting Dou.Git Support or Dou.Git Premium Support. You can control the information we collect about you by limiting what information is in your profile, by keeping your information current, or by contacting Dou.Git Support or Dou.Git Premium Support.

If Dou.Git processes information about you, such as information Dou.Git receives from third parties, and you do not have an account, then you may, subject to applicable law, access, update, alter, delete, or object to the processing of your personal information by contacting Dou.Git Support or Dou.Git Premium Support.

Data portability

As a Dou.Git User, you can always take your data with you. You can clone your repositories to your desktop, for example, or you can use our Data Portability tools to download information we have about you.

Data retention and deletion of data

Generally, Dou.Git retains User Personal Information for as long as your account is active or as needed to provide you services.

If you would like to cancel your account or delete your User Personal Information, you may do so in your user profile. We retain and use your information as necessary to comply with our legal obligations, resolve disputes, and enforce our agreements, but barring legal requirements, we will delete your full profile (within reason) within 90 days of your request. You may contact Dou.Git Support or Dou.Git Premium Support to request the erasure of the data we process on the basis of consent within 30 days.

After an account has been deleted, certain data, such as contributions to other Users' repositories and comments in others' issues, will remain. However, we will delete or de-identify your User Personal Information, including your username and email address, from the author field of issues, pull requests, and comments by associating them with a ghost user.

That said, the email address you have supplied via your Git commit settings will always be associated with your commits in the Git system. If you choose to make your email address private, you should also update your Git commit settings. We are unable to change or delete data in the Git commit history — the Git software is designed to maintain a record — but we do enable you to control what information you put in that record.

Our use of cookies and tracking

Cookies

Dou.Git uses cookies to make interactions with our service easy and meaningful. Cookies are small text files that websites often store on computer hard drives or mobile devices of visitors. We use cookies (and similar technologies, like HTML5 localStorage) to keep you logged in, remember your preferences, and provide information for future development of Dou.Git. For security purposes, we use cookies to identify a device. By using our Website, you agree that we can place these types of cookies on your computer or device. If you disable your browser or device’s ability to accept these cookies, you will not be able to log in or use Dou.Git’s services.

We provide a web page on cookies and tracking that describes the cookies we set, the needs we have for those cookies, and the types of cookies they are (temporary or permanent). It also lists our third-party analytics providers and other service providers, and details exactly which parts of our Website we permit them to track.

Tracking and analytics

We use Matamo to help us evaluate our Users' use of Dou.Git, compile statistical reports on activity, and improve our content and Website performance. We only use these third-party analytics providers on certain areas of our Website.

Some browsers have incorporated "Do Not Track" (DNT) features that can send a signal to the websites you visit indicating you do not wish to be tracked. Dou.Git responds to browser DNT signals and follows the W3C standard for responding to DNT signals. If you have not enabled DNT on a browser that supports it, cookies on some parts of our Website will track your online browsing activity on other online services over time, though we do not permit third parties other than our analytics and service providers to track Dou.Git Users' activity over time on Dou.Git.

How Dou.Git secures your information

Dou.Git takes all measures reasonably necessary to protect User Personal Information from unauthorized access, alteration, or destruction; maintain data accuracy; and help ensure the appropriate use of User Personal Information.

Dou.Git enforces a written security information program. Our program:

• aligns with industry recognized frameworks;
• includes security safeguards reasonably designed to protect the confidentiality, integrity, availability, and resilience of our Users' data;
• is appropriate to the nature, size, and complexity of Dou.Git’s business operations;
• includes incident response and data breach notification processes; and
• complies with applicable information security-related laws and regulations in the geographic regions where Dou.Git does business. In the event of a data breach that affects your User Personal Information, we will act promptly to mitigate the impact of a breach and notify any affected Users without undue delay.

Transmission of data on Dou.Git is encrypted using SSH, HTTPS (TLS), and git repository content is encrypted at rest. We manage our own cages and racks at top-tier data centers with high level of physical and network security, and when data is stored with a third-party storage provider, it is encrypted.

No method of transmission, or method of electronic storage, is 100% secure. Therefore, we cannot guarantee its absolute security. For more information, see our security disclosures.

Dou.Git's global privacy practices

We store and process the information that we collect in the United States in accordance with this Privacy Statement though our service providers may store and process data outside the United States. However, we understand that we have Users from different countries and regions with different privacy expectations, and we try to meet those needs even when the United States does not have the same privacy framework as other countries.

We provide a high standard of privacy protection—as described in this Privacy Statement—to all our users around the world, regardless of their country of origin or location, and we are proud of the levels of notice, choice, accountability, security, data integrity, access, and recourse we provide. We work hard to comply with the applicable data privacy laws wherever we do business, working with our Data Protection Officer as part of a cross-functional team that oversees our privacy compliance efforts. Additionally, if our vendors or affiliates have access to User Personal Information, they must sign agreements that require them to comply with our privacy policies and with applicable data privacy laws.

In particular:

• Dou.Git provides clear methods of unambiguous, informed, specific, and freely given consent at the time of data collection, when we collect your User Personal Information using consent as a basis.
• We collect only the minimum amount of User Personal Information necessary for our purposes, unless you choose to provide more. We encourage you to only give us the amount of data you are comfortable sharing.
• We offer you simple methods of accessing, altering, or deleting the User Personal Information we have collected, where legally permitted.
• We provide our Users notice, choice, accountability, security, and access regarding their User Personal Information, and we limit the purpose for processing it. We also provide our Users a method of recourse and enforcement. These are the Privacy Shield Principles, but they are also just good practices.

How we communicate with you

We use your email address to communicate with you, if you've said that's okay, and only for the reasons you’ve said that’s okay. For example, if you contact our Support team with a request, we respond to you via email. You have a lot of control over how your email address is used and shared on and through Dou.Git. You may manage your communication preferences in your user profile.

By design, the Git version control system associates many actions with a User's email address, such as commit messages. We are not able to change many aspects of the Git system. If you would like your email address to remain private, even when you’re commenting on public repositories, you can create a private email address in your user profile. You should also update your local Git configuration to use your private email address. This will not change how we contact you, but it will affect how others see you. We set current Users' email address private by default, but legacy Dou.Git Users may need to update their settings. Please see more about email addresses in commit messages here.

Depending on your email settings, Dou.Git may occasionally send notification emails about changes in a repository you’re watching, new features, requests for feedback, important policy changes, or to offer customer support. We also send marketing emails, based on your choices and in accordance with applicable laws and regulations. There's an “unsubscribe” link located at the bottom of each of the marketing emails we send you. Please note that you cannot opt out of receiving important communications from us, such as emails from our Support team or system emails, but you can configure your notifications settings in your profile to opt out of other communications.

Our emails may contain a pixel tag, which is a small, clear image that can tell us whether or not you have opened an email and what your IP address is. We use this pixel tag to make our email more effective for you and to make sure we’re not sending you unwanted email.

Changes to our Privacy Statement

Although most changes are likely to be minor, Dou.Git may change our Privacy Statement from time to time. We encourage Users to check our Site Policy repository frequently.