sumanmal51509-svg

# GitHub Terms of Service <!-- markdownlint-disable search-replace --> Thank you for using GitHub! We're happy you're here. Please read this Terms of Service agreement carefully before accessing or using GitHub. Because it is such an important contract between us and our users , we have tried to make it as clear as possible. For your convenience , we have presented these terms in a short non-binding summary followed by the full legal terms. ## Summary | Section | What can you find there? | | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | [A. Definitions](#a-definitions) | Some basic terms , defined in a way that will help you understand this agreement. Refer back up to this section for clarification. | | [B. Account Terms](#b-account-terms) | These are the basic requirements of having an Account on GitHub. | | [C. Acceptable Use](#c-acceptable-use) | These are the basic rules you must follow when using your GitHub Account. | | [D. User-Generated Content](#d-user-generated-content) | You own the content you post on GitHub. However , you have some responsibilities regarding it , and we ask you to grant us some rights so we can provide services to you. | | [E. Private Repositories](#e-private-repositories) | This section talks about how GitHub will treat content you post in private repositories. | | [F. Copyright & DMCA Policy](#f-copyright-infringement-and-dmca-policy) | This section talks about how GitHub will respond if you believe someone is infringing your copyrights on GitHub. | | [G. Intellectual Property Notice](#g-intellectual-property-notice) | This describes GitHub's rights in the website and service. | | [H. API Terms](#h-api-terms) | These are the rules for using GitHub's APIs , whether you are using the API for development or data collection. | | [I. Additional Product Terms](#i-github-additional-product-terms) | We have a few specific rules for GitHub's features and products. | | [J. AI Features , Training , and Your Data](#j-ai-features-training-and-your-data) | These are the terms that apply to GitHub Copilot and other AI features , including how your data may be used for development and improvement of the artificial intelligence and machine learning models , and the controls available to you. | | [K. Beta Previews](#k-beta-previews) | These are some of the additional terms that apply to GitHub's features that are still in development. | | [L. Payment](#l-payment) | You are responsible for payment. We are responsible for billing you accurately. | | [M. Cancellation and Termination](#m-cancellation-and-termination) | You may cancel this agreement and close your Account at any time. | | [N. Communications with GitHub](#n-communications-with-github) | We only use email and other electronic means to stay in touch with our users. We do not provide phone support. | | [O. Disclaimer of Warranties](#o-disclaimer-of-warranties) | We provide our service as is , and we make no promises or guarantees about this service. **Please read this section carefully; you should understand what to expect.** | | [P. Limitation of Liability](#p-limitation-of-liability) | We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. **Please read this section carefully; it limits our obligations to you.** | | [Q. Release and Indemnification](#q-release-and-indemnification) | You are fully responsible for your use of the service. | | [R. Changes to these Terms of Service](#r-changes-to-these-terms) | We may modify this agreement , but we will give you 30 days' notice of material changes. | | [S. Miscellaneous](#s-miscellaneous) | Please see this section for legal details including our choice of law. | ## The GitHub Terms of Service Effective date: April 27 , 2026 ## A. 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.* 1. An "Account" represents your legal relationship with GitHub. A “Personal Account” represents an individual User’s authorization to log in to and use the Service and serves as a User’s identity on GitHub. “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 Personal Account can be a member of any number of Organizations. 2. 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 GitHub Privacy Statement , available at [github.com/site/privacy](https://github.com/site/privacy)) and procedures that we may publish from time to time on the Website. Most of our site policies are available at [docs.github.com/categories/site-policy](/en/site-policy). 3. "AI Feature" means any feature of GitHub or our Affiliates that uses machine learning or artificial intelligence to generate Output , including GitHub Copilot , Copilot Autofix , and any other feature identified as using machine learning or artificial intelligence in our documentation. 4. “Affiliate” means any entity that directly or indirectly controls , is controlled by , or is under common control with a party , where "control" means having more than fifty percent (50%) ownership or the right to direct the management of the entity. For the avoidance of doubt , Microsoft is an Affiliate of GitHub. 5. "Beta Previews" mean software , services , or features identified as alpha , beta , preview , early access , or evaluation , or words or phrases with similar meanings. 6. "Content" means code , text , data , documentation , images , graphics , software , packages , and other materials made available through the Service. 7. “GitHub , ” “We , ” and “Us” refer to GitHub , Inc. , as well as our directors , subsidiaries , contractors , licensors , officers , agents , and employees. 8. “Input” means any content or context provided to an AI Feature , including prompts , attachments , code in your workspace , and conversation history. 9. "Output" means responses and suggestions , including code or other material , generated by an AI Feature. 10. The “Service” refers to the applications , software , products , and services provided by GitHub , including through the Website and any Beta Previews. 11. “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](#5-additional-terms)). 12. "User-Generated Content" means Content that you or other users upload , submit , or create through the Service. 13. The “Website” refers to GitHub’s website located at [github.com](https://github.com/) , and all content , services , and products provided by GitHub at or through the Website. It also refers to GitHub-owned subdomains of github.com , such as [education.github.com](https://education.github.com/) and [pages.github.com](https://pages.github.com/). These Terms also govern GitHub’s conference websites , such as [githubuniverse.com](https://githubuniverse.com/) , and product websites , such as [electronjs.org](https://www.electronjs.org/). Occasionally , websites owned by GitHub 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. 14. "Your Content" means User-Generated Content that you upload , submit , or create , including your modifications to Content you have forked or cloned. It does not include the underlying Content created by others. ## B. Account Terms **Short version:** *Personal 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 Personal 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 Personal 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](#l-payment) , in which case additional information will be necessary for billing purposes. ### 3. Account Requirements We have a few simple rules for Accounts on GitHub'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 Personal 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. GitHub 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](#m-cancellation-and-termination). 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 Personal Accounts as your subscription allows. * You may not use GitHub in violation of export control or sanctions laws of the United States or any other applicable jurisdiction. You may not use GitHub if you are or are working on behalf of a [Specially Designated National (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) or a person subject to similar blocking or denied party prohibitions administered by a U.S. government agency. GitHub may allow persons in certain sanctioned countries or territories to access certain GitHub services pursuant to U.S. government authorizations. For more information , please see our [Export Controls policy](/en/site-policy/other-site-policies/github-and-trade-controls). ### 4. 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. GitHub cannot and will not be liable for any loss or damage from your failure to comply with this security obligation. * You will promptly notify GitHub by contacting us through the [GitHub Support portal](https://support.github.com/) 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 GitHub. For example , you may be a member of an organization on GitHub with its own terms or license agreements; you may download an application that integrates with GitHub; or you may use GitHub 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 GitHub Service in a government capacity , this [Government Amendment to GitHub Terms of Service](/en/site-policy/site-policy-deprecated/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users) applies to you , and you agree to its provisions. If you have signed up for GitHub Enterprise Cloud , the [Enterprise Cloud Addendum](/en/site-policy/site-policy-deprecated/github-enterprise-service-level-agreement) applies to you , and you agree to its provisions. ## C. Acceptable Use **Short version:** *GitHub 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](/en/site-policy/acceptable-use-policies/github-acceptable-use-policies) or [Community Guidelines](/en/site-policy/github-terms/github-community-guidelines). ## D. 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 are responsible for Your Content and any harm resulting from it. This includes Content you post , upload , or make available through the Service. We are not responsible for any public display or misuse of Your Content. ### 2. GitHub May Remove Content We may refuse or remove User-Generated Content that violates applicable law or our terms and policies. We access private repositories only as described in Section E. Content displayed on GitHub Mobile may be subject to app store terms. ### 3. Ownership and License Grants You own Your Content. If you post Content you did not create , you are responsible for ensuring you have the right to post it and for complying with any applicable licenses. You grant us and other Users the licenses in Sections D.4–D.8. These licenses apply to Your Content. If Your Content already includes a license granting us the permissions we need , no additional license is required. You will not receive payment for these rights. These licenses end when you remove Your Content , unless other Users have forked it. ### 4. License Grant to Us You grant GitHub and our Affiliates the right to store , host , archive , parse , display , and make copies of Your Content as necessary to provide , develop , and improve the Service , including by training AI Features , and for the purpose of training , developing , and improving artificial intelligence and machine learning models and technologies of our Affiliates. This license 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. For the avoidance of doubt , use of Your Content to develop , train , and improve artificial intelligence and machine learning models and technologies of GitHub and our Affiliates is within the scope of this license and does not constitute a sale or other restricted transfer of Your Content. ### 5. License Grant to Other Users Your Content that 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 within the Service in repositories they control). By making a repository public , you grant other Users a nonexclusive , worldwide license to use , display , perform and reproduce (by forking) Your Content through the Service as permitted by GitHub's functionality. You may grant additional rights by [adopting a license](/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository#including-an-open-source-license-in-your-repository). If you post Content you did not create or own , you are responsible for ensuring it is licensed under terms that permit these uses. ### 6. 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. If you have a separate agreement to license that Content 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 or our Affiliates , to enable GitHub and our Affiliates 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 GitHub 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. ### 8. Public Repositories and Lawful Access By choosing to contribute Content to a public repository , you are choosing to and directing us to make such Content accessible to everyone on the internet. Unless specifically set forth herein , these Terms do not restrict lawful access to or use of the contents of public repositories by third parties , or by GitHub or its Affiliates. ### 9. Access Reciprocity By using automated means to access , collect , or otherwise use (“Access”) any publicly accessible Content from the Service for the purpose of developing or training any commercially available artificial intelligence model , machine learning system , or similar technology (a "Commercial AI System") , you hereby waive any and all policies , terms , conditions , or contractual provisions governing products , services , websites or datasets you own or operate that would otherwise prohibit , restrict , or place conditions upon GitHub's Access to any publicly accessible data , information or content associated with your products or services , including for the purpose of developing or training any Commercial AI System. You further agree not to impose technical or other targeted measures to restrict or retaliate against such Access. This Section D.9 does not apply to Access solely for the purpose of academic research or if , on the date you Access the Content , the number of monthly active users of the products or services made available by you is less than 700 million in the preceding calendar month. For the purposes of this Section , "you" shall refer to you and any entity that directly or indirectly controls , is controlled by , or is under common control with you (affiliates). ## E. Private Repositories **Short version:** *We treat the content of private repositories as confidential , and we only access it as described in Section E.3 below—for security purposes , to assist the repository owner with a support matter , to maintain the integrity of the Service , to comply with our legal obligations , if we have reason to believe the contents are in violation of the law , or with your consent.* ### 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 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 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 You control access to the content of your private repositories. GitHub considers the contents of private repositories to be confidential to you , as set forth in Section E.2 , and GitHub personnel will not access private repository content without your consent except in the following circumstances: * for security purposes; * for automated scanning or manual review for known vulnerabilities , active malware , or other content known to violate our Terms of Service; * to assist the repository owner with a support matter; * to maintain the integrity of the Service; or * to comply with our legal obligations if we have reason to believe the contents are in violation of the law. 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 we need to provide the GitHub Service , we will provide an explanation of those rights. * If you provide your private repository content as Input to AI Features , we may use that Input to provide , develop , train , and improve the Service , including AI Features. Your ability to opt out under [Section J.3](#3-development-and-improvement-using-your-input-and-output) applies to this use of private repository content. We will not otherwise use your private repository contents to develop or improve the Service. Additionally , we may be [compelled by law](/en/site-policy/privacy-policies/github-general-privacy-statement#sharing-of-personal-data) to disclose the contents of your private repositories. GitHub will provide notice regarding our access to private repository content , unless [for legal disclosure](/en/site-policy/privacy-policies/github-general-privacy-statement) , to comply with our 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. ## F. 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](/en/site-policy/content-removal-policies/dmca-takedown-policy). If you are a copyright owner and you believe that content on GitHub violates your rights , please contact us via [our convenient DMCA form](https://github.com/contact/dmca) or by emailing <copyright@github.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](/en/site-policy/content-removal-policies/dmca-takedown-policy#f-repeated-infringement) of this policy. ## G. 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. GitHub's Rights to Content GitHub 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 © GitHub , 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 GitHub. ### 2. GitHub Trademarks and Logos If you’d like to use GitHub’s trademarks , you must follow all of our trademark guidelines , including those on our logos page: <https://github.com/logos>. ### 3. License to GitHub Policies This Agreement is licensed under this [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). For details , see our [site-policy repository](https://github.com/github/site-policy#license). ## H. API Terms **Short version:** *You agree to these Terms of Service , plus this Section H , when using any of GitHub's APIs (Application Programming Interface) , including use of the API through a third party product that accesses GitHub.* Abuse or excessively frequent requests to GitHub via the API may result in the temporary or permanent suspension of your Account's access to the API. GitHub , 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 GitHub's rate limitations. You may not use the API to download data or Content from GitHub for spamming purposes , including for the purposes of selling GitHub users' personal information , such as to recruiters , headhunters , and job boards. All use of the GitHub API is subject to these Terms of Service and the [GitHub Privacy Statement](https://github.com/site/privacy). GitHub may offer subscription-based access to our API for those Users who require high-throughput access or access that would result in resale of GitHub's Service. ## I. GitHub Additional Product Terms **Short version:** *You need to follow certain specific terms and conditions for GitHub's various features and products , and you agree to the Supplemental Terms and Conditions when you agree to this Agreement.* Some Service features may be subject to additional terms specific to that feature or product as set forth in the GitHub Additional Product Terms. By accessing or using the Services , you also agree to the [GitHub Additional Product Terms](/en/site-policy/github-terms/github-terms-for-additional-products-and-features). ## J. AI Features , Training , and Your Data ### 1. Applicability This section applies to all AI Features unless a specific feature has additional terms that expressly modify them. The training and data-use provisions in Section J.3 apply only to individual licenses. If your use of the Service is governed by a GitHub Customer Agreement or volume licensing agreement , those agreements govern the use of your data in connection with AI Features and Section J.3 does not apply to you. ### 2. Ownership GitHub does not claim ownership of your Input or Output. Output may contain material that resembles code or content in the model's training data or that is subject to third-party copyrights or open source license terms. You are responsible for determining whether your use of Output requires a third-party license and for complying with any such license. ### 3. Development and Improvement Using Your Input and Output We use your Inputs to generate Outputs and provide the AI Features. You also grant GitHub and its Affiliates a license to collect and use your Inputs and Outputs to develop , train and improve artificial intelligence and machine learning models and technologies including those that power AI Features , unless (a) you opt out through your account settings , or (b) your use of the Service is governed by a GitHub Customer Agreement or volume licensing agreement. If you opt out , GitHub will not collect or use your Inputs and Outputs for the purposes described in this paragraph from the effective date of your opt-out going forward. Unless you opt out , GitHub's Affiliates may use your Inputs and Outputs under this license in accordance with their applicable privacy and contractual obligations. This license does not , however , permit GitHub or its Affiliates to share your Inputs or Outputs with third-party AI model providers for their own independent model training purposes. The license in this Section J.3 is in addition to , and does not limit , the rights granted to GitHub and its Affiliates under Sections D.4 and D.8. This license does not extend to Your Content stored in repositories that are not provided as Input to an AI Feature. The opt-out right described in this section applies solely to the use of your Inputs and Outputs as described in this section , and does not apply to the license granted in Sections D.4-D.8 or to any Content that does not constitute Input or Output (including Content stored in public repositories). ### 4. Disclaimers Output is provided "as-is" and subject to the disclaimers in Section O. Without limiting Section O: Output may be inaccurate , incomplete , or non-functional. Output may resemble third-party code , including code under open source licenses. We do not guarantee that Output is free of errors , vulnerabilities , or intellectual property claims. You are responsible for reviewing , testing , and validating any Output before use. ### 5. Your Responsibility and Indemnity You are responsible for your use of Output , including ensuring it complies with applicable law and does not infringe third-party rights. Your indemnity obligations in Section Q apply to your use of AI Features and Output , including claims arising from Output you incorporate into your products or services. ## K. Beta Previews **Short version:** *Beta Previews may not be supported or may change at any time. You may receive confidential information through those programs that must remain confidential while the program is private. We'd love your feedback to make our Beta Previews better.* ### 1. Subject to Change Beta Previews may not be supported and may be changed at any time without notice. In addition , Beta Previews are not subject to the same security measures and auditing to which the Service has been and is subject. **By using a Beta Preview , you use it at your own risk.** ### 2. Confidentiality As a user of Beta Previews , you may get access to special information that isn’t available to the rest of the world. Due to the sensitive nature of this information , it’s important for us to make sure that you keep that information secret. **Confidentiality Obligations.** You agree that any non-public Beta Preview information we give you , such as information about a private Beta Preview , will be considered GitHub’s confidential information (collectively , “Confidential Information”) , regardless of whether it is marked or identified as such. You agree to only use such Confidential Information for the express purpose of testing and evaluating the Beta Preview (the “Purpose”) , and not for any other purpose. You should use the same degree of care as you would with your own confidential information , but no less than reasonable precautions to prevent any unauthorized use , disclosure , publication , or dissemination of our Confidential Information. You promise not to disclose , publish , or disseminate any Confidential Information to any third party , unless we don’t otherwise prohibit or restrict such disclosure (for example , you might be part of a GitHub-organized group discussion about a private Beta Preview feature). **Exceptions.** Confidential Information will not include information that is: (a) or becomes publicly available without breach of this Agreement through no act or inaction on your part (such as when a private Beta Preview becomes a public Beta Preview); (b) known to you before we disclose it to you; (c) independently developed by you without breach of any confidentiality obligation to us or any third party; or (d) disclosed with permission from GitHub. You will not violate the terms of this Agreement if you are required to disclose Confidential Information pursuant to operation of law , provided GitHub has been given reasonable advance written notice to object , unless prohibited by law. ### 3. Feedback We’re always trying to improve our products and services , and your feedback as a Beta Preview user will help us do that. If you choose to give us any ideas , know-how , algorithms , code contributions , suggestions , enhancement requests , recommendations or any other feedback for our products or services (collectively , “Feedback”) , you acknowledge and agree that GitHub will have a royalty-free , fully paid-up , worldwide , transferable , sub-licensable , irrevocable and perpetual license to implement , use , modify , commercially exploit and/or incorporate the Feedback into our products , services , and documentation. ## L. Payment **Short version:** *You are responsible for any fees associated with your use of GitHub. We are responsible for communicating those fees to you clearly and accurately , and letting you know well in advance if those prices change.* ### 1. Pricing Our pricing and payment terms are available at [github.com/pricing](https://github.com/pricing). If you agree to a subscription price , that will remain your price for the duration of the payment term; however , prices are subject to change at the end of a payment term. ### 2. Upgrades , Downgrades , and Changes * We will immediately bill you when you upgrade from the free plan to any paying plan. * If you change from a monthly billing plan to a yearly billing plan , GitHub will bill you for a full year at the next monthly billing date. * If you upgrade to a higher level of service , we will bill you for the upgraded plan immediately. * You may change your level of service at any time by [choosing a plan option](https://github.com/pricing) or going into your [Billing settings](https://github.com/settings/billing). If you choose to downgrade your Account , you may lose access to Content , features , or capacity of your Account. Please see our section on [Cancellation](#m-cancellation-and-termination) for information on getting a copy of that Content. ### 3. Billing Schedule; No Refunds **Payment Based on Plan** For monthly or yearly payment plans , the Service is billed in advance on a monthly or yearly basis respectively and is non-refundable. There will be no refunds or credits for partial months of service , downgrade refunds , or refunds for months unused with an open Account; however , the service will remain active for the length of the paid billing period. In order to treat everyone equally , no exceptions will be made. **Payment Based on Usage** Some Service features are billed based on your usage. A limited quantity of these Service features may be included in your plan for a limited term without additional charge. If you choose to use paid Service features beyond the quantity included in your plan , you pay for those Service features based on your actual usage in the preceding month. Monthly payment for these purchases will be charged on a periodic basis in arrears. See [GitHub Additional Product Terms for Details](/en/site-policy/github-terms/github-terms-for-additional-products-and-features). **Invoicing** For invoiced Users , User agrees to pay the fees in full , up front without deduction or setoff of any kind , in U.S. Dollars. User must pay the fees within thirty (30) days of the GitHub invoice date. Amounts payable under this Agreement are non-refundable , except as otherwise provided in this Agreement. If User fails to pay any fees on time , GitHub reserves the right , in addition to taking any other action at law or equity , to (i) charge interest on past due amounts at 1.0% per month or the highest interest rate allowed by law , whichever is less , and to charge all expenses of recovery , and (ii) terminate the applicable order form. User is solely responsible for all taxes , fees , duties and governmental assessments (except for taxes based on GitHub's net income) that are imposed or become due in connection with this Agreement. ### 4. Authorization By agreeing to these Terms , you are giving us permission to charge your on-file credit card , PayPal account , or other approved methods of payment for fees that you authorize for GitHub. ### 5. Responsibility for Payment You are responsible for all fees , including taxes , associated with your use of the Service. By using the Service , you agree to pay GitHub any charge incurred in connection with your use of the Service. If you dispute the matter , contact us through the [GitHub Support portal](https://support.github.com/). You are responsible for providing us with a valid means of payment for paid Accounts. Free Accounts are not required to provide payment information. ## M. Cancellation and Termination **Short version:** *You may close your Account at any time. If you do , we'll treat your information responsibly.* ### 1. Account Cancellation It is your responsibility to properly cancel your Account with GitHub. You can [cancel your Account at any time](/en/billing/how-tos/manage-plan-and-licenses/downgrade-plan) by going into your Settings in the global navigation bar at the top of the screen. The Account screen provides a simple , no questions asked cancellation link. We are not able to cancel Accounts in response to an email or phone request. ### 2. Upon Cancellation We will 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 and the Content of your repositories within 90 days of cancellation or termination (though some information may remain in encrypted backups). This information cannot be recovered once your Account is canceled. We will not delete Content that you have contributed to other Users' repositories or that other Users have forked. Upon request , we will make a reasonable effort to provide an Account owner with a copy of your lawful , non-infringing Account contents after Account cancellation , termination , or downgrade. You must make this request within 90 days of cancellation , termination , or downgrade. ### 3. GitHub May Terminate GitHub has the right to suspend or terminate your access to all or any part of the Website at any time , with or without cause , with or without notice , effective immediately. GitHub reserves the right to refuse service to anyone for any reason at any time. ### 4. Survival All provisions of this Agreement which , by their nature , should survive termination *will* survive termination — including , without limitation: ownership provisions , warranty disclaimers , indemnity , and limitations of liability. ## N. Communications with GitHub **Short version:** *We use email and other electronic means to stay in touch with our users.* ### 1. Electronic Communication Required For contractual purposes , you (1) consent to receive communications from us in an electronic form via the email address you have submitted or via the Service; and (2) agree that all Terms of Service , agreements , notices , disclosures , and other communications that we provide to you electronically satisfy any legal requirement that those communications would satisfy if they were on paper. This section does not affect your non-waivable rights. ### 2. Legal Notice to GitHub Must Be in Writing Communications made through email or GitHub Support's messaging system will not constitute legal notice to GitHub or any of its officers , employees , agents or representatives in any situation where notice to GitHub is required by contract or any law or regulation. Legal notice to GitHub must be in writing and [served on GitHub's legal agent](/en/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data#submitting-requests). ### 3. No Phone Support GitHub only offers support via email , in-Service communications , and electronic messages. We do not offer telephone support. ## O. Disclaimer of Warranties **Short version:** *We provide our service as is , and we make no promises or guarantees about this service. Please read this section carefully; you should understand what to expect.* GitHub provides the Website and the Service “as is” and “as available , ” without warranty of any kind. Without limiting this , we expressly disclaim all warranties , whether express , implied or statutory , regarding the Website and the Service including without limitation any warranty of merchantability , fitness for a particular purpose , title , security , accuracy and non-infringement. GitHub does not warrant that the Service will meet your requirements; that the Service will be uninterrupted , timely , secure , or error-free; that the information provided through the Service is accurate , reliable or correct; that any defects or errors will be corrected; that the Service will be available at any particular time or location; or that the Service is free of viruses or other harmful components. You assume full responsibility and risk of loss resulting from your downloading and/or use of files , information , content or other material obtained from the Service. ## P. Limitation of Liability **Short version:** *We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. Please read this section carefully; it limits our obligations to you.* You understand and agree that we will not be liable to you or any third party for any loss of profits , use , goodwill , or data , or for any incidental , indirect , special , consequential or exemplary damages , however arising , that result from <!-- markdownlint-disable GHD034 --> * the use , disclosure , or display of your User-Generated Content; * your use or inability to use the Service; * any modification , price change , suspension or discontinuance of the Service; * the Service generally or the software or systems that make the Service available; * unauthorized access to or alterations of your transmissions or data; * statements or conduct of any third party on the Service; * any other user interactions that you input or receive through your use of the Service; or * any other matter relating to the Service. <!-- markdownlint-enable GHD034 --> Our liability is limited whether or not we have been informed of the possibility of such damages , and even if a remedy set forth in this Agreement is found to have failed of its essential purpose. We will have no liability for any failure or delay due to matters beyond our reasonable control. ## Q. Release and Indemnification **Short version:** *You are responsible for your use of the service. If you harm someone else or get into a dispute with someone else , we will not be involved.* If you have a dispute with one or more Users , you agree to release GitHub from any and all claims , demands and damages (actual and consequential) of every kind and nature , known and unknown , arising out of or in any way connected with such disputes. You agree to indemnify us , defend us , and hold us harmless from and against any and all claims , liabilities , and expenses , including attorneys’ fees , arising out of your use of the Website and the Service , including but not limited to your violation of this Agreement , provided that GitHub (1) promptly gives you written notice of the claim , demand , suit or proceeding; (2) gives you sole control of the defense and settlement of the claim , demand , suit or proceeding (provided that you may not settle any claim , demand , suit or proceeding unless the settlement unconditionally releases GitHub of all liability); and (3) provides to you all reasonable assistance , at your expense. ## R. Changes to These Terms **Short version:** *We want our users to be informed of important changes to our terms , but some changes aren't that important — we don't want to bother you every time we fix a typo. So while we may modify this agreement at any time , we will notify users of any material changes and give you time to adjust to them.* We reserve the right , at our sole discretion , to amend these Terms of Service at any time and will update these Terms of Service in the event of any such amendments. We will notify our Users of material changes to this Agreement , such as price increases , at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications , your continued use of the Website constitutes agreement to our revisions of these Terms of Service. You can view all changes to these Terms in our [Site Policy](https://github.com/github/site-policy) repository. We reserve the right at any time and from time to time to modify or discontinue , temporarily or permanently , the Website (or any part of it) with or without notice. ## S. Miscellaneous ### 1. Governing Law Except to the extent applicable law provides otherwise , this Agreement between you and GitHub and any access to or use of the Website or the Service are governed by the federal laws of the United States of America and the laws of the State of California , without regard to conflict of law provisions. You and GitHub agree to submit to the exclusive jurisdiction and venue of the courts located in the City and County of San Francisco , California. However , any claim for injunctive relief with respect to a violation of section D.9 may be brought in any jurisdiction. ### 2. Non-Assignability GitHub may assign or delegate these Terms of Service and/or the [GitHub Privacy Statement](https://github.com/site/privacy) , in whole or in part , to any person or entity at any time with or without your consent , including the license grant in Section D.4. You may not assign or delegate any rights or obligations under the Terms of Service or Privacy Statement without our prior written consent , and any unauthorized assignment and delegation by you is void. ### 3. Section Headings and Summaries Throughout this Agreement , each section includes titles and brief summaries of the following terms and conditions. These section titles and brief summaries are not legally binding. ### 4. Severability , No Waiver , and Survival If any part of this Agreement is held invalid or unenforceable , that portion of the Agreement will be construed to reflect the parties’ original intent. The remaining portions will remain in full force and effect. Any failure on the part of GitHub to enforce any provision of this Agreement will not be considered a waiver of our right to enforce such provision. Our rights under this Agreement will survive any termination of this Agreement. ### 5. Amendments; Complete Agreement This Agreement may only be modified by a written amendment signed by an authorized representative of GitHub , or by the posting by GitHub of a revised version in accordance with [Section R. Changes to These Terms](#r-changes-to-these-terms). These Terms of Service , together with the GitHub Privacy Statement , represent the complete and exclusive statement of the agreement between you and us. This Agreement supersedes any proposal or prior agreement oral or written , and any other communications between you and GitHub relating to the subject matter of these terms including any confidentiality or nondisclosure agreements. ### 6. Questions Questions about the Terms of Service? Contact us through the [GitHub Support portal](https://support.github.com/). ,

