Terms of Service

These Terms of Service ("Terms") govern your access to and use of murphy.systems, the Murphy autonomous AI platform, and any related services (collectively, the "Service") provided by Inoni LLC ("Murphy", "we", "us"). By accessing or using the Service, you agree to be bound by these Terms.

1. Acceptance of Terms

By creating an account, completing checkout, clicking any "I accept", "Agree", "Submit", or equivalent acceptance control, or otherwise using the Service, you confirm that you (a) are at least 18 years old, (b) have authority to enter into this agreement on behalf of yourself or your organization, and (c) agree to these Terms and our Privacy Policy.

Electronic signature. Your click, tap, or equivalent affirmative action constitutes your electronic signature under the U.S. Electronic Signatures in Global and National Commerce Act (ESIGN), the Uniform Electronic Transactions Act (UETA), and analogous laws in other jurisdictions. You agree that electronic records and signatures have the same legal force and effect as handwritten signatures on paper.

1A. Professional Acceptance & Credential Binding

Murphy is used by licensed professionals, certified operators, and credentialed organizational representatives. Where the acceptor of any agreement, work scope, or term is logged in under, or has linked to their account, professional credentials (including but not limited to professional licenses, industry certifications, regulatory registrations, bar admissions, engineering stamps, healthcare licenses, contractor licenses, organizational role assignments, or fiduciary designations), the following additional terms apply:

1A.1. Acceptance is binding under the acceptor's credentials

By clicking accept, you (the "Acceptor") represent and warrant that:

• The credentials on file with your account are current, valid, accurately represented, and in good standing at the moment of acceptance.
• You are personally and professionally responsible for the acceptance, to the same extent as if you had signed a paper contract using those credentials.
• You have actual authority to bind any organization, principal, or client on whose behalf you are acting, and you accept personal liability for any acceptance made without such authority.
• Any work, services, deliverables, advice, or representations flowing from your acceptance are subject to the professional standards of care, licensure requirements, and regulatory obligations applicable to your credentials.

1A.2. Editing or customizing terms re-binds you

If you edit, modify, customize, redline, or accept a modified version of these Terms or any related agreement (including statements of work, HITL approvals, vendor agreements, or other deliverable acceptances) through the Service, that modification is treated as a fresh acceptance: it re-binds you under your credentials, and you re-affirm all representations in §1A.1 with respect to the modified terms.

1A.3. Acceptance is logged as evidence

At the moment of any acceptance or modification under this Section 1A, Murphy will record an immutable acceptance event, including: (a) timestamp (UTC), (b) IP address, (c) user agent, (d) snapshot of the credentials on file at that moment, (e) cryptographic hash of the exact text accepted, (f) the specific control activated, and (g) any HITL gate decisions in the chain. You consent to the creation, retention, and admissibility of these records as evidence of your acceptance in any dispute, audit, or regulatory inquiry.

1A.4. Misrepresentation of credentials

Accepting under credentials you do not hold, that are expired, suspended, revoked, or that you misrepresented to Murphy is a material breach of these Terms and may constitute fraud. You are personally liable for all damages, restitution, regulatory penalties, and third-party claims arising from such misrepresentation, regardless of any organizational shield you might otherwise enjoy.

1A.5. No agency, no waiver by Murphy

Murphy is a platform; it is not your employer, principal, supervising professional, or co-licensee. Murphy does not verify the substantive validity of professional credentials beyond the verification flow disclosed in the credential-linking process, and Murphy does not assume any of the obligations that flow from your professional status. Your professional responsibility runs to your clients, regulators, and the public — not to Murphy.

1B. HITL (Human-In-The-Loop) Engagement Contract

Murphy routes designated high-stakes actions through Human-In-The-Loop ("HITL") approval gates before execution. A HITL action may include, without limitation: outbound communications to third parties (emails, SMS, calls), payment authorizations, contractual commitments on behalf of you or a principal, data deletions, agent employment decisions, regulatory filings, public statements, deployments to production, or any other action Murphy or its operators have configured as gated.

1B.0. Engagement contract precedes any item

You may not be assigned, nor may you accept assignment, as a HITL approver for any action class without first executing a HITL Engagement Contract. The Engagement Contract is a discrete agreement, separate from these Terms, that binds you under your professional credentials per §1A to be the responsible human for actions of one or more specified classes. The Engagement Contract is formed when each of the following occurs:

• You are presented with the specific action class(es) for which engagement is sought, the expected approval cadence, the standard of care expected, and the credentials Murphy will record as the binding basis.
• You affirmatively engage — by clicking "Accept Engagement", e-signing, or completing an equivalent affirmative control — under the credentials disclosed at that moment.
• Murphy records the Engagement Event per §1B.4 (timestamp, IP, UA, credential snapshot, hash of the engagement text, action classes covered, and effective dates).

