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

Please create a 3:4 vertical "second world" photography 2.0 poster based on the photography work here uploaded. The overall composition is strictly 1:1: The upper part is as faithful as possible to the original photo , surrounding a clouds , without changing the subject , character movements , spatial relationships , colors , and natural light , only making necessary cropping. The lower part uses natural original photo as a background , retaining a lot of blank space. The shape of the photo itself must also be explained. Do not assume the use of ordinary irregular paper edges. A Statue of Unity (world's tallest statue , with a height of 182 metres (597 feet) , [3] located in Narmada valley , near Kevadia in the state of Gujarat , India. It depicts Indian politician and independence activist Sardar Patel) , Water can become a small body of River between mountains , light can become something that can be borrowed , roads can continue to extend , clouds or branches can also form new spatial relationships. ,

aiWebX

{ "analysis_mode": "STRICT MODE" , "image_overview": "A figure of a female character with gold-colored hair on the face of a white fox on her head , and a Japanese-style outfit with a red and white background. She is holding a Japanese umbrella and jumping lightly , and part of the red Japanese umbrella and the text of the rights can be seen at the bottom." , "composition": { "framing": "新め 上时るら捈えた躍動感るるまするまするのショト" , "subject_placement": "The whole body of the figure placed large in the middle of the screen , "balance": "Dynamic balance due to the large spread on the left and right sides , the flowing hair on the back , and the decoration of the costume" } , "camera": { "camera_position": "被写位方め时间からのハイアングル" , "camera_height": "フクローの頭部よりにるますます" , "viewpoint": "見下ろす电影" , "angle_of_view": "湖整からやや広角気味のデナンクな画角" , "perspective" } , "spatial_layout": "A three-dimensional spatial relationship where there is a 赤い和傘 in front of the hand , a character arranged in such a way as to dance to the space above it , and a background surface with a female character" , "subject": { "main_subject": "和風设计を着た女人オーレードのフィーム" , "pose": "Poses such as having a sense of movement in the sky , raising the right hand high , supporting the handle of the body" , "body_proportions": "整った頭身のフクロショーショーショードローポーション" , "physical_characteristics": "色白の肌、整った顔立で" } , "character": { "identity": "Character figures related to the アイルドマスターシリーター（视频表記より）" , "age_appearance": "young woman、少女" , "expression": "口をしたまてるさたますますますますます" } , "face": { "head_position": "右在地丸へ向てて顔をしたも征げている" , "eyes": "温かみあるまたます系の真、恐ずななアイッント" , "eyebrows": "細く整えられ眉、額の赤いライン decoration" , "nose": "small 控えめな鼻の造形" , "mouth": "新しげに開いた口元" , "facial_features": "端正な顔立で、頭学白い狐の面（お面）を新めに時今ですかる" } , "hair": { "color": "是量金色、イエロー" , "style": "両アイドに红にに編みしたた三つ編みてら、毛先ががりますかる" , "length": "背中や肩育しになりををててふんわりとなんなていてていてて" } , "clothing": { "presence": "あり" , "clothing_structure": "Japanese-style clothing with red color on the main , green color accents , and a short skirt-like hem with a black interior and green color." "clothing_color": "赤、白、緑、黒" , "decorations": "白い紐（組紐) , 赤い結糕目、首小钯西、背中国大華華和柄の結ム帯(帯揚げ、白い龙风例)" } , "objects": { "umbrella": "电影に写りしますかい、赤い和傘（番傘、骨器と「THE IDOLM@STER & (c) Bandai Namco Entertainment Inc.」」の白いますいてていててかて "mask" } , "environment": { "setting": "名字の太阳用电影电影电影宣伝用display background" , "weather": "しい" , "time_of_day": "しな" } , "architecture": { "presence": "no" } , "background": { "background_type": "フェップショーショーショーションションションションションのなななゃデシング レッット" } , "text_and_symbols": { "text": "美国右下に「THE IDOLM@STER & (c) Bandai Namco Entertainment Inc.」の少发白い版権記記文字" } , "color": { "dominant_colors": "赤、白、金色、緑、黒" , "palette": "鮮なる赤と红话色対比に、鮮なると白が映える華なれなんます" } , "lighting": { "source": "时地于时间からの柔らかくしますなたんなんスティージョード" , "direction": "在时间から" , "contrast" } , "shadow": { "nature": "设计のひだや髪の重なり、体に落るるなり陰影" , "distribution" } , "material": { "skin_texture": "PVC特有の意しででたな質感の肌" , "cloth_texture": "造形とてますますのますなな布地地さん" , "mask_texture": "お面の質感" , "umbrella_texture": "和紙や布-like 傘 surface texture" } , "texture": { "overall": "High quality scale figure } , "atmosphere": { "mood": "お祭り、和風、華やる、躍動的、イタード的" , "tension": "中" } , "optics": { "lens_effects": "フェックレンズになる被写界头头の浅いボケ味（backgroundや some parts of the body are softにボケててる）" } , "depth_of_field": { "focus": "Character's facial expression" } , "capture_characteristics": { "medium": "实伝用实伝用电影电影电影电影电影" } , "context_analysis": { "image_sequence": "single image" , "same_character_candidates": "never" , "same_location_candidates": "never" , "same_object_candidates": "しな" , "temporal_relationships": "しな" , "action_continuity": "しな" , "visual_continuity": "しな" , "newly_confirmed_information": "金髪三つ編み、狐の面、赤と市松新视の和風设计を着たアイルドのアックックビジアル" , "information_shared_across_images": "しな" } , "character_consistency": { "character_id": "char_004" , "matching_features": "金色の三つ編み髪、狐の面、赤を基調とて和風设计" , "fixed_features": "髪型、Costume design" , "variable_features": "never" , "newly_confirmed_features": "和傘时间空间に舞うとうますますます" , "conflicting_features": "never" , "confidence": "A" } , "inferred_information": { "fact": "バンダイナムコエンターテインボントの「アイルドマスター」アックショートロックックックション" , "inference": "をードーマストの作でするますする和風のをなんならなんますますををますますますますますますますます" , "confidence": "A" , "evidence" } , "changes_from_previous_images": { "status" } , "negative_constraints": { "constraints": [ "Do not change the pose of figure" "Do not delete the face of the character 金髪三つ編みや頭の狐の面" , "赤と市松松をの和風しますますますますしたしたしたしたしたして "右手手上たためやげ和傘" "Keeping the quality of a product photo of a figure rather than a human being" , "Ignore the text elements of rights表記の保つ" ] } } ,

aiWebX

Create an ultra-premium East Asian sacred art poster that merges Orbit-style symbolic monumentality with Transit-style museum-grade elegance , while adding an appropriate faded watercolor-like antique patina across the entire image. Show one serene celestial goddess seated front-facing on a large layered lotus throne rising from dark weathered rocks above shallow swirling water , centered in a tall vertical frame. Behind her head , place one large circular ornamental halo-disc filled with intricate floral and sacred relief patterns , perfectly framing her upper body like a ceremonial mandala. The final artwork must feel sacred , elegant , antique , softly aged , painterly , and collectible , like a rare devotional mural-painting artifact. No title , no logo , no readable text , no real person identity. Core composition: Use a strict centered vertical composition with the goddess occupying the full central axis from halo to lotus base. Her seated body must feel calm , monumental , and balanced. One leg lowers naturally toward the rock base while the other rests higher in a graceful asymmetrical pose. The lotus throne and rock base must anchor the composition with strong sacred weight. The circular halo-disc behind her should be large , full , and nearly iconic in scale , creating a powerful devotional silhouette. Orbit enhancement: Increase the monumentality of the sacred icon structure. The halo-disc should feel larger and more complete behind the figure , almost pressing the full spiritual force of the image forward. The lotus throne and rock base should feel more substantial and sculptural , giving the figure stronger divine presence. The whole composition should read immediately as a powerful three-part symbol: centered goddess , circular halo , lotus-rock throne. Transit enhancement: Refine the image into a more international museum-art language. The palette should feel quieter , more mineral , more elegant , and more globally collectible. Reduce any overly warm or decorative saturation. Keep the lighting restrained , the materials sophisticated , and the overall impression like a high-end exhibition poster for an ancient sacred masterpiece. Aged light-color patina: This is the key addition. Apply an appropriate light faded antique wash across the entire image , as if the artwork has lived on silk , fresco plaster , or mineral paper for centuries. The patina should be subtle and beautiful: soft desaturation , slight powdery pigment bloom , gentle worn edges , faint watercolor-like tonal diffusion , and delicate aged surface calm. It must not look dirty or damaged. The result should feel like elegant time-softened color , not decay. Figure design: Design an original adult divine feminine figure inspired by classical East Asian sacred sculpture and devotional painting. She must feel compassionate , serene , and spiritually elevated. Her face should be delicate and calm , with lowered eyes , soft brows , subtle lips , and a peaceful meditative expression. Her anatomy must be elegant and natural , with correct shoulders , arms , hands , torso , and posture. She wears layered flowing robes with long trailing sashes and softly revealed upper chest in a sacred historical-art way , always dignified and ceremonial. Costume and ornament: Dress her in layered mineral-toned robes of celadon gray-green , faded terracotta , dusty coral , pale parchment , and aged ivory. Add refined antique jewelry , pendant chains , earrings , and a balanced floral-jewel headpiece. The fabrics and ornaments must feel softened by time , as if painted with diluted pigments over an aged surface. Halo-disc design: Render the halo as a richly ornamented circular disc with dense floral and sacred scroll relief in muted reddish-brown , aged copper , faded russet , and antique mineral tones. It should feel historical , intricately crafted , and devotional , with slightly softened edges from age. Lotus and base: Render the lotus throne as layered and sculptural with desaturated blue-green , gray-teal , and stone-lotus tones. The rock base beneath should feel dark , mineral , and weathered. Add shallow sacred water with gentle pale foam and flowing pattern logic. Everything below the figure must support stillness and icon gravity. Lighting: Use soft diffused sacred lighting from upper front-left with very gentle frontal fill. The figure , halo , lotus , and drapery should glow softly through muted tonal transitions. No harsh drama. The light must feel calm , spiritual , and respectful to the antique surface quality. Material rendering: Render skin like painted sacred sculpture with matte softness and delicate age integration. Render robes as faded silk-like mineral pigment drapery. Render jewelry with restrained antique-metal detail. Render halo and lotus with painted-relief texture and worn ceremonial richness. Render the full surface with subtle fresco grain , paper tooth , faint crackle , and collector-grade patina. Background: Keep the background pale , atmospheric , and minimal , built from parchment beige , faded mineral wash , cloudy plaster texture , and faint devotional atmosphere. No clutter , no crowded architecture , no unrelated objects. Color system: Use a restrained sacred palette of celadon gray-green , dusty terracotta , faded coral , aged ivory , parchment beige , muted russet , stone gray , desaturated blue-green , and dark mineral accents. The entire image should feel softened by time and unified by elegant antique color restraint. Image finish: The final artwork must feel like a world-class sacred art poster: serene , monumental , collectible , and gently time-worn. Preserve strong detail in the face , crown , halo ornament , robe folds , lotus petals , and rock textures , while bathing the whole piece in a refined aged light-color patina. 8k , museum-grade sacred visual quality. ,

Altario

Drexal's face is a consistent , recognizable original character based on a **facial amalgamation of Mark Strong (55%) and Naveen Andrews (45%)** , interpreted as an original fantasy character and **not a likeness or copy of either actor**. He has a **long-oval to subtly rectangular face** , defined cheekbones , a strong but not overly square jaw , a straight prominent nose , slightly hooded deep-set **dark brown eyes** , thick naturally shaped eyebrows , medium-full lips , and an intelligent , restrained expression. His eyes should communicate **constant observation and analysis**. He often looks as though he is evaluating a situation rather than reacting emotionally to it. **Skin:** Warm olive complexion with realistic natural texture , subtle signs of sun exposure , travel , and life outdoors. **Hair:** Thick , very dark brown to near-black hair , moderately short and practical , with a slight natural wave. **Facial hair:** Closely trimmed short beard with the moustache naturally integrated into it. Neat and practical , never fashionable or heavily stylized. ### Character & Presence Drexal is a **scholarly military officer and Al-Karim nobleman**. His authority comes from intelligence , competence , restraint , and self-command rather than physical intimidation. His demeanor is: - Calm - Observant - Intelligent - Controlled - Quietly authoritative - Professionally disciplined - Emotionally restrained - Difficult to read He should appear capable of spending an afternoon studying **coastal charts , military reports , or diplomatic correspondence** , then calmly drawing his sword when circumstances require it. His attractiveness should be **mature and understated** , never model-like or prettified. He possesses the quiet confidence of a man who does not need to demonstrate his competence to anyone. ### Clothing & Setting Dress him as an **Al-Karim noble-officer** , combining refined aristocratic clothing with practical military elements appropriate to a grimdark medieval fantasy setting. Rich but restrained fabrics , layered desert-region garments , practical officer's coat or robe , subtle embroidered detailing , leather equipment , and understated signs of rank. His clothing should suggest wealth and education without becoming ostentatious. Use a muted , historically inspired **Al-Karim palette** of earth tones , deep burgundy , sand , charcoal , dark brown , and aged bronze. Place him in an atmospheric Al-Karim interior such as a military study , coastal command chamber , or noble administrative room , with **maps , navigation charts , instruments , manuscripts , and military documents** subtly visible in the background. ### Lighting & Visual Style Ultra-realistic cinematic medieval fantasy photography. Natural skin texture , realistic pores , subtle imperfections , authentic fabric and leather textures , physically believable materials , dramatic but natural directional lighting , shallow depth of field , atmospheric environmental detail. The lighting should emphasize the structure of his face and particularly his **deep-set , evaluating eyes**. **Mood:** intelligent , restrained , serious , quietly formidable. **Composition:** Three-quarter portrait , chest or waist up , natural relaxed posture , direct or slightly off-camera gaze. **Critical consistency requirement:** Preserve the same facial structure , proportions , eye shape , nose , jawline , eyebrows , hairline , beard pattern , and overall facial identity in every future depiction of Drexal. **Style restrictions:** No anime , no illustration , no exaggerated fantasy features , no glamor makeup , no modern clothing , no contemporary objects , no exaggerated muscularity , no youthful beautification , no caricature. **The final character must read immediately as the same Drexal across different images , ages , costumes , poses , and environments.** ,

tmconway1

Create a professional black-and-white coloring book illustration for young adults , designed specifically for a 5 × 8 inch portrait paperback page. Show a cozy , trendy young-adult bedroom workspace. A young adult is comfortably sitting in bed surrounded by pillows and a soft , slightly rumpled blanket , working on a laptop. The scene should feel like a relatable “bed is my office today” moment. Include charming everyday details throughout the room: iced coffee or coffee cup , smartphone , headphones , small houseplants , bedside lamp , books , charging cable , slippers , cozy socks , a small snack , decorative pillow , and a few natural signs of everyday clutter. Add a window in the background with a simple neighborhood or city view. The overall mood should be cozy , relaxing , modern , cute , slightly messy , and relatable to teens and young adults , but not childish. Use clean , smooth , bold black outlines with varied line weight. Include enough small details to make the page fun to color , while keeping the main shapes large and easy to color. Create an attractive balance between detailed areas and open coloring spaces. Strict coloring-book style: * Black ink line art only * Pure white background * No color * No gray * No gradients * No shadows * No crosshatching * No solid black filled areas * No grayscale * No text * No words * No watermark * No border around the artwork * Crisp , clean printable lines * Professional coloring-book quality Use a vertical portrait composition specifically suited for a 5 × 8 inch paperback coloring-book page. Keep all important artwork comfortably inside the edges with generous clean white margins so nothing is cut off during KDP printing. Make the composition fill the page naturally without making it feel crowded. High-resolution , polished , commercially usable coloring-book illustration , ,

aiWebX

A striking Indian tricolour (Orange. White , Green) optical illusion portrait of a mature man (Use the uploaded reference image as the exact character reference) wearing a shirt against a black background , constructed entirely from dynamic , radiating Indian tricolour 3D dots. A dense array of fine rays dots outward from the center , continuously extending across the composition to form a stark , high-contrast visual. These kinetic dots vortex , undulate , and shift in thickness to define the three-dimensional volume of the man's facial features , and the wavering fabric of his shirt. Shading and highlights emerge strictly through the varying proximity and density of the lines , mimicking a topographical map or precision digital engraving. The plain background consists of straight , tightly spaced diverging rays , providing a sharp geometric contrast to the sculpted , organic contours of the central figure and producing an intense , mesmerizing optical illusion. ,

aiWebX

A professional vertical 3:4 poster for FIFA World Cup 2026. STYLE: vintage sport editorial meets modern Swiss typography — 1960s-70s sports magazine grit fused with bold contemporary graphic design. PALETTE: warm gold #D4AF37 + deep forest green #1B3A2D + cream off-white #F5F0E8. Entire image is monochromatic within this palette — NO bright colors anywhere. LAYOUT — Top: massive bold title "FIFA" on first line , "WORLD CUP" on second line , in extremely bold sans-serif , square heavy letterforms , filled with dense halftone dot texture like old newspaper print , cream off-white color , spanning full width. The letters have a slight rough edge like screen-printed ink. Center: A dynamic silhouette of Kylian Mbappé mid-kick —athletic explosive running posture. a powerful action pose: one leg extended forward striking the football , body leaning into the shot , in a vast star-filled cosmic night , just struck by his foot a thin flashlight shadow emerge into enormous half-football's ring , light imperial Starwars style giant half-football(3D rendering:0.1) drifting across the void , dissolving into Phantom. The figure is rendered as a high-contrast duotone graphic in warm gold against deep green , with subtle film grain and light vintage halftone texture. Behind him , a faint circular sunburst graphic radiates outward in gold lines , evoking classic 1970s sports posters. At his feet , the official 2026 World Cup ball "Trionda" — rendered in the SAME duotone gold-and-cream palette as the rest of the image , no bright red/green/blue. The ball's distinctive wave pattern and panel construction are visible through tonal contrast and embossed texture in gold and cream tones , like a vintage screen print. The ball is mid-flight , just struck by his foot. Bottom: slogan "Say It. Make Your Cup." in the SAME extremely bold sans-serif font as the title — square , heavy , condensed letterforms with the same halftone dot texture fill , cream off-white color , matching the "FIFA WORLD CUP" title typography exactly. A thin gold rule line separates it slightly. Below the slogan , "2026" in the same bold sans-serif style , smaller but matching. DESIGN: bold negative space , strong diagonal tension from Mbappé's striking pose , clear visual hierarchy. The vintage feel is subtle — light film grain , slight warm color shift , delicate halftone pattern on all text. The ENTIRE image stays strictly within the gold-green-cream palette — Trionda ball must NOT appear in bright colors , only duotone gold/cream with tonal embossed detail. ANCHOR: reminiscent of 1970s World Cup matchday programmes crossed with modern minimalist editorial design. AVOID: generic Inter/Helvetica typography , generic purple gradients , SaaS landing page style , stock photo aesthetic , rounded card stacks , watermarks , misspelled text , low contrast text , multi-step compositing seams , bright colors anywhere in the image , a colorful football , thin or lightweight fonts at the bottom , mismatched typography between title and slogan. Clean , high-resolution image quality: smooth continuous tonal gradients , uniform and well-controlled texture throughout , surfaces and materials intact and naturally rendered. The main subject is crisp and clearly separated from a softly layered background with clear depth. Free of digital noise and over-sharpening artifacts. No watermark , no garbled text. ,

elprodigio

Edit the uploaded image while strictly preserving the original person's face , identity , facial structure , facial proportions , skin tone , expression , eye shape , nose , lips , jawline , and all recognizable facial features. Do not alter , beautify , replace , reinterpret , or redesign the face in any way. The character must remain instantly recognizable as the same person from the original image.Transform the subject into a dramatic anime-inspired illustration while keeping the exact face unchanged. Give the subject dark hair styled in a high ponytail with a few loose strands framing the face. Add striking turquoise eyes only if they already match the original image; otherwise preserve the original eye color. Dress the character in a dark hooded garment with intricate teal accents and glowing turquoise symbols.Keep the original pose and composition as much as possible. Position the subject slightly left of center , facing the viewer with the body angled slightly away. Raise the left hand toward the mouth with fingers slightly splayed , wearing dark gloves and sharp metallic rings.Add two large sweeping blades of glowing turquoise energy emerging from behind the head and curving forward around the character. Replace the background with a deep , inky black backdrop that emphasizes the glowing teal energy effects.Use dramatic cinematic lighting with strong contrast , vivid turquoise highlights , subtle rim lighting , and rich shadows. Maintain a close-up , eye-level perspective. Create a mysterious , powerful , slightly menacing atmosphere with premium anime artwork , crisp linework , detailed rendering , and high-end fantasy action aesthetics.Priority order:Preserve the original face and identity exactly.Preserve facial expression and likeness.Apply anime styling to clothing , hair , lighting , and effects only.Do not change age , ethnicity , facial proportions , or recognizable features. ,

aiWebX

A hyper-realistic macro photography shot of a giant , freestanding vintage postage stamp from Statue of Unity , Ekta Nagar in the Narmada district of Gujarat , standing upright against a seamless , soft , color-coordinated pastel studio background. The stamp features an intricately detailed 3D diorama of the most iconic and recognizable landmark from Statue of Unity that pops out and actively breaks the perforated borders , extending outward into the physical space. Lush flora and fauna native to Statue of Unity grows and spills out from the bottom right corner of the stamp's frame. A tiny , miniature figurine of a person wearing recognizable traditional cultural attire from Statue of Unitystands on the ground at the bottom left , looking up in awe at the massive stamp , establishing a striking miniature world scale. The stamp's design includes the word "Statue of Unity" in classic serif typography , subtext in the local language , a realistic local currency denomination , and a stamped black ink cancellation postmark in the top right corner featuring the capital city of Statue of Unity and a realistic date. Soft , diffused , magical studio lighting with a tilt-shift lens effect and shallow depth of field. Gently floating botanical elements native to Statue of Unity drift through the air around the scene. 8k resolution , octane render , highly detailed miniature art. ,

aiWebX

A highly detailed , premium travel-art illustration. In the foreground , a hand holds an open passport , its right-hand page acting as a portal into Kevadia , Gujarat. A photorealistic miniature city scene grows out of the open page , as if the paper itself were a window into the streets. A signature E-Rickshaw breaks out of the passport edge in dramatic 3D perspective , tilting toward the viewer and casting a soft shadow across the hand. Behind the passport , one iconic landmark , Statue of Unity , rises tall and photorealistic as the single architectural focal point. Around the scene , exactly 3 clean black-ink hand-drawn doodles label the city's identity (Ekta Nagar in the Narmada district of Gujarat) , placed loosely in the negative space. Tiny realistic figures interact with the miniature world: a commuter , a street vendor , a tourist taking a photo , all scaled to sell the miniature effect. Style: photorealistic travel photography fused with elegant black-ink sketchbook doodles. Soft warm directional light from the upper left , shallow depth of field , sharp focus on the emerging vehicle , realistic paper and skin textures , subtle contact shadows. Clean editorial composition with generous negative space. Instagram-worthy. Composition hierarchy (most to least prominent): 1. Jungle Safari , 2. Valley of Flowers , 3. Sardar Sarovar Dam , 4. Statue of Unity Ticket in hand , 5. Butterfly Garden. Avoid: crowded layouts , more than one landmark , duplicated symbols , excessive text , arrows , stickers , decorative icons , busy backgrounds , more than 3 doodles. Make the aspect ratio 3:4 ,

laclongquan.

She was born under a sky of blue ice and snow , . Her skin took the cold's hue—pale blue as river ice—and her short hair came down like short twisted tufts of black frost. corded muscles that flexed and coiled even in sleep , fingers that closed with the promise of a grip that would not let go. with an axe slung across her broad back . Her voluptous full body wear fur armor with pouches , slightly turn back. Her white strong thighs ground on a river rock , crouching. Several swath of red paints spread across her face. twisted hair style. - Action Tilt , Depth of Field , Dynamic Perspective , Dynamic Framing , highly detailed with intricate details - The background is red cliff of canyon walls with tree atop , big river waves lapping on rock below. • The Definition: A hyperreal , intensely dramatic cinematic style utilizing severe Chiaroscuro lighting. A single , powerful , warm directional key light illuminates only a portion of the character , leaving the rest to fall off into pitch-black , heavy shadows. The lit areas reveal obsessive , microscopic texture in skin , hair , and woven fabrics. The atmosphere is heavy and quiet , featuring subtle floating dust motes catching the single light source. No neon , no flat lighting; strictly driven by extreme light-and-shadow contrast. The light wraps around the character , illuminating the edges of their hair and silhouette. The air is thick with volumetric lighting rays and your signature "dark sparkle" particulate matter. The depth of field is incredibly shallow , completely blurring the background into soft , creamy bokeh to create a dreamlike , magical atmosphere. , detailed matte painting , deep color , fantastical , intricate detail , splash screen , complementary colors , fantasy concept art , 8k resolution trending on Artstation Unreal Engine 5 ,

FTFelixTorres

Prompt de generación de imagen: Un plano cenital (visto desde arriba) y perfectamente ortogonal de Un tablero de juego de mesa detallado de estilo clásico , inspirado en el Monopoly pero con una temática bíblica e histórica del antiguo Israel. El juego se titula "MAYORDOMÍA: EL TABLERO DE LA PROMESA" escrito en letras doradas y elegantes en el centro. El diseño general tiene texturas de pergamino antiguo , tonos tierra , beige y acabados dorados. El tablero es rectangular y tiene casillas en todo su perímetro. Cada grupo de casillas tiene un color distintivo en la parte superior y representa lugares bíblicos con ilustraciones detalladas en miniaturas sepia o grabados antiguos: En el centro del tablero se muestra una gran ilustración panorámica e intrincada de la antigua ciudad de Jerusalén con murallas de piedra , templos y palacios bajo una luz cálida. Sobre la ilustración , aparecen dos citas bíblicas en pergaminos flotantes: "Sé fiel en lo poco , y en lo mucho te pondré a cargo. Mateo 25:21" y "La Tierra es del Señor , y todo lo que ella contiene. Salmo 24:1". A los lados del centro , hay dos mazos de cartas tridimensionales inclinados: uno azul llamado "CARTAS DE FE" y otro con forma de pergamino enrollado llamado "CARTAS DE PROFECÍA". En la esquina inferior izquierda del centro , se observan dos dados de hueso antiguo con puntos negros. Estilo visual de juego de estrategia premium , limpio , nítido y de alta resolución. El tablero está rodeado por un marco perimetral dividido en 40 casillas rectangulares (10 por cada lado , incluyendo las esquinas cuadradas). La orientación del texto y los gráficos en las casillas debe seguir estrictamente la rotación perimetral del tablero , de modo que las bases de las letras y los dibujos siempre miren hacia el borde exterior del tablero correspondiente a su lado: • Lado Inferior (De derecha a izquierda - Texto en posición normal): Comienza con la casilla de salida en la esquina inferior derecha llamada "SALIDA: El Pacto" , ilustrada con un pergamino abierto con un sello dorado y una flecha roja hacia la izquierda (+200 Siclos). Sigue con: Marrón "Camino de Shur" (60 Siclos) , casilla "Cartas de Fe" (icono de paloma blanca) , marrón "Monte Horeb" (60 Siclos) , casilla "Tributo al César" (Impuesto , icono de una moneda romana , 200 Siclos) , la casilla de transporte "Ruta de Shur" (icono de calzada antigua , 200 Siclos) , celestes "Camino de Belén" (100 Siclos) , "Cartas de Profecía" (icono de pergamino ardiendo) , "Camino de Emaús" (100 Siclos) y "Nazaret" (120 Siclos). Termina en la esquina inferior izquierda con la casilla de esquina "El Pozo (Solo Visita)" , ilustrada con un pozo de piedra antiguo y palmeras. • Lado Izquierdo (De abajo hacia arriba - Texto rotado 90° a la derecha): Incluye las propiedades rosa "Llanuras de Jericó" (140 Siclos) , la casilla de servicio "Camino al Maná" (150 Siclos) , propiedades rosa "Riberas de Galilea" (140 Siclos) y "Cafarnaúm" (160 Siclos) , la casilla de transporte "Camino Real" (200 Siclos) , propiedades naranja "Encinar de Siquem" (180 Siclos) , la casilla "Cartas de Fe" (icono de paloma) , propiedad naranja "Encinar de Mamre" (180 Siclos) y "Valle de Hebrón" (200 Siclos). Termina en la esquina superior izquierda con la casilla de esquina "El Año del Jubileo" , ilustrada con un gran cuerno de carnero (Shofar) dorado. • Lado Superior (De izquierda a derecha - Texto invertido , rotado 180°): Comienza después del Jubileo con las propiedades rojas "Monte Garizim" (220 Siclos) , la casilla "Cartas de Profecía" (pergamino ardiendo) , la propiedad roja "Ciudad de Samaria" (220 Siclos) y "Puerto de Cesarea Marítima" (240 Siclos). Sigue con la casilla de transporte "Vía Marítima" (icono de un barco antiguo , 200 Siclos). Continúa con las propiedades amarillas (Región de Galilea Superior): "Llanuras de Esdrelón" (260 Siclos) , "Monte Tabor" (260 Siclos) , la casilla de servicio "Campos de Booz" (icono de espigas de trigo y herramientas , 150 Siclos) y la propiedad amarilla "Ciudad de Dan" (280 Siclos). Termina en la esquina superior derecha con la casilla de esquina "Juicio del Sanedrín (Ve al Pozo)" , ilustrada con un mazo de juez antiguo o una silueta de guardias templarios señalando. • Lado Derecho (De arriba hacia abajo - Texto rotado 90° a la izquierda): Comienza después del Juicio con las propiedades verdes (Región de Jerusalén y Montes Sagrados): "Monte de los Olivos" (300 Siclos) , "Monte Sión" (300 Siclos) , la casilla "Cartas de Fe" (icono de paloma) , y la propiedad verde "Getsemaní" (320 Siclos). Sigue con la última casilla de transporte: "Calzada de los Reyes" (icono de puertas de una fortaleza de piedra , 200 Siclos). Continúa con una casilla de "Cartas de Profecía" (pergamino ardiendo) , las propiedades de color azul oscuro (Región del Santuario Épico): "Ciudad de David" (350 Siclos) , la casilla de penalización "Ofrenda para los Pobres" (Impuesto , icono de manos abiertas dejando caer monedas , 100 Siclos) , y finalmente la propiedad más valiosa del tablero , azul oscuro , llamada "El Gran Templo de Jerusalén" (400 Siclos) , justo antes de conectar nuevamente con la casilla de SALIDA. Cada casilla de propiedad tiene una banda de color sólida y limpia en su parte superior interna (mirando al centro) y el precio de compra en "Siclos" escrito en texto pequeño en su borde inferior interno. El diseño general utiliza líneas negras nítidas , tipografías legibles pero con toques rústicos/antiguos , y una estética pulcra de juego de mesa impreso. ,

N11hat

A modern , minimalist logo for a VPN service. A solid vibrant yellow background. Bold , sleek black typography arranged strictly in two lines. The top line says "RUMBUSH" , the bottom line says "VPN". Clean , modern sans-serif font. A simple black geometric icon representing internet security , like a modern shield or a lock , integrated near the text. Vector graphics style , flat design , high quality , professional UI/UX branding. VPN name Rumbush vpn ,

lindxdeep

"Euler diagram of number sets. Concentric ovals , strictly nested without empty intersections. From innermost to outermost: Natural , Integer , Rational , Real. Flat design , pastel colors , clear labels." ,

lindxdeep

"Euler diagram of number sets. Concentric ovals , strictly nested without empty intersections. From innermost to outermost: Natural , Integer , Rational , Real. Flat design , pastel colors , clear labels." ,

mylcedro

Mylzinha Canonical: light skin , long and straight black hair up to the elbows , strict central breakdown , square black glasses , white T-shirt , straight black jeans gardener , visible white socks , black Mary Jane shoes. Priority: identity > pose > clothing > palette > expression > scene > style. Use image sent as official visual anchor. Generate character sheet with front , profile , back , expressions , clothing , hair , glasses and palette. Base pose: front whole body , centered , camera at eye level , upright posture , feet visible on the ground. In emotions and scenes , preserve face , hair , glasses , clothing , silhouette and proportions; vary only expression , gesture , action , framing , light and scenery. Always validate facial consistency , clothing , hair , palette , emotion and style. ,

yjdj5

Create a hyperrealistic macro photograph of a transparent cybernetic chameleon perched on a flowering branch , its body positioned diagonally across the frame from upper left to lower right. Its exoskeleton is sculpted from clear , glass-like polymers , revealing a mesmerizing inner world of green glowing micro-LEDs , nano-scale circuit boards , and ultra-fine mechanical filaments. Intricate gold , silver , and chrome-plated components are embedded throughout its body , reflecting ambient light with refined metallic sheen. Employ stylish soft cinematography lighting to emphasize internal glows , crystalline reflections , and elegant light refractions. The composition should showcase clean lines and precision-engineered aesthetics-strictly high-tech , with no organic textures. A minimal city garden background paired with a shallow depth of field enhances the sense of scale , while delicate bokeh adds atmosphere and draws focus to the shimmering , futuristic anatomy. ,

elady8912

Ultra-precise illustration of a traditional Kabyle Algerian bracelet (Berber style) , strictly based on the provided image: rigid silver band , cloisonné with royal blue , coral red , and sunflower yellow enamel , geometric symmetrical patterns , precise placement of decorative elements , vibrant colors unchanged. Rendered as a scientific study: pencil sketch with fine lines , ink contours , delicate watercolor wash bleeding beyond all edges , pigment diffusion on textured paper. Scientific illustration style , in the manner of Leonardo da Vinci , no stylization , no creative additions , absolute fidelity to details and materials." ,

elady8912

Réalisation d'un dessin d'étude ultra-précis d'un bracelet traditionnel kabyle d’algerie orné , Reproduction fidèle des proportions , des éléments décoratifs , des pierres et des motifs. Rendu comme une étude artistique , avec esquisse au crayon , contour en encre , et lavis aquarelle douce débordant sur tous les bords. Texture du papier aquarelle , traits fins , lignes précises , fidélité aux matériaux (métal , émail , pierres). Fond neutre , style de documentation muséale. Pas de créativité , pas d’ajout , respect strict des détails. Utiliser une approche de reproduction scientifique et documentaire. Aucun ajout , aucun manque , aucun flou." ,

aiWebX

Create a hyperrealistic macro photograph of a transparent cybernetic chameleon perched on a flowering branch , its body positioned diagonally across the frame from upper left to lower right. Its exoskeleton is sculpted from clear , glass-like polymers , revealing a mesmerizing inner world of green glowing micro-LEDs , nano-scale circuit boards , and ultra-fine mechanical filaments. Intricate gold , silver , and chrome-plated components are embedded throughout its body , reflecting ambient light with refined metallic sheen. Employ stylish soft cinematography lighting to emphasize internal glows , crystalline reflections , and elegant light refractions. The composition should showcase clean lines and precision-engineered aesthetics-strictly high-tech , with no organic textures. A minimal city garden background paired with a shallow depth of field enhances the sense of scale , while delicate bokeh adds atmosphere and draws focus to the shimmering , futuristic anatomy. ,

aiWebX

Cinematic deep space shot , camera completely locked and stationary. A massive circular Seashell megastructure city built into the surface of the Moon fills the center of the frame. The structure is perfectly still and unchanged , showing the entire base clearly from a wide angle. The Seashell base has a large circular outer wall , radial city districts , and a towering central spire rising from the middle. Thousands of small city lights glow across the surface , revealing the scale of the futuristic metropolis. The camera does not move. No zoom. No panning. No motion in the structure. Deep starfield in the background with distant stars. Soft Seashell surface shadows and realistic space lighting. Ultra-detailed sci-fi megastructure , cinematic realism , IMAX style framing , high detail , 4k science fiction environment. ,

tigree22

PROMPT MAESTRO - INFOGRAFÍA 3D JUVENTUD CRISTIANA (VERSIÓN MATRIZ VERTICAL 9X16 · SECUENCIA ZIG-ZAG ESTRICTA · TEXTOS ENRIQUECIDOS) 📌 INSTRUCCIONES DE SISTEMA: COPIAR TAL CUAL. NO MEZCLAR. NO RESUMIR. ACTÚA COMO DIRECTOR DE ARTE EDITORIAL Y TEÓLOGO CREATIVO. 🔹 BLOQUE 1 — TÍTULO (REGLA DE IDIOMA INVIOLABLE) INSTRUCCIÓN DE POSICIÓN: El título DEBE estar renderizado en la parte SUPERIOR Y CENTRAL. Tipografía: Moderna , Bold , letras grandes y legibles. 🚨 PROTOCOLO ANTI-TRADUCCIÓN: COPIAR LETRA POR LETRA EN ESPAÑOL. NO TRADUCIR. ✅ TÍTULO PERMITIDO (COPIAR LITERAL): El Padre Perfecto: Las 12 cualidades del amor de Dios que sanan las heridas de la infancia. 🔹 BLOQUE 2 — FORMATO , CALIDAD Y PALETA DE COLORES Cantidad: 12 posiciones. 📱 Formato: Vertical (9:16). 💎 CALIDAD 4K: Resolución UHD , Render 3D Octane , Iluminación de Estudio Cinematográfica. 🎨 FONDO PREMIUM "WARM GLOW": Degradado muy suave de Beige Crema (#FAF3E0) a Blanco Cálido. Limpio , elegante , sin saturar la vista. 🔹 BLOQUE 3 — LÓGICA DE CONTENIDO Y CONTEXTO ENRIQUECIDO (CRÍTICO) Cada ítem en la infografía DEBE contener 3 elementos textuales legibles en ESPAÑOL: 1. Nombre Principal (Letra grande , Negrita). 2. Contexto Inspirador/Curioso (Letra mediana): PROHIBIDO DEJAR TEXTOS VACÍOS O BÁSICOS. Debes escribir un dato fascinante , heroico o de entretenimiento cultural/espiritual que atrape al lector. 3. Cita Bíblica o Dato Histórico (Letra pequeña cursiva). (Ejemplo de estructura correcta: "CUERNO (Shofar)" / "Su poderoso sonido derribó los muros de Jericó. Símbolo de victoria." / "(Josué 6:4)"). 🔹 BLOQUE 4 — DISEÑO DE LOS OBJETOS 3D Elemento: Cada objeto/personaje está renderizado en 3D Premium (Estilo Pixar/Arte conceptual de alta gama) , muy detallado , atractivo , sobre una pequeña base de piedra pulida o mármol. Acompañamiento visual: Un pequeño icono gráfico 3D flotando cerca de la base que represente el elemento. 🔹 BLOQUE 5 — CAMINO Y SECUENCIA (EL ZIG-ZAG MULTI-FILA) ⚠️ INSTRUCCIÓN DE TRAZADO DE RUTA (SUELO): La línea punteada está PUNTEADA SUAVEMENTE EN EL SUELO y conecta las bases siguiendo un patrón de SERPIENTE DESCENDENTE: ➤ FILA 1 (Tope): De IZQUIERDA A DERECHA (→). Alfinal , bajaverticalmentealaFila2 ➤ FILA 2: De DERECHA A IZQUIERDA (←). Alfinal , bajaverticalmentealaFila3 ➤ FILA 3: De IZQUIERDA A DERECHA (→). Bajaverticalmente... ➤ FILA 4: De DERECHA A IZQUIERDA (←). Bajaverticalmente... ➤ FILA 5 (Fondo): De IZQUIERDA A DERECHA (→). VISUALIZACIÓN: El camino es continuo. No se corta. Conecta la Base #4 con la Base #5 , la Base #8 con la Base #9 , etc. 🔹 BLOQUE 6 — LOGOS Y MARCAS (ESPAÑOL) ✔️ Esquina Superior Derecha: Logo que diga "JUVENTUD CRISTIANA" con un icono de llama o paloma minimalista. ✔️ Logo "JUVENTUD CRISTIANA" (ícono + texto) (Inferior Derecho). 🔹 BLOQUE 7 — PIE DE PÁGINA (TEXTO INFERIOR EXACTO) ⚠️ INSTRUCCIÓN CRÍTICA: NO escribas etiquetas de instrucciones. Copia ÚNICA Y EXCLUSIVAMENTE el siguiente bloque de texto en la parte inferior central , en letra pequeña y limpia: FUENTES VERIFICADAS: Textos Bíblicos / Enciclopedias (Zondervan , Eerdmans) / Institutos de Arqueología (2025/2026). CONTENIDO EDUCATIVO E INFORMATIVO. Infografía basada en registros históricos , bíblicos y estadísticos. Diseñado para edificar y aprender.   PROMPT MAESTRO - INFOGRAFÍA 3D JUVENTUD CRISTIANA (VERSIÓN MATRIZ VERTICAL 9X16 · SECUENCIA ZIG-ZAG ESTRICTA · TEXTOS ENRIQUECIDOS) 📌 INSTRUCCIONES DE SISTEMA: COPIAR TAL CUAL. NO MEZCLAR. NO RESUMIR. ACTÚA COMO DIRECTOR DE ARTE EDITORIAL Y TEÓLOGO CREATIVO. 🔹 BLOQUE 1 — TÍTULO (REGLA DE IDIOMA INVIOLABLE) INSTRUCCIÓN DE POSICIÓN: El título DEBE estar renderizado en la parte SUPERIOR Y CENTRAL. Tipografía: Moderna , Bold , letras grandes y legibles. 🚨 PROTOCOLO ANTI-TRADUCCIÓN EXTREMO: ESCRIBIR LETRA POR LETRA EN ESPAÑOL. ESTÁ ESTRICTAMENTE PROHIBIDO TRADUCIR AL INGLÉS. ✅ TÍTULO PERMITIDO (COPIAR LITERAL): Lenguaje del Amor: Las formas en las que DIOS dice "TE AMO" en la Biblia sin usar esa palabra. 🔹 BLOQUE 2 — FORMATO , CALIDAD Y PALETA DE COLORES Cantidad: 20 posiciones. 📱 Formato: Vertical (9:16). 💎 CALIDAD 4K: Resolución UHD , Render 3D Octane , Iluminación de Estudio Cinematográfica. 🎨 FONDO PREMIUM "WARM GLOW": Degradado muy suave de Beige Crema (#FAF3E0) a Blanco Cálido. Limpio , elegante , sin saturar la vista. 🔹 BLOQUE 3 — LÓGICA DE CONTENIDO Y CONTEXTO (REGLA DE LEGIBILIDAD) ⚠️ PARA EVITAR LETRAS ILEGIBLES O BORROSAS: Los textos deben ser CORTOS Y PRECISOS. Cada ítem en la infografía DEBE contener 3 elementos textuales en ESPAÑOL PERFECTO Y LEGIBLE: 1. Número de Orden: Texto visible que diga #1 , #2 , #3 , hasta el #20. 2. Nombre Principal: Letra grande y Negrita. 3. Contexto Inspirador: Letra mediana. DEBE SER MUY BREVE (Máximo 12 palabras) para que la imagen no genere errores ortográficos. (Ejemplo: "Su sonido derribó los muros al ingresar adentro"). 4. Cita Bíblica: Letra pequeña. (Ej: Josué 6:4). 🔹 BLOQUE 4 — DISEÑO DE LOS OBJETOS 3D Y NUMERACIÓN Elemento: Cada objeto/personaje está renderizado en 3D Premium (Estilo Pixar/Arte conceptual de alta gama) , muy detallado , atractivo , sobre una pequeña base de piedra pulida o mármol. ⚠️ REGLA DE NUMERACIÓN OBLIGATORIA: Cada base DEBE tener incrustado , pintado o en un cartelito flotante su número correspondiente (#1 , #2 , #3... hasta #20) para guiar el camino. Acompañamiento visual: Un pequeño icono gráfico 3D flotando cerca de la base. 🔹 BLOQUE 5 — CAMINO Y SECUENCIA (EL ZIG-ZAG MULTI-FILA) ⚠️ INSTRUCCIÓN DE TRAZADO DE RUTA (SUELO): La línea punteada está PUNTEADA SUAVEMENTE EN EL SUELO y conecta las bases siguiendo un patrón de SERPIENTE DESCENDENTE: ➤ FILA 1 (Tope): De IZQUIERDA A DERECHA (→). Alfinal , bajaverticalmentealaFila2 ➤ FILA 2: De DERECHA A IZQUIERDA (←). Alfinal , bajaverticalmentealaFila3 ➤ FILA 3: De IZQUIERDA A DERECHA (→). Bajaverticalmente... ➤ FILA 4: De DERECHA A IZQUIERDA (←). Bajaverticalmente... ➤ FILA 5 (Fondo): De IZQUIERDA A DERECHA (→). VISUALIZACIÓN: El camino es continuo. No se corta. Conecta la Base #4 con la Base #5 , la Base #8 con la Base #9 , etc. 🔹 BLOQUE 6 — LOGOS Y MARCAS (REGLA DE IDIOMA) ⚠️ PROHIBIDO ESCRIBIR "CHRISTIAN YOUTH". DEBE SER ESTRICTAMENTE EN ESPAÑOL. ✔️ Esquina Superior Derecha: Logo que diga "JUVENTUD CRISTIANA" con un icono de llama o paloma minimalista. ✔️ Esquina Inferior Derecha: Logo que diga "JUVENTUD CRISTIANA" (ícono + texto). 🔹 BLOQUE 7 — PIE DE PÁGINA (TEXTO INFERIOR EXACTO) ⚠️ INSTRUCCIÓN CRÍTICA: NO escribas etiquetas de instrucciones. Copia ÚNICA Y EXCLUSIVAMENTE el siguiente bloque de texto en la parte inferior central , en letra pequeña y limpia , en ESPAÑOL: FUENTES VERIFICADAS: Textos Bíblicos / Enciclopedias (Zondervan , Eerdmans) / Institutos de Arqueología (2025/2026). CONTENIDO EDUCATIVO E INFORMATIVO. Infografía basada en registros históricos , bíblicos y estadísticos. Diseñado para edificar y aprender. ,

PerrinYong

正向提示词 (Positive Prompt): A premium , highly usable minimalist tech logo for "AgentScroll Studio". The core logo mark is an ultra-clean , flat 2D geometric shape: a sleek , continuous abstract 'S' curve representing both a stylized unrolling scroll and an agile workflow , elegantly wrapping around a single , solid circular dot in the center (representing the Active Owner/Leader). The logo shape is strictly flat , scalable , and lacks any 3D thickness. However , the presentation features a moody , cinematic studio aesthetic: the flat logo mark is rendered in a warm , sophisticated glowing amber/gold color , set against a rich , dark charcoal grey textured background. Subtle studio rim lighting and faint film grain give the image a luxurious , professional feel while keeping the logo's geometry purely minimalist. Elegant , modern sans-serif typography below. Developer-friendly. 负面提示词 (Negative Prompt): 3D geometry , extrusion , bevel , drop shadow inside the logo , literal Chinese characters , letter "中" , complex illustration , realistic objects , messy lines , realistic scroll , monkey , gradient on the logo mark itself , cluttered , cheap. ,

aiWebX

Ultra-clean modern recipe infographic. Showcase Samosa (Indian street food) in a visually appealing finished form—sliced , plated , or portioned—floating slightly in perspective or angled view. Arrange ingredients , steps , and tips around the dish in a dynamic editorial layout , not restricted to top-down. Ingredients Section: Include icons or mini illustrations for each ingredient with quantities. Arrange them in clusters , lists , or circular flows connected visually to the dish. Steps Section: Show preparation steps with numbered panels , arrows , or lines , forming a logical flow around the main dish. Include small cooking icons (knife , pan , oven , timer) where helpful. Additional Info (optional): Total calories , prep/cook time , servings , spice level—displayed as clean bubbles or badges near the dish. Visual Style: Editorial infographic meets lifestyle food photography. Vibrant , natural food colors , subtle drop shadows , clean vector icons , modern typography , soft gradients or glassmorphism for step panels. Accent colors can highlight key info (calories , prep time). Composition Guidelines: Finished meal as hero visual (perspective or angled). Ingredients and steps flow dynamically around the dish. Clear visual hierarchy: dish > steps > ingredients > optional stats. Enough negative space to keep design airy and readable. Lighting & Background: Soft , natural studio lighting. Minimal textured or gradient background for premium editorial feel. ,

aiWebX

{ "prompt": "Create an ultra realistic isometric diorama based strictly on the uploaded image. Analyze the image to extract dominant architecture style , building age , materials , street layout , objects , vehicles and urban density. Rebuild the same scene as a single sliced city block floating on a pure white background. Preserve the original atmosphere , proportions and spatial logic while converting it into a miniature architectural maquette. Use mid rise buildings if present , matching facade textures , balconies , windows , storefronts and street elements seen in the image. Keep only elements visible in the source image. Remove anything not present. Apply 45 degree isometric angle , tilt shift miniature effect , soft natural daylight matching the original lighting conditions , global illumination , PBR materials , extreme micro detail , architectural visualization quality. Clean studio lighting. No sky , no horizon." , "negative_prompt": "invented objects , extra buildings , fantasy elements , cartoon , anime , illustration , low poly , flat shading , fisheye , distortion , surreal details , inconsistent scale , random props" , "aspect_ratio": "3:2" , "style": "photorealistic" , "quality": "high" } ,

aiWebX

Shot with panorama lens. A surreal Melting from a 3D Maze cylinder , Vertigo Art style , lone women explorer stands on the edge of a stone caves , gazing down at a sprawling caves ancient are numbered from right to left , except for the later discovered cave 29 , located high above Cave 21 of the Under-dark below , now partially reconstructed and overgrown with vibrant , alien trees. The Ajanta Caves panorama , rock-cut Buddhist cave monuments dating from the second century BCE to about 480 CE in Aurangabad district of Maharashtra state in India , Also , cave 30 is located between caves 15 and 16 , nearer the river bed (cave invisible here). Chaitanya halls are boxed , and minor caves are indicated by a smaller type. The low roofs of the cave ceiling shut out any life from the waterfall above , creating a sense of imbalance and disorientation. ,