sumanmal51509-svg

# GitHub Terms of Service <!-- markdownlint-disable search-replace --> Thank you for using GitHub! We're happy you're here. Please read this Terms of Service agreement carefully before accessing or using GitHub. Because it is such an important contract between us and our users , we have tried to make it as clear as possible. For your convenience , we have presented these terms in a short non-binding summary followed by the full legal terms. ## Summary | Section | What can you find there? | | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | [A. Definitions](#a-definitions) | Some basic terms , defined in a way that will help you understand this agreement. Refer back up to this section for clarification. | | [B. Account Terms](#b-account-terms) | These are the basic requirements of having an Account on GitHub. | | [C. Acceptable Use](#c-acceptable-use) | These are the basic rules you must follow when using your GitHub Account. | | [D. User-Generated Content](#d-user-generated-content) | You own the content you post on GitHub. However , you have some responsibilities regarding it , and we ask you to grant us some rights so we can provide services to you. | | [E. Private Repositories](#e-private-repositories) | This section talks about how GitHub will treat content you post in private repositories. | | [F. Copyright & DMCA Policy](#f-copyright-infringement-and-dmca-policy) | This section talks about how GitHub will respond if you believe someone is infringing your copyrights on GitHub. | | [G. Intellectual Property Notice](#g-intellectual-property-notice) | This describes GitHub's rights in the website and service. | | [H. API Terms](#h-api-terms) | These are the rules for using GitHub's APIs , whether you are using the API for development or data collection. | | [I. Additional Product Terms](#i-github-additional-product-terms) | We have a few specific rules for GitHub's features and products. | | [J. AI Features , Training , and Your Data](#j-ai-features-training-and-your-data) | These are the terms that apply to GitHub Copilot and other AI features , including how your data may be used for development and improvement of the artificial intelligence and machine learning models , and the controls available to you. | | [K. Beta Previews](#k-beta-previews) | These are some of the additional terms that apply to GitHub's features that are still in development. | | [L. Payment](#l-payment) | You are responsible for payment. We are responsible for billing you accurately. | | [M. Cancellation and Termination](#m-cancellation-and-termination) | You may cancel this agreement and close your Account at any time. | | [N. Communications with GitHub](#n-communications-with-github) | We only use email and other electronic means to stay in touch with our users. We do not provide phone support. | | [O. Disclaimer of Warranties](#o-disclaimer-of-warranties) | We provide our service as is , and we make no promises or guarantees about this service. **Please read this section carefully; you should understand what to expect.** | | [P. Limitation of Liability](#p-limitation-of-liability) | We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. **Please read this section carefully; it limits our obligations to you.** | | [Q. Release and Indemnification](#q-release-and-indemnification) | You are fully responsible for your use of the service. | | [R. Changes to these Terms of Service](#r-changes-to-these-terms) | We may modify this agreement , but we will give you 30 days' notice of material changes. | | [S. Miscellaneous](#s-miscellaneous) | Please see this section for legal details including our choice of law. | ## The GitHub Terms of Service Effective date: April 27 , 2026 ## A. 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.* 1. An "Account" represents your legal relationship with GitHub. A “Personal Account” represents an individual User’s authorization to log in to and use the Service and serves as a User’s identity on GitHub. “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 Personal Account can be a member of any number of Organizations. 2. 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 GitHub Privacy Statement , available at [github.com/site/privacy](https://github.com/site/privacy)) and procedures that we may publish from time to time on the Website. Most of our site policies are available at [docs.github.com/categories/site-policy](/en/site-policy). 3. "AI Feature" means any feature of GitHub or our Affiliates that uses machine learning or artificial intelligence to generate Output , including GitHub Copilot , Copilot Autofix , and any other feature identified as using machine learning or artificial intelligence in our documentation. 4. “Affiliate” means any entity that directly or indirectly controls , is controlled by , or is under common control with a party , where "control" means having more than fifty percent (50%) ownership or the right to direct the management of the entity. For the avoidance of doubt , Microsoft is an Affiliate of GitHub. 5. "Beta Previews" mean software , services , or features identified as alpha , beta , preview , early access , or evaluation , or words or phrases with similar meanings. 6. "Content" means code , text , data , documentation , images , graphics , software , packages , and other materials made available through the Service. 7. “GitHub , ” “We , ” and “Us” refer to GitHub , Inc. , as well as our directors , subsidiaries , contractors , licensors , officers , agents , and employees. 8. “Input” means any content or context provided to an AI Feature , including prompts , attachments , code in your workspace , and conversation history. 9. "Output" means responses and suggestions , including code or other material , generated by an AI Feature. 10. The “Service” refers to the applications , software , products , and services provided by GitHub , including through the Website and any Beta Previews. 11. “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](#5-additional-terms)). 12. "User-Generated Content" means Content that you or other users upload , submit , or create through the Service. 13. The “Website” refers to GitHub’s website located at [github.com](https://github.com/) , and all content , services , and products provided by GitHub at or through the Website. It also refers to GitHub-owned subdomains of github.com , such as [education.github.com](https://education.github.com/) and [pages.github.com](https://pages.github.com/). These Terms also govern GitHub’s conference websites , such as [githubuniverse.com](https://githubuniverse.com/) , and product websites , such as [electronjs.org](https://www.electronjs.org/). Occasionally , websites owned by GitHub 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. 14. "Your Content" means User-Generated Content that you upload , submit , or create , including your modifications to Content you have forked or cloned. It does not include the underlying Content created by others. ## B. Account Terms **Short version:** *Personal 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 Personal 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 Personal 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](#l-payment) , in which case additional information will be necessary for billing purposes. ### 3. Account Requirements We have a few simple rules for Accounts on GitHub'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 Personal 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. GitHub 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](#m-cancellation-and-termination). 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 Personal Accounts as your subscription allows. * You may not use GitHub in violation of export control or sanctions laws of the United States or any other applicable jurisdiction. You may not use GitHub if you are or are working on behalf of a [Specially Designated National (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) or a person subject to similar blocking or denied party prohibitions administered by a U.S. government agency. GitHub may allow persons in certain sanctioned countries or territories to access certain GitHub services pursuant to U.S. government authorizations. For more information , please see our [Export Controls policy](/en/site-policy/other-site-policies/github-and-trade-controls). ### 4. 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. GitHub cannot and will not be liable for any loss or damage from your failure to comply with this security obligation. * You will promptly notify GitHub by contacting us through the [GitHub Support portal](https://support.github.com/) 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 GitHub. For example , you may be a member of an organization on GitHub with its own terms or license agreements; you may download an application that integrates with GitHub; or you may use GitHub 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 GitHub Service in a government capacity , this [Government Amendment to GitHub Terms of Service](/en/site-policy/site-policy-deprecated/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users) applies to you , and you agree to its provisions. If you have signed up for GitHub Enterprise Cloud , the [Enterprise Cloud Addendum](/en/site-policy/site-policy-deprecated/github-enterprise-service-level-agreement) applies to you , and you agree to its provisions. ## C. Acceptable Use **Short version:** *GitHub 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](/en/site-policy/acceptable-use-policies/github-acceptable-use-policies) or [Community Guidelines](/en/site-policy/github-terms/github-community-guidelines). ## D. 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 are responsible for Your Content and any harm resulting from it. This includes Content you post , upload , or make available through the Service. We are not responsible for any public display or misuse of Your Content. ### 2. GitHub May Remove Content We may refuse or remove User-Generated Content that violates applicable law or our terms and policies. We access private repositories only as described in Section E. Content displayed on GitHub Mobile may be subject to app store terms. ### 3. Ownership and License Grants You own Your Content. If you post Content you did not create , you are responsible for ensuring you have the right to post it and for complying with any applicable licenses. You grant us and other Users the licenses in Sections D.4–D.8. These licenses apply to Your Content. If Your Content already includes a license granting us the permissions we need , no additional license is required. You will not receive payment for these rights. These licenses end when you remove Your Content , unless other Users have forked it. ### 4. License Grant to Us You grant GitHub and our Affiliates the right to store , host , archive , parse , display , and make copies of Your Content as necessary to provide , develop , and improve the Service , including by training AI Features , and for the purpose of training , developing , and improving artificial intelligence and machine learning models and technologies of our Affiliates. This license 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. For the avoidance of doubt , use of Your Content to develop , train , and improve artificial intelligence and machine learning models and technologies of GitHub and our Affiliates is within the scope of this license and does not constitute a sale or other restricted transfer of Your Content. ### 5. License Grant to Other Users Your Content that 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 within the Service in repositories they control). By making a repository public , you grant other Users a nonexclusive , worldwide license to use , display , perform and reproduce (by forking) Your Content through the Service as permitted by GitHub's functionality. You may grant additional rights by [adopting a license](/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository#including-an-open-source-license-in-your-repository). If you post Content you did not create or own , you are responsible for ensuring it is licensed under terms that permit these uses. ### 6. 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. If you have a separate agreement to license that Content 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 or our Affiliates , to enable GitHub and our Affiliates 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 GitHub 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. ### 8. Public Repositories and Lawful Access By choosing to contribute Content to a public repository , you are choosing to and directing us to make such Content accessible to everyone on the internet. Unless specifically set forth herein , these Terms do not restrict lawful access to or use of the contents of public repositories by third parties , or by GitHub or its Affiliates. ### 9. Access Reciprocity By using automated means to access , collect , or otherwise use (“Access”) any publicly accessible Content from the Service for the purpose of developing or training any commercially available artificial intelligence model , machine learning system , or similar technology (a "Commercial AI System") , you hereby waive any and all policies , terms , conditions , or contractual provisions governing products , services , websites or datasets you own or operate that would otherwise prohibit , restrict , or place conditions upon GitHub's Access to any publicly accessible data , information or content associated with your products or services , including for the purpose of developing or training any Commercial AI System. You further agree not to impose technical or other targeted measures to restrict or retaliate against such Access. This Section D.9 does not apply to Access solely for the purpose of academic research or if , on the date you Access the Content , the number of monthly active users of the products or services made available by you is less than 700 million in the preceding calendar month. For the purposes of this Section , "you" shall refer to you and any entity that directly or indirectly controls , is controlled by , or is under common control with you (affiliates). ## E. Private Repositories **Short version:** *We treat the content of private repositories as confidential , and we only access it as described in Section E.3 below—for security purposes , to assist the repository owner with a support matter , to maintain the integrity of the Service , to comply with our legal obligations , if we have reason to believe the contents are in violation of the law , or with your consent.* ### 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 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 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 You control access to the content of your private repositories. GitHub considers the contents of private repositories to be confidential to you , as set forth in Section E.2 , and GitHub personnel will not access private repository content without your consent except in the following circumstances: * for security purposes; * for automated scanning or manual review for known vulnerabilities , active malware , or other content known to violate our Terms of Service; * to assist the repository owner with a support matter; * to maintain the integrity of the Service; or * to comply with our legal obligations if we have reason to believe the contents are in violation of the law. 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 we need to provide the GitHub Service , we will provide an explanation of those rights. * If you provide your private repository content as Input to AI Features , we may use that Input to provide , develop , train , and improve the Service , including AI Features. Your ability to opt out under [Section J.3](#3-development-and-improvement-using-your-input-and-output) applies to this use of private repository content. We will not otherwise use your private repository contents to develop or improve the Service. Additionally , we may be [compelled by law](/en/site-policy/privacy-policies/github-general-privacy-statement#sharing-of-personal-data) to disclose the contents of your private repositories. GitHub will provide notice regarding our access to private repository content , unless [for legal disclosure](/en/site-policy/privacy-policies/github-general-privacy-statement) , to comply with our 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. ## F. 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](/en/site-policy/content-removal-policies/dmca-takedown-policy). If you are a copyright owner and you believe that content on GitHub violates your rights , please contact us via [our convenient DMCA form](https://github.com/contact/dmca) or by emailing <copyright@github.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](/en/site-policy/content-removal-policies/dmca-takedown-policy#f-repeated-infringement) of this policy. ## G. 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. GitHub's Rights to Content GitHub 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 © GitHub , 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 GitHub. ### 2. GitHub Trademarks and Logos If you’d like to use GitHub’s trademarks , you must follow all of our trademark guidelines , including those on our logos page: <https://github.com/logos>. ### 3. License to GitHub Policies This Agreement is licensed under this [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). For details , see our [site-policy repository](https://github.com/github/site-policy#license). ## H. API Terms **Short version:** *You agree to these Terms of Service , plus this Section H , when using any of GitHub's APIs (Application Programming Interface) , including use of the API through a third party product that accesses GitHub.* Abuse or excessively frequent requests to GitHub via the API may result in the temporary or permanent suspension of your Account's access to the API. GitHub , 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 GitHub's rate limitations. You may not use the API to download data or Content from GitHub for spamming purposes , including for the purposes of selling GitHub users' personal information , such as to recruiters , headhunters , and job boards. All use of the GitHub API is subject to these Terms of Service and the [GitHub Privacy Statement](https://github.com/site/privacy). GitHub may offer subscription-based access to our API for those Users who require high-throughput access or access that would result in resale of GitHub's Service. ## I. GitHub Additional Product Terms **Short version:** *You need to follow certain specific terms and conditions for GitHub's various features and products , and you agree to the Supplemental Terms and Conditions when you agree to this Agreement.* Some Service features may be subject to additional terms specific to that feature or product as set forth in the GitHub Additional Product Terms. By accessing or using the Services , you also agree to the [GitHub Additional Product Terms](/en/site-policy/github-terms/github-terms-for-additional-products-and-features). ## J. AI Features , Training , and Your Data ### 1. Applicability This section applies to all AI Features unless a specific feature has additional terms that expressly modify them. The training and data-use provisions in Section J.3 apply only to individual licenses. If your use of the Service is governed by a GitHub Customer Agreement or volume licensing agreement , those agreements govern the use of your data in connection with AI Features and Section J.3 does not apply to you. ### 2. Ownership GitHub does not claim ownership of your Input or Output. Output may contain material that resembles code or content in the model's training data or that is subject to third-party copyrights or open source license terms. You are responsible for determining whether your use of Output requires a third-party license and for complying with any such license. ### 3. Development and Improvement Using Your Input and Output We use your Inputs to generate Outputs and provide the AI Features. You also grant GitHub and its Affiliates a license to collect and use your Inputs and Outputs to develop , train and improve artificial intelligence and machine learning models and technologies including those that power AI Features , unless (a) you opt out through your account settings , or (b) your use of the Service is governed by a GitHub Customer Agreement or volume licensing agreement. If you opt out , GitHub will not collect or use your Inputs and Outputs for the purposes described in this paragraph from the effective date of your opt-out going forward. Unless you opt out , GitHub's Affiliates may use your Inputs and Outputs under this license in accordance with their applicable privacy and contractual obligations. This license does not , however , permit GitHub or its Affiliates to share your Inputs or Outputs with third-party AI model providers for their own independent model training purposes. The license in this Section J.3 is in addition to , and does not limit , the rights granted to GitHub and its Affiliates under Sections D.4 and D.8. This license does not extend to Your Content stored in repositories that are not provided as Input to an AI Feature. The opt-out right described in this section applies solely to the use of your Inputs and Outputs as described in this section , and does not apply to the license granted in Sections D.4-D.8 or to any Content that does not constitute Input or Output (including Content stored in public repositories). ### 4. Disclaimers Output is provided "as-is" and subject to the disclaimers in Section O. Without limiting Section O: Output may be inaccurate , incomplete , or non-functional. Output may resemble third-party code , including code under open source licenses. We do not guarantee that Output is free of errors , vulnerabilities , or intellectual property claims. You are responsible for reviewing , testing , and validating any Output before use. ### 5. Your Responsibility and Indemnity You are responsible for your use of Output , including ensuring it complies with applicable law and does not infringe third-party rights. Your indemnity obligations in Section Q apply to your use of AI Features and Output , including claims arising from Output you incorporate into your products or services. ## K. Beta Previews **Short version:** *Beta Previews may not be supported or may change at any time. You may receive confidential information through those programs that must remain confidential while the program is private. We'd love your feedback to make our Beta Previews better.* ### 1. Subject to Change Beta Previews may not be supported and may be changed at any time without notice. In addition , Beta Previews are not subject to the same security measures and auditing to which the Service has been and is subject. **By using a Beta Preview , you use it at your own risk.** ### 2. Confidentiality As a user of Beta Previews , you may get access to special information that isn’t available to the rest of the world. Due to the sensitive nature of this information , it’s important for us to make sure that you keep that information secret. **Confidentiality Obligations.** You agree that any non-public Beta Preview information we give you , such as information about a private Beta Preview , will be considered GitHub’s confidential information (collectively , “Confidential Information”) , regardless of whether it is marked or identified as such. You agree to only use such Confidential Information for the express purpose of testing and evaluating the Beta Preview (the “Purpose”) , and not for any other purpose. You should use the same degree of care as you would with your own confidential information , but no less than reasonable precautions to prevent any unauthorized use , disclosure , publication , or dissemination of our Confidential Information. You promise not to disclose , publish , or disseminate any Confidential Information to any third party , unless we don’t otherwise prohibit or restrict such disclosure (for example , you might be part of a GitHub-organized group discussion about a private Beta Preview feature). **Exceptions.** Confidential Information will not include information that is: (a) or becomes publicly available without breach of this Agreement through no act or inaction on your part (such as when a private Beta Preview becomes a public Beta Preview); (b) known to you before we disclose it to you; (c) independently developed by you without breach of any confidentiality obligation to us or any third party; or (d) disclosed with permission from GitHub. You will not violate the terms of this Agreement if you are required to disclose Confidential Information pursuant to operation of law , provided GitHub has been given reasonable advance written notice to object , unless prohibited by law. ### 3. Feedback We’re always trying to improve our products and services , and your feedback as a Beta Preview user will help us do that. If you choose to give us any ideas , know-how , algorithms , code contributions , suggestions , enhancement requests , recommendations or any other feedback for our products or services (collectively , “Feedback”) , you acknowledge and agree that GitHub will have a royalty-free , fully paid-up , worldwide , transferable , sub-licensable , irrevocable and perpetual license to implement , use , modify , commercially exploit and/or incorporate the Feedback into our products , services , and documentation. ## L. Payment **Short version:** *You are responsible for any fees associated with your use of GitHub. We are responsible for communicating those fees to you clearly and accurately , and letting you know well in advance if those prices change.* ### 1. Pricing Our pricing and payment terms are available at [github.com/pricing](https://github.com/pricing). If you agree to a subscription price , that will remain your price for the duration of the payment term; however , prices are subject to change at the end of a payment term. ### 2. Upgrades , Downgrades , and Changes * We will immediately bill you when you upgrade from the free plan to any paying plan. * If you change from a monthly billing plan to a yearly billing plan , GitHub will bill you for a full year at the next monthly billing date. * If you upgrade to a higher level of service , we will bill you for the upgraded plan immediately. * You may change your level of service at any time by [choosing a plan option](https://github.com/pricing) or going into your [Billing settings](https://github.com/settings/billing). If you choose to downgrade your Account , you may lose access to Content , features , or capacity of your Account. Please see our section on [Cancellation](#m-cancellation-and-termination) for information on getting a copy of that Content. ### 3. Billing Schedule; No Refunds **Payment Based on Plan** For monthly or yearly payment plans , the Service is billed in advance on a monthly or yearly basis respectively and is non-refundable. There will be no refunds or credits for partial months of service , downgrade refunds , or refunds for months unused with an open Account; however , the service will remain active for the length of the paid billing period. In order to treat everyone equally , no exceptions will be made. **Payment Based on Usage** Some Service features are billed based on your usage. A limited quantity of these Service features may be included in your plan for a limited term without additional charge. If you choose to use paid Service features beyond the quantity included in your plan , you pay for those Service features based on your actual usage in the preceding month. Monthly payment for these purchases will be charged on a periodic basis in arrears. See [GitHub Additional Product Terms for Details](/en/site-policy/github-terms/github-terms-for-additional-products-and-features). **Invoicing** For invoiced Users , User agrees to pay the fees in full , up front without deduction or setoff of any kind , in U.S. Dollars. User must pay the fees within thirty (30) days of the GitHub invoice date. Amounts payable under this Agreement are non-refundable , except as otherwise provided in this Agreement. If User fails to pay any fees on time , GitHub reserves the right , in addition to taking any other action at law or equity , to (i) charge interest on past due amounts at 1.0% per month or the highest interest rate allowed by law , whichever is less , and to charge all expenses of recovery , and (ii) terminate the applicable order form. User is solely responsible for all taxes , fees , duties and governmental assessments (except for taxes based on GitHub's net income) that are imposed or become due in connection with this Agreement. ### 4. Authorization By agreeing to these Terms , you are giving us permission to charge your on-file credit card , PayPal account , or other approved methods of payment for fees that you authorize for GitHub. ### 5. Responsibility for Payment You are responsible for all fees , including taxes , associated with your use of the Service. By using the Service , you agree to pay GitHub any charge incurred in connection with your use of the Service. If you dispute the matter , contact us through the [GitHub Support portal](https://support.github.com/). You are responsible for providing us with a valid means of payment for paid Accounts. Free Accounts are not required to provide payment information. ## M. Cancellation and Termination **Short version:** *You may close your Account at any time. If you do , we'll treat your information responsibly.* ### 1. Account Cancellation It is your responsibility to properly cancel your Account with GitHub. You can [cancel your Account at any time](/en/billing/how-tos/manage-plan-and-licenses/downgrade-plan) by going into your Settings in the global navigation bar at the top of the screen. The Account screen provides a simple , no questions asked cancellation link. We are not able to cancel Accounts in response to an email or phone request. ### 2. Upon Cancellation We will 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 and the Content of your repositories within 90 days of cancellation or termination (though some information may remain in encrypted backups). This information cannot be recovered once your Account is canceled. We will not delete Content that you have contributed to other Users' repositories or that other Users have forked. Upon request , we will make a reasonable effort to provide an Account owner with a copy of your lawful , non-infringing Account contents after Account cancellation , termination , or downgrade. You must make this request within 90 days of cancellation , termination , or downgrade. ### 3. GitHub May Terminate GitHub has the right to suspend or terminate your access to all or any part of the Website at any time , with or without cause , with or without notice , effective immediately. GitHub reserves the right to refuse service to anyone for any reason at any time. ### 4. Survival All provisions of this Agreement which , by their nature , should survive termination *will* survive termination — including , without limitation: ownership provisions , warranty disclaimers , indemnity , and limitations of liability. ## N. Communications with GitHub **Short version:** *We use email and other electronic means to stay in touch with our users.* ### 1. Electronic Communication Required For contractual purposes , you (1) consent to receive communications from us in an electronic form via the email address you have submitted or via the Service; and (2) agree that all Terms of Service , agreements , notices , disclosures , and other communications that we provide to you electronically satisfy any legal requirement that those communications would satisfy if they were on paper. This section does not affect your non-waivable rights. ### 2. Legal Notice to GitHub Must Be in Writing Communications made through email or GitHub Support's messaging system will not constitute legal notice to GitHub or any of its officers , employees , agents or representatives in any situation where notice to GitHub is required by contract or any law or regulation. Legal notice to GitHub must be in writing and [served on GitHub's legal agent](/en/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data#submitting-requests). ### 3. No Phone Support GitHub only offers support via email , in-Service communications , and electronic messages. We do not offer telephone support. ## O. Disclaimer of Warranties **Short version:** *We provide our service as is , and we make no promises or guarantees about this service. Please read this section carefully; you should understand what to expect.* GitHub provides the Website and the Service “as is” and “as available , ” without warranty of any kind. Without limiting this , we expressly disclaim all warranties , whether express , implied or statutory , regarding the Website and the Service including without limitation any warranty of merchantability , fitness for a particular purpose , title , security , accuracy and non-infringement. GitHub does not warrant that the Service will meet your requirements; that the Service will be uninterrupted , timely , secure , or error-free; that the information provided through the Service is accurate , reliable or correct; that any defects or errors will be corrected; that the Service will be available at any particular time or location; or that the Service is free of viruses or other harmful components. You assume full responsibility and risk of loss resulting from your downloading and/or use of files , information , content or other material obtained from the Service. ## P. Limitation of Liability **Short version:** *We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. Please read this section carefully; it limits our obligations to you.* You understand and agree that we will not be liable to you or any third party for any loss of profits , use , goodwill , or data , or for any incidental , indirect , special , consequential or exemplary damages , however arising , that result from <!-- markdownlint-disable GHD034 --> * the use , disclosure , or display of your User-Generated Content; * your use or inability to use the Service; * any modification , price change , suspension or discontinuance of the Service; * the Service generally or the software or systems that make the Service available; * unauthorized access to or alterations of your transmissions or data; * statements or conduct of any third party on the Service; * any other user interactions that you input or receive through your use of the Service; or * any other matter relating to the Service. <!-- markdownlint-enable GHD034 --> Our liability is limited whether or not we have been informed of the possibility of such damages , and even if a remedy set forth in this Agreement is found to have failed of its essential purpose. We will have no liability for any failure or delay due to matters beyond our reasonable control. ## Q. Release and Indemnification **Short version:** *You are responsible for your use of the service. If you harm someone else or get into a dispute with someone else , we will not be involved.* If you have a dispute with one or more Users , you agree to release GitHub from any and all claims , demands and damages (actual and consequential) of every kind and nature , known and unknown , arising out of or in any way connected with such disputes. You agree to indemnify us , defend us , and hold us harmless from and against any and all claims , liabilities , and expenses , including attorneys’ fees , arising out of your use of the Website and the Service , including but not limited to your violation of this Agreement , provided that GitHub (1) promptly gives you written notice of the claim , demand , suit or proceeding; (2) gives you sole control of the defense and settlement of the claim , demand , suit or proceeding (provided that you may not settle any claim , demand , suit or proceeding unless the settlement unconditionally releases GitHub of all liability); and (3) provides to you all reasonable assistance , at your expense. ## R. Changes to These Terms **Short version:** *We want our users to be informed of important changes to our terms , but some changes aren't that important — we don't want to bother you every time we fix a typo. So while we may modify this agreement at any time , we will notify users of any material changes and give you time to adjust to them.* We reserve the right , at our sole discretion , to amend these Terms of Service at any time and will update these Terms of Service in the event of any such amendments. We will notify our Users of material changes to this Agreement , such as price increases , at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications , your continued use of the Website constitutes agreement to our revisions of these Terms of Service. You can view all changes to these Terms in our [Site Policy](https://github.com/github/site-policy) repository. We reserve the right at any time and from time to time to modify or discontinue , temporarily or permanently , the Website (or any part of it) with or without notice. ## S. Miscellaneous ### 1. Governing Law Except to the extent applicable law provides otherwise , this Agreement between you and GitHub and any access to or use of the Website or the Service are governed by the federal laws of the United States of America and the laws of the State of California , without regard to conflict of law provisions. You and GitHub agree to submit to the exclusive jurisdiction and venue of the courts located in the City and County of San Francisco , California. However , any claim for injunctive relief with respect to a violation of section D.9 may be brought in any jurisdiction. ### 2. Non-Assignability GitHub may assign or delegate these Terms of Service and/or the [GitHub Privacy Statement](https://github.com/site/privacy) , in whole or in part , to any person or entity at any time with or without your consent , including the license grant in Section D.4. You may not assign or delegate any rights or obligations under the Terms of Service or Privacy Statement without our prior written consent , and any unauthorized assignment and delegation by you is void. ### 3. Section Headings and Summaries Throughout this Agreement , each section includes titles and brief summaries of the following terms and conditions. These section titles and brief summaries are not legally binding. ### 4. Severability , No Waiver , and Survival If any part of this Agreement is held invalid or unenforceable , that portion of the Agreement will be construed to reflect the parties’ original intent. The remaining portions will remain in full force and effect. Any failure on the part of GitHub to enforce any provision of this Agreement will not be considered a waiver of our right to enforce such provision. Our rights under this Agreement will survive any termination of this Agreement. ### 5. Amendments; Complete Agreement This Agreement may only be modified by a written amendment signed by an authorized representative of GitHub , or by the posting by GitHub of a revised version in accordance with [Section R. Changes to These Terms](#r-changes-to-these-terms). These Terms of Service , together with the GitHub Privacy Statement , represent the complete and exclusive statement of the agreement between you and us. This Agreement supersedes any proposal or prior agreement oral or written , and any other communications between you and GitHub relating to the subject matter of these terms including any confidentiality or nondisclosure agreements. ### 6. Questions Questions about the Terms of Service? Contact us through the [GitHub Support portal](https://support.github.com/). ,

