In short: Merget runs your builds, pushes to your repositories and lets agents act for you. That only works when everyone uses it in good faith. Use the Service lawfully, keep your code and your agents out of Merget's infrastructure, other customers' work and other people's rights, do not work around limits or share accounts, and report security problems privately. We enforce this Policy in proportion to the harm.
This Acceptable Use Policy (the "Policy") is part of, and is incorporated into, the Merget Terms of Service (the "Terms"). Capitalized words used but not defined here have the meanings given in the Terms. "We", "us" and "our" refer to Merget, Inc. ("Merget"); "you" and "your" refer to the person or entity using the Service, including through an Agent. If you have a signed agreement with Merget, that agreement governs to the extent it conflicts with this Policy.
1. Comply with the law
You use the Service in compliance with all applicable laws and regulations and with the Terms, this Policy, the API and Agent Terms and the Privacy Statement. The Service is offered only to users located in the United States (see the Terms, section B, United States only). You do not use the Service in violation of export-control or sanctions laws (see the Terms, section U).
2. Safety
We do not allow content or activity on the Service that:
- is unlawful or promotes unlawful activity;
- is sexually obscene or relates to sexual exploitation or abuse, including of minors (we prohibit child sexual abuse material absolutely and report it as the law requires);
- is libelous, defamatory or fraudulent;
- harasses, abuses or threatens any individual or group, including our employees and other users; or
- incites or glorifies violence.
Merget is a developer tool and its surfaces are not public. These rules apply to what you put in pull requests, repository names, organization names, profile fields, support conversations and anything else that reaches Merget or another person through the Service.
3. Intellectual property, authenticity and the privacy of others
We do not allow content or activity on the Service that:
- infringes any proprietary right of any party, including patent, trademark, trade secret, copyright, right of publicity or other right (for copyright complaints, see the Terms, section Q);
- shares unauthorized product-licensing keys, software for generating them, or software for bypassing license checks;
- impersonates any person or entity, including Merget and its staff, or misrepresents who you are or who you act for; or
- violates the privacy of any third party, such as by putting another person's personal information in a repository, a pull request or a support conversation without a lawful basis.
You represent that you have the rights you need to the code, prompts, recipes, secrets and other materials you connect to or give the Service, for the uses the Terms describe, Model training included, and you are responsible for complying with every open-source and third-party license that applies to them (see the Terms, sections D and K).
4. Spam and inauthentic activity
We do not allow activity on the Service that is or involves:
- creating accounts or organizations by automated means, or fake accounts;
- bulk or automated activity meant to burden Merget's systems or to inflate usage, such as opening pull requests or triggering runs for no development purpose;
- phishing or attempted phishing, including through pull request content, agent prompts or support messages;
- relaying unsolicited advertising or solicitation through Merget's systems; or
- using the Service to propagate abuse on GitHub or another platform.
5. Security of the Service, of other customers and of others
We do not allow content or activity on the Service that:
- develops, hosts or delivers malware, ransomware, spyware, credential-stealing tools or attack infrastructure, or that otherwise supports an active attack causing technical harm, where there is no dual-use purpose before the abuse;
- uses the Service to disrupt, or to gain or attempt to gain unauthorized access to, any service, device, data, account or network;
- includes code, build commands, test commands, regenerate commands, recipes, validation secrets, dependencies or repository content designed to attack, escape, probe or tamper with Merget's build environment, the repair agent's environment, Merget's own systems, other customers' builds, repositories or data, private networks, or Merget's credentials and model-service credentials;
- runs cryptocurrency mining, proxies, network scanners, denial-of-service tools or any workload unrelated to building, testing and verifying the repository inside Merget's build or regenerate steps;
- introduces secrets, tokens or credentials into a repository, a recipe or a pull request to make Merget use them, except validation secrets stored through the Service as the Documentation describes; or
- crafts pull request content, repository content, tool output or agent prompts to make an Agent, the repair agent or another person take an action they did not intend.
Security research. Legitimate security research and dual-use security tools are permitted. Testing of Merget's own systems is permitted only under the Vulnerability Disclosure Policy, on the systems it names and within its rules. Testing of anyone else's systems through the Service is permitted only where you are authorized and it affects only the systems that authorization covers.
6. Accounts, tokens, permissions and limits
You must not:
- share an Account, a password, a second factor, recovery codes, a session, an OAuth token or an agent key with anyone, or let more than one person use an Account;
- use a token or an agent key outside the permissions and the organization its person chose for it, or work around an Owner's agent controls, a repository's agent access level or a repository's GitHub permissions;
- have an Agent take, or try to take, a step the Service reserves for a person signed in to the dashboard, or act as an Owner;
- circumvent the Free plan's limits, the spending cap, the credit allowance, the rate limits, the daily graph allowance or any other limit the Documentation describes, including by splitting work across accounts or organizations;
- use the Free plan for more than one organization doing real work, or create extra accounts or organizations to multiply the Free allowance, to evade its repository or member limits, or to avoid paying for extra credits;
- turn on Queue or Autonomous mode, or confirm Turn off strict, for a repository you are not authorized to make those decisions for; or
- approve a fork or bot commit you have not reviewed.
7. Automated access and scraping
The HTTP API and the MCP server, used with OAuth tokens or agent keys as the Documentation describes, are the ways to reach the Service with software. You must not:
- scrape, crawl or bulk-extract the dashboard, the sign-in pages, the in-app documentation or the API beyond the documented routes and their limits;
- retry a refused request in a loop, or work around a
429response or a refusal that names a permission; - cache, store or extract Customer Content or Outputs beyond the session that serves them, or, without the Organization's agreement, build a dataset or a model from its Customer Content, Outputs or tool output, or from the Documentation; or
- register a client with false metadata, or present one client as another.
8. Resale and competing products
You will not reproduce, duplicate, copy, sell, resell or exploit any portion of the Service or access to it, or use the Service, its Outputs or its Documentation to build a competing or substitute product, without our written permission. You may build tools, scripts and agents on the API and MCP server for your own organization's use under the API and Agent Terms.
9. Excessive use of resources
The Service's usage limits vary with the plan and the features you use. If your usage, including builds, runs, graph queries, API calls, storage or bandwidth, is significantly excessive relative to other customers using similar features, we may throttle your activity, pause a repository or an organization, or otherwise limit your use until it is reduced. We may, after notice where practicable, turn off repositories that place undue strain on our infrastructure. The Terms, section H, describes the credit allowance and the spending cap; the Documentation describes the rate limits.
10. High-risk uses
Do not use the Service to prepare, verify or merge code for weapons, for critical infrastructure control, for medical or safety-critical systems, or for other uses where an error could cause death, personal injury or severe damage, unless a qualified person reviews every change before it is merged and you comply with the laws that apply to that field. Autonomous mode is not suitable for such code. The Terms, section K, describes your responsibilities in regulated and high-risk contexts.
11. Advertising
The Service is not a place to advertise. Repository, organization and profile fields, pull request content and support conversations must not be used for promotional marketing. You may describe your own project accurately in its own repository.
12. Protection of other users
You must not engage in activity that significantly harms other customers or users of the Service. We interpret this Policy and resolve disputes in favor of protecting our customers as a whole.
13. Enforcement
We may act on a violation of this Policy or the Terms in proportion to the harm: warn you, throttle or limit your use, turn a repository off, revoke an Agent, suspend an Account, an Organization or a token, or terminate your access (see the Terms, sections E and I). Where the violation threatens the Service or other customers, we may act first and notify you afterwards. In serious cases we may refer the matter to law enforcement or other authorities. Our decision not to act in one case does not waive our right to act in another.
Reinstatement and appeal. If your Account, Organization or Agent has been limited or suspended and you believe we got it wrong, write to support@merget.ai with the Account and the Organization concerned. We review timely requests and reply.
14. Reporting
To report content or activity that you believe violates this Policy, write to support@merget.ai. For copyright infringement, use the process in the Terms, section Q. To report a security vulnerability in Merget, follow the Vulnerability Disclosure Policy and write to security@merget.ai.
15. Changes
We may change this Policy. For a material change we give at least 30 days' notice by email to the address on your Account; your continued use of the Service after the effective date is your acceptance. Changes that are not material take effect when published. This version replaces the version effective November 15, 2026, the first published version of this Policy.
Contact
Merget, Inc.
418 Broadway, Unit 7259, Albany, NY 12207
support@merget.ai