
Manage GitHub
What you don't know !
Silent Waste
84%
of people lose money every month on unused services
Lack of Transparency
60%
of users feel lost facing cancellation terms
Budget Illusion
82%
of consumers underestimate the cost of their automatic withdrawals
Fear of Commitment
44%
of subscribers have experienced a 'commercial trap' experience
Legal Validation
All our letters are written by legal experts to guarantee their compliance.
Legal Commitment
We generate legally binding documents that your provider is obligated to honor.
Immediate Efficiency
Free yourself from your commitments in less than 2 minutes, directly online.
Budget Optimization
Regain control of your finances by stopping superfluous withdrawals.
Cancel GitHub: The Right Way
How to cancel your GitHub subscription and delete your account in the UK
What is GitHub and why you might want to cancel
GitHub is the world's leading software development platform, hosting over 100 million developers who collaborate on code, manage projects, and build software together. Founded in 2008 and acquired by Microsoft in 2018, GitHub provides cloud-based repositories, version control using Git, and automation tools that developers rely on daily. For UK users, GitHub operates under the same global infrastructure whilst complying with British consumer protection laws.
You might use GitHub as an individual developer showcasing your portfolio, as part of a professional team managing private repositories, or as part of an enterprise organisation with advanced security requirements. The platform hosts everything from personal hobby projects to critical open-source software powering the internet. However, if you've decided GitHub no longer meets your needs, or you're paying for features you don't use, cancelling is straightforward once you know the steps.
At Stopee, we understand that subscription fatigue is real. You may have upgraded to a paid plan months ago, only to find yourself using the free tier's features. Or perhaps you've switched to a competing platform. Whatever your reason, we'll walk you through cancelling your GitHub subscription and protecting your data throughout the process.
Is your GitHub account costing you money?
First, determine whether you're actually paying for GitHub. Many developers use the Free plan indefinitely and never spend a penny. If you've upgraded to Team or Enterprise plans, or subscribed to GitHub Copilot, you're incurring monthly charges against your payment method. Log into your GitHub account and navigate to your billing settings to see your current plan and upcoming charges.
Common reasons UK users cancel GitHub
You might cancel because you've completed a project and no longer need the premium features. You could be moving your repositories to another platform like GitLab or Gitea. You may have upgraded for GitHub Copilot during a trial, only to find the AI assistant doesn't match your workflow. Or perhaps you're consolidating your software development tools and eliminating redundant subscriptions. Whatever your reason, Stopee is here to ensure you cancel without losing access to your code or incurring unexpected charges.
GitHub pricing and subscription plans explained
Understanding GitHub's pricing structure helps you decide whether cancellation makes sense or whether downgrading to the Free plan better serves your needs.
Current GitHub pricing in GBP
| Plan | Cost | Key features | Best for |
|---|---|---|---|
| Free | £0/month | Unlimited public and private repositories, 2,000 CI/CD minutes, 500MB package storage, community support | Individual developers and open-source contributors |
| Team | £3.20 per user/month | Everything in Free, plus 3,000 CI/CD minutes, 2GB package storage, required code reviewers, branch protection rules | Professional development teams and small businesses |
| Enterprise | £16.80 per user/month | 50,000 CI/CD minutes, 50GB package storage, SAML authentication, advanced auditing, security features, dedicated support | Large organisations with compliance and security requirements |
| GitHub Copilot Individual | £8/month | AI-powered code suggestions, works in VS Code and JetBrains IDEs | Individual developers wanting AI assistance |
| GitHub Copilot Business | £15 per user/month | Copilot for teams, organisation-wide policies, audit logs | Teams deploying AI coding assistance across departments |
What you need to know before cancelling
Cancelling your GitHub paid plan doesn't delete your account or repositories. You'll automatically move to the Free tier, keeping access to unlimited public and private repositories. This matters because many users don't realise they can downgrade rather than cancel entirely, preserving their code history and contributions.
If you're on a Team or Enterprise plan and need to cancel, check whether your repositories exceed the Free tier's CI/CD minute allocation. If you're running resource-intensive automated workflows, you may hit limits after cancellation. Plan your workflow optimisation before you cancel, or export critical repositories to external storage as a backup.
Warning: Cancelling a GitHub Copilot subscription is separate from cancelling your main GitHub plan. You can end Copilot access whilst keeping your Team or Enterprise plan active, or vice versa. Confirm which subscription you're actually ending before proceeding.
Your consumer rights when cancelling GitHub in the UK
The UK Consumer Rights Act 2015 protects you when cancelling digital services, including GitHub subscriptions.
What the consumer rights act 2015 guarantees
You have the right to receive services that are as described, fit for purpose, and delivered with reasonable care and skill. If GitHub fails to deliver these standards, you can request a refund. Additionally, you have a 14-day cooling-off period from the date you purchase a subscription to cancel and receive a full refund, provided you haven't substantially used the service. This right applies to both Team and Enterprise plans.
After the 14-day period, GitHub's own cancellation policy takes over. Most paid plans can be cancelled at any point in your billing cycle. You'll stop being charged at the end of your current billing period, but you won't receive a refund for the unused portion of your current month. This is standard practice for monthly subscriptions across the UK.
Escalation points if GitHub refuses to refund
If you cancel within the 14-day cooling-off window and GitHub refuses a refund, or if you experience technical issues preventing cancellation, you can escalate to the Information Commissioner's Office (ICO) or the Citizens Advice Consumer Service. Document all communication with GitHub support, including timestamps and case numbers. Stopee recommends keeping screenshots of your billing page and cancellation requests as evidence if you need to dispute a charge with your bank or payment provider.
How to cancel your GitHub subscription step by step
Cancelling GitHub involves accessing your billing settings and confirming the cancellation. Here's exactly what you need to do.
Cancelling on the GitHub website or desktop
- Log into your GitHub account at github.com using your username and password.
- If you use two-factor authentication (2FA), have your authenticator app or backup codes ready.
- Click your profile picture in the top right corner and select "Settings" from the dropdown menu.
- On mobile, tap the menu icon (three horizontal lines) and scroll to "Settings".
- In the left sidebar, click "Billing and plans".
- You'll see your current plan, next billing date, and payment method on this page.
- Under "Current plan", click "Edit plan" or the downgrade option.
- To cancel, you're actually downgrading to the Free plan (the lowest tier).
- Select the Free plan and click "Continue".
- GitHub will show a summary of what features you'll lose and what you'll retain.
- Review the warning about any features you'll no longer have access to, then click "Downgrade to Free" to confirm.
- Your paid plan access ends immediately, but you can use GitHub free features right away.
- You will not be charged again after your current billing cycle completes.
Pro tip: If you want to cancel GitHub Copilot separately from your main plan, navigate to "Billing and plans", find the Copilot section, and click "Cancel Copilot subscription". This removes AI features but keeps your main GitHub access unchanged.
Cancelling if you're part of an organisation
If your GitHub account belongs to an organisation with a Team or Enterprise plan, you cannot cancel the plan yourself. Only the organisation owner or billing manager can downgrade or cancel. Contact your organisation administrator to request cancellation. They'll have access to the billing settings and can process the change.
Warning: If you're an organisation owner wanting to cancel a Team or Enterprise plan covering multiple users, all team members will lose premium features once the plan downgrades. Notify your team before initiating cancellation to avoid unexpected disruptions.
What happens after you cancel GitHub
Cancelling doesn't delete your account or repositories, which is reassuring news. Understanding what changes helps you prepare for life after cancellation.
Your data and repositories after cancellation
All your repositories remain accessible under the Free plan. Public repositories stay public, private repositories stay private, and your contribution history is preserved forever. You can continue pushing code, opening pull requests, and collaborating with others. The only limitations are the removal of premium features like advanced CI/CD minutes or organisation management tools.
If you need to export your repositories before cancelling, use Git's clone command to create local backups. For each repository, run `git clone --mirror https://github.com/username/repository.git`, which creates a complete copy including all branches and history. This takes minutes and ensures you have offline access to your code.
Timeline of changes after downgrading
Your cancellation takes effect immediately when you confirm the downgrade. You lose access to paid features right away, including GitHub Copilot suggestions and advanced CI/CD minutes. However, you retain access to all your repositories and can continue using the Free plan indefinitely at no cost. No refund is issued for the remainder of your billing cycle unless you cancelled within the 14-day cooling-off period.
After 30 days of account inactivity, GitHub may deactivate your account temporarily, though your repositories remain safe. If you return and log in, your account reactivates automatically with no data loss.
Refunds and billing after cancellation
Understanding GitHub's refund policy prevents disappointment and helps you claim money you're entitled to.
When you receive a refund
You receive a refund only if you cancel within 14 days of your initial subscription purchase, provided you haven't substantially used the service. "Substantially used" means accessing advanced features available only on your paid tier, such as Organisation management or CI/CD minutes beyond the Free tier's allocation. Simply logging in or viewing repositories doesn't trigger this exclusion.
If you're entitled to a refund, GitHub processes it within 14 business days to your original payment method. The refund appears as a credit on your bank or credit card statement. Check your payment account around day 21 after requesting cancellation to confirm receipt. If the refund doesn't appear, contact GitHub support with your cancellation date and original transaction ID.
How to request a refund if you're within the cooling-off period
- Log into GitHub and navigate to "Settings" > "Billing and plans".
- Click "Contact support" in the top right corner or visit github.com/support.
- Select "Billing" as the issue category and describe your request: "I purchased a [plan name] subscription on [date] and would like to request a refund within the 14-day cooling-off period under the Consumer Rights Act 2015".
- Attach a screenshot of your billing page showing the purchase date and amount.
- Submit the request and note your support ticket number.
- GitHub support typically responds within 2-3 business days. If they refuse, escalate to Citizens Advice Consumer Service using your support ticket as evidence.
Pro tip: Keep all confirmation emails from GitHub, screenshots of your billing page, and dated records of when you requested cancellation. This documentation protects you if a dispute arises.
Common mistakes when cancelling GitHub
Cancellation should be painless, but we've seen users trip themselves up. Learning from these mistakes saves you time and frustration.
Mistake 1: thinking cancellation deletes your account
Many users hesitate to cancel because they fear losing their repositories and contribution history forever. This isn't true. Downgrading to the Free plan preserves everything. Your public repositories, private repositories, pull requests, issues, and all collaboration history remain intact. The only difference is you lose access to premium features. If you want to delete your account entirely, that's a separate, deliberate action you must request specifically.
Mistake 2: cancelling without exporting cI/CD secrets or workflows
If you've created GitHub Actions workflows or stored secrets for CI/CD pipelines, cancelling removes your access to advanced minutes and may disable automated deployments. Before cancelling, export all your workflow files (stored in `.github/workflows/`) and note any secrets you've configured. You can re-import these into a new platform or keep them for reference if you return to GitHub later.
Mistake 3: forgetting about copilot subscriptions
GitHub Copilot runs as a separate subscription from your main GitHub plan. You can have an active Copilot subscription even after downgrading your GitHub plan to Free. Check your "Billing and plans" page carefully and cancel Copilot separately if you're not using it. Stopee frequently encounters users paying £8 monthly for Copilot they forgot about.
Mistake 4: missing the 14-day refund window
Your cooling-off period starts the day you purchase a subscription, not the day you first try the service. If you upgraded on a Monday, you must request cancellation by the following Monday to qualify for a refund. After 14 days, refunds aren't guaranteed under consumer law. Mark your calendar or set a phone reminder when you upgrade, so you don't lose this right.
Protecting yourself: what to do before cancelling
A quick pre-cancellation checklist ensures you don't lose anything important and maximises your refund chances.
Your cancellation checklist
- Check your billing date. Calculate whether you're within 14 days of your subscription start date.
- If yes, you may qualify for a full refund. Document the purchase date.
- If no, expect no refund under consumer law. Cancellation takes effect at the end of your current billing cycle.
- Export all critical repositories using `git clone --mirror`. Store them locally or on external backup storage.
- Review your GitHub Actions workflows and export any `.github/workflows/` files you want to preserve.
- Check for any GitHub Pages websites you're hosting. Note their URLs so you can migrate them if needed.
- Screenshot your current billing page, showing your plan name, billing date, and amount charged.
- Review any organisations you manage. If you're the owner, confirm other admins are in place before your plan downgrades.
- Cancel GitHub Copilot if you're subscribed, separate from your main plan cancellation.
- Document today's date and your support ticket number (if applicable) for refund tracking.
Pro tip: If you're cancelling because you've switched to GitLab or Bitbucket, use their built-in repository import tools. Most competing platforms can import your GitHub repositories, issues, and pull requests automatically, preserving your history.
Comparing GitHub with alternatives
Before you cancel, consider whether switching rather than cancelling better serves your needs.
GitHub versus competing platforms
| Platform | Pricing | Best for | Key difference |
|---|---|---|---|
| GitHub (Free) | £0/month | Individual developers, open-source | Largest community, best integration with Microsoft tools |
| GitLab | £0-£228/month | Teams wanting self-hosted options | Built-in CI/CD, stronger DevOps focus |
| Gitea | Self-hosted (free) | Organisations needing complete control | Lightweight, runs on your own servers |
| Bitbucket | £0-£8/month | Teams already using Jira | Stronger Atlassian ecosystem integration |
| Codeberg | £0/month | Open-source projects, privacy-conscious users | Non-profit, privacy-focused, community-run |
If you're paying for GitHub Team at £3.20 per user monthly primarily for CI/CD minutes, GitLab's free tier includes 400 CI/CD minutes, which might suffice. If you need advanced security scanning or dedicated support, you may actually need Enterprise features elsewhere too. Stopee recommends trialling your alternative before cancelling GitHub entirely, so you can migrate smoothly without losing access during the transition.
How stopee helps you cancel GitHub with confidence
Cancelling subscriptions shouldn't feel risky or complicated. At Stopee, we've helped thousands of consumers cancel software subscriptions safely and recover refunds they're entitled to. Our step-by-step guides remove the guesswork, flag the traps, and ensure you know your consumer rights before you cancel.
Whether you're cancelling GitHub because you've switched platforms, eliminated redundant tools, or simply decided the paid features aren't worth your money, Stopee gives you the knowledge to act confidently. We explain the 14-day cooling-off period under the Consumer Rights Act 2015, show you exactly where to click to downgrade, and tell you exactly what happens to your repositories after you cancel.
Visit Stopee.com today to explore guides for cancelling hundreds of other subscriptions, from streaming services to productivity tools. Our mission is empowering you to take control of your subscriptions and your spending. Stopee has helped thousands of consumers cancel GitHub and recover money they didn't know they were entitled to claim.
Summary: cancelling GitHub in the UK
| Step | What to do | Time needed |
|---|---|---|
| 1. Check if you're owed a refund | Count days since subscription start. If under 14 days, you may qualify for a full refund under consumer law. | 2 minutes |
| 2. Back up your repositories | Run `git clone --mirror` for critical repos and export any GitHub Actions workflows. | 10-30 minutes |
| 3. Log into GitHub settings | Navigate to github.com, click your profile, select "Settings", then "Billing and plans". | 1 minute |
| 4. Downgrade to Free | Click "Edit plan", select Free, review changes, and confirm "Downgrade to Free". | 2 minutes |
| 5. Request a refund (if applicable) | Contact GitHub support within 14 days citing the Consumer Rights Act 2015, attaching your billing screenshot. | 3 minutes to request, 3-5 days to receive |
| 6. Confirm no further charges | Check your bank account after your final billing date. No charge should appear after downgrade takes effect. | 30 seconds |
Contact information and next steps
If GitHub refuses your cancellation request or disputes a refund you're entitled to under the Consumer Rights Act 2015, escalate your complaint to:
Citizens Advice Consumer Service
Phone: 0808 223 1133 (free, Monday-Friday 09:00-17:00)
Website: citizensadvice.org.uk
Email complaints to your local Citizens Advice office.
Information Commissioner's Office (ICO)
Website: ico.org.uk
Phone: 0303 123 1113
Use this channel if your complaint involves data protection or privacy breaches.
Your bank or payment provider
If GitHub continues charging after you've cancelled, contact your bank's dispute team. They can reverse unauthorised charges and investigate why the cancellation didn't stop the billing cycle.
Cancelling GitHub doesn't have to be stressful. You've learned exactly where to click, what rights protect you, and what to expect after you downgrade. Stopee stands ready to guide you through cancelling any other subscriptions cluttering your life. Visit Stopee.com now and take back control of your spending.