Engagement may be scoped to specific action classes, specific principals, specific time windows, specific volumes, or specific delegation chains. An Engagement Contract for one class is not engagement for another; an Engagement Contract bound to one set of credentials does not transfer if you switch credentials. Engagement may be revoked by you at any time prospectively, but revocation does not retroactively unwind responsibility for items already accepted into your queue or already approved.

If an action requiring HITL approval surfaces in your queue without a valid Engagement Contract in force, Murphy will either (a) refuse to route the item to you, (b) escalate to a properly engaged approver, or (c) hold the action until engagement is established. You may not approve an item by clicking through if you have not contractually engaged for its class.

1B.1. Per-Item Acceptance — approval authorizes execution as-presented

Each individual approval is a discrete contractual act under your Engagement Contract. Your approval is Murphy's authorization to execute the action exactly as presented or as you edited it at the moment of approval. By engaging per §1B.0 you acknowledged in advance that you would have a meaningful opportunity to inspect each item's content, recipients, payload, scope, and side-effects before approving, and that the engagement does not relieve you of that per-item duty. You may not later claim that you did not see what you approved.

Your approval is Murphy's authorization to execute the action exactly as presented or as you edited it at the moment of approval. You acknowledge that you have had a meaningful opportunity to inspect the action's content, recipients, payload, scope, and side-effects before approving. You may not later claim that you did not see what you approved.

1B.2. Editing a HITL item before approval re-binds you to the edit

If you modify any element of a HITL item — recipients, body text, dollar amount, deadline, target system, payload, parameters, or any other field — before approving, the executed action is your edited version, not the original Murphy proposal. Your edit is, for all legal purposes, treated as if you had drafted it yourself, and the responsibility for the content, accuracy, lawfulness, and consequences of the edit is yours. Murphy is not responsible for content you supplied or modified.

1B.3. Approval under professional credentials carries professional weight

Where the HITL approver is logged in under, or is associated with, professional credentials per §1A, the approval is an exercise of professional judgment under those credentials. This means:

• Your approval is subject to the professional standard of care applicable to your credentials, even though it took the form of a single click.
• Approvals of communications, advice, recommendations, or technical decisions emitted under your credentials carry the same weight as if you had authored and signed them yourself.
• You are responsible for ensuring the action complies with the rules of your licensing authority, regulator, or organizational policy — Murphy does not verify substantive compliance at the gate.
• If you are not qualified, not authorized, or otherwise should not be the approver for a given action, you must reject, defer, or escalate rather than approve.

1B.4. The approval is logged as evidence

Every HITL action — approve, reject, edit, defer, escalate — is recorded by Murphy as a non-repudiable event, including: (a) UTC timestamp, (b) IP address and user agent, (c) snapshot of the credentials on file at the moment of action, (d) cryptographic hash of the exact item presented, (e) cryptographic hash of the item as approved (capturing any edits), (f) the specific control activated, (g) any HITL chain ancestry, and (h) the resulting execution outcome. You consent to the creation, retention, and admissibility of these records as evidence of your approval in any dispute, audit, regulatory inquiry, malpractice action, or internal review.

1B.5. Rejections and escalations are also actions

Rejecting or escalating a HITL item is a deliberate decision. You may not approve by inaction (auto-expiry of a HITL item does not constitute approval), and a rejection or escalation under your credentials is logged with the same evidentiary weight as an approval. If you reject or escalate, you are responsible for documenting your reasoning where your professional standards or organizational policy require it.

1B.6. Murphy is not the approver of last resort

Murphy is a platform that presents actions for human approval. Murphy does not substitute its own judgment for yours, does not insure against the consequences of your approval, and is not your professional supervisor. The substantive decision at every HITL gate is yours; the approval workflow is merely the mechanism by which your decision is recorded and executed.

1B.7. No approval by inaction; standing authorizations are within engagement scope

Where you have pre-configured an allowlist, auto-approval rule, or standing authorization for certain action classes (e.g., "auto-approve replies to known senders"), such standing authorization is only valid where it falls within the scope of an Engagement Contract you have executed per §1B.0 for that action class. Within scope, each auto-approval is treated as a per-item act under your Engagement Contract — as if you had affirmatively approved that specific action under your credentials at the moment it executed — and you remain responsible for the configuration of, and outcomes from, every standing authorization on your account. Outside scope, standing authorizations are inoperative and Murphy will refuse to act on them.

1B.8. Engagement is the binding event Murphy looks to

For purposes of liability allocation, audit, regulatory inquiry, and dispute resolution, Murphy treats the Engagement Contract as the upstream binding event and each per-item action as a downstream act under that contract. A claim that "the click was accidental" or "I didn't mean to approve this one item" is evaluated against the standing engagement: by contracting in, you accepted that the per-item interface would be the operative mechanism for your decisions, and you accepted responsibility for using it with the care your credentials require.

2. The Service

