GitHub Copilot Policy and Billing Changes: Upfront Seat Charges and Longer Chat Retention

GitHub Copilot is a common part of how commercial software gets written, whether by an in-house team or by an outside firm providing software development services. On August 28, 2026, GitHub published a changelog notice titled Upcoming changes to GitHub Copilot policies and billing, covering three separate changes with effective dates on September 1, September 28 and October 1, 2026.

None of the three changes the listed price of a seat. Together, though, they affect when you are charged, how long Copilot chat data is kept, which administrative policy controls access, and how much effort Copilot spends on automated code review by default.

If your organization pays for Copilot Business or Copilot Enterprise, these are administrative settings someone should look at this month. This article sets out what GitHub announced and what to check.

Change 1: sign-ups reopened and seats are charged upfront

GitHub's notice says new sign-ups for Copilot Business and Copilot Enterprise reopened on September 1, 2026, with updated account vetting. Alongside that, the billing model for seats changes. According to the notice, new seat assignments on these plans require payment for the seat before the user gets Copilot access, and for existing customers the change applies from October 1, 2026, with assigned seats charged upfront at the start of the next billing cycle.

The notice also says that additional payment is required when usage goes beyond the included allowance, and that included usage may be prorated monthly in line with how seat costs are prorated.

GitHub lists what stays the same: pricing is unchanged, revoking a seat does not produce a prorated refund, seats added in the middle of a cycle are still prorated, and spend controls and usage tracking remain available. It adds a caution that fully canceling Copilot and returning later may trigger the updated vetting and billing behavior.

Change 2: one unified Copilot experience under a single policy

The second change is described as taking effect no earlier than September 28, 2026. GitHub says Copilot Chat on github.com, Copilot Chat in GitHub Mobile and the Copilot cloud agent are being relaunched as a single experience. The cloud agent is the feature that works on a task in GitHub's own environment and returns a proposed change for review, as opposed to an assistant running inside a developer's editor.

Two details in the notice matter to administrators. First, the separate policies that controlled those three features are replaced by one policy, and the unified experience is enabled by default. The notice says an organization that opts out loses Copilot access on github.com and in GitHub Mobile.

Second, the notice says chat data in the unified experience is retained for the lifetime of the account, where it was previously kept for 28 days. That is a material change for any company with a data retention policy.

Because GitHub worded the date as "no earlier than", and we did not find a separate launch confirmation in the September 2026 changelog entries we reviewed, check your own Copilot settings to see whether the unified policy is already live for your account.

Change 3: Copilot code review defaults to Balanced

The third change was scheduled for September 28, 2026. GitHub's notice says the default effort level for Copilot code review moves from Lite to Balanced, for existing and new repositories and organizations that use the feature. Organizations that wanted to keep Lite as the default were told to select it explicitly in repository or organization settings before that date.

The notice does not put a number on the difference in cost or usage between the two levels. If your team uses Copilot code review heavily, it is reasonable to assume a more thorough default review consumes more of your included usage, but confirm that against your own usage reports instead of relying on the assumption.

Related controls now in preview

Separately from the August 28 notice, GitHub's weekly Copilot release notes published on September 25, 2026 describe two features in public preview that are relevant to risk management. One is local sandboxing in the Copilot app, which GitHub says limits an agent's access to files, networks and credentials. The other is assisted approvals for Copilot agent sessions in JetBrains IDEs, which automatically approve tool calls judged to be low risk.

Both are previews, not generally available features, so they may change. They point in different directions: sandboxing narrows what an agent can touch, while assisted approvals reduce how often a person is asked to confirm an action. A team should decide deliberately whether to enable either one.

What this means for your business

This section is our interpretation, offered as guidance and not as legal advice.

The billing change is mostly a cash flow and housekeeping matter. Paying upfront for every assigned seat, with no refund when a seat is revoked, makes unused seats more expensive to ignore. Companies that assign Copilot to everyone by default, including people who rarely write code, have a clear reason to review assignments.

The retention change is the one to take to whoever handles privacy and security. Developers paste code, error messages and sometimes customer data into chat. Moving from a 28-day window to retention for the life of the account changes how long that material exists on a third-party service. UK companies working under UK GDPR and US companies with contractual or state-level privacy obligations often commit to specific retention periods, so compare the new behavior with what your policies and client contracts say. GitHub's own documentation and your agreement with GitHub are the authority on exactly what is stored and what controls exist.

If you outsource development, the same questions apply to your supplier. Your code may pass through their Copilot account, not yours. Our guide on how to outsource software development from the US or UK covers the wider set of questions to ask a vendor about tools and data handling.

What to do next

An organization owner or enterprise administrator can cover most of this in one sitting:

• Open Copilot settings and read the unified experience policy. Decide whether it should stay enabled, knowing that opting out removes Copilot on github.com and GitHub Mobile.
• Ask your privacy or security lead to review the chat retention change against internal policy and client commitments, and give developers clear guidance on what must not be pasted into chat.
• Check the code review effort setting at organization and repository level and choose Lite or Balanced deliberately.
• Audit seat assignments before your next billing cycle, remove seats that are not used, and confirm spend controls are set for usage beyond the included allowance.
• If a vendor writes code for you, ask which AI coding tools they use on your project and under whose account.

Conclusion

GitHub's August 28, 2026 notice introduced upfront seat billing for Copilot Business and Enterprise, a single policy for a unified Copilot experience with much longer chat retention, and a Balanced default for Copilot code review. Seat prices did not change, but the defaults did, and defaults are what most organizations end up running. A short review of settings, seats and retention is enough to make sure the new behavior matches what your company intends.

Entrant Technologies builds websites, web applications, mobile apps and custom software. If you want to discuss how AI coding tools would be used on a project we build for you, you can contact us and ask.