sumanmal51509-svg

# GitHub Terms of Service <!-- markdownlint-disable search-replace --> Thank you for using GitHub! We're happy you're here. Please read this Terms of Service agreement carefully before accessing or using GitHub. Because it is such an important contract between us and our users , we have tried to make it as clear as possible. For your convenience , we have presented these terms in a short non-binding summary followed by the full legal terms. ## Summary | Section | What can you find there? | | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | [A. Definitions](#a-definitions) | Some basic terms , defined in a way that will help you understand this agreement. Refer back up to this section for clarification. | | [B. Account Terms](#b-account-terms) | These are the basic requirements of having an Account on GitHub. | | [C. Acceptable Use](#c-acceptable-use) | These are the basic rules you must follow when using your GitHub Account. | | [D. User-Generated Content](#d-user-generated-content) | You own the content you post on GitHub. However , you have some responsibilities regarding it , and we ask you to grant us some rights so we can provide services to you. | | [E. Private Repositories](#e-private-repositories) | This section talks about how GitHub will treat content you post in private repositories. | | [F. Copyright & DMCA Policy](#f-copyright-infringement-and-dmca-policy) | This section talks about how GitHub will respond if you believe someone is infringing your copyrights on GitHub. | | [G. Intellectual Property Notice](#g-intellectual-property-notice) | This describes GitHub's rights in the website and service. | | [H. API Terms](#h-api-terms) | These are the rules for using GitHub's APIs , whether you are using the API for development or data collection. | | [I. Additional Product Terms](#i-github-additional-product-terms) | We have a few specific rules for GitHub's features and products. | | [J. AI Features , Training , and Your Data](#j-ai-features-training-and-your-data) | These are the terms that apply to GitHub Copilot and other AI features , including how your data may be used for development and improvement of the artificial intelligence and machine learning models , and the controls available to you. | | [K. Beta Previews](#k-beta-previews) | These are some of the additional terms that apply to GitHub's features that are still in development. | | [L. Payment](#l-payment) | You are responsible for payment. We are responsible for billing you accurately. | | [M. Cancellation and Termination](#m-cancellation-and-termination) | You may cancel this agreement and close your Account at any time. | | [N. Communications with GitHub](#n-communications-with-github) | We only use email and other electronic means to stay in touch with our users. We do not provide phone support. | | [O. Disclaimer of Warranties](#o-disclaimer-of-warranties) | We provide our service as is , and we make no promises or guarantees about this service. **Please read this section carefully; you should understand what to expect.** | | [P. Limitation of Liability](#p-limitation-of-liability) | We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. **Please read this section carefully; it limits our obligations to you.** | | [Q. Release and Indemnification](#q-release-and-indemnification) | You are fully responsible for your use of the service. | | [R. Changes to these Terms of Service](#r-changes-to-these-terms) | We may modify this agreement , but we will give you 30 days' notice of material changes. | | [S. Miscellaneous](#s-miscellaneous) | Please see this section for legal details including our choice of law. | ## The GitHub Terms of Service Effective date: April 27 , 2026 ## A. 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.* 1. An "Account" represents your legal relationship with GitHub. A “Personal Account” represents an individual User’s authorization to log in to and use the Service and serves as a User’s identity on GitHub. “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 Personal Account can be a member of any number of Organizations. 2. 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 GitHub Privacy Statement , available at [github.com/site/privacy](https://github.com/site/privacy)) and procedures that we may publish from time to time on the Website. Most of our site policies are available at [docs.github.com/categories/site-policy](/en/site-policy). 3. "AI Feature" means any feature of GitHub or our Affiliates that uses machine learning or artificial intelligence to generate Output , including GitHub Copilot , Copilot Autofix , and any other feature identified as using machine learning or artificial intelligence in our documentation. 4. “Affiliate” means any entity that directly or indirectly controls , is controlled by , or is under common control with a party , where "control" means having more than fifty percent (50%) ownership or the right to direct the management of the entity. For the avoidance of doubt , Microsoft is an Affiliate of GitHub. 5. "Beta Previews" mean software , services , or features identified as alpha , beta , preview , early access , or evaluation , or words or phrases with similar meanings. 6. "Content" means code , text , data , documentation , images , graphics , software , packages , and other materials made available through the Service. 7. “GitHub , ” “We , ” and “Us” refer to GitHub , Inc. , as well as our directors , subsidiaries , contractors , licensors , officers , agents , and employees. 8. “Input” means any content or context provided to an AI Feature , including prompts , attachments , code in your workspace , and conversation history. 9. "Output" means responses and suggestions , including code or other material , generated by an AI Feature. 10. The “Service” refers to the applications , software , products , and services provided by GitHub , including through the Website and any Beta Previews. 11. “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](#5-additional-terms)). 12. "User-Generated Content" means Content that you or other users upload , submit , or create through the Service. 13. The “Website” refers to GitHub’s website located at [github.com](https://github.com/) , and all content , services , and products provided by GitHub at or through the Website. It also refers to GitHub-owned subdomains of github.com , such as [education.github.com](https://education.github.com/) and [pages.github.com](https://pages.github.com/). These Terms also govern GitHub’s conference websites , such as [githubuniverse.com](https://githubuniverse.com/) , and product websites , such as [electronjs.org](https://www.electronjs.org/). Occasionally , websites owned by GitHub 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. 14. "Your Content" means User-Generated Content that you upload , submit , or create , including your modifications to Content you have forked or cloned. It does not include the underlying Content created by others. ## B. Account Terms **Short version:** *Personal 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 Personal 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 Personal 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](#l-payment) , in which case additional information will be necessary for billing purposes. ### 3. Account Requirements We have a few simple rules for Accounts on GitHub'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 Personal 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. GitHub 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](#m-cancellation-and-termination). 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 Personal Accounts as your subscription allows. * You may not use GitHub in violation of export control or sanctions laws of the United States or any other applicable jurisdiction. You may not use GitHub if you are or are working on behalf of a [Specially Designated National (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) or a person subject to similar blocking or denied party prohibitions administered by a U.S. government agency. GitHub may allow persons in certain sanctioned countries or territories to access certain GitHub services pursuant to U.S. government authorizations. For more information , please see our [Export Controls policy](/en/site-policy/other-site-policies/github-and-trade-controls). ### 4. 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. GitHub cannot and will not be liable for any loss or damage from your failure to comply with this security obligation. * You will promptly notify GitHub by contacting us through the [GitHub Support portal](https://support.github.com/) 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 GitHub. For example , you may be a member of an organization on GitHub with its own terms or license agreements; you may download an application that integrates with GitHub; or you may use GitHub 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 GitHub Service in a government capacity , this [Government Amendment to GitHub Terms of Service](/en/site-policy/site-policy-deprecated/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users) applies to you , and you agree to its provisions. If you have signed up for GitHub Enterprise Cloud , the [Enterprise Cloud Addendum](/en/site-policy/site-policy-deprecated/github-enterprise-service-level-agreement) applies to you , and you agree to its provisions. ## C. Acceptable Use **Short version:** *GitHub 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](/en/site-policy/acceptable-use-policies/github-acceptable-use-policies) or [Community Guidelines](/en/site-policy/github-terms/github-community-guidelines). ## D. 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 are responsible for Your Content and any harm resulting from it. This includes Content you post , upload , or make available through the Service. We are not responsible for any public display or misuse of Your Content. ### 2. GitHub May Remove Content We may refuse or remove User-Generated Content that violates applicable law or our terms and policies. We access private repositories only as described in Section E. Content displayed on GitHub Mobile may be subject to app store terms. ### 3. Ownership and License Grants You own Your Content. If you post Content you did not create , you are responsible for ensuring you have the right to post it and for complying with any applicable licenses. You grant us and other Users the licenses in Sections D.4–D.8. These licenses apply to Your Content. If Your Content already includes a license granting us the permissions we need , no additional license is required. You will not receive payment for these rights. These licenses end when you remove Your Content , unless other Users have forked it. ### 4. License Grant to Us You grant GitHub and our Affiliates the right to store , host , archive , parse , display , and make copies of Your Content as necessary to provide , develop , and improve the Service , including by training AI Features , and for the purpose of training , developing , and improving artificial intelligence and machine learning models and technologies of our Affiliates. This license 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. For the avoidance of doubt , use of Your Content to develop , train , and improve artificial intelligence and machine learning models and technologies of GitHub and our Affiliates is within the scope of this license and does not constitute a sale or other restricted transfer of Your Content. ### 5. License Grant to Other Users Your Content that 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 within the Service in repositories they control). By making a repository public , you grant other Users a nonexclusive , worldwide license to use , display , perform and reproduce (by forking) Your Content through the Service as permitted by GitHub's functionality. You may grant additional rights by [adopting a license](/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository#including-an-open-source-license-in-your-repository). If you post Content you did not create or own , you are responsible for ensuring it is licensed under terms that permit these uses. ### 6. 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. If you have a separate agreement to license that Content 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 or our Affiliates , to enable GitHub and our Affiliates 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 GitHub 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. ### 8. Public Repositories and Lawful Access By choosing to contribute Content to a public repository , you are choosing to and directing us to make such Content accessible to everyone on the internet. Unless specifically set forth herein , these Terms do not restrict lawful access to or use of the contents of public repositories by third parties , or by GitHub or its Affiliates. ### 9. Access Reciprocity By using automated means to access , collect , or otherwise use (“Access”) any publicly accessible Content from the Service for the purpose of developing or training any commercially available artificial intelligence model , machine learning system , or similar technology (a "Commercial AI System") , you hereby waive any and all policies , terms , conditions , or contractual provisions governing products , services , websites or datasets you own or operate that would otherwise prohibit , restrict , or place conditions upon GitHub's Access to any publicly accessible data , information or content associated with your products or services , including for the purpose of developing or training any Commercial AI System. You further agree not to impose technical or other targeted measures to restrict or retaliate against such Access. This Section D.9 does not apply to Access solely for the purpose of academic research or if , on the date you Access the Content , the number of monthly active users of the products or services made available by you is less than 700 million in the preceding calendar month. For the purposes of this Section , "you" shall refer to you and any entity that directly or indirectly controls , is controlled by , or is under common control with you (affiliates). ## E. Private Repositories **Short version:** *We treat the content of private repositories as confidential , and we only access it as described in Section E.3 below—for security purposes , to assist the repository owner with a support matter , to maintain the integrity of the Service , to comply with our legal obligations , if we have reason to believe the contents are in violation of the law , or with your consent.* ### 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 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 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 You control access to the content of your private repositories. GitHub considers the contents of private repositories to be confidential to you , as set forth in Section E.2 , and GitHub personnel will not access private repository content without your consent except in the following circumstances: * for security purposes; * for automated scanning or manual review for known vulnerabilities , active malware , or other content known to violate our Terms of Service; * to assist the repository owner with a support matter; * to maintain the integrity of the Service; or * to comply with our legal obligations if we have reason to believe the contents are in violation of the law. 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 we need to provide the GitHub Service , we will provide an explanation of those rights. * If you provide your private repository content as Input to AI Features , we may use that Input to provide , develop , train , and improve the Service , including AI Features. Your ability to opt out under [Section J.3](#3-development-and-improvement-using-your-input-and-output) applies to this use of private repository content. We will not otherwise use your private repository contents to develop or improve the Service. Additionally , we may be [compelled by law](/en/site-policy/privacy-policies/github-general-privacy-statement#sharing-of-personal-data) to disclose the contents of your private repositories. GitHub will provide notice regarding our access to private repository content , unless [for legal disclosure](/en/site-policy/privacy-policies/github-general-privacy-statement) , to comply with our 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. ## F. 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](/en/site-policy/content-removal-policies/dmca-takedown-policy). If you are a copyright owner and you believe that content on GitHub violates your rights , please contact us via [our convenient DMCA form](https://github.com/contact/dmca) or by emailing <copyright@github.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](/en/site-policy/content-removal-policies/dmca-takedown-policy#f-repeated-infringement) of this policy. ## G. 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. GitHub's Rights to Content GitHub 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 © GitHub , 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 GitHub. ### 2. GitHub Trademarks and Logos If you’d like to use GitHub’s trademarks , you must follow all of our trademark guidelines , including those on our logos page: <https://github.com/logos>. ### 3. License to GitHub Policies This Agreement is licensed under this [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). For details , see our [site-policy repository](https://github.com/github/site-policy#license). ## H. API Terms **Short version:** *You agree to these Terms of Service , plus this Section H , when using any of GitHub's APIs (Application Programming Interface) , including use of the API through a third party product that accesses GitHub.* Abuse or excessively frequent requests to GitHub via the API may result in the temporary or permanent suspension of your Account's access to the API. GitHub , 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 GitHub's rate limitations. You may not use the API to download data or Content from GitHub for spamming purposes , including for the purposes of selling GitHub users' personal information , such as to recruiters , headhunters , and job boards. All use of the GitHub API is subject to these Terms of Service and the [GitHub Privacy Statement](https://github.com/site/privacy). GitHub may offer subscription-based access to our API for those Users who require high-throughput access or access that would result in resale of GitHub's Service. ## I. GitHub Additional Product Terms **Short version:** *You need to follow certain specific terms and conditions for GitHub's various features and products , and you agree to the Supplemental Terms and Conditions when you agree to this Agreement.* Some Service features may be subject to additional terms specific to that feature or product as set forth in the GitHub Additional Product Terms. By accessing or using the Services , you also agree to the [GitHub Additional Product Terms](/en/site-policy/github-terms/github-terms-for-additional-products-and-features). ## J. AI Features , Training , and Your Data ### 1. Applicability This section applies to all AI Features unless a specific feature has additional terms that expressly modify them. The training and data-use provisions in Section J.3 apply only to individual licenses. If your use of the Service is governed by a GitHub Customer Agreement or volume licensing agreement , those agreements govern the use of your data in connection with AI Features and Section J.3 does not apply to you. ### 2. Ownership GitHub does not claim ownership of your Input or Output. Output may contain material that resembles code or content in the model's training data or that is subject to third-party copyrights or open source license terms. You are responsible for determining whether your use of Output requires a third-party license and for complying with any such license. ### 3. Development and Improvement Using Your Input and Output We use your Inputs to generate Outputs and provide the AI Features. You also grant GitHub and its Affiliates a license to collect and use your Inputs and Outputs to develop , train and improve artificial intelligence and machine learning models and technologies including those that power AI Features , unless (a) you opt out through your account settings , or (b) your use of the Service is governed by a GitHub Customer Agreement or volume licensing agreement. If you opt out , GitHub will not collect or use your Inputs and Outputs for the purposes described in this paragraph from the effective date of your opt-out going forward. Unless you opt out , GitHub's Affiliates may use your Inputs and Outputs under this license in accordance with their applicable privacy and contractual obligations. This license does not , however , permit GitHub or its Affiliates to share your Inputs or Outputs with third-party AI model providers for their own independent model training purposes. The license in this Section J.3 is in addition to , and does not limit , the rights granted to GitHub and its Affiliates under Sections D.4 and D.8. This license does not extend to Your Content stored in repositories that are not provided as Input to an AI Feature. The opt-out right described in this section applies solely to the use of your Inputs and Outputs as described in this section , and does not apply to the license granted in Sections D.4-D.8 or to any Content that does not constitute Input or Output (including Content stored in public repositories). ### 4. Disclaimers Output is provided "as-is" and subject to the disclaimers in Section O. Without limiting Section O: Output may be inaccurate , incomplete , or non-functional. Output may resemble third-party code , including code under open source licenses. We do not guarantee that Output is free of errors , vulnerabilities , or intellectual property claims. You are responsible for reviewing , testing , and validating any Output before use. ### 5. Your Responsibility and Indemnity You are responsible for your use of Output , including ensuring it complies with applicable law and does not infringe third-party rights. Your indemnity obligations in Section Q apply to your use of AI Features and Output , including claims arising from Output you incorporate into your products or services. ## K. Beta Previews **Short version:** *Beta Previews may not be supported or may change at any time. You may receive confidential information through those programs that must remain confidential while the program is private. We'd love your feedback to make our Beta Previews better.* ### 1. Subject to Change Beta Previews may not be supported and may be changed at any time without notice. In addition , Beta Previews are not subject to the same security measures and auditing to which the Service has been and is subject. **By using a Beta Preview , you use it at your own risk.** ### 2. Confidentiality As a user of Beta Previews , you may get access to special information that isn’t available to the rest of the world. Due to the sensitive nature of this information , it’s important for us to make sure that you keep that information secret. **Confidentiality Obligations.** You agree that any non-public Beta Preview information we give you , such as information about a private Beta Preview , will be considered GitHub’s confidential information (collectively , “Confidential Information”) , regardless of whether it is marked or identified as such. You agree to only use such Confidential Information for the express purpose of testing and evaluating the Beta Preview (the “Purpose”) , and not for any other purpose. You should use the same degree of care as you would with your own confidential information , but no less than reasonable precautions to prevent any unauthorized use , disclosure , publication , or dissemination of our Confidential Information. You promise not to disclose , publish , or disseminate any Confidential Information to any third party , unless we don’t otherwise prohibit or restrict such disclosure (for example , you might be part of a GitHub-organized group discussion about a private Beta Preview feature). **Exceptions.** Confidential Information will not include information that is: (a) or becomes publicly available without breach of this Agreement through no act or inaction on your part (such as when a private Beta Preview becomes a public Beta Preview); (b) known to you before we disclose it to you; (c) independently developed by you without breach of any confidentiality obligation to us or any third party; or (d) disclosed with permission from GitHub. You will not violate the terms of this Agreement if you are required to disclose Confidential Information pursuant to operation of law , provided GitHub has been given reasonable advance written notice to object , unless prohibited by law. ### 3. Feedback We’re always trying to improve our products and services , and your feedback as a Beta Preview user will help us do that. If you choose to give us any ideas , know-how , algorithms , code contributions , suggestions , enhancement requests , recommendations or any other feedback for our products or services (collectively , “Feedback”) , you acknowledge and agree that GitHub will have a royalty-free , fully paid-up , worldwide , transferable , sub-licensable , irrevocable and perpetual license to implement , use , modify , commercially exploit and/or incorporate the Feedback into our products , services , and documentation. ## L. Payment **Short version:** *You are responsible for any fees associated with your use of GitHub. We are responsible for communicating those fees to you clearly and accurately , and letting you know well in advance if those prices change.* ### 1. Pricing Our pricing and payment terms are available at [github.com/pricing](https://github.com/pricing). If you agree to a subscription price , that will remain your price for the duration of the payment term; however , prices are subject to change at the end of a payment term. ### 2. Upgrades , Downgrades , and Changes * We will immediately bill you when you upgrade from the free plan to any paying plan. * If you change from a monthly billing plan to a yearly billing plan , GitHub will bill you for a full year at the next monthly billing date. * If you upgrade to a higher level of service , we will bill you for the upgraded plan immediately. * You may change your level of service at any time by [choosing a plan option](https://github.com/pricing) or going into your [Billing settings](https://github.com/settings/billing). If you choose to downgrade your Account , you may lose access to Content , features , or capacity of your Account. Please see our section on [Cancellation](#m-cancellation-and-termination) for information on getting a copy of that Content. ### 3. Billing Schedule; No Refunds **Payment Based on Plan** For monthly or yearly payment plans , the Service is billed in advance on a monthly or yearly basis respectively and is non-refundable. There will be no refunds or credits for partial months of service , downgrade refunds , or refunds for months unused with an open Account; however , the service will remain active for the length of the paid billing period. In order to treat everyone equally , no exceptions will be made. **Payment Based on Usage** Some Service features are billed based on your usage. A limited quantity of these Service features may be included in your plan for a limited term without additional charge. If you choose to use paid Service features beyond the quantity included in your plan , you pay for those Service features based on your actual usage in the preceding month. Monthly payment for these purchases will be charged on a periodic basis in arrears. See [GitHub Additional Product Terms for Details](/en/site-policy/github-terms/github-terms-for-additional-products-and-features). **Invoicing** For invoiced Users , User agrees to pay the fees in full , up front without deduction or setoff of any kind , in U.S. Dollars. User must pay the fees within thirty (30) days of the GitHub invoice date. Amounts payable under this Agreement are non-refundable , except as otherwise provided in this Agreement. If User fails to pay any fees on time , GitHub reserves the right , in addition to taking any other action at law or equity , to (i) charge interest on past due amounts at 1.0% per month or the highest interest rate allowed by law , whichever is less , and to charge all expenses of recovery , and (ii) terminate the applicable order form. User is solely responsible for all taxes , fees , duties and governmental assessments (except for taxes based on GitHub's net income) that are imposed or become due in connection with this Agreement. ### 4. Authorization By agreeing to these Terms , you are giving us permission to charge your on-file credit card , PayPal account , or other approved methods of payment for fees that you authorize for GitHub. ### 5. Responsibility for Payment You are responsible for all fees , including taxes , associated with your use of the Service. By using the Service , you agree to pay GitHub any charge incurred in connection with your use of the Service. If you dispute the matter , contact us through the [GitHub Support portal](https://support.github.com/). You are responsible for providing us with a valid means of payment for paid Accounts. Free Accounts are not required to provide payment information. ## M. Cancellation and Termination **Short version:** *You may close your Account at any time. If you do , we'll treat your information responsibly.* ### 1. Account Cancellation It is your responsibility to properly cancel your Account with GitHub. You can [cancel your Account at any time](/en/billing/how-tos/manage-plan-and-licenses/downgrade-plan) by going into your Settings in the global navigation bar at the top of the screen. The Account screen provides a simple , no questions asked cancellation link. We are not able to cancel Accounts in response to an email or phone request. ### 2. Upon Cancellation We will 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 and the Content of your repositories within 90 days of cancellation or termination (though some information may remain in encrypted backups). This information cannot be recovered once your Account is canceled. We will not delete Content that you have contributed to other Users' repositories or that other Users have forked. Upon request , we will make a reasonable effort to provide an Account owner with a copy of your lawful , non-infringing Account contents after Account cancellation , termination , or downgrade. You must make this request within 90 days of cancellation , termination , or downgrade. ### 3. GitHub May Terminate GitHub has the right to suspend or terminate your access to all or any part of the Website at any time , with or without cause , with or without notice , effective immediately. GitHub reserves the right to refuse service to anyone for any reason at any time. ### 4. Survival All provisions of this Agreement which , by their nature , should survive termination *will* survive termination — including , without limitation: ownership provisions , warranty disclaimers , indemnity , and limitations of liability. ## N. Communications with GitHub **Short version:** *We use email and other electronic means to stay in touch with our users.* ### 1. Electronic Communication Required For contractual purposes , you (1) consent to receive communications from us in an electronic form via the email address you have submitted or via the Service; and (2) agree that all Terms of Service , agreements , notices , disclosures , and other communications that we provide to you electronically satisfy any legal requirement that those communications would satisfy if they were on paper. This section does not affect your non-waivable rights. ### 2. Legal Notice to GitHub Must Be in Writing Communications made through email or GitHub Support's messaging system will not constitute legal notice to GitHub or any of its officers , employees , agents or representatives in any situation where notice to GitHub is required by contract or any law or regulation. Legal notice to GitHub must be in writing and [served on GitHub's legal agent](/en/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data#submitting-requests). ### 3. No Phone Support GitHub only offers support via email , in-Service communications , and electronic messages. We do not offer telephone support. ## O. Disclaimer of Warranties **Short version:** *We provide our service as is , and we make no promises or guarantees about this service. Please read this section carefully; you should understand what to expect.* GitHub provides the Website and the Service “as is” and “as available , ” without warranty of any kind. Without limiting this , we expressly disclaim all warranties , whether express , implied or statutory , regarding the Website and the Service including without limitation any warranty of merchantability , fitness for a particular purpose , title , security , accuracy and non-infringement. GitHub does not warrant that the Service will meet your requirements; that the Service will be uninterrupted , timely , secure , or error-free; that the information provided through the Service is accurate , reliable or correct; that any defects or errors will be corrected; that the Service will be available at any particular time or location; or that the Service is free of viruses or other harmful components. You assume full responsibility and risk of loss resulting from your downloading and/or use of files , information , content or other material obtained from the Service. ## P. Limitation of Liability **Short version:** *We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. Please read this section carefully; it limits our obligations to you.* You understand and agree that we will not be liable to you or any third party for any loss of profits , use , goodwill , or data , or for any incidental , indirect , special , consequential or exemplary damages , however arising , that result from <!-- markdownlint-disable GHD034 --> * the use , disclosure , or display of your User-Generated Content; * your use or inability to use the Service; * any modification , price change , suspension or discontinuance of the Service; * the Service generally or the software or systems that make the Service available; * unauthorized access to or alterations of your transmissions or data; * statements or conduct of any third party on the Service; * any other user interactions that you input or receive through your use of the Service; or * any other matter relating to the Service. <!-- markdownlint-enable GHD034 --> Our liability is limited whether or not we have been informed of the possibility of such damages , and even if a remedy set forth in this Agreement is found to have failed of its essential purpose. We will have no liability for any failure or delay due to matters beyond our reasonable control. ## Q. Release and Indemnification **Short version:** *You are responsible for your use of the service. If you harm someone else or get into a dispute with someone else , we will not be involved.* If you have a dispute with one or more Users , you agree to release GitHub from any and all claims , demands and damages (actual and consequential) of every kind and nature , known and unknown , arising out of or in any way connected with such disputes. You agree to indemnify us , defend us , and hold us harmless from and against any and all claims , liabilities , and expenses , including attorneys’ fees , arising out of your use of the Website and the Service , including but not limited to your violation of this Agreement , provided that GitHub (1) promptly gives you written notice of the claim , demand , suit or proceeding; (2) gives you sole control of the defense and settlement of the claim , demand , suit or proceeding (provided that you may not settle any claim , demand , suit or proceeding unless the settlement unconditionally releases GitHub of all liability); and (3) provides to you all reasonable assistance , at your expense. ## R. Changes to These Terms **Short version:** *We want our users to be informed of important changes to our terms , but some changes aren't that important — we don't want to bother you every time we fix a typo. So while we may modify this agreement at any time , we will notify users of any material changes and give you time to adjust to them.* We reserve the right , at our sole discretion , to amend these Terms of Service at any time and will update these Terms of Service in the event of any such amendments. We will notify our Users of material changes to this Agreement , such as price increases , at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications , your continued use of the Website constitutes agreement to our revisions of these Terms of Service. You can view all changes to these Terms in our [Site Policy](https://github.com/github/site-policy) repository. We reserve the right at any time and from time to time to modify or discontinue , temporarily or permanently , the Website (or any part of it) with or without notice. ## S. Miscellaneous ### 1. Governing Law Except to the extent applicable law provides otherwise , this Agreement between you and GitHub and any access to or use of the Website or the Service are governed by the federal laws of the United States of America and the laws of the State of California , without regard to conflict of law provisions. You and GitHub agree to submit to the exclusive jurisdiction and venue of the courts located in the City and County of San Francisco , California. However , any claim for injunctive relief with respect to a violation of section D.9 may be brought in any jurisdiction. ### 2. Non-Assignability GitHub may assign or delegate these Terms of Service and/or the [GitHub Privacy Statement](https://github.com/site/privacy) , in whole or in part , to any person or entity at any time with or without your consent , including the license grant in Section D.4. You may not assign or delegate any rights or obligations under the Terms of Service or Privacy Statement without our prior written consent , and any unauthorized assignment and delegation by you is void. ### 3. Section Headings and Summaries Throughout this Agreement , each section includes titles and brief summaries of the following terms and conditions. These section titles and brief summaries are not legally binding. ### 4. Severability , No Waiver , and Survival If any part of this Agreement is held invalid or unenforceable , that portion of the Agreement will be construed to reflect the parties’ original intent. The remaining portions will remain in full force and effect. Any failure on the part of GitHub to enforce any provision of this Agreement will not be considered a waiver of our right to enforce such provision. Our rights under this Agreement will survive any termination of this Agreement. ### 5. Amendments; Complete Agreement This Agreement may only be modified by a written amendment signed by an authorized representative of GitHub , or by the posting by GitHub of a revised version in accordance with [Section R. Changes to These Terms](#r-changes-to-these-terms). These Terms of Service , together with the GitHub Privacy Statement , represent the complete and exclusive statement of the agreement between you and us. This Agreement supersedes any proposal or prior agreement oral or written , and any other communications between you and GitHub relating to the subject matter of these terms including any confidentiality or nondisclosure agreements. ### 6. Questions Questions about the Terms of Service? Contact us through the [GitHub Support portal](https://support.github.com/). ,

