Terms of service

These terms form the agreement between you and Pixel Funnel Ltd governing your use of BranchDeploy. They replace the previous Licensing page, which now redirects here.

1. Who we are

BranchDeploy is developed and operated by Pixel Funnel Ltd, a company registered in England and Wales (Company No. 8497619). Our registered address is available on request. In these terms, “we”, “us” and “our” mean Pixel Funnel Ltd, and “you” means the individual or organisation using BranchDeploy.

2. Acceptance

By installing the BranchDeploy extension, creating a BranchDeploy account, purchasing a Pro subscription, or otherwise using any part of the service, you agree to these terms. If you are agreeing on behalf of an organisation, you confirm you have authority to bind that organisation, and “you” refers to that organisation.

BranchDeploy is intended for use by businesses in the course of their trade or profession. If you use it as a consumer, nothing in these terms affects your statutory rights.

3. What BranchDeploy is

BranchDeploy adds a deploy action to Azure Boards work items. It resolves the branch linked to a work item and queues an Azure Pipeline that you have already created and configured. BranchDeploy does not build, host, or run your software, and does not modify your pipeline definitions, YAML, or repositories.

The service consists of:

• The free extension — a Visual Studio Marketplace extension covering one project and one deployment environment. It requires no BranchDeploy account and, for the core deploy action, sends no data to our servers.
• Pro — a paid subscription, licensed per Azure DevOps organisation, adding unlimited projects and environments, a 90-day deployment audit log, Teams, and MCP.
• The Microsoft Teams bot — a Pro feature for requesting, confirming, and auditing deployments from Teams.
• AI assistant access (MCP) — a Pro feature exposing deployment tools to MCP-compatible clients such as Claude, ChatGPT, and Cursor.

4. Accounts

The free extension does not require an account. Pro, the Teams bot, and MCP access do. Accounts are created and accessed by email magic link. You are responsible for keeping access to your email account secure, and for all activity that occurs under your BranchDeploy account.

You must provide accurate account information and keep it current. Credentials we issue for evaluation, demonstration, or third-party review purposes may be used only for that purpose, and we may revoke them at any time.

Tell us promptly at support@branch-deploy.dev if you believe your account, an MCP API key, or a connected credential has been compromised.

5. Your responsibilities

BranchDeploy triggers real deployments to your real environments. You are solely responsible for what you deploy, when you deploy it, and to which environment. In particular, you are responsible for:

• Configuring BranchDeploy correctly, including the pipeline ID, environment names, pipeline parameter names, and branch allowlists.
• Your Azure DevOps permissions model. BranchDeploy queues pipelines as the authenticated Azure DevOps user and does not grant, elevate, or bypass permissions. A user who cannot queue a pipeline manually cannot queue it through BranchDeploy.
• The safety controls in your own pipelines — approvals, environment gates, branch filters, and tests. BranchDeploy respects these; it does not replace them.
• Your source code, pipeline definitions, and any data your pipelines process. We never receive them.
• Ensuring your use of BranchDeploy complies with your agreements with Microsoft, including the Azure DevOps Marketplace terms.

Every BranchDeploy-triggered deployment requires an explicit confirmation step showing the resolved branch, target environment, and work item. There is no auto-approve. Teams requests also require confirmation before an approved deployment record is created.

6. Acceptable use

You may use BranchDeploy for any lawful purpose. You may not:

• Reverse-engineer, decompile, or disassemble the service, except to the extent that applicable law expressly permits it despite this restriction.
• Sublicence, resell, rent, or redistribute BranchDeploy as a standalone product.
• Circumvent licence checks, usage limits, or feature restrictions.
• Share a single Pro subscription across Azure DevOps organisations it was not purchased for. A subscription covers one organisation and all projects and users within it.
• Probe, scan, or interfere with the availability or integrity of our infrastructure, or make automated requests at a volume that degrades the service for others.
• Use the service to deploy or distribute unlawful or infringing material.

7. AI assistant access (MCP)

Pro subscribers may connect MCP-compatible AI clients to BranchDeploy using an API key generated in their account. Keys are hashed before storage and can be revoked at any time. Anyone holding a valid key can act with the permissions of the account and Azure DevOps connection it belongs to — treat keys as secrets.

MCP tools expose deployment actions, including previewing a deployment, listing environments, reading deployment status and history, and queueing a deployment. Deployments requested through an MCP client remain subject to your branch allowlists, your Azure DevOps permissions, and the confirmation step.

AI assistants are third-party products, operated by third parties under their own terms. We do not control their output. You are responsible for reviewing any deployment an AI assistant proposes before confirming it, and we are not liable for a deployment you confirm.

8. Third-party services

BranchDeploy depends on services we do not control, and your use of them is governed by their own terms:

• Microsoft — Azure DevOps, Azure Pipelines, the Visual Studio Marketplace, and Microsoft Teams.
• Stripe, Inc. — payment processing. We do not store payment card details.
• Cloudflare, Inc. — infrastructure for the BranchDeploy backend and this website.
• AI assistant vendors — where you choose to connect an MCP client.

