If you pay for a GitHub plan, GitHub can change the price with at least 30 days' notice by website posting or email. If you keep using the paid service after the new price takes effect, you've agreed to pay the new amount.
This analysis describes what GitHub's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
The agreement reserves GitHub's right to raise prices unilaterally with 30 days' notice, and continued use of the paid service after that date constitutes acceptance of the new price without requiring affirmative re-authorization of the new charge amount.
GitHub's updated Terms of Service now include an explicit section governing AI features, including Copilot. The new section establishes specific contractual terms for how user data may be collected, …
Paid subscribers may see price changes take effect 30 days after notice, with continued use treated as acceptance. Monitoring the email address registered to your GitHub account for pricing change notices is the primary mechanism for identifying and responding to increases before they take effect.
How other platforms handle this
DeepL reserves the right to amend these terms and conditions at any time. Customers will be notified of changes with reasonable notice. Continued use of the services after the effective date of changes constitutes acceptance of the amended terms. DeepL may also change subscription prices, with notic...
We reserve the right to change both these terms and the fees in effect on renewal of your subscription, to reflect factors such as changes to our business, different product offerings, or new economic conditions. We will give you no less than 30 days' advance notice of any material changes via a mes...
We calculate and bill fees and charges monthly. We may bill you more frequently for fees accrued if we suspect that your account is fraudulent or at risk of non-payment. You will pay us the applicable fees and charges for use of the Service Offerings as described on the AWS Site using one of the pay...
Monitoring
GitHub has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.
"If you are on a paid plan, you agree to pay us the monthly or annual fees indicated for that service. We reserve the right to change our prices. If we do change prices, we will provide notice of the change on the Site or in email to you, at our option, at least 30 days before the change is to take effect. Your continued use of the paid Services after the price change becomes effective constitutes your agreement to pay the changed amount.— Excerpt from GitHub's GitHub Terms of Service
REGULATORY LANDSCAPE: Automatic price increases without affirmative user re-consent may engage state automatic renewal laws, including California's Automatic Renewal Law (Business and Professions Code Section 17600 et seq.), which requires clear disclosure of material changes and in some circumstances may require affirmative re-consent. The FTC Act's unfair or deceptive practices standard is relevant to the adequacy of the 30-day notice mechanism. EU consumer protection law may impose additional requirements on price modification clauses in consumer contracts. GOVERNANCE EXPOSURE: Medium. The 30-day advance notice requirement is a standard commercial practice for subscription services. The 'continued use equals acceptance' mechanism for price changes is operationally significant for procurement teams managing software subscriptions at scale, as it may result in budget exposure if change notices are not monitored. JURISDICTION FLAGS: California's Automatic Renewal Law may require affirmative acknowledgment of price increases for consumer subscribers rather than passive acceptance through continued use. EU member states with strong consumer protection frameworks may limit the enforceability of unilateral price change provisions in consumer agreements. Enterprise customers with negotiated contracts should confirm whether standard ToS pricing provisions apply or are superseded. CONTRACT AND VENDOR IMPLICATIONS: Finance and procurement teams should establish a process for monitoring GitHub billing notifications and reconciling subscription costs against approved budgets. The provision does not address refund rights for prepaid annual subscriptions where pricing changes mid-term, which is a due diligence gap for organizations on annual plans. COMPLIANCE CONSIDERATIONS: Organizations subject to California's Automatic Renewal Law should assess whether the notice-and-continued-use mechanism satisfies state disclosure requirements for their user population. Legal teams should review whether annual subscription terms lock in pricing for the subscription period or whether mid-term price changes are permitted under the standard ToS.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Watcher: 10 platforms + same-day alerts. No credit card required.
Professional Governance Intelligence
Need to monitor specific governance provisions?
Professional includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
The agreement reserves GitHub's right to raise prices unilaterally with 30 days' notice, and continued use of the paid service after that date constitutes acceptance of the new price without requiring affirmative re-authorization of the new charge amount.
Paid subscribers may see price changes take effect 30 days after notice, with continued use treated as acceptance. Monitoring the email address registered to your GitHub account for pricing change notices is the primary mechanism for identifying and responding to increases before they take effect.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by GitHub.