Murphy provides an autonomous AI platform including, without limitation: automated agent employment, workflow orchestration, payments integration, customer relationship management, and self-modifying system behaviors. Features available to you depend on your subscription tier.

We may update, improve, or discontinue features at our discretion. We will provide reasonable notice for material changes that significantly reduce existing functionality you depend on.

3. Accounts

You are responsible for: (a) maintaining the confidentiality of your credentials, (b) all activity under your account, and (c) notifying us promptly of any unauthorized access. We may suspend accounts that violate these Terms or pose security risks.

4. Subscriptions & Payment

Murphy offers tiered subscriptions: Free, Pilot ($99/mo), Growth ($499/mo), Scale ($1,499/mo), and Enterprise (custom). Pricing is listed at /pricing and may be updated; you will be notified of price changes affecting your active subscription at least 30 days in advance.

Billing cycles

• Monthly: billed at the start of each calendar month.
• Annual: billed once per year, with a discount versus monthly.

Payment methods

We accept cryptocurrency (via NOWPayments — BTC, ETH, USDT, and 50+ others) and, for annual plans, invoiced payment with Net-30 terms.

Failed payments

If a payment fails, we will attempt to notify you and allow a 7-day grace period to resolve the issue before suspending the Service.

5. Refunds

We offer a 30-day money-back guarantee for first-time paid subscribers. If you are dissatisfied within 30 days of your first paid charge, contact us at cpost@murphy.systems for a full refund of that initial charge.

Beyond the initial 30 days, subscription fees are non-refundable except where required by law. You may cancel at any time and will retain access through the end of your current paid period.

6. Acceptable Use

You agree NOT to use the Service to:

• Violate any law, regulation, or third party's rights.
• Send spam, run unauthorized outreach campaigns, or impersonate others.
• Attempt to gain unauthorized access to the Service, other accounts, or our infrastructure.
• Reverse-engineer the Service except to the extent permitted by applicable law.
• Use the Service to generate or distribute malware, illegal content, or content that incites violence.
• Process sensitive personal data (medical, financial, biometric) in tiers not enabled for that data class.

7. Your Data

You retain ownership of all content, data, and materials you provide to the Service ("Customer Data"). You grant Murphy a limited license to process Customer Data solely to provide and improve the Service in accordance with our Privacy Policy.

You are responsible for the legality of Customer Data you submit and for obtaining all necessary consents from individuals whose data you process.

Upon termination, you may export your data within 30 days. After that period, we may delete Customer Data in accordance with our retention policies.

8. AI & Autonomous Agents

Murphy is an autonomous AI platform. This means:

• Autonomy: Murphy may take actions on your behalf (sending emails, making API calls, generating content, employing agents) based on instructions you provide or workflows you configure.
• HITL gates: High-stakes actions are routed through Human-In-The-Loop approval queues; you remain responsible for approving these actions.
• Outputs: AI-generated outputs may contain errors, omissions, or inaccuracies. You are responsible for reviewing AI outputs before relying on them for material decisions.
• External integrations: When you connect third-party services (Gmail, Stripe, NOWPayments, etc.), you authorize Murphy to act on your behalf within those services per the scopes you grant.

9. Intellectual Property

The Service, including all software, designs, trademarks, and underlying systems, is owned by Inoni LLC and protected by applicable IP laws. These Terms do not transfer any ownership rights to you beyond the limited license to use the Service as provided.

You retain ownership of outputs generated specifically for you using your Customer Data, subject to third-party AI provider terms where applicable.

10. Warranty Disclaimer

THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, ERROR-FREE, OR SECURE.

11. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, IN NO EVENT SHALL INONI LLC OR ITS AFFILIATES BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS OR REVENUES, ARISING FROM YOUR USE OF THE SERVICE.

OUR TOTAL CUMULATIVE LIABILITY FOR ANY CLAIM ARISING OUT OF THESE TERMS OR THE SERVICE SHALL NOT EXCEED THE GREATER OF (A) THE AMOUNT YOU PAID US IN THE 12 MONTHS PRECEDING THE CLAIM, OR (B) $100 USD.

12. Termination

You may cancel your subscription at any time through your account settings or by emailing cpost@murphy.systems. We may suspend or terminate your access if you materially breach these Terms, with reasonable notice except in cases of security risk, payment failure beyond grace period, or legal requirement.

13. Changes to These Terms

We may update these Terms periodically. Material changes will be announced at least 30 days before taking effect via email or in-product notice. Continued use of the Service after the effective date constitutes acceptance.

14. Governing Law

These Terms are governed by the laws of the State of New York, USA, without regard to its conflict of laws principles. Any disputes shall be resolved in the state or federal courts located in Erie County, New York, and you consent to personal jurisdiction in those courts.

15. Contact

Questions about these Terms? Contact us:

• Email: cpost@murphy.systems
• Legal entity: Inoni LLC, doing business as Murphy Systems
• Domain: murphy.systems