sumanmal51509-svg

# GitHub Terms of Service <!-- markdownlint-disable search-replace --> Thank you for using GitHub! We're happy you're here. Please read this Terms of Service agreement carefully before accessing or using GitHub. Because it is such an important contract between us and our users , we have tried to make it as clear as possible. For your convenience , we have presented these terms in a short non-binding summary followed by the full legal terms. ## Summary | Section | What can you find there? | | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | [A. Definitions](#a-definitions) | Some basic terms , defined in a way that will help you understand this agreement. Refer back up to this section for clarification. | | [B. Account Terms](#b-account-terms) | These are the basic requirements of having an Account on GitHub. | | [C. Acceptable Use](#c-acceptable-use) | These are the basic rules you must follow when using your GitHub Account. | | [D. User-Generated Content](#d-user-generated-content) | You own the content you post on GitHub. However , you have some responsibilities regarding it , and we ask you to grant us some rights so we can provide services to you. | | [E. Private Repositories](#e-private-repositories) | This section talks about how GitHub will treat content you post in private repositories. | | [F. Copyright & DMCA Policy](#f-copyright-infringement-and-dmca-policy) | This section talks about how GitHub will respond if you believe someone is infringing your copyrights on GitHub. | | [G. Intellectual Property Notice](#g-intellectual-property-notice) | This describes GitHub's rights in the website and service. | | [H. API Terms](#h-api-terms) | These are the rules for using GitHub's APIs , whether you are using the API for development or data collection. | | [I. Additional Product Terms](#i-github-additional-product-terms) | We have a few specific rules for GitHub's features and products. | | [J. AI Features , Training , and Your Data](#j-ai-features-training-and-your-data) | These are the terms that apply to GitHub Copilot and other AI features , including how your data may be used for development and improvement of the artificial intelligence and machine learning models , and the controls available to you. | | [K. Beta Previews](#k-beta-previews) | These are some of the additional terms that apply to GitHub's features that are still in development. | | [L. Payment](#l-payment) | You are responsible for payment. We are responsible for billing you accurately. | | [M. Cancellation and Termination](#m-cancellation-and-termination) | You may cancel this agreement and close your Account at any time. | | [N. Communications with GitHub](#n-communications-with-github) | We only use email and other electronic means to stay in touch with our users. We do not provide phone support. | | [O. Disclaimer of Warranties](#o-disclaimer-of-warranties) | We provide our service as is , and we make no promises or guarantees about this service. **Please read this section carefully; you should understand what to expect.** | | [P. Limitation of Liability](#p-limitation-of-liability) | We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. **Please read this section carefully; it limits our obligations to you.** | | [Q. Release and Indemnification](#q-release-and-indemnification) | You are fully responsible for your use of the service. | | [R. Changes to these Terms of Service](#r-changes-to-these-terms) | We may modify this agreement , but we will give you 30 days' notice of material changes. | | [S. Miscellaneous](#s-miscellaneous) | Please see this section for legal details including our choice of law. | ## The GitHub Terms of Service Effective date: April 27 , 2026 ## A. 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.* 1. An "Account" represents your legal relationship with GitHub. A “Personal Account” represents an individual User’s authorization to log in to and use the Service and serves as a User’s identity on GitHub. “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 Personal Account can be a member of any number of Organizations. 2. 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 GitHub Privacy Statement , available at [github.com/site/privacy](https://github.com/site/privacy)) and procedures that we may publish from time to time on the Website. Most of our site policies are available at [docs.github.com/categories/site-policy](/en/site-policy). 3. "AI Feature" means any feature of GitHub or our Affiliates that uses machine learning or artificial intelligence to generate Output , including GitHub Copilot , Copilot Autofix , and any other feature identified as using machine learning or artificial intelligence in our documentation. 4. “Affiliate” means any entity that directly or indirectly controls , is controlled by , or is under common control with a party , where "control" means having more than fifty percent (50%) ownership or the right to direct the management of the entity. For the avoidance of doubt , Microsoft is an Affiliate of GitHub. 5. "Beta Previews" mean software , services , or features identified as alpha , beta , preview , early access , or evaluation , or words or phrases with similar meanings. 6. "Content" means code , text , data , documentation , images , graphics , software , packages , and other materials made available through the Service. 7. “GitHub , ” “We , ” and “Us” refer to GitHub , Inc. , as well as our directors , subsidiaries , contractors , licensors , officers , agents , and employees. 8. “Input” means any content or context provided to an AI Feature , including prompts , attachments , code in your workspace , and conversation history. 9. "Output" means responses and suggestions , including code or other material , generated by an AI Feature. 10. The “Service” refers to the applications , software , products , and services provided by GitHub , including through the Website and any Beta Previews. 11. “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](#5-additional-terms)). 12. "User-Generated Content" means Content that you or other users upload , submit , or create through the Service. 13. The “Website” refers to GitHub’s website located at [github.com](https://github.com/) , and all content , services , and products provided by GitHub at or through the Website. It also refers to GitHub-owned subdomains of github.com , such as [education.github.com](https://education.github.com/) and [pages.github.com](https://pages.github.com/). These Terms also govern GitHub’s conference websites , such as [githubuniverse.com](https://githubuniverse.com/) , and product websites , such as [electronjs.org](https://www.electronjs.org/). Occasionally , websites owned by GitHub 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. 14. "Your Content" means User-Generated Content that you upload , submit , or create , including your modifications to Content you have forked or cloned. It does not include the underlying Content created by others. ## B. Account Terms **Short version:** *Personal 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 Personal 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 Personal 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](#l-payment) , in which case additional information will be necessary for billing purposes. ### 3. Account Requirements We have a few simple rules for Accounts on GitHub'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 Personal 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. GitHub 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](#m-cancellation-and-termination). 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 Personal Accounts as your subscription allows. * You may not use GitHub in violation of export control or sanctions laws of the United States or any other applicable jurisdiction. You may not use GitHub if you are or are working on behalf of a [Specially Designated National (SDN)](https://www.treasury.gov/resource-center/sanctions/SDN-List/Pages/default.aspx) or a person subject to similar blocking or denied party prohibitions administered by a U.S. government agency. GitHub may allow persons in certain sanctioned countries or territories to access certain GitHub services pursuant to U.S. government authorizations. For more information , please see our [Export Controls policy](/en/site-policy/other-site-policies/github-and-trade-controls). ### 4. 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. GitHub cannot and will not be liable for any loss or damage from your failure to comply with this security obligation. * You will promptly notify GitHub by contacting us through the [GitHub Support portal](https://support.github.com/) 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 GitHub. For example , you may be a member of an organization on GitHub with its own terms or license agreements; you may download an application that integrates with GitHub; or you may use GitHub 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 GitHub Service in a government capacity , this [Government Amendment to GitHub Terms of Service](/en/site-policy/site-policy-deprecated/amendment-to-github-terms-of-service-applicable-to-us-federal-government-users) applies to you , and you agree to its provisions. If you have signed up for GitHub Enterprise Cloud , the [Enterprise Cloud Addendum](/en/site-policy/site-policy-deprecated/github-enterprise-service-level-agreement) applies to you , and you agree to its provisions. ## C. Acceptable Use **Short version:** *GitHub 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](/en/site-policy/acceptable-use-policies/github-acceptable-use-policies) or [Community Guidelines](/en/site-policy/github-terms/github-community-guidelines). ## D. 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 are responsible for Your Content and any harm resulting from it. This includes Content you post , upload , or make available through the Service. We are not responsible for any public display or misuse of Your Content. ### 2. GitHub May Remove Content We may refuse or remove User-Generated Content that violates applicable law or our terms and policies. We access private repositories only as described in Section E. Content displayed on GitHub Mobile may be subject to app store terms. ### 3. Ownership and License Grants You own Your Content. If you post Content you did not create , you are responsible for ensuring you have the right to post it and for complying with any applicable licenses. You grant us and other Users the licenses in Sections D.4–D.8. These licenses apply to Your Content. If Your Content already includes a license granting us the permissions we need , no additional license is required. You will not receive payment for these rights. These licenses end when you remove Your Content , unless other Users have forked it. ### 4. License Grant to Us You grant GitHub and our Affiliates the right to store , host , archive , parse , display , and make copies of Your Content as necessary to provide , develop , and improve the Service , including by training AI Features , and for the purpose of training , developing , and improving artificial intelligence and machine learning models and technologies of our Affiliates. This license 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. For the avoidance of doubt , use of Your Content to develop , train , and improve artificial intelligence and machine learning models and technologies of GitHub and our Affiliates is within the scope of this license and does not constitute a sale or other restricted transfer of Your Content. ### 5. License Grant to Other Users Your Content that 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 within the Service in repositories they control). By making a repository public , you grant other Users a nonexclusive , worldwide license to use , display , perform and reproduce (by forking) Your Content through the Service as permitted by GitHub's functionality. You may grant additional rights by [adopting a license](/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository#including-an-open-source-license-in-your-repository). If you post Content you did not create or own , you are responsible for ensuring it is licensed under terms that permit these uses. ### 6. 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. If you have a separate agreement to license that Content 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 or our Affiliates , to enable GitHub and our Affiliates 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 GitHub 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. ### 8. Public Repositories and Lawful Access By choosing to contribute Content to a public repository , you are choosing to and directing us to make such Content accessible to everyone on the internet. Unless specifically set forth herein , these Terms do not restrict lawful access to or use of the contents of public repositories by third parties , or by GitHub or its Affiliates. ### 9. Access Reciprocity By using automated means to access , collect , or otherwise use (“Access”) any publicly accessible Content from the Service for the purpose of developing or training any commercially available artificial intelligence model , machine learning system , or similar technology (a "Commercial AI System") , you hereby waive any and all policies , terms , conditions , or contractual provisions governing products , services , websites or datasets you own or operate that would otherwise prohibit , restrict , or place conditions upon GitHub's Access to any publicly accessible data , information or content associated with your products or services , including for the purpose of developing or training any Commercial AI System. You further agree not to impose technical or other targeted measures to restrict or retaliate against such Access. This Section D.9 does not apply to Access solely for the purpose of academic research or if , on the date you Access the Content , the number of monthly active users of the products or services made available by you is less than 700 million in the preceding calendar month. For the purposes of this Section , "you" shall refer to you and any entity that directly or indirectly controls , is controlled by , or is under common control with you (affiliates). ## E. Private Repositories **Short version:** *We treat the content of private repositories as confidential , and we only access it as described in Section E.3 below—for security purposes , to assist the repository owner with a support matter , to maintain the integrity of the Service , to comply with our legal obligations , if we have reason to believe the contents are in violation of the law , or with your consent.* ### 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 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 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 You control access to the content of your private repositories. GitHub considers the contents of private repositories to be confidential to you , as set forth in Section E.2 , and GitHub personnel will not access private repository content without your consent except in the following circumstances: * for security purposes; * for automated scanning or manual review for known vulnerabilities , active malware , or other content known to violate our Terms of Service; * to assist the repository owner with a support matter; * to maintain the integrity of the Service; or * to comply with our legal obligations if we have reason to believe the contents are in violation of the law. 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 we need to provide the GitHub Service , we will provide an explanation of those rights. * If you provide your private repository content as Input to AI Features , we may use that Input to provide , develop , train , and improve the Service , including AI Features. Your ability to opt out under [Section J.3](#3-development-and-improvement-using-your-input-and-output) applies to this use of private repository content. We will not otherwise use your private repository contents to develop or improve the Service. Additionally , we may be [compelled by law](/en/site-policy/privacy-policies/github-general-privacy-statement#sharing-of-personal-data) to disclose the contents of your private repositories. GitHub will provide notice regarding our access to private repository content , unless [for legal disclosure](/en/site-policy/privacy-policies/github-general-privacy-statement) , to comply with our 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. ## F. 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](/en/site-policy/content-removal-policies/dmca-takedown-policy). If you are a copyright owner and you believe that content on GitHub violates your rights , please contact us via [our convenient DMCA form](https://github.com/contact/dmca) or by emailing <copyright@github.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](/en/site-policy/content-removal-policies/dmca-takedown-policy#f-repeated-infringement) of this policy. ## G. 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. GitHub's Rights to Content GitHub 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 © GitHub , 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 GitHub. ### 2. GitHub Trademarks and Logos If you’d like to use GitHub’s trademarks , you must follow all of our trademark guidelines , including those on our logos page: <https://github.com/logos>. ### 3. License to GitHub Policies This Agreement is licensed under this [Creative Commons Zero license](https://creativecommons.org/publicdomain/zero/1.0/). For details , see our [site-policy repository](https://github.com/github/site-policy#license). ## H. API Terms **Short version:** *You agree to these Terms of Service , plus this Section H , when using any of GitHub's APIs (Application Programming Interface) , including use of the API through a third party product that accesses GitHub.* Abuse or excessively frequent requests to GitHub via the API may result in the temporary or permanent suspension of your Account's access to the API. GitHub , 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 GitHub's rate limitations. You may not use the API to download data or Content from GitHub for spamming purposes , including for the purposes of selling GitHub users' personal information , such as to recruiters , headhunters , and job boards. All use of the GitHub API is subject to these Terms of Service and the [GitHub Privacy Statement](https://github.com/site/privacy). GitHub may offer subscription-based access to our API for those Users who require high-throughput access or access that would result in resale of GitHub's Service. ## I. GitHub Additional Product Terms **Short version:** *You need to follow certain specific terms and conditions for GitHub's various features and products , and you agree to the Supplemental Terms and Conditions when you agree to this Agreement.* Some Service features may be subject to additional terms specific to that feature or product as set forth in the GitHub Additional Product Terms. By accessing or using the Services , you also agree to the [GitHub Additional Product Terms](/en/site-policy/github-terms/github-terms-for-additional-products-and-features). ## J. AI Features , Training , and Your Data ### 1. Applicability This section applies to all AI Features unless a specific feature has additional terms that expressly modify them. The training and data-use provisions in Section J.3 apply only to individual licenses. If your use of the Service is governed by a GitHub Customer Agreement or volume licensing agreement , those agreements govern the use of your data in connection with AI Features and Section J.3 does not apply to you. ### 2. Ownership GitHub does not claim ownership of your Input or Output. Output may contain material that resembles code or content in the model's training data or that is subject to third-party copyrights or open source license terms. You are responsible for determining whether your use of Output requires a third-party license and for complying with any such license. ### 3. Development and Improvement Using Your Input and Output We use your Inputs to generate Outputs and provide the AI Features. You also grant GitHub and its Affiliates a license to collect and use your Inputs and Outputs to develop , train and improve artificial intelligence and machine learning models and technologies including those that power AI Features , unless (a) you opt out through your account settings , or (b) your use of the Service is governed by a GitHub Customer Agreement or volume licensing agreement. If you opt out , GitHub will not collect or use your Inputs and Outputs for the purposes described in this paragraph from the effective date of your opt-out going forward. Unless you opt out , GitHub's Affiliates may use your Inputs and Outputs under this license in accordance with their applicable privacy and contractual obligations. This license does not , however , permit GitHub or its Affiliates to share your Inputs or Outputs with third-party AI model providers for their own independent model training purposes. The license in this Section J.3 is in addition to , and does not limit , the rights granted to GitHub and its Affiliates under Sections D.4 and D.8. This license does not extend to Your Content stored in repositories that are not provided as Input to an AI Feature. The opt-out right described in this section applies solely to the use of your Inputs and Outputs as described in this section , and does not apply to the license granted in Sections D.4-D.8 or to any Content that does not constitute Input or Output (including Content stored in public repositories). ### 4. Disclaimers Output is provided "as-is" and subject to the disclaimers in Section O. Without limiting Section O: Output may be inaccurate , incomplete , or non-functional. Output may resemble third-party code , including code under open source licenses. We do not guarantee that Output is free of errors , vulnerabilities , or intellectual property claims. You are responsible for reviewing , testing , and validating any Output before use. ### 5. Your Responsibility and Indemnity You are responsible for your use of Output , including ensuring it complies with applicable law and does not infringe third-party rights. Your indemnity obligations in Section Q apply to your use of AI Features and Output , including claims arising from Output you incorporate into your products or services. ## K. Beta Previews **Short version:** *Beta Previews may not be supported or may change at any time. You may receive confidential information through those programs that must remain confidential while the program is private. We'd love your feedback to make our Beta Previews better.* ### 1. Subject to Change Beta Previews may not be supported and may be changed at any time without notice. In addition , Beta Previews are not subject to the same security measures and auditing to which the Service has been and is subject. **By using a Beta Preview , you use it at your own risk.** ### 2. Confidentiality As a user of Beta Previews , you may get access to special information that isn’t available to the rest of the world. Due to the sensitive nature of this information , it’s important for us to make sure that you keep that information secret. **Confidentiality Obligations.** You agree that any non-public Beta Preview information we give you , such as information about a private Beta Preview , will be considered GitHub’s confidential information (collectively , “Confidential Information”) , regardless of whether it is marked or identified as such. You agree to only use such Confidential Information for the express purpose of testing and evaluating the Beta Preview (the “Purpose”) , and not for any other purpose. You should use the same degree of care as you would with your own confidential information , but no less than reasonable precautions to prevent any unauthorized use , disclosure , publication , or dissemination of our Confidential Information. You promise not to disclose , publish , or disseminate any Confidential Information to any third party , unless we don’t otherwise prohibit or restrict such disclosure (for example , you might be part of a GitHub-organized group discussion about a private Beta Preview feature). **Exceptions.** Confidential Information will not include information that is: (a) or becomes publicly available without breach of this Agreement through no act or inaction on your part (such as when a private Beta Preview becomes a public Beta Preview); (b) known to you before we disclose it to you; (c) independently developed by you without breach of any confidentiality obligation to us or any third party; or (d) disclosed with permission from GitHub. You will not violate the terms of this Agreement if you are required to disclose Confidential Information pursuant to operation of law , provided GitHub has been given reasonable advance written notice to object , unless prohibited by law. ### 3. Feedback We’re always trying to improve our products and services , and your feedback as a Beta Preview user will help us do that. If you choose to give us any ideas , know-how , algorithms , code contributions , suggestions , enhancement requests , recommendations or any other feedback for our products or services (collectively , “Feedback”) , you acknowledge and agree that GitHub will have a royalty-free , fully paid-up , worldwide , transferable , sub-licensable , irrevocable and perpetual license to implement , use , modify , commercially exploit and/or incorporate the Feedback into our products , services , and documentation. ## L. Payment **Short version:** *You are responsible for any fees associated with your use of GitHub. We are responsible for communicating those fees to you clearly and accurately , and letting you know well in advance if those prices change.* ### 1. Pricing Our pricing and payment terms are available at [github.com/pricing](https://github.com/pricing). If you agree to a subscription price , that will remain your price for the duration of the payment term; however , prices are subject to change at the end of a payment term. ### 2. Upgrades , Downgrades , and Changes * We will immediately bill you when you upgrade from the free plan to any paying plan. * If you change from a monthly billing plan to a yearly billing plan , GitHub will bill you for a full year at the next monthly billing date. * If you upgrade to a higher level of service , we will bill you for the upgraded plan immediately. * You may change your level of service at any time by [choosing a plan option](https://github.com/pricing) or going into your [Billing settings](https://github.com/settings/billing). If you choose to downgrade your Account , you may lose access to Content , features , or capacity of your Account. Please see our section on [Cancellation](#m-cancellation-and-termination) for information on getting a copy of that Content. ### 3. Billing Schedule; No Refunds **Payment Based on Plan** For monthly or yearly payment plans , the Service is billed in advance on a monthly or yearly basis respectively and is non-refundable. There will be no refunds or credits for partial months of service , downgrade refunds , or refunds for months unused with an open Account; however , the service will remain active for the length of the paid billing period. In order to treat everyone equally , no exceptions will be made. **Payment Based on Usage** Some Service features are billed based on your usage. A limited quantity of these Service features may be included in your plan for a limited term without additional charge. If you choose to use paid Service features beyond the quantity included in your plan , you pay for those Service features based on your actual usage in the preceding month. Monthly payment for these purchases will be charged on a periodic basis in arrears. See [GitHub Additional Product Terms for Details](/en/site-policy/github-terms/github-terms-for-additional-products-and-features). **Invoicing** For invoiced Users , User agrees to pay the fees in full , up front without deduction or setoff of any kind , in U.S. Dollars. User must pay the fees within thirty (30) days of the GitHub invoice date. Amounts payable under this Agreement are non-refundable , except as otherwise provided in this Agreement. If User fails to pay any fees on time , GitHub reserves the right , in addition to taking any other action at law or equity , to (i) charge interest on past due amounts at 1.0% per month or the highest interest rate allowed by law , whichever is less , and to charge all expenses of recovery , and (ii) terminate the applicable order form. User is solely responsible for all taxes , fees , duties and governmental assessments (except for taxes based on GitHub's net income) that are imposed or become due in connection with this Agreement. ### 4. Authorization By agreeing to these Terms , you are giving us permission to charge your on-file credit card , PayPal account , or other approved methods of payment for fees that you authorize for GitHub. ### 5. Responsibility for Payment You are responsible for all fees , including taxes , associated with your use of the Service. By using the Service , you agree to pay GitHub any charge incurred in connection with your use of the Service. If you dispute the matter , contact us through the [GitHub Support portal](https://support.github.com/). You are responsible for providing us with a valid means of payment for paid Accounts. Free Accounts are not required to provide payment information. ## M. Cancellation and Termination **Short version:** *You may close your Account at any time. If you do , we'll treat your information responsibly.* ### 1. Account Cancellation It is your responsibility to properly cancel your Account with GitHub. You can [cancel your Account at any time](/en/billing/how-tos/manage-plan-and-licenses/downgrade-plan) by going into your Settings in the global navigation bar at the top of the screen. The Account screen provides a simple , no questions asked cancellation link. We are not able to cancel Accounts in response to an email or phone request. ### 2. Upon Cancellation We will 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 and the Content of your repositories within 90 days of cancellation or termination (though some information may remain in encrypted backups). This information cannot be recovered once your Account is canceled. We will not delete Content that you have contributed to other Users' repositories or that other Users have forked. Upon request , we will make a reasonable effort to provide an Account owner with a copy of your lawful , non-infringing Account contents after Account cancellation , termination , or downgrade. You must make this request within 90 days of cancellation , termination , or downgrade. ### 3. GitHub May Terminate GitHub has the right to suspend or terminate your access to all or any part of the Website at any time , with or without cause , with or without notice , effective immediately. GitHub reserves the right to refuse service to anyone for any reason at any time. ### 4. Survival All provisions of this Agreement which , by their nature , should survive termination *will* survive termination — including , without limitation: ownership provisions , warranty disclaimers , indemnity , and limitations of liability. ## N. Communications with GitHub **Short version:** *We use email and other electronic means to stay in touch with our users.* ### 1. Electronic Communication Required For contractual purposes , you (1) consent to receive communications from us in an electronic form via the email address you have submitted or via the Service; and (2) agree that all Terms of Service , agreements , notices , disclosures , and other communications that we provide to you electronically satisfy any legal requirement that those communications would satisfy if they were on paper. This section does not affect your non-waivable rights. ### 2. Legal Notice to GitHub Must Be in Writing Communications made through email or GitHub Support's messaging system will not constitute legal notice to GitHub or any of its officers , employees , agents or representatives in any situation where notice to GitHub is required by contract or any law or regulation. Legal notice to GitHub must be in writing and [served on GitHub's legal agent](/en/site-policy/other-site-policies/guidelines-for-legal-requests-of-user-data#submitting-requests). ### 3. No Phone Support GitHub only offers support via email , in-Service communications , and electronic messages. We do not offer telephone support. ## O. Disclaimer of Warranties **Short version:** *We provide our service as is , and we make no promises or guarantees about this service. Please read this section carefully; you should understand what to expect.* GitHub provides the Website and the Service “as is” and “as available , ” without warranty of any kind. Without limiting this , we expressly disclaim all warranties , whether express , implied or statutory , regarding the Website and the Service including without limitation any warranty of merchantability , fitness for a particular purpose , title , security , accuracy and non-infringement. GitHub does not warrant that the Service will meet your requirements; that the Service will be uninterrupted , timely , secure , or error-free; that the information provided through the Service is accurate , reliable or correct; that any defects or errors will be corrected; that the Service will be available at any particular time or location; or that the Service is free of viruses or other harmful components. You assume full responsibility and risk of loss resulting from your downloading and/or use of files , information , content or other material obtained from the Service. ## P. Limitation of Liability **Short version:** *We will not be liable for damages or losses arising from your use or inability to use the service or otherwise arising under this agreement. Please read this section carefully; it limits our obligations to you.* You understand and agree that we will not be liable to you or any third party for any loss of profits , use , goodwill , or data , or for any incidental , indirect , special , consequential or exemplary damages , however arising , that result from <!-- markdownlint-disable GHD034 --> * the use , disclosure , or display of your User-Generated Content; * your use or inability to use the Service; * any modification , price change , suspension or discontinuance of the Service; * the Service generally or the software or systems that make the Service available; * unauthorized access to or alterations of your transmissions or data; * statements or conduct of any third party on the Service; * any other user interactions that you input or receive through your use of the Service; or * any other matter relating to the Service. <!-- markdownlint-enable GHD034 --> Our liability is limited whether or not we have been informed of the possibility of such damages , and even if a remedy set forth in this Agreement is found to have failed of its essential purpose. We will have no liability for any failure or delay due to matters beyond our reasonable control. ## Q. Release and Indemnification **Short version:** *You are responsible for your use of the service. If you harm someone else or get into a dispute with someone else , we will not be involved.* If you have a dispute with one or more Users , you agree to release GitHub from any and all claims , demands and damages (actual and consequential) of every kind and nature , known and unknown , arising out of or in any way connected with such disputes. You agree to indemnify us , defend us , and hold us harmless from and against any and all claims , liabilities , and expenses , including attorneys’ fees , arising out of your use of the Website and the Service , including but not limited to your violation of this Agreement , provided that GitHub (1) promptly gives you written notice of the claim , demand , suit or proceeding; (2) gives you sole control of the defense and settlement of the claim , demand , suit or proceeding (provided that you may not settle any claim , demand , suit or proceeding unless the settlement unconditionally releases GitHub of all liability); and (3) provides to you all reasonable assistance , at your expense. ## R. Changes to These Terms **Short version:** *We want our users to be informed of important changes to our terms , but some changes aren't that important — we don't want to bother you every time we fix a typo. So while we may modify this agreement at any time , we will notify users of any material changes and give you time to adjust to them.* We reserve the right , at our sole discretion , to amend these Terms of Service at any time and will update these Terms of Service in the event of any such amendments. We will notify our Users of material changes to this Agreement , such as price increases , at least 30 days prior to the change taking effect by posting a notice on our Website or sending email to the primary email address specified in your GitHub account. Customer's continued use of the Service after those 30 days constitutes agreement to those revisions of this Agreement. For any other modifications , your continued use of the Website constitutes agreement to our revisions of these Terms of Service. You can view all changes to these Terms in our [Site Policy](https://github.com/github/site-policy) repository. We reserve the right at any time and from time to time to modify or discontinue , temporarily or permanently , the Website (or any part of it) with or without notice. ## S. Miscellaneous ### 1. Governing Law Except to the extent applicable law provides otherwise , this Agreement between you and GitHub and any access to or use of the Website or the Service are governed by the federal laws of the United States of America and the laws of the State of California , without regard to conflict of law provisions. You and GitHub agree to submit to the exclusive jurisdiction and venue of the courts located in the City and County of San Francisco , California. However , any claim for injunctive relief with respect to a violation of section D.9 may be brought in any jurisdiction. ### 2. Non-Assignability GitHub may assign or delegate these Terms of Service and/or the [GitHub Privacy Statement](https://github.com/site/privacy) , in whole or in part , to any person or entity at any time with or without your consent , including the license grant in Section D.4. You may not assign or delegate any rights or obligations under the Terms of Service or Privacy Statement without our prior written consent , and any unauthorized assignment and delegation by you is void. ### 3. Section Headings and Summaries Throughout this Agreement , each section includes titles and brief summaries of the following terms and conditions. These section titles and brief summaries are not legally binding. ### 4. Severability , No Waiver , and Survival If any part of this Agreement is held invalid or unenforceable , that portion of the Agreement will be construed to reflect the parties’ original intent. The remaining portions will remain in full force and effect. Any failure on the part of GitHub to enforce any provision of this Agreement will not be considered a waiver of our right to enforce such provision. Our rights under this Agreement will survive any termination of this Agreement. ### 5. Amendments; Complete Agreement This Agreement may only be modified by a written amendment signed by an authorized representative of GitHub , or by the posting by GitHub of a revised version in accordance with [Section R. Changes to These Terms](#r-changes-to-these-terms). These Terms of Service , together with the GitHub Privacy Statement , represent the complete and exclusive statement of the agreement between you and us. This Agreement supersedes any proposal or prior agreement oral or written , and any other communications between you and GitHub relating to the subject matter of these terms including any confidentiality or nondisclosure agreements. ### 6. Questions Questions about the Terms of Service? Contact us through the [GitHub Support portal](https://support.github.com/). ,

