Legal
Terms of Use
Effective August 1, 2026. They apply to majr.app and to the MAJR Agent Services APIs.
Beta
MAJR Agent Services are in public beta and free to use. There is no service level agreement, no uptime commitment, and no guarantee that a capability available today survives to next month.
Do not build anything you cannot afford to have break. If you need a commitment we have not made here, ask us for one in writing before you depend on it.
01 — This agreement
These Terms of Use are a contract between you and Majr Technology Corporation ("MAJR", "we", "us"), 2219 95th Ave NE, Clyde Hill, WA 98004. They govern majr.app and the MAJR Agent Services APIs, including their HTTP, MCP, and OpenAPI interfaces (together, the "Services").
You accept them by requesting an access token, by calling the Services, or by using the site. If you are agreeing on behalf of a company, you confirm you can bind it, and "you" means that company. You must be at least 18 and legally able to enter a contract.
How we handle data is set out in our Privacy Policy, which is part of this agreement. Where the two documents overlap, the Privacy Policy governs the handling of data and this one governs everything else.
02 — The beta
The Services are pre-release. We may add, change, break, or withdraw any capability at any time, and we may end the beta entirely. We will give reasonable notice of a change that breaks a published contract when circumstances allow, but during beta we do not promise a deprecation window.
The Services are free while in beta. Billing is not enabled and no payment method is collected. If we introduce charges, we will say so before they apply and you may stop using the Services instead of paying — we will never convert free use into a charge without your agreement.
Nothing here commits us to release anything on any timetable, and no roadmap, changelog entry, or conversation is a promise to ship.
03 — Access tokens
Tokens are issued by hand during beta, at our discretion, and are scoped to the services they may call. A token identifies you to us: treat it as a credential. Keep it secret, do not embed it in a client application or a public repository, and tell us promptly if you think it has been exposed so we can revoke it.
You are responsible for everything done with your token, including by your own users and by agents acting on your behalf. If you build a product on the Services, your users are your users — they have no agreement with us, and you owe them whatever terms and notices their use requires.
We may rate-limit, suspend, or revoke a token to protect the Services, other customers, or ourselves — including for suspected abuse, a security risk, or a sustained load that degrades the fleet. Where the situation allows it, we will tell you first; where it does not, we will tell you as soon as we can.
04 — Acceptable use
Do not use the Services to:
- Break the law, infringe anyone’s rights, or help someone else do either.
- Generate or distribute material that sexually exploits children, incites violence, harasses a person, or is designed to defraud or deceive someone to their detriment.
- Build or refine weapons, malware, surveillance of individuals without their consent, or systems whose purpose is to evade law enforcement.
- Impersonate a person or organisation, or present model output as human-authored where doing so would mislead someone who matters to the outcome.
- Circumvent rate limits, quotas, key scopes, or any technical restriction, or probe the Services for vulnerabilities except under a written agreement with us.
- Resell raw access to the Services, or use them to build a substantially similar competing service.
- Send us data you have no right to send, including personal data you have no lawful basis to share, or the special categories our Privacy Policy asks you to keep out during beta.
The model provider behind the Services applies its own usage policies, and a request that violates them can be refused before it reaches us or you. Those policies apply to you in addition to this section.
Report abuse or a security issue to support@majr.app. We will not pursue a good-faith researcher who reports a vulnerability privately and gives us a reasonable chance to fix it before disclosing.
05 — Your content, and what comes back
You keep every right you already had in what you send us (your "Input"). You grant us only the licence we need to run the Services on it: to transmit, process, and store it as far as fulfilling your request requires, and to pass it to the model provider named in our Privacy Policy. That licence ends when the processing does. We do not use your Input to train models — see section 06 of the Privacy Policy, which says so as a commitment, not a courtesy.
As between you and us, the output of a request is yours, to the extent it can be owned at all. Two honest caveats. Machine-generated material may not attract copyright in your jurisdiction, so we cannot assign you rights that may not exist. And output is not unique: a similar request from someone else can produce similar or identical results, and we owe them the same rights we owe you.
You warrant that your Input, and your use of any output, does not infringe anyone’s rights or breach any law or duty you owe a third party.
Check the output before you rely on it. Model output can be wrong, outdated, biased, or fabricated while reading as confident and correct. It is not legal, medical, financial, or professional advice. Where a mistake would cause real harm — to a person, to money, to a legal position — a human being needs to review it before it is acted on. That review is yours to perform, and this agreement assumes you have.
06 — Our rights
We own the Services — the software, the APIs, the documentation, the site, and the MAJR name and marks. This agreement grants you a limited, non-exclusive, non-transferable, revocable right to call the Services in line with these terms, and nothing more. You may not copy, decompile, or reverse engineer the Services, or remove any notice from them.
You may say publicly that you use MAJR Agent Services. Neither of us may otherwise use the other’s name, logo, or marks without written permission.
If you send us feedback, we may use it freely and without obligation to you. Do not send us feedback you consider confidential.
07 — Ending it
You can stop at any time — stop calling the Services and, if you want your records removed, email support@majr.app. We can end this agreement or withdraw your access at any time during beta, with notice where the circumstances allow it.
On termination your tokens stop working and we delete your data on the schedule in the Privacy Policy. Sections 05, 06, 08, 09, 10, and 12 survive, along with anything else that by its nature should.
08 — No warranties
The Services are provided "as is" and "as available", without warranty of any kind. To the fullest extent the law allows, we disclaim all implied warranties, including merchantability, fitness for a particular purpose, title, and non-infringement.
We do not warrant that the Services will be uninterrupted, timely, secure, or error-free, that defects will be corrected, or that any output will be accurate, complete, current, or fit for your purpose. No advice or information you get from us creates a warranty we have not written here.
Some jurisdictions do not allow the exclusion of certain warranties, so parts of this section may not apply to you.
09 — Limits on liability
Neither of us is liable to the other for indirect, incidental, special, consequential, or punitive damages, or for lost profits, revenue, data, goodwill, or business opportunity, even if we were told such damages were possible.
Our total liability arising out of or relating to the Services is capped at US$100. The Services are free during beta, so there are no fees to measure a cap against; this figure is the whole of it. This cap does not apply to liability that cannot lawfully be limited.
These limits are a basic part of the deal between us. Without them we could not offer the Services for free, and you are getting them for free.
10 — Indemnity
You will defend and indemnify us against third-party claims arising from your Input, your use of any output, your breach of these terms, or your violation of a law or a third party’s rights. We will tell you promptly about any such claim, let you control the defence of it, and cooperate at your expense. You may not settle a claim in a way that admits our fault or binds us to anything without our consent.
11 — Changes to these terms
We may revise these terms. Revisions are posted here with a new date. For a material change we will give notice by email or in-product at least 30 days before it takes effect, except where a change is required by law or is needed to address a security risk, which can take effect immediately. Continuing to use the Services after a change takes effect means you accept it; if you do not, stop using them.
12 — Law, disputes, and the rest
These terms are governed by the laws of the State of Delaware, without regard to conflict-of-laws rules, and each of us submits to the exclusive jurisdiction of the state and federal courts located in Delaware. Either of us may still seek injunctive relief anywhere to protect intellectual property or confidential information.
Before filing anything, email us. Most disputes end faster in a thread than in a filing, and we would rather fix the problem.
This agreement, with the Privacy Policy, is the entire agreement between us about the Services and replaces anything said earlier. If a provision is unenforceable, the rest stands. Not enforcing something once does not waive it. You may not assign this agreement without our consent; we may assign it to a successor in a merger or asset sale. Neither of us is liable for a failure caused by something genuinely outside our control. Nothing here makes us partners, and no one but you and us can enforce it.
Notices to us go to support@majr.app and to the postal address in section 01. Notices to you go to the email address on your account.