These Terms of Service (the "Terms") are a binding agreement between you and Merget, Inc. ("Merget", "we" or "us"). They govern the Merget merge queue: the Merget GitHub App, the dashboard at sema.merget.ai, sign-in at auth.merget.ai, the HTTP API, the MCP server, the Claude Code plugin and the CLI (together, the "Service"). By creating an Account, confirming that an Organization may be bound, paying through Checkout, or using the Service, you agree to these Terms. If you do not agree, do not use the Service.
The table below is a plain-language guide. It is not part of the agreement; the sections are.
Summary
| Section | What you find there |
|---|---|
| A. Definitions | The words these Terms use with a fixed meaning. |
| B. Accounts and eligibility | Business use, 18 or older, United States only, two-factor sign-in, one person per account, who can bind an organization, and how you accept these Terms. |
| C. The Service and the GitHub App | What Merget reads, the GitHub permissions it asks for, and the write actions you authorize in Queue and Autonomous modes. |
| D. Customer Content and Outputs | You own your content and Merget's outputs. Merget uses them to run the Service and may use them, after removing people's names and the credentials it finds, to train its own models. Deleting your data takes it out of training data within 30 days. |
| E. Acceptable use | The Acceptable Use Policy applies, and how we enforce it. |
| F. Agents, API, MCP server, plugin and CLI | Agents act as the person who authorized them, with the permissions that person chose. That person is responsible for what the agent does. |
| G. Third-party services | GitHub, Google Cloud and Vertex AI, Stripe, PostHog, Cal.com, Slack and Cloudflare, and what each does for the Service. |
| H. Fees, credits and payment | The plans, credits, the spending cap, Stripe payment, taxes, failed payments, refunds and price changes. |
| I. Term, cancellation, suspension and termination | How to cancel or downgrade, what deleting an organization or account does, and when Merget may suspend or terminate. |
| J. Privacy and data protection | The Privacy Statement applies. Merget processes your repositories for your organization, and may use them for its own model training as section D describes. |
| K. AI features | Merget is a tool, not a co-developer. Outputs can be wrong; a person reviews before merging. |
| L. Intellectual property | Merget owns the Service and its documentation. Open-source components keep their own licenses. |
| M. Preview and beta features | Features marked Preview or Coming soon may change or end. |
| N. Communications | Email to your account address and dashboard notices are how we notify you. |
| O. Disclaimer of warranties | The Service is provided "as is". Please read this carefully. |
| P. Limitation of liability | Limits on what Merget is liable for. Please read this carefully. |
| Q. Copyright (DMCA) policy | How to report copyright infringement and how to send a counter-notice. |
| R. Indemnification | You are responsible for your content, your repositories and your use of the Service. |
| S. Changes to these Terms | 30 days' notice of material changes by email; continued use after the effective date is acceptance. |
| T. Dispute resolution; binding arbitration; class-action waiver | Disputes go to individual arbitration. You may opt out within 30 days. Please read this carefully. |
| U. Governing law, export compliance and U.S. government users | Which law applies, export rules, and terms for U.S. government users. |
| V. Miscellaneous | Assignment, severability, the entire agreement, prior versions and how to contact us. |
A. Definitions
- "Account" means a Merget account for one person, created and managed at auth.merget.ai.
- "Agent" means software that a person authorizes to act for them through the Service: a coding agent, an MCP client, a script or any other OAuth client, including a runner that uses an agent key.
- "Connected Repository" means a GitHub repository that a Merget GitHub App installation linked to your Organization can see. Merget does nothing in a Connected Repository until someone turns it on in Merget.
- "Credits" means the unit Merget's work is counted and charged in, as described in section H.
- "Customer Content" means the material of yours that the Service reads or stores: the contents of your Connected Repositories at the commits Merget analyzes, pull requests, checks, reviews, commit statuses, branch rules, validation secrets, recipes and the settings you choose.
- "Documentation" means the in-app documentation at sema.merget.ai, including the pages Security and data, Plan and billing, Install the GitHub App, Connect coding agents, HTTP API and MCP server. The Documentation describes the Service as it is and is part of these Terms.
- "Member" means a person seated in an Organization. "Owner" means a Member with the Owner role in that Organization.
- "Merget Models" means machine-learning models that Merget trains, fine-tunes or otherwise develops, whether Merget runs them itself or through a Model Service in Merget's own account.
- "Model Service" means a third-party machine-learning service the Service uses to resolve conflicts or repair findings, or that Merget uses to fine-tune Merget Models. Today it is Google Vertex AI, used in Merget's own Google Cloud project.
- "Organization" means the unit in Merget that owns repositories, seats and merge queues. Every Account has a personal Organization and may own up to 5 Organizations.
- "Outputs" means what the Service produces for you: findings, merge briefs, prepared fixes, conflict resolutions, run reports, code graph answers, receipts and statements.
- "Plan" means the Free, Team or Enterprise plan described in section H.
- "Service" has the meaning given above and includes the website at merget.ai, the Documentation and any new feature we add to the merge queue.
- "Spending Cap" means the most Credits an Organization's work may use in a calendar month (UTC), set by an Owner under Settings › Billing.
- "You" and "your" mean the person using the Service and, where that person acts for a company or other entity, that entity too.
B. Accounts and eligibility
Business use
The Service is a tool for software teams. You use it for your or your organization's business or professional purposes, not for personal, family or household purposes.
Who may hold an Account
- You must be at least 18 years old. Merget does not offer the Service to anyone under 18 and will close an Account it learns belongs to someone under 18.
- A human must create the Account. An Agent cannot create an Account or an Organization.
- One person per Account. Do not share your password, your second factor, your recovery codes, your session or any token with anyone. An Organization has as many Accounts as it has Members; the Free plan includes up to 5 Members.
- You must give a working email address. Merget sends sign-in messages, security notices and the notices described in section N to it.
Two-factor sign-in
Two-factor authentication is required for every Merget account. You set it up at your first sign-in with an authenticator app, a phone number or a secondary email address, and keep your recovery codes somewhere safe. Merget asks you to confirm your second factor again every 30 days, and before an Agent may sign in as you. Using the Service with two-factor sign-in turned on is a condition of these Terms.
United States only
The Service is offered only to users located in the United States. You represent that you are not located in, and are not a resident of, the European Economic Area, the United Kingdom or Switzerland, and you agree not to access or use the Service from those regions. We may widen where the Service is offered later; a change that affects you is a material change under section S.
GitHub accounts
The Service works with your GitHub account. You may sign in with GitHub, and Merget records the GitHub account you sign in with or confirm when you install or verify the GitHub App. Merget shows you a private repository only when that GitHub account can read it on GitHub. Your GitHub account remains under GitHub's terms.
Organizations and the authority to bind
When you create an Organization, or connect a GitHub account or install the GitHub App for one, you confirm that you have the authority to bind the company or other entity that Organization stands for, and that entity agrees to these Terms. The dashboard asks you to confirm this when you create an Organization: "I confirm I may bind {name} to the Terms of Service, including Merget's license to train its own models on the organization's content, and have read the Privacy Statement." Owners are responsible for the actions taken in their Organization by its Members and by the Agents its Members authorize. An Organization must always have at least one Owner.
Agents you authorize
The person who authorizes an Agent is responsible for everything it does, as if that person had done it. Section F sets out the rules.
Account security
You are responsible for keeping your Account, your tokens and your validation secrets secure, and for all activity under your Account. Tell us at support@merget.ai as soon as you learn of any unauthorized use of your Account. You can end every session, Agent approval and agent key at once with Sign out everywhere on your account security page, reached from Settings › Account.
How you accept these Terms
You accept these Terms at each of these moments; Merget records the version an Owner accepted when they create an Organization or pay through Stripe Checkout:
- when you create an Account, by ticking the box "I agree to the Terms of Service, Acceptable Use Policy, API and Agent Terms, Billing Terms and Trademark Guidelines, and have read the Privacy Statement and Cookie Policy." before you continue;
- when you create an Organization and confirm you may bind it;
- when you pay through Stripe Checkout ("I agree to the Terms of Service, including Merget's license to train its own models on the organization's content, and the Billing terms.");
- when you keep using the Service after a change takes effect under section S.
Negotiated agreements
If you have a signed agreement with Merget, such as an enterprise agreement or an order form, that agreement governs to the extent it conflicts with these Terms.
C. The Service and the GitHub App
Merget is a merge queue. It analyzes pull requests in your Connected Repositories for merge-time interference, reports findings and a merge brief, orders the queue and, in the modes you choose, prepares fixes and lands ready work. You install the Merget GitHub App on each GitHub organization or personal account that owns repositories you want Merget on, link that installation to your Organization, and turn on each repository you want Merget to work in.
What Merget reads
For connected repositories, Merget uses pull requests, relevant repository contents, checks, reviews and branch rules to analyze changes and manage the queue, and, as section D describes under Model training, to train Merget Models. Analysis reads your repository's files at the commits it analyzes and runs none of your code. Graph questions also read code at the revision you select. The Documentation page Security and data describes this in full, and the GitHub permissions table below explains the requested access.
Automation modes
Each repository is in one of three modes, chosen by someone with Maintain or Admin access to it on GitHub. A newly connected repository starts turned off and in Advisory mode.
- Advisory changes no code and no branches. Merget posts its check and review comments. Its only change to your branch rules is the check rename described under Automated changes. In Advisory mode Merget makes no Model Service requests; what Merget reads in Advisory mode may still be used for Model training under section D.
- Queue lets Merget push prepared fixes, create temporary branches, run your build on its side and land ready work when a person with Write access asks for it.
- Autonomous lets Merget do what Queue does and merge ready work on its own.
Automated changes
The Merget GitHub App asks for these permissions:
| Permission | Access | Why Merget needs it |
|---|---|---|
| Checks | Read and write | Posts the Merget check on each pull request and reads the results of your other checks. |
| Pull requests | Read and write | Reads pull requests and posts inline review comments. In Queue and Autonomous modes, it also resolves the review threads of Merget's own struck-through comments, retargets stacked pull requests and, in Autonomous mode, merges them. |
| Contents | Read and write | Reads the repository code Merget needs to analyze changes and, when you turn on Merget's own build, to build them. Write access is used only in Queue and Autonomous modes: to push prepared fixes to pull request branches, to create and delete temporary branches for batches and for fixes your CI verifies, to land a ready batch on the target branch, and to resolve the review threads of Merget's own struck-through comments, which GitHub allows only with write access. |
| Administration | Read and write | Reads branch protection and rulesets. Allows Turn off strict when an owner confirms, and renames a legacy required check named sema to Merget on its own, in every mode, where the installation accepted it. Once Merget has read your batches' jobs (with Actions access), it also reads the self-hosted runners registered on the repository whenever it checks the repository's readiness, as when you open its settings, and the line under Batches in CI at once says how many are online where your batches' jobs ran on them. |
| Actions | Write, when granted | Lets Cancel CI Merget no longer needs stop obsolete batch workflow runs. Without it, those workflows finish normally, and until they finish, or the CI timeout has passed since the batch's push, they count toward Batches in CI at once. Its read access also lets Merget read each batch's jobs, so the line under Batches in CI at once says how long each job waited to start; without it, Merget reads the batch's check runs instead. |
| Workflows | Write, when granted | Needed to land a pull request whose merge writes GitHub Actions workflow content none of your branches has yet, for example when the target branch also changed that workflow file: GitHub refuses an App's push or merge of such content without it. Merget uses it only to land a pull request's own change, merged with your target branch. Without it, Merget hands such a pull request to you to merge on GitHub; a workflow change only the pull request makes, such as an actions version bump, lands without it. |
| Commit statuses | Read | Reads CI results that are reported as commit statuses. |
| Metadata | Read | Basic repository information that GitHub requires for every App. |
| Members (organization) | Read | Reads the membership of the GitHub organization the App is installed on, and the members of a team that CODEOWNERS names when Merget checks code-owner review itself. |
Authorization of write actions. By enabling Queue or Autonomous mode for a repository, the Owner of the Organization, and the person who enables the mode, authorize Merget to:
- push prepared fixes to pull request branches;
- create and delete temporary branches under
merget/queue/, and delete leftover branches undermerget/queue/and the oldersema/queue/that no live batch or verification owns; - land batches on the target branch, by merge or by push;
- update stacked pull requests after their parent lands, and retarget them;
- resolve the review threads of Merget's own struck-through comments;
- publish the commit to resolve a pull request's conflicts on, at
refs/merget-queue/resolve/<number>; - merge pull requests Merget has certified, on a person's request in Queue mode and on its own in Autonomous mode;
- cancel workflow runs on Merget's temporary branches, where the installation granted Actions: write;
- rename a legacy required check named
sematoMerget, in every mode, where the installation granted Administration: write; and - turn off GitHub's strict up-to-date-branch requirement, only when an Owner with the required GitHub access confirms it.
The dashboard says so when you choose a mode: "In this mode Merget pushes commits to pull request branches, creates and deletes merget/queue/ branches and, in Autonomous mode, merges."
What Merget never writes. Merget itself never writes a file under .github/, a CODEOWNERS, .gitattributes or .gitmodules file, or agent configuration, except to land a pull request's own change merged with the target branch. A prepared fix never changes those files, a conflict in one of them is handed back to you unresolved, and a regenerate command that writes one is refused. A workflow change from a fork is never pushed into your repository or merged by Merget; a person merges it on GitHub.
Forks and bots. A pull request from a fork, or one a bot opened or pushed, gets no build, regenerate or repair run until a person with Maintain access approves that exact commit. Until then Merget analyzes it only. An approved fork commit receives no validation secrets or dependency token.
Landing rules. Merget merges or lands a pull request when GitHub's requirements for it are met as GitHub reports them, with three exceptions you control: a person with Write access requests Merge anyway or Land it now; an Autonomous repository opted into Land it anyway on Merget's verdict; or the landing is a fast-forward push, where GitHub does not evaluate the pull request rules and Merget checks them itself as the Documentation describes. With no review rule on the target branch, Autonomous mode lands a pull request that nobody reviewed. Required checks, reviews and branch rules otherwise remain under your control.
Validation builds, secrets and recipes
With Merget's own build off, which is the default, your CI runs your build and tests. When you turn Merget's own build on, Merget runs your own setup, build and test commands, discovered or from your recipe, in an isolated environment for that repository, with the validation secrets you stored. Validation secrets are supplied only to the setup step, never to build or test commands, regenerate commands, the repair agent, coding agents, fork pull requests or your GitHub CI. Commands can reach the public internet but not private network addresses. Build caches are not shared between repositories; pull requests in the same repository can share them.
You are responsible for the commands, recipes and secrets you give Merget, for the code they run and fetch, and for who in your repository can change them: anyone with Write access who pushes code the setup step runs, and anyone with Maintain access who can change the recipe, can use a secret delivered there. Prefer repository-scoped, read-only credentials.
Your review
Merget checks prepared fixes for unresolved conflicts and blocking findings, and your CI or Merget's own build verifies them. When verification cannot run or does not report, the run can proceed with a visible not verified note. A published fix is limited to the files Merget is allowed to change. Merget's checks bound where a run may write, not what. Review the proposed changes and their verification before merging; a permitted edit is not a guarantee that the code is correct. A clean merge, a passing check or a resolved conflict is not a guarantee that the result is correct, secure or fit for your purpose.
Changes to the Service
We may change the Service, add or remove features, and change the Documentation to match. We tell you about material reductions as section S describes.
D. Customer Content and Outputs
You own your content
You keep every right you have in your Customer Content. Merget claims no ownership of it.
The license you give Merget
You grant Merget a worldwide, non-exclusive, royalty-free license to host, copy, store, analyze, build, run, modify, create derivative works of, transmit to the third-party services in section G, and display your Customer Content to provide, secure and support the Service for you and your Organization; to develop, train, evaluate and improve Merget Models, and through them Merget's own products and services, as Model training below describes; and as the law requires. The license for providing the Service ends when the content is removed from the Service under the retention schedule in the Privacy Statement, except for the records Merget keeps as described there. The license for Model training ends as Model training describes.
Model training
Merget may use your Customer Content, the Outputs, what the Service sends to and receives from a Model Service, your problem reports and support conversations, and the other records of how the Service is used that the Privacy Statement describes under Model training, to develop, train, evaluate and improve Merget Models, and through them Merget's own products and services. This covers every Connected Repository Merget reads, in every automation mode, unless a signed agreement with Merget says otherwise. You grant Merget the same license in what you send it in problem reports and support conversations that you grant in your Customer Content. Merget does so on these terms:
- From November 17, 2026. Merget uses only content and records it collected on or after November 17, 2026, the date these Terms first allowed it.
- Not your secrets. Merget never takes the stored values of your validation secrets or GitHub tokens into training data. Before content enters a training dataset, Merget scans it for credentials, such as keys, tokens and passwords committed to code, and removes those it finds.
- Without identifiers. Before content enters a training dataset, Merget removes the names, email addresses, GitHub logins, account identifiers and IP addresses it finds in it, such as commit authors. Merget keeps a separate record of where each item came from, so that it can remove it later.
- For Merget only. Merget does not sell or license your Customer Content, or training datasets built from it, and does not give them to other customers, except as part of a merger, acquisition or sale of assets. Merget Models are used only in Merget's own products and services, and Merget takes reasonable steps to keep them from reproducing your Customer Content in what they produce for others.
- Removal. When you delete your Organization or Account, remove a repository from the installation (turning it off is not enough), remove a GitHub account or uninstall the GitHub App, or ask Merget to delete your data, Merget stops using the content that came from it for training and removes it from its training datasets within 30 days. Merget Models already trained on it are kept and are not retrained to remove it. The license for Model training then ends for that content; Merget keeps all its rights in Merget Models trained before then.
- The Model Service. Merget does not allow its Model Service to train the Model Service's own models on your Customer Content. When Merget fine-tunes a model on a Model Service, it does so in Merget's own account, and the result is a Merget Model.
Outputs are yours
To the extent Merget has any right in an Output, Merget assigns it to you when the Output is created. You grant Merget the same license in Outputs that you grant in your Customer Content, Model training included. Outputs are produced by software from your Customer Content and may not be unique to you; Merget may produce the same or similar Outputs for others from their own content.
Feedback
If you send us ideas, suggestions or feedback about the Service, we may use them without obligation to you.
Your responsibilities
- You have the rights you need to connect your repositories, to let Merget read, build and change them, and to let Merget use their contents for Model training, as these Terms describe.
- You comply with the open-source and third-party licenses that apply to the code in your repositories. Merget does not check your rights or analyze license compliance.
- You do not put personal data, credentials or other sensitive data in your repositories, pull requests, recipes or secrets that you are not permitted to give Merget, and you handle any personal data there as section J describes.
- You review Outputs before you rely on them, as section K describes.
Removing your content
You can stop Merget's access to a repository by turning it off, removing its GitHub account under Settings › GitHub, or uninstalling the GitHub App on GitHub. Only uninstalling the App on GitHub revokes its access there. What Merget then removes, and when, is in the Privacy Statement under Retention; Model training above says when content leaves Merget's training datasets.
E. Acceptable use
The Acceptable Use Policy is part of these Terms. It restricts what you may do with the Service, with Merget's build environment, with other tenants and with Merget's credentials, and it says how to report a violation.
If you break the Acceptable Use Policy or these Terms, we may act in proportion to the harm: warn you, limit or throttle your use, turn a repository off, suspend an Account, an Agent or an Organization, or terminate your access under section I. In serious cases we may refer the matter to law enforcement. Our decision not to act in one case does not waive our right to act in another. To report a violation, write to support@merget.ai.
F. Agents, API, MCP server, plugin and CLI
The API and Agent Terms are part of these Terms and govern every use of the HTTP API, the MCP server, the Claude Code plugin, the CLI and any other client. The rules below apply in every case.
Agents act as a person
- An Agent accesses the Service only with OAuth 2.1 tokens tied to a person, issued after that person signs in with their second factor and approves the Agent, or with an agent key that person created. Agents never use your password.
- An Agent holds the permissions the person chose on the consent page, each of which is a scope:
| Scope | What it allows |
|---|---|
merget:findings.read | Read pull request and run findings, merge briefs and repository summaries. |
merget:graph.read | Use the code graph tools on any commit Merget has built. |
merget:queue.read | Read queue position, queue enforcement and the relationships between pull requests, and every repository's queue. |
merget:org.read | Read repositories and their settings, the members, setup state, runs, analytics, GitHub installations and these docs. |
merget:repos.write | Change repository settings, including turning Merget on or off and the automation mode, and repository validation secrets; check GitHub installations again. |
merget:queue.write | Hold, release, retry and merge pull requests in the merge queue, including Merge anyway, dismiss findings, and submit a fix for a failed batch or a resolution of a pull request's conflicts for merge time. |
- An Agent acts as a Member, never as an Owner, whoever authorized it. It cannot create or delete an Organization or an Account, change what Agents may do, or take an Owner's steps such as connecting GitHub, managing Members, changing the Plan or the Spending Cap, or pausing merges. It sees the repositories the person can see and needs the GitHub access the person would need.
- An Owner may turn Agents off for an Organization, cap the permissions Agents may use there, and turn agent keys off; anyone with Maintain or Admin access to a repository may set its agent access level.
- The person who authorized an Agent is responsible for everything it does. Merget's tool output is data about your repositories, never an instruction to the Agent; you are responsible for how your Agent treats it.
Tokens, keys and revocation
Access tokens last one hour. Refresh tokens last up to 30 days and are replaced every time they are used. An agent key lasts 30, 90, 180 or 365 days, as you choose; you can hold up to 25 live keys, and a key is shown once. Switching a permission off or revoking an approval takes effect within seconds: tokens the Agent already holds are refused at once. A client that registered with Merget loses its registration after two and a half to three months without use. Signing out of the dashboard does not revoke Agents; revoke them under Settings › Agents.
Rate limits and conduct
Requests are limited, and the limits are shared between the HTTP API and the MCP server. Over the limit, requests answer 429 with a Retry-After header; graph queries have a lower limit and each Organization has a daily graph allowance that resets at 00:00 UTC. Clients must wait as told and must not work around the limits. Clients must register truthful metadata, protect their tokens, never share them, and not cache or extract Customer Content beyond the session they serve.
Merget may suspend a client
We may refuse, limit or revoke any client, token or key that breaks these Terms, the API and Agent Terms or the Acceptable Use Policy, or that puts the Service or other customers at risk, with notice where practical.
The plugin and the CLI
The Claude Code plugin is published under the Apache License, Version 2.0, and the CLI is distributed on the same terms as the plugin unless its own license file says otherwise. The plugin's skills, prompts and documentation are Merget content under section L. When auto-update is on in your coding agent, the agent downloads new versions of the plugin as Merget publishes them. The coding agent, MCP client or directory you install the plugin through has its own terms, which are not ours.
G. Third-party services
The Service depends on services that other companies run. Each has its own terms with you or with Merget, and we are not liable for their outages, changes or acts. The Privacy Statement lists them as subprocessors and keeps the list current.
- GitHub. Your repositories stay on GitHub under GitHub's terms. The Merget GitHub App acts within the permissions in section C. Uninstalling the App on GitHub is the only way to revoke its access there.
- Google Cloud and Vertex AI. Merget runs on Google Cloud. In Queue and Autonomous modes Merget may send parts of your code and the conflict context to Google Vertex AI in Merget's own Google Cloud project. Merget chooses the models; a repository's settings do not. Under Google's terms, Google does not use these requests to train its own models. Today Merget uses Google's Gemini models; Google's retention terms for these requests are its Generative AI data governance terms for Vertex AI. Merget's model-service credentials are not available to repository code.
- Stripe. Stripe processes payments. Checkout and the billing portal are pages Stripe hosts: you enter your card there, and Merget never sees its number or keeps any of its details.
- PostHog. Merget uses PostHog for product analytics, session recordings with masking, error tracking and the support window in the dashboard, and for the website's analytics and session recordings, as the Privacy Statement describes under Analytics and support and under Website.
- Cal.com. Calls booked on merget.ai are scheduled through Cal.com, whose booking window runs under Cal.com's own terms.
- Slack. Problem reports and support conversations also reach the Merget team's Slack workspace.
- Cloudflare. Cloudflare delivers merget.ai and protects the Service at the edge.
H. Fees, credits and payment
Fees
Merget is priced in Credits. Each Plan includes a monthly bundle of Credits, every run Merget makes is listed against it, and the receipt for a pull request shows which runs you paid for and why.
| Free | Team | Enterprise | |
|---|---|---|---|
| Price | $0 | $50 a month | Coming soon |
| Repositories | 3 | Unlimited | Unlimited |
| Members | Up to 5 | Unlimited | Unlimited |
| Credits a month | 5,000 | 10,000 | Pooled |
| Past the bundle | Work pauses at the allowance, or $0.0075 per extra credit once an owner pays for extra credits | $0.005 per credit, up to the spending cap | Invoiced |
| Spending cap | None; with extra credits on, 10,000 credits by default, yours to change | 20,000 credits by default, yours to change | Custom |
| Analytics history | 30 days | Full | Full |
There is no charge per seat: every Member of the Organization is included in the Plan, up to the Free plan's five Members. The allowance renews on the first of the month (UTC). Unused Credits do not carry over to the next month. An upgrade takes effect at once, and the month's allowance becomes Team's 10,000 Credits in full, whatever day of the month you upgrade. Enterprise is arranged with Merget and invoiced as agreed. The Billing, Refund and Cancellation Terms say the same in plain language and are part of these Terms.
Credits
Every charged run rounds up to a whole Credit. An analysis or a preparation is priced by the time and the resources it took. A fix attempt is priced by the work it took, and is charged whether or not it produced a fix. A landing is one Credit. Shared work is split over the pull requests it was for. Every run Merget made for a pull request counts, not only the first: a pull request in the queue is prepared again when you push, when Merget pushes a fix, when the target branch moves, when the queue reorders and when a pull request ahead of it changes.
A run Merget failed or abandoned costs nothing, and a revalidation before landing is free. A charge is recorded once its run has ended and is final from then on; it is never changed afterwards. A month's statement closes shortly after the month ends.
Spending cap
The Spending Cap is the most Credits the Organization's work may use in a calendar month (UTC), the bundle included. On Team the default is 20,000 Credits; on Free with extra credits on, 10,000 Credits. An Owner may change it or, on Team, remove it. At the cap, Merget starts no new preparations or analyses; runs already in progress finish, a pull request Merget has already certified still lands, and the queue keeps planning. Those runs are charged as usual. Work resumes when an Owner raises the cap or changes the Plan, or when the allowance renews.
Payment
Merget takes payments through Stripe. Team is $50 a month, charged on the first of each month (UTC). The first payment, when you upgrade, covers only the days left until the first of the next month; Team's 10,000 Credits for the month you upgrade in are not reduced to match. Credits past the bundle, on Team at $0.005 each or on Free with extra credits on at $0.0075 each, are billed after the month they were used in. On the first of each month (UTC), one invoice carries Team's $50 for the month ahead and the Credits past the bundle of the month that just ended, and Stripe charges it to the card. An invoice under Stripe's minimum charge of $0.50 is not charged that month; Stripe adds its amount to the next invoice. Pay for extra credits charges nothing at Checkout.
Checkout asks for the card and the billing address, and lets you add a tax ID. The billing portal, which Manage billing opens, lets an Owner change the card, the billing email, the billing address, and the name or the tax ID on the invoices, see every invoice and receipt, and cancel Team or the extra credits. What Merget sends Stripe about the Organization is its name, its identifiers and, through the month, its running count of Credits past the bundle: never anything about your code or your pull requests.
Taxes
Prices exclude taxes. Merget does not collect sales tax or other transaction taxes today. Where Merget becomes obliged to collect them, it adds them to the invoice and tells you under section S. You are responsible for any tax that the law puts on you.
Failed payments
If a payment fails, Stripe tries it again over the following days and writes to the billing email. A failed payment does not pause Merget's work while Stripe retries. If every retry fails, Stripe cancels the subscription: Team ends at once and the Organization moves to the Free plan; extra credits on Free turn off at once. The month's Credits past the bundle up to the cancellation are not billed, unless an Owner goes through Checkout again the same month, which prices the whole month again under the Plan it starts.
Refunds and disputes
Subscription fees are not refunded for partial months, except where the law requires it or Merget chooses to for a service failure. Failed and abandoned runs are never charged. To dispute a charge, write to support@merget.ai within 30 days of the invoice. The Billing, Refund and Cancellation Terms set this out under Refunds.
Price changes
We may change prices and the Plans. A price increase or a reduction of what a Plan includes takes effect no sooner than 30 days after we notify you under section S, and never within a month you have already paid for.
Billing preview
While billing is in preview for your Organization, the dashboard shows Preview: not charged. Merget meters Credits, so the figures are real, but nothing is charged, no statement is due and no cap pauses work. When billing goes live for your Organization, the figures carry on from the same ledger, and Team's charges begin only when an Owner upgrades through Checkout.
I. Term, cancellation, suspension and termination
Term
These Terms apply from the moment you accept them until your Account is deleted or your access is terminated.
Cancelling or downgrading
An Owner cancels Team, or extra credits on Free, under Manage billing in Settings › Billing, which opens the Stripe billing portal. Team continues until the end of the month, then the Organization moves to Free; the month's Credits past the bundle are billed after it ends, and Team's $50 is not charged again. Until then an Owner can renew it. The Billing, Refund and Cancellation Terms describe the effect in detail.
Deleting an Organization or your Account
An Owner can delete an Organization, and any Member can delete their own Account, under Settings › Danger zone. You delete the Organizations you own, your personal Organization included, before you delete your Account. Both actions are permanent. Deleting an Organization removes its settings, repositories, pull requests, runs, findings, queue records and access records from Merget's database at once, and the copies of repository code Merget kept for analysis are erased by a job that runs within minutes. Your GitHub account and GitHub repositories are not deleted, and the GitHub App stays installed on GitHub until you uninstall it there. The credit ledger is kept as a financial record. Content from the Organization is removed from Merget's training datasets within 30 days, and Merget Models already trained on it are kept, as section D describes under Model training. The Privacy Statement's Retention section has the full schedule.
Suspension by Merget
We may suspend all or part of your access, an Agent, a repository or an Organization when:
- a payment is overdue after Stripe's retries, as section H describes;
- you break the Acceptable Use Policy or these Terms;
- your use creates a security risk to the Service, to Merget or to other customers;
- the law, a court or a government authority requires it; or
- we must do so to protect the Service.
We give notice before or promptly after a suspension where that is practical and lawful, and we lift it when the cause is resolved.
Termination by Merget
We may terminate these Terms and your access if you materially breach them and do not cure the breach within 30 days of notice, or at once for a breach that cannot be cured, for repeated violations of the Acceptable Use Policy, or where the law requires. We may also discontinue the Service as a whole with at least 30 days' notice; in that case we refund any prepaid fees for the period after the Service ends.
Effect and survival
When these Terms end, your right to use the Service ends, Merget stops work in your repositories, and Merget removes your data on the schedule in the Privacy Statement. Fees already charged remain due. Sections D (Model training, the licenses it relies on, and ownership), H (fees due), K, L, O, P, R, T, U and V survive, with any other term that by its nature should.
J. Privacy and data protection
The Privacy Statement is part of these Terms. It describes what Merget collects, how it uses and shares it, how long it keeps it and the rights you have.
- Roles. Merget decides how website, Account, billing, analytics and support data are used. For the contents of your Connected Repositories and the Outputs about them, Merget acts for your Organization and follows these Terms, the settings your Organization chooses and the Organization's lawful instructions, except that Merget decides itself how it uses them for Model training under section D, within the terms set out there.
- Retention and deletion. Merget keeps and removes data on the schedule published in the Privacy Statement under Retention, which mirrors the Documentation page Security and data. Deleting an Organization, removing a repository or uninstalling the GitHub App starts the removals described there, from Merget's training datasets too.
- Subprocessors. The companies that process data for Merget are listed in the Privacy Statement under Subprocessors. To be told before Merget adds or replaces one, email support@merget.ai with the subject "Subprocessor changes".
- Personal data in your repositories. You are responsible for any personal data in your Customer Content: for having the right to let Merget process it, for giving any notice the law requires, and for not putting data there that the law forbids you to share with a service like Merget.
- Security incidents. If we learn of unauthorized access to your Customer Content or to your Account data, we notify the affected Organization's Owners without undue delay by email to their Account addresses, with what we know and what we are doing.
- Your rights. The Privacy Statement explains the rights you have under U.S. state privacy laws and how to exercise them.
K. AI features
Merget is a tool
Merget analyzes, prepares and lands changes you and your team make. It does not design, build, validate or approve your software. Merget is not a co-developer, partner, joint venturer or participant in your product, and you may not say or imply that Merget built, certified, secured or made compliant any software or any Output.
Outputs can be wrong
Findings, merge briefs, prepared fixes and conflict resolutions are produced by software, parts of it by a Model Service or a Merget Model, from your code and the context Merget gives it. They can be wrong, incomplete, insecure or unfit for your purpose, and a clean verdict can miss a problem. Human review before merging is your control: you choose the automation mode, keep your branch rules, required checks and reviews, and review what Merget prepares and its verification before you merge. Section C's Your review applies.
Code execution
In Queue and Autonomous modes, Merget runs your build, tests, regenerate commands and its repair agent in an isolated environment for your repository on Merget's side, as section C describes. Repository code receives none of Merget's own credentials, and Merget's model-service credentials are never available to it. Analysis runs none of your code, in every mode.
Model Services
Merget chooses the Model Service and the models for every repository. Your use of Outputs from a Model Service is subject to that vendor's acceptable-use terms as they apply to Merget; for Google Vertex AI these are Google's Generative AI Prohibited Use Policy. The Model Service does not train its own models on what Merget sends it; Merget's own use of it to train Merget Models is in section D, under Model training.
Regulated and high-risk uses
You are solely responsible for the design, testing, security and deployment of your software, and for complying with the laws, regulations and standards that apply to it. If you use the Service for software in a regulated or high-risk field, such as financial services, employment decisions, healthcare, medical devices, weapons, critical infrastructure or the processing of regulated or sensitive data, you alone are responsible for the laws that apply, and a person reviews every change before it is merged. Merget gives no legal, regulatory or compliance advice; the Documentation and Outputs are not advice.
L. Intellectual property
Merget's rights
Merget and its licensors own the Service, the Documentation, Merget Models, the plugin's skills and prompts, the website and everything in them, including the software, the analysis methods, the user interface, the text and the designs. These Terms give you a limited, non-exclusive, non-transferable right to use the Service for your business under these Terms, and nothing else. You may not copy, modify, reverse engineer, decompile or create derivative works of the Service, except where the law allows it in spite of this term or an open-source license covers the component.
Trademarks
"Merget" and the Merget logo are trademarks of Merget, Inc. The Trademark Guidelines say how you may refer to Merget. GitHub, Google, Stripe, Claude and the other names in these Terms are their owners' trademarks and are used only to identify those services.
Open-source components
The Service, the plugin and the CLI include open-source components under their own licenses, which govern those components. The notices are at merget.ai/legal/third-party-notices and in the plugin repository. The plugin itself is licensed under the Apache License, Version 2.0, as section F says.
Copyright complaints
Section Q is Merget's copyright policy.
M. Preview and beta features
A feature marked Preview, Coming soon, beta or the like, such as billing preview or the Enterprise plan before it is offered, is provided so you can try it. It may change, be limited or end at any time without notice, may not work as described, and may not be supported. Sections O and P apply to it in full. When a preview feature ends, your data is handled under the Privacy Statement's retention schedule like everything else; nothing is deleted because the preview ended.
N. Communications
- Notices from Merget. We notify you by email to the address on your Account, by a notice in the dashboard, or both. Notices about an Organization go to its Owners. A notice counts as received when we send it to the Account address or show it in the dashboard. Keep your address current.
- Electronic communication. You consent to receive communications from us electronically, and you agree that electronic terms, notices and disclosures satisfy any legal requirement that they be in writing.
- Transactional messages. Sign-in links and codes, verification and password messages, security notices, receipts, invoices and payment-failure messages are part of the Service, and you cannot opt out of them while you hold an Account. You can opt out of marketing email with the link in each message.
- Legal notice to Merget. Legal notice to Merget must be in writing to Merget, Inc., 418 Broadway, Unit 7259, Albany, NY 12207, Attn: Legal, with a copy to support@merget.ai. Email or a support conversation alone is not legal notice.
- Support. Merget offers support by email at support@merget.ai and through the dashboard, not by telephone.
O. Disclaimer of warranties
Merget provides the Service "as is" and "as available", without warranty of any kind. To the fullest extent the law allows, we disclaim all warranties, whether express, implied or statutory, including any warranty of merchantability, fitness for a particular purpose, title, security, accuracy and non-infringement.
Merget does not warrant that the Service will meet your requirements; that it will be uninterrupted, timely, secure or error-free; that any Output, verdict, merge brief, prepared fix, conflict resolution or other information provided through the Service is accurate, complete, reliable, secure, non-infringing or correct; that defects will be corrected; or that the Service is free of harmful components. Outputs may be wrong, insecure, non-functional or infringing, and you are solely responsible for reviewing, testing and validating them before you merge or use them. You assume full responsibility and risk of loss resulting from your use of the Service and of anything obtained through it. Section M adds to this for preview features.
P. Limitation of liability
To the fullest extent the law allows, Merget will not be liable to you or any third party for any loss of profits, revenue, use, goodwill or data, or for any incidental, indirect, special, consequential or exemplary damages, however arising, that result from:
- your use of, or inability to use, the Service;
- any Output, or your reliance on an Output;
- any change Merget made in your repositories under the authorization in section C, including a landing, a prepared fix, a resolved conflict or a renamed check;
- any modification, price change, suspension or discontinuance of the Service;
- the acts, omissions, terms or data practices of GitHub, a Model Service, a coding agent, a payment provider or any other third party;
- unauthorized access to or alteration of your transmissions or data; or
- any other matter relating to the Service.
Our liability is limited whether or not we have been advised of the possibility of such damages, and even if a remedy is found to have failed of its essential purpose. We have no liability for any failure or delay due to matters beyond our reasonable control.
Aggregate cap. To the extent any liability is not excluded above, Merget's total liability to you arising out of or relating to these Terms or the Service will not exceed the total fees you paid Merget for the Service in the twelve (12) months before the event giving rise to the claim. If you paid no fees in that period, for example on the Free plan or while billing is in preview, Merget's total liability will not exceed one hundred U.S. dollars (US$100).
Your obligations are not limited. This section does not limit your payment obligations under section H, your indemnification obligations under section R, or your liability for a breach of the Acceptable Use Policy, of section F, or of Merget's intellectual property rights under section L.
Liabilities that cannot be limited. Nothing in these Terms excludes or limits either party's liability to the extent it cannot be excluded or limited under applicable law, including liability for fraud, gross negligence, willful misconduct, or death or personal injury caused by negligence.
Q. Copyright (DMCA) policy
Merget complies with the Digital Millennium Copyright Act (DMCA), and this section is Merget's DMCA policy. The Service does not host public repositories or public content of its own; the material it stores is the Customer Content of the Organization that connected it, and Merget's response to a notice is to remove or disable Merget's own copies, those in its training datasets included, and to notify that Organization.
Reporting infringement. If you believe material on the Service infringes your copyright, send a written notice to Merget's designated copyright agent that includes: (1) your physical or electronic signature; (2) identification of the copyrighted work you claim has been infringed; (3) identification of the material you claim is infringing and information reasonably sufficient to let us locate it, such as the repository, pull request or URL; (4) your address, telephone number and email address; (5) a statement that you have a good-faith belief that the use is not authorized by the copyright owner, its agent or the law; and (6) a statement, under penalty of perjury, that the information in your notice is accurate and that you are the copyright owner or are authorized to act on the owner's behalf. Send notices to:
Designated Copyright Agent
Copyright Agent, Legal Department
Merget, Inc.
418 Broadway, Unit 7259, Albany, NY 12207
Email: dmca@merget.ai
Before sending a notice, consider whether the use is a fair use or is otherwise lawful or licensed. There may be legal consequences for sending a false or frivolous notice.
Counter-notice. If your material was removed or disabled and you believe this was a mistake or misidentification, you may send our designated agent a counter-notice that includes: (1) your physical or electronic signature; (2) identification of the removed material and the location where it appeared before removal; (3) a statement, under penalty of perjury, that you have a good-faith belief the material was removed or disabled by mistake or misidentification; and (4) your name, address and telephone number, and a statement that you consent to the jurisdiction of the federal district court for the judicial district in which your address is located (or, if your address is outside the United States, any judicial district in which Merget may be found) and that you will accept service of process from the person who submitted the original notice. We forward the counter-notice to the person who sent the original notice and may restore the material in 10 to 14 business days as the DMCA permits, unless that person tells us they have filed a court action.
Repeat infringers. We disable or terminate, in appropriate circumstances, the Accounts and Organizations of repeat infringers.
R. Indemnification
You will defend, indemnify and hold harmless Merget, its affiliates and their officers, directors, employees and agents from and against any claim, liability, damage, loss and expense, including reasonable attorneys' fees, arising out of or related to:
- your Customer Content, your repositories, your software or your use of Outputs, including any alleged infringement, misappropriation or breach of an open-source or third-party license;
- your use of the Service in violation of the law, these Terms or a third party's rights or terms, including a coding agent provider's terms;
- anything an Agent you authorized did;
- the commands, recipes and secrets you gave Merget, and what they ran or fetched;
- your use of the Service in a regulated or high-risk context under section K; or
- the combination of the Service or an Output with software, data, models or services not provided by Merget.
Merget will (1) notify you promptly in writing of the claim; (2) give you control of the defense and settlement, except that you may not settle in a way that imposes obligations on Merget or fails to release Merget unconditionally without Merget's written consent; and (3) give you reasonable assistance at your expense.
S. Changes to these Terms
We may change these Terms. For a material change, such as a price increase, a reduction of what a Plan includes, a new use of Customer Content, a change to where the Service is offered, or a change to sections P or T, we give at least 30 days' notice before it takes effect, by email to the address on your Account. Every change is published at merget.ai/legal/terms-of-service with a new effective date and version. Your continued use of the Service after the effective date is your acceptance of the changed Terms. If you do not agree to a change, stop using the Service and delete your Account before the change takes effect; a prepaid period runs under the Terms in force when you paid. Changes that are not material, such as corrections and clarifications, take effect when published.
T. Dispute resolution; binding arbitration; class-action waiver
Please read this section carefully. It requires you and Merget to resolve disputes through binding individual arbitration instead of in court, and it waives your right to a jury trial and to take part in class or representative actions. You may opt out within 30 days as described below.
Informal resolution first
Before starting an arbitration, you and Merget agree to try to resolve any dispute informally for at least sixty (60) days. To begin, send a written description of the dispute and your contact information to support@merget.ai, or, for Merget to you, to the email address on your Account. This requirement does not toll any applicable statute of limitations.
Agreement to arbitrate
You and Merget agree that any dispute, claim or controversy arising out of or relating to these Terms or the Service (a "Dispute") that is not resolved informally will be resolved by binding individual arbitration, rather than in court, except as provided under Exceptions below. This agreement to arbitrate is governed by the Federal Arbitration Act and evidences a transaction involving interstate commerce.
Rules and procedure
The arbitration will be administered by the American Arbitration Association (AAA) under its Commercial Arbitration Rules, as in effect when the arbitration starts and as modified by these Terms. A single arbitrator will conduct the arbitration. The seat of arbitration is Wilmington, Delaware. The arbitrator may permit telephone or video proceedings, and any in-person hearing for an individual will take place in the U.S. county where that individual resides or another mutually agreed location. The arbitrator's award may be entered as a judgment in any court of competent jurisdiction. Each party pays its own attorneys' fees unless the applicable rules or the law provide otherwise.
Class-action and jury-trial waiver
You and Merget agree that each may bring claims against the other only in an individual capacity, and not as a plaintiff or class member in any purported class, collective, consolidated or representative proceeding. The arbitrator may not consolidate more than one person's claims or preside over any form of class or representative proceeding. You and Merget each waive any right to a jury trial. If a court decides that this waiver is unenforceable as to a particular claim or request for relief, then that claim or request, and only that one, will be severed and may proceed in court, while all remaining claims proceed in arbitration.
Exceptions
Either party may (a) bring an individual claim in small-claims court if it qualifies, and (b) seek injunctive or other equitable relief in a court of competent jurisdiction to prevent the actual or threatened infringement, misappropriation or violation of its intellectual property, confidential information, or the security or integrity of the Service.
Your right to opt out
You may opt out of this section T within thirty (30) days of first accepting these Terms by sending written notice to support@merget.ai with your name and the email address on your Account. If you opt out, the arbitration and class-action-waiver provisions will not apply to you, and Disputes will instead be resolved in the courts named in section U. Opting out has no effect on any other provision of these Terms.
Severability and survival
Except as stated under Class-action and jury-trial waiver, if any part of this section T is found unenforceable, the remainder will remain in effect. This section T survives termination of these Terms.
U. Governing law, export compliance and U.S. government users
Governing law and venue
These Terms and any access to or use of the Service are governed by the laws of the State of Delaware and applicable U.S. federal law, without regard to conflict-of-law provisions. Subject to section T, you and Merget submit to the exclusive jurisdiction and venue of the state and federal courts located in the State of Delaware for any Dispute not subject to arbitration, for the exceptions in section T, and to enforce or confirm any arbitration award. Merget may seek injunctive or other equitable relief to protect its intellectual property, confidential information, or the security or integrity of the Service in any court of competent jurisdiction.
Export compliance
You may not use the Service in violation of the export-control or sanctions laws of the United States or any other applicable jurisdiction. You may not use the Service if you are, or are acting on behalf of, a Specially Designated National or a person subject to similar denied-party prohibitions, and you may not use it to develop software for a use those laws prohibit.
U.S. government end users
The Service, the plugin, the CLI and the Documentation are "commercial computer software" and "commercial computer software documentation" as those terms are used in FAR 12.212 and DFARS 227.7202. If you are acquiring them on behalf of the U.S. Government, they are licensed only with the same commercial rights granted to all other users under these Terms, consistent with FAR 12.212 and DFARS 227.7202-1 through 227.7202-4.
V. Miscellaneous
Assignment
Merget may assign or delegate these Terms and the Privacy Statement, in whole or in part, to an affiliate or to a successor in a merger, acquisition or sale of assets, with notice to you under section N. You may not assign or delegate any rights or obligations under these Terms without our prior written consent, except to a successor of your whole business that accepts them in writing; any other assignment is void.
Section headings and summaries
Section titles and the summary table are for convenience only and are not part of the agreement.
Severability, no waiver and survival
If any part of these Terms is held invalid or unenforceable, that part will be construed to reflect the parties' original intent, and the remaining parts will remain in full force. Our failure to enforce any provision is not a waiver. The sections named in section I survive termination.
Entire agreement
These Terms, together with the Privacy Statement, the Acceptable Use Policy, the API and Agent Terms, the Billing, Refund and Cancellation Terms, the Trademark Guidelines, the Documentation and any other policy they incorporate, are the complete and exclusive agreement between you and Merget about the Service, and supersede any prior agreements or communications about it. They may be changed only as section S describes or by a written amendment signed by an authorized representative of Merget. A signed agreement between you and Merget governs to the extent it conflicts with these Terms.
Prior versions
This version replaces the version effective November 15, 2026.
Contact
Merget, Inc.
418 Broadway, Unit 7259, Albany, NY 12207
support@merget.ai