aiWebX

The image features three pink tulips with water droplets on their petals , positioned diagonally from the top right to the bottom left. The flowers have green stems and leaves extending outward. Surrounding the tulips are numerous small clear crystals scattered across a light pink background. Interspersed among the crystals are several silver heart-shaped ornaments of varying sizes; some hearts appear textured or encrusted with tiny stones. Additionally , there are multiple large round pearls in shades of white and off-white placed near the lower part of the composition. One pearl is situated at the very top center above the uppermost tulip petal , another lies next to the middle flower's stem towards the mid-left , two more rest close together below this one (one slightly larger) , followed by smaller clusters spread out around them—some forming loose groups while others stand alone further apart toward the edges where they blend into the crystal scattering. ,

aguranata_98094

A whimsical character scene featuring a cute anthropomorphic cat with large , expressive purple eyes and fluffy white fur , standing elegantly in a traditional kimono with intricate blue and gold designs. The background is a serene night setting illuminated by soft lantern lights and a full moon casting a gentle glow. The cat's long tail swirls gracefully , enhancing the sense of movement. This enchanting atmosphere is rich with magical elements , capturing a sense of wonder and tranquility. Soft bokeh effects blur the background slightly , focusing attention on the cat's detailed facial features and delicate attire. Use vibrant colors to enhance the whimsical feel , and apply a smooth , painterly style to blend realism with fantasy. Additionally , ensure depth and contrast in lighting , highlighting the character's features and the surrounding environment. ,

