GitHub · GitHub Terms of Service · View original document ↗

Payment, Billing, and Pricing Changes

Medium severity High confidence Explicitdocumentlanguage Unique · 0 of 343 platforms
Share 𝕏 Share in Share 🔒 PDF
Recent governance activity GitHub recorded 2 documented changes in the last 30 days.
Start monitoring updates
Monitor governance changes for GitHub Create a free account to receive the weekly governance digest and monitor one platform for governance changes.
Create free account No credit card required.
Document Record

What it is

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

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

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.

Recent Activity

This document changed recently

Medium Apr 28, 2026

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, used, and retained for developing and improving AI and machine learning models, and identifies what controls are available to users. The practical effect is that AI-related data practices are now consolidated under dedicated contractual language rather than dispersed across general service terms.

View change record →
Medium Apr 19, 2026

GitHub's Terms of Service update on April 19, 2026 involved substantial revisions across 54 sentences, with 40 sentences removed and 4 added. The extent of change suggests modifications to core service provisions; however, without access to the specific language that was modified, removed, or added, the precise operational implications for users cannot be determined. Users should review the updated Terms directly to understand how the changes affect their usage rights, account obligations, or dispute resolution procedures.

View change record →

Clause Stability Stable

0
Changes
3
Months Monitored
May 12, 2026
First Seen
May 22, 2026
Last Seen
This clause type exists across 535 other provisions on other platforms.

Consumer impact (what this means for users)

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.

What you can do

⚠️ These actions may provide transparency or partial mitigation but may not fully address the underlying issue. Effectiveness varies by jurisdiction and individual circumstances.
  • Cancel Subscription
    Within 30 days
    If you do not agree to a price change, navigate to GitHub Settings, then Billing, and downgrade to a free plan or cancel your paid subscription before the 30-day notice period expires.

How other platforms handle this

Wise Medium

We may change our fees and exchange rate spreads at any time by giving you notice in accordance with this Agreement. Changes to fees and exchange rates may take effect immediately or on a date specified in the notice.

Stripe Medium

Stripe may revise these General Terms, the Services Terms, and the Fees at any time by posting updated versions to our website or notifying you by email. The updated version will be effective as of the time it is posted or, if we notify you by email, as stated in the email. Your continued use of the...

Uber Medium

Uber does not guarantee the availability of Services. Prices for Services may increase significantly during times of high demand. Uber will use reasonable efforts to inform you of charges that may apply. You are responsible for all charges incurred under your account.

See all platforms with this clause type →

Monitoring

GitHub has changed this document before.

Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.

Start Monitor free trial Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
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

ConductAtlas Analysis

Institutional analysis (Compliance & governance intelligence)

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.

Track 1 platform — free Try Monitor free for 14 days

Free: track 1 platform + weekly digest. Monitor: 25 platforms + same-day alerts. No credit card required.

Applicable agencies

  • FTC
    The FTC has jurisdiction over subscription billing practices and the adequacy of disclosure for automatic price changes in consumer service agreements
    File a complaint →
  • State AG
    California's Automatic Renewal Law and similar state statutes may create additional disclosure and consent obligations for subscription price changes
    File a complaint →

Provision details

Document information
Document
GitHub Terms of Service
Entity
GitHub
Document last updated
May 5, 2026
Tracking information
First tracked
May 10, 2026
Last verified
May 12, 2026
Record ID
CA-P-011573
Document ID
CA-D-00253
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
610460507af6f60333f6195921a4e0d9629d1fea528d1220cda7340159b5b46b
Analysis generated
May 10, 2026 17:12 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: GitHub
Document: GitHub Terms of Service
Record ID: CA-P-011573
Captured: 2026-05-10 17:12:21 UTC
SHA-256: 610460507af6f603…
URL: https://conductatlas.com/platform/github/github-terms-of-service/payment-billing-and-pricing-changes/
Accessed: June 27, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Compliance Governance Intelligence

Need to monitor specific governance provisions?

Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.

Arbitration clauses AI governance Data rights Indemnification Retention policies
Start Compliance free trial

Or start with Monitor →

Built from archived source documents, structured governance mappings, and historical version tracking.

Frequently Asked Questions

What does GitHub's Payment, Billing, and Pricing Changes clause do?

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.

How does this clause affect you?

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.

Is ConductAtlas affiliated with GitHub?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by GitHub.