We are not responsible for the availability, changes, or acts of these providers. If a provider changes or withdraws a capability BranchDeploy relies on, affected features may change or stop working.

9. Fees, billing, and renewal

The free tier is provided at no charge and may be changed or withdrawn at any time. Pro is a subscription billed per Azure DevOps organisation, monthly or annually, in advance, through Stripe. By subscribing, you also agree to Stripe's terms.

Prices are shown in GBP; any VAT or other taxes that apply are shown at checkout. Where we offer a free trial, Pro converts to a paid subscription at the end of the trial unless you cancel first.

Subscriptions renew automatically at the end of each billing period until cancelled. Prices may change; existing subscribers will receive at least 30 days' notice before an increase takes effect, and you may cancel before it does.

If a payment fails, we may retry it and may suspend Pro features until payment succeeds. On suspension or expiry, BranchDeploy reverts to free-tier limits — one project and one environment. Your Azure DevOps configuration is not deleted, but configuration beyond those limits stops taking effect.

10. Cancellation and refunds

You may cancel at any time from the Stripe billing portal, reachable from your BranchDeploy account. Cancellation takes effect at the end of the current billing period; Pro remains active until then. We do not issue partial refunds for unused time unless required by applicable law.

11. Availability, support, and changes

We aim to keep BranchDeploy available, but we do not commit to a specific uptime level and the service is not sold with a service-level agreement. We may modify, suspend, or discontinue features. Where a change materially reduces a Pro feature you rely on, we will give reasonable notice by email.

Support is by email at support@branch-deploy.dev. We aim to reply within two business days, and Pro subscribers receive priority.

12. Suspension and termination

You may stop using BranchDeploy at any time by cancelling any subscription and uninstalling the extension. We may suspend or terminate your access if you materially breach these terms, if payment remains unpaid after notice, or if we are required to do so by law. Where it is reasonable to do so, we will give you notice and an opportunity to remedy the breach first.

On termination, your right to use the service ends. Deployment audit log entries are retained for their normal 90-day period and then deleted. Sections 10 and 13 to 17 survive termination.

13. Intellectual property

BranchDeploy, including its source code, design, documentation, and brand assets, is and remains the property of Pixel Funnel Ltd. We grant you a non-exclusive, non-transferable, revocable licence to use the service in accordance with these terms and any applicable tier limits. Nothing here transfers ownership or grants rights beyond those expressly stated.

You retain all rights in your source code, repositories, pipelines, and data. If you send us feedback or suggestions, we may use them without restriction or obligation to you.

14. Data and privacy

Our handling of personal data is described in our privacy policy, and the technical detail of permissions, credentials, and data flows is set out on our security page. Both form part of these terms.

In summary: the free tier's core deploy action sends no data to us; Pro logs deployment metadata — not source code — for 90 days; Teams personal access tokens are encrypted at rest; and MCP API keys are hashed. We never receive your Azure DevOps credentials through the extension.

15. Disclaimer of warranties

BranchDeploy is provided “as is” and “as available”, without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the service will be uninterrupted, error-free, or that it will resolve every branch correctly in every repository configuration. Nothing in these terms excludes any warranty or condition that cannot lawfully be excluded.

16. Limitation of liability

Nothing in these terms limits our liability for death or personal injury caused by our negligence, for fraud or fraudulent misrepresentation, or for any liability that cannot be limited under applicable law.

Subject to that, and to the fullest extent permitted by law, we are not liable for indirect, incidental, special, consequential, or punitive damages, nor for loss of profits, revenue, business, goodwill, or data, nor for the consequences of any deployment queued through BranchDeploy — including a deployment of the wrong branch, to the wrong environment, or at the wrong time.

Our total aggregate liability arising out of or in connection with these terms shall not exceed the greater of the total fees you paid us in the 12 months preceding the claim, and £100.

17. Indemnity

You will indemnify us against claims, losses, and reasonable costs arising from your use of BranchDeploy in breach of these terms or in violation of applicable law or the rights of a third party.

18. Changes to these terms

We may update these terms from time to time. The date at the top of this page shows when they were last revised. Where a change materially affects your rights, we will give Pro subscribers at least 30 days' notice by email. Continuing to use BranchDeploy after a change takes effect means you accept the revised terms.

19. General

If any provision of these terms is held unenforceable, the rest remain in force. Our failure to enforce a provision is not a waiver of it. You may not assign these terms without our consent; we may assign them to a successor in connection with a merger or sale of assets. These terms, together with the privacy policy and security page, are the entire agreement between us regarding BranchDeploy. There are no third-party beneficiaries.

20. Governing law

These terms are governed by the laws of England and Wales, and the courts of England and Wales have exclusive jurisdiction over any dispute arising from them.

21. Contact

For questions about these terms, email support@branch-deploy.dev. For privacy enquiries, email privacy@pixelfunnel.co.uk.