awdfjdsl

The image portrays a male elf with striking features. His hair is a light blonde , and styled in a sophisticated updo. The hair is pulled back from his face , with the majority gathered into a bun or knot at the crown of his head , leaving a long , flowing section cascading down his back. The length of the loose hair reaches below his shoulders. His skin tone is fair , almost porcelain , with a subtle rosy undertone. His most distinctive features are his pointed ears , characteristic of elves , which are clearly visible. His facial features are delicate yet strong. He has large , expressive light grey or blue eyes , which are emphasized by well-defined eyebrows. His nose is straight and slender , and his mouth is slightly full with a soft , almost neutral expression. While his expression is not overtly emotional , there is a hint of seriousness and perhaps determination in his gaze. He has a slender but not frail build. His posture is erect and confident , suggesting strength and self-assurance. The elf's attire consists of a suit of armor that appears to be made of metal , with a predominantly silver or steel finish. The armor is detailed with intricate designs and textures , suggesting craftsmanship and possibly a high social standing. Underneath the armor , a glimpse of an olive-green or muted green garment is visible at the collar. He wears a silver circlet or diadem on his forehead , adorned with what appears to be a small gemstone or similar embellishment in the center. Additionally , he has simple , small earrings hanging from his ears. Overall , the elf's appearance combines elements of both elegance and strength , suggesting a character who may be both powerful and refined. ,

