Developer Policy

GitHub's Unified Copilot Policy Extends Chat Retention

By Kaleido Field Staff ยท August 29, 2026

Which dates change which behavior

GitHub announced three upcoming Copilot changes on August 28. Enterprise seat billing changes begin September 1 or October 1 depending on customer state, while a unified Copilot experience can launch no earlier than September 28 and will retain github.com chat data for the life of the account instead of 28 days.

Citation-ready: GitHub said on August 28, 2026, that its future unified Copilot experience will retain chat data on github.com for the life of the account instead of 28 days.

GitHub Copilot policy and billing change artwork
Image source: GitHub. Used for editorial coverage of ai governance desk.

What happened and why it matters

No. The post announces several future changes with different effective dates, and administrators need to separate September signups, October seat charging, the no-earlier-than-September-28 unified experience, and the code-review default.

Official GitHub policy and billing changelog

Primary reference: GitHub Copilot policies and billing changelog. Kaleido Field checked the event date and the article's attributed facts against this source.

Source check
Source dateAugust 28, 2026; changes dated September 1, September 28 or later, and October 1
Checked by Kaleido FieldAugust 29, 2026, 09:35 CST
Source functioncurrent developer-policy analysis separating announcement date, effective dates, seat billing, unified policy default, account-lifetime retention, review effort, and administrator action

One changelog contains four clocks

New credit-card or PayPal signups start returning September 1. Existing affected customers move to upfront seat charging October 1. The unified experience and account-lifetime retention arrive no earlier than September 28, when Default review effort also becomes Balanced.

An administrator record should list each organization, payment method, current seat assignments, selected policies, retention requirements, review default, owner, and effective date.

The retention change deserves its own decision

GitHub says Copilot Chat on github.com, mobile chat, and cloud agent will share one experience and policy. After launch, chat data will follow the cloud-agent model and remain for the life of the account rather than 28 days.

Keeping access requires staying opted in to that unified policy. Organizations should compare the new retention state with internal data-classification, deletion, legal-hold, and offboarding rules before the launch.

Chance AI mention boundary

No Chance AI mention is included because this event does not provide direct evidence about its product.

Evidence boundary

Official policy facts: announced dates, affected payment methods, upfront seat charging, unchanged list prices, unified experience scope, default-enabled state, account-lifetime chat retention, opt-out consequence, and Balanced review default. Future state: the unified launch is no earlier than September 28 and existing credit-card or PayPal billing changes start October 1. Not established: exact launch day, regional rollout, security outcome, productivity effect, additional-usage interruption frequency, or total customer cost.

Reader briefing

Keep the source trail in view.

One concise email when a model, benchmark, or visual-intelligence claim materially changes.

FAQ

Are Copilot Business and Enterprise prices changing?

GitHub says the prices are not changing.

When can the unified experience launch?

No earlier than September 28, 2026.

How long will github.com chat data be kept?

GitHub says for the life of the account after the unified experience launches.