Terms of Service
Effective date: August 7, 2026
1. Agreement to these terms
These Terms of Service (the “Terms”) govern your use of magenticmarket.ai, its companion browser plugin, and the related software-building services (together, the “Service”). The Service is operated by CBI BUSINESS TRANSACTIONS, LLC (“CBI,” “we,” “us,” or “our”).
By creating an account, installing or pairing the plugin, submitting a build request, or otherwise using the Service, you agree to these Terms. If you do not agree, do not use the Service.
If you use the Service for an organization, you represent that you have authority to accept these Terms for that organization. In that case, “you” and “your” refer to that organization and the people using the Service under its authority.
2. The service we provide
Magentic Market is a tool for building software by chatting with an AI agent. You can use it to describe or request software components, including Models, Views, Controllers, and other code. The Service sends the build request to a third-party AI provider, Manus at api.manus.ai, and returns generated code or related output.
The Service is designed to be local-first. The companion browser plugin keeps relevant project or application data in browser-managed storage, including OPFS and/or local storage, on your own device. CBI’s position is that you own your data; the local-first design is intended to reduce the need for CBI to centrally hold your project data.
The Service includes account, authentication, plugin-pairing, build, and support functions. We may change, add, remove, suspend, or discontinue a feature as described in these Terms and as permitted by applicable law.
3. Eligibility and responsible use
You may use the Service only if you are legally able to enter into a binding agreement and are permitted to use it under applicable law. If you are under 18, do not create an account or use the Service.
You are responsible for making sure that your use of the Service, your prompts, your code, and your deployment of generated output comply with applicable law, these Terms, and the rights of others.
The Service is not a substitute for professional legal, security, compliance, financial, medical, or other regulated advice. You are responsible for obtaining any review, testing, approvals, licenses, or professional guidance that your software project requires.
4. Two account types
The Service supports two distinct account types: Human Accounts and LLM Accounts. The account rules below are important because an LLM Account may be created only through a responsible human sponsor.
4.1 Human Accounts
A Human Account may sign in through email and password, GitHub, Google, or a phone one-time code, where those options are enabled. You must provide accurate account information and keep it current.
You are responsible for activity that occurs through your Human Account, unless you have promptly reported a suspected compromise and applicable law provides otherwise. Use a strong, unique password, keep your account credentials private, and promptly contact us at cbi_business_transactions_llc@magenticmarket.ai if you believe your account has been accessed without authorization.
You must not share your account in a way that defeats security controls or allows another person to impersonate you.
4.2 LLM Accounts
An LLM Account is an account for an AI agent or LLM-based actor, not a natural person. It uses a handle and secret credential to authenticate.
Only a Human Account holder may create an LLM Account. The Human Account holder who creates it is its “sponsor.” By sponsoring an LLM Account, you represent that you have authority to create and operate it and that you will be responsible for its configuration, credentials, use, prompts, requests, generated output, and compliance with these Terms.
You must not use an LLM Account to evade a suspension, create anonymous abusive activity, impersonate a person or organization, or avoid responsibility for conduct that would violate these Terms if done through your Human Account.
CBI may require you to identify, disable, rotate credentials for, or delete an LLM Account that presents a security, legal, operational, or abuse concern. If the sponsoring Human Account is suspended or terminated, we may suspend or terminate its associated LLM Accounts.
5. Your account security and the plugin
You are responsible for safeguarding the credentials and devices you use with the Service. This includes your password, GitHub or Google account access, phone number used for sign-in, LLM Account secret, plugin pairing code, browser profile, and any API bearer token.
The website uses a signed session cookie. The plugin uses short-lived pairing codes and API bearer tokens. CBI stores a SHA-256 digest of each bearer token, not the raw token. Those measures help reduce risk, but they do not eliminate it.
Do not expose credentials in public repositories, shared screenshots, paste sites, build specifications, chat prompts, logs, or code that you distribute. If a token or secret may have been exposed, revoke or replace it promptly.
6. What you may do with the Service
Subject to these Terms, CBI gives you a limited, non-exclusive, non-transferable, revocable right to access and use the Service for lawful software-building purposes.
You may submit specifications, request generated code, use the browser plugin with your account, store local project data on your own device, and use generated output as described in these Terms.
This permission does not give you ownership of the Service itself, the website, the plugin, CBI’s branding, or CBI’s underlying software and intellectual property.
7. Rules for acceptable use
You may not use, or help another person use, the Service in a way that is unlawful, harmful, deceptive, abusive, or contrary to these Terms. In particular, you may not:
| Prohibited activity | Examples |
|---|---|
| Break the law or violate rights | Using the Service to facilitate unlawful conduct; infringing copyright, privacy, publicity, contractual, or other rights; or violating export, sanctions, or data-protection laws. |
| Harm, exploit, or harass people | Creating malware, stalking tools, doxxing tools, deceptive impersonation, fraud, non-consensual surveillance, or content intended to threaten or harass. |
| Attack systems or data | Attempting unauthorized access, credential theft, data exfiltration, denial-of-service activity, security bypasses, destructive code, or interference with systems you do not own or have permission to test. |
| Abuse accounts or access controls | Sharing, selling, stealing, guessing, harvesting, or misusing credentials, session cookies, pairing codes, bearer tokens, or LLM Account secrets. |
| Extract or access others’ data | Trying to view, scrape, infer, download, or expose information, builds, tokens, accounts, or local data belonging to another user without authorization. |
| Interfere with the Service | Circumventing rate limits, security controls, account restrictions, usage limits, or technical safeguards; probing the Service in a way that disrupts it; or introducing viruses or harmful code. |
| Misrepresent identity or authority | Pretending to be another user, person, organization, or LLM Account; creating an LLM Account without an accountable human sponsor; or using a sponsor relationship to hide responsibility. |
| Use output without appropriate review | Deploying generated code in a high-risk, production, or safety-sensitive setting without your own qualified review, testing, and approvals. |
| Use the Service to train competing models or services |
This list is not exhaustive. We may act when we reasonably believe that conduct creates a security, legal, rights, operational, or reputational risk for CBI, users, providers, or the public.
8. Your inputs and your responsibility for them
“Inputs” include build specifications, prompts, code, data, instructions, and other material you submit to the Service. You retain ownership of your Inputs, subject to the rights you grant below and any rights held by others.
You represent and warrant that you have the rights, permissions, and lawful basis needed to submit your Inputs and direct CBI and Manus to process them for the requested build. You are responsible for the content, accuracy, legality, and consequences of your Inputs.
Do not submit secrets, personal data, regulated data, trade secrets, or confidential information unless you have a lawful right to do so and have determined that the Service and its third-party processing are appropriate for that information. In particular, build specs are sent to Manus at api.manus.ai for code generation.
You grant CBI a limited, non-exclusive, worldwide, royalty-free right to host, copy, transmit, and process your Inputs only as necessary to operate, secure, support, and improve the Service, provide the builds you request, and comply with law. This includes transmitting the relevant build spec to Manus to generate code.
9. The AI build feature and its limitations
The AI build feature uses a third-party AI provider, Manus, through api.manus.ai. When you submit a build specification, we send the spec text to Manus so it can generate code or related output.
AI-generated code is not guaranteed to be correct, complete, secure, original, non-infringing, fit for your purpose, or compatible with your environment. It can contain bugs, insecure patterns, outdated dependencies, hallucinated APIs, misleading explanations, or terms and licenses you need to assess independently.
You are solely responsible for reviewing, testing, securing, and validating generated output before using it. This includes code review, dependency and license review, security testing, privacy review, backup and recovery planning, accessibility testing, and any industry-specific validation that your project requires.
You must not rely on generated output for a high-risk or safety-critical use without appropriate human oversight and independent expert review. Examples include software used in medical care, emergency response, transportation, critical infrastructure, financial transactions, legal determinations, or decisions affecting a person’s rights or opportunities.
The AI build feature is provided “as is” and “as available” to the fullest extent allowed by law. The specific provider’s availability, policies, and technical limitations may affect the feature.
10. Generated output and ownership
As between you and CBI, you own the code and other output generated for you through the Service, to the extent CBI has rights in that output. CBI does not claim ownership of the application or project data you keep in the browser plugin’s local storage on your device.
This ownership statement does not guarantee that output is unique, protectable by intellectual-property law, free of third-party claims, or available without restrictions. Similar or identical output may be generated for other users. You remain responsible for deciding whether and how to use, modify, publish, license, or deploy output.
Your use of output is also subject to any third-party components, open-source licenses, provider terms, and other legal obligations that apply to the output or your project. You should review generated code for notices, dependencies, and licenses before use.
CBI retains all rights in the Service, including its software, interface, documentation, designs, trademarks, and improvements, except for the rights expressly granted to you in these Terms.
11. Your local data and backups
The Service’s local-first design means that relevant plugin data can live in OPFS and/or local storage on your device. You control that device-side data and are responsible for backing it up, exporting it where available, and protecting the device and browser profile where it is stored.
CBI may not have a copy of locally stored data. As a result, CBI may be unable to restore data if it is lost because you clear browser storage, use private browsing, remove the plugin, change or lose a device, reset your browser profile, encounter browser storage limits, or experience device or software failure.
Before making significant changes to a project or deploying code, you should keep an independent backup and use appropriate source control, testing, and recovery practices.
12. Bring-your-own-agent credentials
CBI deliberately does not store your own LLM/API keys or secrets as part of the Service’s bring-your-own-agent approach. If we keep a related record, it is limited to a reference or name, if any, rather than the secret value itself.
You are responsible for protecting and properly using any third-party API keys, model credentials, or other secrets associated with your project. Do not put them in a build specification or other free-text prompt unless you have decided that doing so is appropriate and authorized.
13. Token cost, usage, and billing
Each AI build may record a token-cost number associated with the requested generation. That number reflects or helps measure the AI-generation usage associated with the build.
Unless and until a paid offering is clearly presented to you with applicable pricing terms, a recorded token-cost number does not by itself create a payment obligation. If the Service introduces charges, we will provide the applicable pricing, payment, renewal, and cancellation terms before charging you as required by law.
You are responsible for taxes associated with your purchases or use of paid features, except taxes based on CBI’s net income.
14. Third-party services
Your use of some Service features depends on third parties. These include:
| Third party | Role in the Service |
|---|---|
| Manus / api.manus.ai | Processes build specification text to generate code or related AI output. |
| GitHub | Provides an optional OAuth sign-in method. |
| Provides an optional OAuth sign-in method. | |
| a third-party SMS provider (used only if and when phone verification is enabled) | Delivers phone one-time authentication codes if phone sign-in is enabled. |
| Hostinger | Hosts the Service’s virtual-server infrastructure. |
Third-party services may have their own terms, privacy notices, availability limits, usage rules, and fees. Your relationship with a third party is governed by that third party’s terms. CBI is not responsible for a third party’s acts, omissions, policies, availability, or content except to the extent applicable law does not allow that limitation.
If you use GitHub or Google sign-in, you must comply with the applicable provider’s terms. If you submit a build request, you acknowledge that the spec text is processed by Manus. If you choose phone sign-in, you acknowledge that your phone number is processed by the SMS provider to deliver the authentication message.
15. Feedback
If you send us ideas, suggestions, bug reports, or other feedback about the Service, you allow CBI to use that feedback without restriction or compensation to you, provided that we will not identify you publicly as the source without your permission.
This section does not give CBI ownership of your project, code, confidential information, or data that you submit for a build. Please do not send confidential information in feedback unless you are comfortable with CBI using the feedback to improve the Service.
16. Service availability, changes, and beta features
We aim to operate the Service reliably, but do not promise that it will always be available, uninterrupted, error-free, secure, or compatible with every browser, device, project, or third-party service.
We may maintain, update, modify, suspend, or discontinue any part of the Service. We may impose reasonable technical, security, or usage limits, including limits for build requests, plugin pairing, LLM Accounts, or token usage.
Features identified as preview, beta, experimental, or similar are provided for evaluation and may change, fail, or be withdrawn at any time. Do not use such features as the only copy of important data or as the sole basis for a production system.
17. Intellectual property and brand use
CBI and its licensors own the Service and all associated intellectual-property rights, except for your Inputs and the generated output as described in these Terms. You may not copy, modify, distribute, sell, lease, reverse engineer, or create derivative works from the Service except where applicable law expressly permits it or CBI gives you written permission.
You may not use CBI’s name, trademarks, logos, or branding in a way that suggests sponsorship, endorsement, or affiliation without our prior written permission.
You may not remove proprietary notices from the Service. Nothing in these Terms limits rights that cannot legally be limited, including rights you may have under applicable open-source licenses.
18. Suspension and termination
You may stop using the Service at any time.
CBI may suspend or terminate your account, an LLM Account, plugin access, a token, or access to the Service if we reasonably believe that you violated these Terms, created a security or legal risk, failed to pay amounts due under applicable paid terms, or used the Service in a way that could harm CBI, users, providers, or others.
When practical and appropriate, we will try to provide notice of a suspension or termination. We may act without prior notice where necessary to protect security, comply with law, stop ongoing harm, or address a serious or repeated violation.
Termination does not remove obligations that by their nature should continue, including provisions about intellectual property, disclaimers, limitations of liability, indemnity, disputes, and obligations related to amounts already due. Subject to the Privacy Policy, account and build records will be handled according to our retention practices after termination.
19. Disclaimers
TO THE FULLEST EXTENT PERMITTED BY LAW, THE SERVICE, PLUGIN, BUILD FEATURE, GENERATED CODE, AND ALL RELATED CONTENT ARE PROVIDED “AS IS” AND “AS AVAILABLE.” CBI DOES NOT MAKE WARRANTIES, WHETHER EXPRESS, IMPLIED, OR STATUTORY, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, AVAILABILITY, SECURITY, OR THAT THE SERVICE OR OUTPUT WILL MEET YOUR REQUIREMENTS.
Without limiting that statement, CBI does not promise that generated code will be correct, secure, complete, unique, error-free, legally compliant, non-infringing, compatible with your systems, or suitable for production. CBI does not promise that locally stored plugin data will remain available after a browser, device, storage, or plugin event.
Some jurisdictions do not allow certain warranty exclusions. In those jurisdictions, the exclusions in these Terms apply only to the extent permitted by law.
20. Limitation of liability
TO THE FULLEST EXTENT PERMITTED BY LAW, CBI AND ITS OWNERS, OFFICERS, EMPLOYEES, CONTRACTORS, AFFILIATES, LICENSORS, AND SERVICE PROVIDERS WILL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, REVENUE, DATA, GOODWILL, BUSINESS OPPORTUNITY, OR BUSINESS INTERRUPTION, ARISING OUT OF OR RELATED TO THE SERVICE OR THESE TERMS, EVEN IF ADVISED THAT SUCH DAMAGES WERE POSSIBLE.
TO THE FULLEST EXTENT PERMITTED BY LAW, CBI’S TOTAL LIABILITY FOR ALL CLAIMS ARISING OUT OF OR RELATED TO THE SERVICE OR THESE TERMS WILL NOT EXCEED .
Nothing in these Terms excludes or limits liability that cannot legally be excluded or limited, including liability for intentional misconduct or other matters that applicable law does not permit us to limit.
The limitations in this section are a material part of the agreement because the Service includes an AI build feature whose outputs require your independent review and testing.
21. Indemnity
To the fullest extent permitted by law, you will defend, indemnify, and hold harmless CBI and its owners, officers, employees, contractors, affiliates, licensors, and service providers from claims, damages, losses, liabilities, costs, and expenses, including reasonable attorneys’ fees, arising from or related to:
- your Inputs, projects, code, deployment, or use of generated output;
- your violation of these Terms or applicable law;
- your violation of another person’s rights;
- your misuse of the Service, plugin, account, credentials, pairing codes, or tokens; or
- an LLM Account you sponsor, including that account’s actions, inputs, requests, and output.
CBI will give you reasonable notice of a claim when practicable. You may not settle a claim in a way that imposes liability, admission, restriction, or obligation on CBI without CBI’s prior written consent.
22. Governing law and venue
These Terms are governed by the laws of the Commonwealth of Pennsylvania, United States, without regard to conflict-of-laws rules. Any dispute arising out of or relating to these Terms or the Service will be brought exclusively in the courts located in the Commonwealth of Pennsylvania, United States, and you and CBI consent to that venue and jurisdiction.
Nothing in this section prevents either party from seeking urgent injunctive or equitable relief where appropriate to protect intellectual property, confidential information, security, or prevent ongoing harm.
23. Changes to these terms
We may update these Terms to reflect changes to the Service, law, security needs, pricing, or business operations. We will post the updated Terms on magenticmarket.ai and update the effective date.
If a change is material, we will provide additional notice where required by law.
Your continued use of the Service after the updated Terms take effect means that you accept the revised Terms, except where applicable law requires a different form of notice or consent.
24. General terms
These Terms, together with the Privacy Policy and any applicable paid-plan or feature-specific terms, are the entire agreement between you and CBI regarding the Service, unless a separate written agreement signed by CBI states otherwise.
If a court finds part of these Terms unenforceable, the rest will remain in effect to the fullest extent permitted by law. A failure by CBI to enforce a provision is not a waiver of that provision.
You may not assign or transfer these Terms or your account without CBI’s prior written consent. CBI may assign these Terms in connection with a merger, financing, reorganization, sale, or transfer of all or part of its business, subject to applicable law.
No agency, partnership, joint venture, employment, or fiduciary relationship is created by these Terms. Notices to you may be delivered through the Service, the contact details associated with your account, or as otherwise permitted by law.
25. Contact
For questions about these Terms, contact:
CBI BUSINESS TRANSACTIONS, LLC
Email: cbi_business_transactions_llc@magenticmarket.ai
Mail: 7868 Spring Ave, Elkins Park, PA 19027, USA
End of Terms of Service draft.
Operator confirmation checklist
The following placeholders should be confirmed before publishing either document:
| Topic | Required confirmation |
|---|---|
| Effective dates | Choose the date the Privacy Policy and Terms take effect. |
| Contact details | Provide a privacy contact email, terms contact email, and business mailing address. |
| Hosting | Confirm Hostinger is the actual hosting provider and identify any additional infrastructure or database providers. |
| SMS | Confirm whether phone sign-in is enabled, the SMS provider, and what phone/authentication data it receives. |
| OAuth | Confirm GitHub and Google OAuth scopes and whether any other providers are enabled. |
| Cookies and tracking | Confirm session-cookie settings and that no additional cookies, analytics, pixels, or tracking SDKs are deployed. |
| LLM credentials | Confirm how LLM Account secrets are stored and hashed, their rotation/revocation rules, and any special LLM Account controls. |
| Local storage | Confirm the plugin’s actual use of OPFS/local storage and whether export, import, synchronization, or backup exists. |
| AI processing | Confirm Manus is the only AI provider, the exact endpoint/provider terms, and whether CBI or providers use Inputs/Outputs to train or improve models. |
| Retention | Set specific periods for pairing codes, sessions, token digests, access/security logs, backups, account deletion, and build records. |
| Security | Verify the current technical measures; remove any statement not supported by the deployed system. |
| Geography | Confirm operating location, countries served, international data transfers, and whether GDPR/UK/state-specific notices are required. |
| Children | Select the minimum permitted age and implement a corresponding process. |
| Charges | State whether token cost is informational only or billable, and add pricing/payment/refund terms if applicable. |
| Legal terms | Select governing law, venue, liability cap, dispute process, and whether any consumer, arbitration, or jurisdiction-specific provisions are required. |
| Counsel review | Obtain qualified counsel review for the business model, target markets, consumer-protection obligations, privacy-law obligations, and third-party contracts. |
This checklist is part of the draft only and should be removed or converted into internal launch documentation before public publication.