awdfjdsl

The image portrays a male elf with striking features. His hair is a light blonde , and styled in a sophisticated updo. The hair is pulled back from his face , with the majority gathered into a bun or knot at the crown of his head , leaving a long , flowing section cascading down his back. The length of the loose hair reaches below his shoulders. His skin tone is fair , almost porcelain , with a subtle rosy undertone. His most distinctive features are his pointed ears , characteristic of elves , which are clearly visible. His facial features are delicate yet strong. He has large , expressive light grey or blue eyes , which are emphasized by well-defined eyebrows. His nose is straight and slender , and his mouth is slightly full with a soft , almost neutral expression. While his expression is not overtly emotional , there is a hint of seriousness and perhaps determination in his gaze. He has a slender but not frail build. His posture is erect and confident , suggesting strength and self-assurance. The elf's attire consists of a suit of armor that appears to be made of metal , with a predominantly silver or steel finish. The armor is detailed with intricate designs and textures , suggesting craftsmanship and possibly a high social standing. Underneath the armor , a glimpse of an olive-green or muted green garment is visible at the collar. He wears a silver circlet or diadem on his forehead , adorned with what appears to be a small gemstone or similar embellishment in the center. Additionally , he has simple , small earrings hanging from his ears. Overall , the elf's appearance combines elements of both elegance and strength , suggesting a character who may be both powerful and refined. ,

awdfjdsl

The image portrays a male elf with striking features. His hair is a light blonde , and styled in a sophisticated updo. The hair is pulled back from his face , with the majority gathered into a bun or knot at the crown of his head , leaving a long , flowing section cascading down his back. The length of the loose hair reaches below his shoulders. His skin tone is fair , almost porcelain , with a subtle rosy undertone. His most distinctive features are his pointed ears , characteristic of elves , which are clearly visible. His facial features are delicate yet strong. He has large , expressive light grey or blue eyes , which are emphasized by well-defined eyebrows. His nose is straight and slender , and his mouth is slightly full with a soft , almost neutral expression. While his expression is not overtly emotional , there is a hint of seriousness and perhaps determination in his gaze. He has a slender but not frail build. His posture is erect and confident , suggesting strength and self-assurance. The elf's attire consists of a suit of armor that appears to be made of metal , with a predominantly silver or steel finish. The armor is detailed with intricate designs and textures , suggesting craftsmanship and possibly a high social standing. Underneath the armor , a glimpse of an olive-green or muted green garment is visible at the collar. He wears a silver circlet or diadem on his forehead , adorned with what appears to be a small gemstone or similar embellishment in the center. Additionally , he has simple , small earrings hanging from his ears. Overall , the elf's appearance combines elements of both elegance and strength , suggesting a character who may be both powerful and refined. ,

awdfjdsl

The image portrays a male elf with striking features. His hair is a light blonde , and styled in a sophisticated updo. The hair is pulled back from his face , with the majority gathered into a bun or knot at the crown of his head , leaving a long , flowing section cascading down his back. The length of the loose hair reaches below his shoulders. His skin tone is fair , almost porcelain , with a subtle rosy undertone. His most distinctive features are his pointed ears , characteristic of elves , which are clearly visible. His facial features are delicate yet strong. He has large , expressive light grey or blue eyes , which are emphasized by well-defined eyebrows. His nose is straight and slender , and his mouth is slightly full with a soft , almost neutral expression. While his expression is not overtly emotional , there is a hint of seriousness and perhaps determination in his gaze. He has a slender but not frail build. His posture is erect and confident , suggesting strength and self-assurance. The elf's attire consists of a suit of armor that appears to be made of metal , with a predominantly silver or steel finish. The armor is detailed with intricate designs and textures , suggesting craftsmanship and possibly a high social standing. Underneath the armor , a glimpse of an olive-green or muted green garment is visible at the collar. He wears a silver circlet or diadem on his forehead , adorned with what appears to be a small gemstone or similar embellishment in the center. Additionally , he has simple , small earrings hanging from his ears. Overall , the elf's appearance combines elements of both elegance and strength , suggesting a character who may be both powerful and refined. ,

awdfjdsl

The image portrays a male elf with striking features. His hair is a light blonde , and styled in a sophisticated updo. The hair is pulled back from his face , with the majority gathered into a bun or knot at the crown of his head , leaving a long , flowing section cascading down his back. The length of the loose hair reaches below his shoulders. His skin tone is fair , almost porcelain , with a subtle rosy undertone. His most distinctive features are his pointed ears , characteristic of elves , which are clearly visible. His facial features are delicate yet strong. He has large , expressive light grey or blue eyes , which are emphasized by well-defined eyebrows. His nose is straight and slender , and his mouth is slightly full with a soft , almost neutral expression. While his expression is not overtly emotional , there is a hint of seriousness and perhaps determination in his gaze. He has a slender but not frail build. His posture is erect and confident , suggesting strength and self-assurance. The elf's attire consists of a suit of armor that appears to be made of metal , with a predominantly silver or steel finish. The armor is detailed with intricate designs and textures , suggesting craftsmanship and possibly a high social standing. Underneath the armor , a glimpse of an olive-green or muted green garment is visible at the collar. He wears a silver circlet or diadem on his forehead , adorned with what appears to be a small gemstone or similar embellishment in the center. Additionally , he has simple , small earrings hanging from his ears. Overall , the elf's appearance combines elements of both elegance and strength , suggesting a character who may be both powerful and refined. ,

awdfjdsl

The image portrays a male elf with striking features. His hair is a light blonde , and styled in a sophisticated updo. The hair is pulled back from his face , with the majority gathered into a bun or knot at the crown of his head , leaving a long , flowing section cascading down his back. The length of the loose hair reaches below his shoulders. His skin tone is fair , almost porcelain , with a subtle rosy undertone. His most distinctive features are his pointed ears , characteristic of elves , which are clearly visible. His facial features are delicate yet strong. He has large , expressive light grey or blue eyes , which are emphasized by well-defined eyebrows. His nose is straight and slender , and his mouth is slightly full with a soft , almost neutral expression. While his expression is not overtly emotional , there is a hint of seriousness and perhaps determination in his gaze. He has a slender but not frail build. His posture is erect and confident , suggesting strength and self-assurance. The elf's attire consists of a suit of armor that appears to be made of metal , with a predominantly silver or steel finish. The armor is detailed with intricate designs and textures , suggesting craftsmanship and possibly a high social standing. Underneath the armor , a glimpse of an olive-green or muted green garment is visible at the collar. He wears a silver circlet or diadem on his forehead , adorned with what appears to be a small gemstone or similar embellishment in the center. Additionally , he has simple , small earrings hanging from his ears. Overall , the elf's appearance combines elements of both elegance and strength , suggesting a character who may be both powerful and refined. ,

awdfjdsl

The image portrays a male elf with striking features. His hair is a light blonde , and styled in a sophisticated updo. The hair is pulled back from his face , with the majority gathered into a bun or knot at the crown of his head , leaving a long , flowing section cascading down his back. The length of the loose hair reaches below his shoulders. His skin tone is fair , almost porcelain , with a subtle rosy undertone. His most distinctive features are his pointed ears , characteristic of elves , which are clearly visible. His facial features are delicate yet strong. He has large , expressive light grey or blue eyes , which are emphasized by well-defined eyebrows. His nose is straight and slender , and his mouth is slightly full with a soft , almost neutral expression. While his expression is not overtly emotional , there is a hint of seriousness and perhaps determination in his gaze. He has a slender but not frail build. His posture is erect and confident , suggesting strength and self-assurance. The elf's attire consists of a suit of armor that appears to be made of metal , with a predominantly silver or steel finish. The armor is detailed with intricate designs and textures , suggesting craftsmanship and possibly a high social standing. Underneath the armor , a glimpse of an olive-green or muted green garment is visible at the collar. He wears a silver circlet or diadem on his forehead , adorned with what appears to be a small gemstone or similar embellishment in the center. Additionally , he has simple , small earrings hanging from his ears. Overall , the elf's appearance combines elements of both elegance and strength , suggesting a character who may be both powerful and refined. ,

awdfjdsl

The image portrays a male elf with striking features. His hair is a light blonde , and styled in a sophisticated updo. The hair is pulled back from his face , with the majority gathered into a bun or knot at the crown of his head , leaving a long , flowing section cascading down his back. The length of the loose hair reaches below his shoulders. His skin tone is fair , almost porcelain , with a subtle rosy undertone. His most distinctive features are his pointed ears , characteristic of elves , which are clearly visible. His facial features are delicate yet strong. He has large , expressive light grey or blue eyes , which are emphasized by well-defined eyebrows. His nose is straight and slender , and his mouth is slightly full with a soft , almost neutral expression. While his expression is not overtly emotional , there is a hint of seriousness and perhaps determination in his gaze. He has a slender but not frail build. His posture is erect and confident , suggesting strength and self-assurance. The elf's attire consists of a suit of armor that appears to be made of metal , with a predominantly silver or steel finish. The armor is detailed with intricate designs and textures , suggesting craftsmanship and possibly a high social standing. Underneath the armor , a glimpse of an olive-green or muted green garment is visible at the collar. He wears a silver circlet or diadem on his forehead , adorned with what appears to be a small gemstone or similar embellishment in the center. Additionally , he has simple , small earrings hanging from his ears. Overall , the elf's appearance combines elements of both elegance and strength , suggesting a character who may be both powerful and refined. ,

awdfjdsl

The image portrays a male elf with striking features. His hair is a light blonde , and styled in a sophisticated updo. The hair is pulled back from his face , with the majority gathered into a bun or knot at the crown of his head , leaving a long , flowing section cascading down his back. The length of the loose hair reaches below his shoulders. His skin tone is fair , almost porcelain , with a subtle rosy undertone. His most distinctive features are his pointed ears , characteristic of elves , which are clearly visible. His facial features are delicate yet strong. He has large , expressive light grey or blue eyes , which are emphasized by well-defined eyebrows. His nose is straight and slender , and his mouth is slightly full with a soft , almost neutral expression. While his expression is not overtly emotional , there is a hint of seriousness and perhaps determination in his gaze. He has a slender but not frail build. His posture is erect and confident , suggesting strength and self-assurance. The elf's attire consists of a suit of armor that appears to be made of metal , with a predominantly silver or steel finish. The armor is detailed with intricate designs and textures , suggesting craftsmanship and possibly a high social standing. Underneath the armor , a glimpse of an olive-green or muted green garment is visible at the collar. He wears a silver circlet or diadem on his forehead , adorned with what appears to be a small gemstone or similar embellishment in the center. Additionally , he has simple , small earrings hanging from his ears. Overall , the elf's appearance combines elements of both elegance and strength , suggesting a character who may be both powerful and refined. ,

awdfjdsl

The image portrays a male elf with striking features. His hair is a light blonde , and styled in a sophisticated updo. The hair is pulled back from his face , with the majority gathered into a bun or knot at the crown of his head , leaving a long , flowing section cascading down his back. The length of the loose hair reaches below his shoulders. His skin tone is fair , almost porcelain , with a subtle rosy undertone. His most distinctive features are his pointed ears , characteristic of elves , which are clearly visible. His facial features are delicate yet strong. He has large , expressive light grey or blue eyes , which are emphasized by well-defined eyebrows. His nose is straight and slender , and his mouth is slightly full with a soft , almost neutral expression. While his expression is not overtly emotional , there is a hint of seriousness and perhaps determination in his gaze. He has a slender but not frail build. His posture is erect and confident , suggesting strength and self-assurance. The elf's attire consists of a suit of armor that appears to be made of metal , with a predominantly silver or steel finish. The armor is detailed with intricate designs and textures , suggesting craftsmanship and possibly a high social standing. Underneath the armor , a glimpse of an olive-green or muted green garment is visible at the collar. He wears a silver circlet or diadem on his forehead , adorned with what appears to be a small gemstone or similar embellishment in the center. Additionally , he has simple , small earrings hanging from his ears. Overall , the elf's appearance combines elements of both elegance and strength , suggesting a character who may be both powerful and refined. ,

Oussama-SABBAHI

Fairness means ensuring your analysis doesn't create or reinforce bias. This can be challenging , but if the analysis is not objective , the conclusions can be misleading and even harmful. In this reading , you’re going to explore some best practices you can use to guide your work toward a more fair analysis! Consider fairness Following are some strategies that support fair analysis: Best practice Explanation Example Consider all of the available data Part of your job as a data analyst is to determine what data is going to be useful for your analysis. Often there will be data that isn’t relevant to what you’re focusing on or doesn’t seem to align with your expectations. But you can’t just ignore it; it’s critical to consider all of the available data so that your analysis reflects the truth and not just your own expectations. A state’s Department of Transportation is interested in measuring traffic patterns on holidays. At first , they only include metrics related to traffic volumes and the fact that the days are holidays. But the data team realizes they failed to consider how weather on these holidays might also affect traffic volumes. Considering this additional data helps them gain more complete insights. Identify surrounding factors As you’ll learn throughout these courses , context is key for you and your stakeholders to understand the final conclusions of any analysis. Similar to considering all of the data , you also must understand surrounding factors that could influence the insights you’re gaining. A human resources department wants to better plan for employee vacation time in order to anticipate staffing needs. HR uses a list of national bank holidays as a key part of the data-gathering process. But they fail to consider important holidays that aren’t on the bank calendar , which introduces bias against employees who celebrate them. It also gives HR less useful results because bank holidays may not necessarily apply to their actual employee population. Include self-reported data Self-reporting is a data collection technique where participants provide information about themselves. Self-reported data can be a great way to introduce fairness in your data collection process. People bring conscious and unconscious bias to their observations about the world , including about other people. Using self-reporting methods to collect data can help avoid these observer biases. Additionally , separating self-reported data from other data you collect provides important context to your conclusions! A data analyst is working on a project for a brick-and-mortar retailer. Their goal is to learn more about their customer base. This data analyst knows they need to consider fairness when they collect data; they decide to create a survey so that customers can self-report information about themselves. By doing that , they avoid bias that might be introduced with other demographic data collection methods. For example , if they had sales associates report their observations about customers , they might introduce any unconscious bias the employees had to the data. Use oversampling effectively When collecting data about a population , it’s important to be aware of the actual makeup of that population. Sometimes , oversampling can help you represent groups in that population that otherwise wouldn’t be represented fairly. Oversampling is the process of increasing the sample size of nondominant groups in a population. This can help you better represent them and address imbalanced datasets. A fitness company is releasing new digital content for users of their equipment. They are interested in designing content that appeals to different users , knowing that different people may interact with their equipment in different ways. For example , part of their user-base is age 70 or older. In order to represent these users , they oversample them in their data. That way , decisions they make about their fitness content will be more inclusive. Think about fairness from beginning to end To ensure that your analysis and final conclusions are fair , be sure to consider fairness from the earliest stages of a project to when you act on the data insights. This means that data collection , cleaning , processing , and analysis are all performed with fairness in mind. A data team kicks off a project by including fairness measures in their data-collection process. These measures include oversampling their population and using self-reported data. However , they fail to inform stakeholders about these measures during the presentation. As a result , stakeholders leave with skewed understandings of the data. Learning from this experience , they add key information about fairness considerations to future stakeholder presentations. ,

yidahis

Create an image of a bouquet made up of red roses and baby's breath , captured in a direct front-facing angle. The flowers should be captured using a professional lens , ensuring that every detail of the blooms is visible and sharp. The final product should be a high-quality 8K wallpaper suitable for use as a desktop background or screensaver. To create a visually interesting composition , consider placing the larger red roses in the center of the bouquet and surrounding them with smaller baby's breath flowers. The baby's breath can be scattered throughout the bouquet to add texture and depth while still allowing the roses to remain the focal point. To enhance the natural beauty of the flowers , consider playing with lighting to create shadows and highlights that add depth to the image. Additionally , consider placing the bouquet against a plain backdrop to highlight the intricate details of the flowers. You may also want to experiment with different angles and compositions to create a unique and visually striking image. Finally , adding bokeh or light flares can enhance the dreamy feel of the image and contribute to the overall aesthetic of the bouquet. ,

johncoffey294

Designing a coffee bag for "John Coffee" in the Páramo of Santander , Colombia , will require a logo and background that reflect the brand's identity and the unique characteristics of the region. Here's a description of a possible design: Logo: Central Icon: Consider using an iconic element that represents both coffee and the Páramo of Santander. This could be a combination of a coffee cup and the silhouette of the páramo's mountains. Nature: Incorporate elements of the páramo's natural beauty , such as native flora , like frailejones , and fauna like birds or rabbits. These elements can encircle the central icon. Colors: Utilize a color palette that captures the essence of the Páramo , with shades of green and blue representing the natural landscape and perhaps deep brown for coffee. Typography: Choose a font that reflects the brand's personality , whether it's rustic , modern , or elegant. Ensure that the brand name "John Coffee" is clearly legible. Text: Place the brand name "John Coffee" and the location "Páramo of Santander , Colombia" in proximity to or around the central icon. Bag Background: Natural Background: Use a background image or pattern that showcases the stunning scenery of the Páramo of Santander. This could include mountains , rolling hills , and clouds. It should create a sense of place and emphasize the brand's connection to the region. Colors: Harmonize the background colors with the logo's color palette to create a cohesive and visually pleasing design. Product Information: On the back of the bag , provide essential details about the coffee , including its variety , processing method , tasting notes , and any unique selling points. Remember , it's crucial to collaborate with a professional graphic designer to bring your vision to life. This design concept is a starting point and can be tailored to fit your brand's identity and preferences. Additionally , ensure that the bag complies with all legal requirements for coffee packaging and labeling in Colombia and any target markets. ,

matiaslionelromero

Imagine a drawing that shows three human figures in different poses , each representing a type of Greek love. The first figure can represent "Eros , " passionate and romantic love. You can depict them with passionate gestures and a facial expression full of desire. The second figure can represent "Philia , " fraternal and friendly love. Draw this figure embracing or sharing a gesture of closeness with other characters , reflecting the importance of friendship and camaraderie. The third figure can represent "Agape , " unconditional and altruistic love. You can show this figure extending their arms in a gesture of acceptance and compassion towards others. Make sure to capture a serene facial expression filled with kindness. In the center of the drawing , draw a heart that connects the three figures , symbolizing the interconnectedness of the different types of love. Inside the heart , you can add symbols representing unity , such as a ribbon or a mandala. Additionally , you can incorporate Greek elements like columns or a landscape reminiscent of ancient Greece to emphasize the historical and philosophical context. , Water Color ,

savazquez2004

In the center of the image , there is a caricatured and colorful representation of a Mexican insurgent soldier from the Independence era. The soldier wears a charro hat adorned with bright feathers and an excessively festive outfit with an abundance of ruffles and lace. He holds a sword that shines in golden tones and carries a Mexican flag with the colors of the national flag waving behind him. In the background , there is an eclectic mix of Mexican kitsch elements: giant cacti wearing mariachi hats , piñatas shaped like Independence heroes , a extravagantly dressed mariachi playing the guitar , a donkey painted with psychedelic designs carrying a barrel of tequila , and an Angel of Independence with colorful wings and sparkling sequins. The sky behind all of this is filled with colorful fireworks and streamers , creating an atmosphere of exaggerated celebration. Additionally , humorous details such as giant chili peppers and floating tacos can be included. ,

webrepjas1

Appearance: The Giant Wolf Spider is an enormous arachnid , resembling a regular wolf spider but scaled up to a terrifying size. It has long , hairy legs , and its body can be up to 3 feet in length. The spider's exoskeleton is a mix of dark brown and black , camouflaging it in shadows and making it hard to spot in dimly lit environments. Its multiple eyes gleam with an eerie luminescence , providing it with excellent night vision. Features: Giant Wolf Spiders possess venomous fangs that they use to paralyze their prey. While their venom is not usually fatal to human-sized creatures , it can cause temporary paralysis and intense pain. They are incredibly agile and quick , making them adept ambush predators. Habitat: Giant Wolf Spiders are most commonly found in dark and damp environments , such as caves , forests , and subterranean tunnels. They are skilled at weaving complex webs that serve as both traps for their prey and a means to detect nearby movement. Behavior: These arachnids are solitary creatures and prefer to hunt alone. Despite their size , they are surprisingly stealthy and capable of stalking their prey unnoticed until they strike. They are skilled climbers and can scale walls and ceilings with ease. Role in the World: In your DND world , Giant Wolf Spiders might be common threats in certain regions , especially in dense forests or caves. They could be encountered as natural inhabitants of the wilderness or serve as guardians to ancient ruins and abandoned places. Their venomous bite and ability to ensnare their prey in webs make them formidable foes for adventurers. Encountering a Giant Wolf Spider in your campaign could lead to tense and suspenseful moments. The spiders might ambush adventurers , trying to paralyze them with their venom before delivering a deadly bite. Players might need to exercise caution and utilize strategies to counter the spider's agility and web traps effectively. Additionally , the presence of Giant Wolf Spiders can add an element of danger and fear to the wild and untamed areas of your world , making players wary of what lurks in the shadows and the darkness. ,

lluisx2

Requesting a unique and customized tattoo design that covers the entire front of the leg , from the foot to the top of the knee. The design should be four times longer than its width and be inspired by the blackwork style with pointillism shading in black and white , without colors. It should be related to the music group Enigma , incorporating elements and styles from the designs and arts of their album covers in a detailed , dark style with a freehand appearance , similar to styles drawn with ink pen. The tattoo should be imposing and highlight iconic elements of Enigma and their art. Additionally , generate a visual representation of how the tattoo would look applied to the front of the leg. ,

EsdrasMujica

Create a visually appealing ad for the sale of mobile phones inspired by Grand Theft Auto V. Highlight multiple models of phones (such as XYZ2000 , ABC3000) , showcase the key features of the phones (like sleek designs , high-resolution cameras , long battery life) , and include any special promotions or discounts if applicable (e.g. , 20% off for a limited time). Additionally , incorporate the seller's contact information , such as the website , phone number , or store address , using the iconic style of Grand Theft Auto V as inspiration. ,

lluisx2

Requesting a unique and customized tattoo design that covers the entire front of the leg , from the foot to the top of the knee. The design should be four times longer than its width and be inspired by the blackwork style with pointillism shading in black and white , without colors. It should be related to Sauron or the dragons associated with Sauron from Tolkien's universe , focusing on one or multiple dragons in a detailed , dark style with a freehand appearance , similar to styles drawn with ink pen. The tattoo should be imposing and highlight iconic elements of Sauron and his dragons , using shadows in a pointillism style. Additionally , generate a visual representation of how the tattoo would look applied to the front of the leg. ,

KaioXd889322

distinctive metal steampunk planets Victorian clock , with emblems of success and motivation , enhance the image of the circular emblem , adding a radiant glow effect to the golden elements and finer details in the icons around the central book. Additionally , I created more examples with variations of this design to provide a range of options for your “Successor Tool” brand. I hope these new creations meet your expectations and enrich your Instagram profile even more. ,

anotherinova

Positive Prompt: "A detailed technical illustration that shows two key stages of oil well operation using modern and clear visual design. On the left side , the 'Heat Carrier Injection' process is depicted. A pump jack , widely used in the oil industry to move liquid from the well , is shown on the surface. Red arrows highlight key steps in the process. The first step is the plunger lift , which plays a crucial role in the operation of the pump. This process is facilitated by lifting the plunger inside the pumping equipment in preparation for the injection. The second step involves securing the tubing column to a suspended plug , an important measure to ensure the temporary closure of the well and prevent unwanted discharge while preparing for the heat carrier injection. Subsurface , the illustration shows components like the tubing and working rods involved in this process. The entire system is presented in cross-section to demonstrate how it functions in real conditions , providing a deeper understanding of the equipment interaction during heat carrier injection. On the right side of the illustration , the 'Production Phase' is shown. The pump jack is again depicted on the surface , but now the focus is on the oil extraction process. Arrows indicate several important operations. First , the dismantling of a solid ring is shown , which is removed to prepare the well for operation. Next , the installation of a polished rod is highlighted , an important component of the pumping system that allows for effective force transmission for the pump's operation. Finally , the lowering of the plunger is illustrated , which initiates the system's operation in extraction mode. The cross-sectional view of the well illustrates how the pumping system elements work during oil extraction. Specifically , equipment such as the SPR-57 cylinder and plunger are highlighted as crucial for ensuring oil production. All elements are clearly labeled with descriptions , making it easier to understand the processes and equipment. The illustration is designed in a modern style with clear lines and bright colors to simplify the perception of complex technical processes. All key operations are marked with explanatory arrows , and labels help quickly orient the viewer on the actions being performed at each stage. Both surface and subsurface equipment are represented in cross-section , providing a comprehensive understanding of all stages of well operation. This illustration is suitable for use in educational and professional materials within the oil and gas industry , as it provides a visual and understandable representation of the heat carrier injection process and subsequent oil extraction." Negative Prompt: "The illustration lacks sufficient detail , reducing its practical value for technical specialists and engineers. Firstly , key components of the equipment , such as the tubing , column pipes , and plunger , are presented schematically and without explanatory labels , making it challenging to understand specific processes and steps. Important stages , such as the plunger lift or the dismantling of the solid ring , are depicted too simplistically , and due to the lack of detailed indicators , it is unclear how these operations are carried out. The subsurface part of the equipment in cross-section is also inadequately detailed: there are no precise labels for all layers and components necessary to understand the complete structure and system interactions. The SPR-57 cylinder , which is a crucial part of the production process , is not visualized with sufficient clarity , potentially leading to misunderstandings of its functions and role in the process. Additionally , there is no clear indication of the flow of fluids , such as the heat carrier injection or liquid circulation. The red arrows used to highlight key processes are not sufficiently informative: their trajectory may confuse the user , as they do not clearly point to specific elements of the system , and their placement on the diagram appears cluttered. This complicates the perception of the overall logic of the processes. As a result , the illustration appears superficial and unsuitable for use in professional technical instructions or educational materials. Finally , the overall design of the illustration is outdated , which diminishes its visual appeal. Modern illustrations require cleaner , clearer graphics with bright and unambiguous indicators and explanatory captions to enhance clarity and ease of understanding , which is lacking in this case. All these factors make the illustration less useful for engineering tasks and necessitate revisions to meet contemporary quality standards in the oil and gas industry." These prompts provide a comprehensive overview of both the strengths and weaknesses of the illustration. ,

webrepjas1

Appearance: A Swarm of Spiders is a horrifying and unsettling sight , as it consists of hundreds or even thousands of spiders working together as a single entity. The swarm appears as a writhing mass of crawling legs , forming a dark and undulating cloud of arachnids. The individual spiders in the swarm vary in size , but they are typically small , ranging from tiny spiders to larger ones with leg spans of a few inches. The swarm's color can range from a mix of dark browns and blacks to lighter hues , depending on the types of spiders comprising it. Features: The Swarm of Spiders moves with a coordinated fluidity , as if guided by an unseen intelligence. While each spider is relatively weak on its own , the collective strength of the swarm is overwhelming. The swarm is highly aggressive , attacking anything that comes within its vicinity. Its bite can deliver venom that , while not deadly , can cause pain , discomfort , and temporary paralysis. The swarm's sheer numbers can be its greatest advantage , allowing it to overwhelm and immobilize even larger creatures. Habitat: Swarms of Spiders are typically found in areas with a high concentration of spiders , such as dense forests , abandoned structures , or ancient ruins. They may inhabit dark and secluded places where their presence can go unnoticed until it's too late for unsuspecting intruders. Behavior: Swarms of Spiders are driven by instinct and the collective intelligence of the individual spiders that make up the swarm. They act as a cohesive unit , attacking en masse to subdue their prey and cocoon it in sticky webs. Swarms of Spiders can move quickly , scaling walls and surfaces with ease , which makes them challenging to escape from once they have engaged a target. Role in the World: In your DND world , Swarms of Spiders could be a terrifying threat lurking in the wild and dark corners of the land. They might be drawn to areas of powerful magic or necromantic influence , serving as guardians to forbidden places or the minions of evil spellcasters. The sight of a Swarm of Spiders can instill fear and panic in adventurers , as they face an unrelenting horde of venomous creatures. Encountering a Swarm of Spiders in your campaign can be a harrowing experience for adventurers. The swarm's ability to cover large areas and its relentless pursuit make it a deadly adversary. Players might need to think creatively to avoid or disperse the swarm , using spells , fire , or other area-of-effect attacks to fend off the spider horde. Additionally , the presence of Swarms of Spiders can create a sense of dread and trepidation , heightening the tension in areas where they are known to dwell , making players ever watchful for the signs of these arachnid hordes. ,

enrriquemateo64

Generate an image of a whale for a children's book. The whale should be a simple and friendly drawing , suitable for children to color and , if they wish , cut out. Ensure that the whale is centered on the page and large enough for children to easily color the details. Use bright and friendly colors. Additionally , include an outer outline around the whale so that children can easily cut it out. The design should be simple yet appealing to young children. , , Pencil Sketch ,

webrepjas1

Appearance: The Crocodile is a large and powerful reptile , known for its distinctive long snout , sharp teeth , and armored body. Its scales can have various shades of green , brown , or gray , blending in with the murky waters and marshes it inhabits. The Crocodile's eyes and nostrils are positioned on the top of its head , allowing it to remain mostly submerged while still keeping a watchful eye on potential prey. Features: The Crocodile is an apex predator in aquatic environments , using its powerful jaws to seize and drag its prey underwater. It possesses incredible strength and resilience , making it a fearsome hunter and a challenging opponent for adventurers who venture into its territory. Crocodiles are well-adapted for both land and water , able to move quickly on land and remain submerged for extended periods. Habitat: Crocodiles are typically found in freshwater bodies such as rivers , lakes , and swamps , though they can also inhabit saltwater habitats like estuaries and coastal areas. They are highly territorial creatures , claiming areas of water as their own hunting grounds. In your DND world , they might be guardians of hidden treasures or sacred places. Behavior: Crocodiles are ambush predators , relying on stealth and patience to catch their prey unaware. They lie submerged , often with only their eyes and nostrils visible , and strike with lightning speed when an opportunity presents itself. Crocodiles are more aggressive during their breeding season or if they feel threatened. Role in the World: In your DND world , Crocodiles could be symbols of primal power and ancient guardians. They might be revered or feared by local tribes as creatures of great significance in their myths and beliefs. Druids and rangers might have a connection with Crocodiles , viewing them as an essential part of the natural order. Encountering a Crocodile in the wild can be a dangerous and adrenaline-pumping event for adventurers. Players must be cautious around bodies of water known to be inhabited by Crocodiles , as these creatures can launch surprise attacks. Crossing rivers or exploring swampy terrain could become treacherous , and players will need to be vigilant to spot the telltale signs of lurking predators. The presence of Crocodiles in your campaign adds an element of danger and excitement to aquatic and marshy environments. They can create memorable and intense encounters , challenging players to use their wits and skills to outmaneuver and defeat these fearsome reptilian predators. Additionally , the idea of crossing treacherous waters or exploring hidden marshlands where Crocodiles dwell can evoke a sense of adventure and exploration in your DND world. ,