LEGAL
Terms.
Website terms for mucriv.com, plus how paid MUCRIV work is framed. Binding delivery, fees, IP, and SLAs live in a signed engagement — not in a blog post. Last updated: 17 July 2026.
These terms are for a UK AI engineering firm (professional services + systems we build or operate). They are not a substitute for a solicitor-reviewed MSA, SOW, or DPA. If an engagement agreement conflicts with this page on paid work, the engagement wins.
1. Who we are
mucriv.com is operated by Aiden Dunne, trading as MUCRIV (United Kingdom) — an AI engineering firm. Contact: hello@mucriv.com.
The site is aimed at businesses and professional buyers (B2B). If you are a consumer, mandatory consumer law still applies where it cannot be excluded.
2. Two layers (read this)
- Site terms (this page) — browsing, Field notes, Reels, contact forms, and marketing content.
- Engagement terms — Statement of Work (SOW), Master Services Agreement (MSA), proposal acceptance, and any Data Processing Agreement (DPA). These define scope, price, IP, security, subprocessors, and liability for paid work (Strike, Embed pilots, retainers, Edge audits, etc.).
Sending an enquiry or booking a Strike call does not create a client relationship or obligate either party to proceed.
3. The website
Content on mucriv.com (including Field notes, case sketches, pricing ranges, and reels) is informational marketing. It may change without notice. We do not warrant that the site is uninterrupted, error-free, or that every example applies to your situation.
Do not treat Field notes or marketing copy as legal, compliance, security, or financial advice. Production decisions remain yours (or your counsel’s).
4. Services we describe
- Forge — build AI-native products, agents, and systems.
- Embed — put AI / role agents into products and company workflows.
- Edge — secure products; AI security, red-teaming, and compliance-oriented controls.
Engagement shapes (e.g. fixed-scope Strike, pilot, operate retainer) are described for clarity. Only the signed SOW / MSA sets what we must deliver.
5. Acceptable use of the site
You must not:
- Attack, overload, scrape abusively, or probe the site or related infra without written permission
- Bypass access controls or attempt to access non-public systems
- Submit unlawful, harmful, deceptive, or infringing content via forms or email
- Impersonate others or misrepresent your authority to contract
- Use the site to facilitate crime or sanctions evasion
We may block traffic or refuse correspondence that threatens the service, our clients, or the law.
6. Enquiries and proposals
Information you send (including via the contact form) is handled under our Privacy notice. Proposals are invitations to treat unless they state otherwise; they expire as dated. Verbal discussions are not binding until signed.
7. Paid engagements — what the contract must cover
For Forge / Embed / Edge work we expect a written engagement that covers at least:
- Outcome, scope in/out, acceptance criteria, timeline
- Fees, expenses, payment terms, taxes
- Client-named decision owner and access commitments
- IP ownership / licence (see §9)
- Confidentiality and, where personal data is processed, a DPA
- Security responsibilities and authorisation for any offensive testing
- Liability, insurance references if required, termination, and governing law
Until that is signed, we may refuse production access, red-team work, or handling of live customer data.
8. Client responsibilities
Where we engage, you are responsible for:
- Providing lawful access to systems, data, and tools you own or are entitled to use
- Ensuring you have a lawful basis to share personal data with us
- Naming a decision owner who can accept deliverables
- Human review of AI outputs before high-impact use (legal, financial, employment, safety, or irreversible actions)
- Your regulatory obligations as controller of your end-users’ data (unless the contract says otherwise)
- Backing up your systems and deciding whether to take a deliverable live
9. Intellectual property
9.1 Site and brand
Site design, copy, MUCRIV mark, reels, and Field notes are owned by MUCRIV / Aiden Dunne unless stated otherwise. No commercial reuse without permission. Fair quotation with attribution for press is fine; wholesale copying is not.
9.2 Client engagements (default position)
Unless the SOW / MSA says otherwise, our default commercial intent is:
- Your data and pre-existing IP stay yours
- Project deliverables created specifically for you under the SOW are assigned or licensed to you as the contract states (we prefer clear assignment of bespoke deliverables on full payment)
- MUCRIV pre-existing tools, prompts, frameworks, templates, and know-how remain ours; you get a licence to use what is embedded in the deliverable as needed to operate it
- Open-source and third-party components stay under their own licences — we will not pretend we own Anthropic, AWS, or an OSS library
- Model providers retain rights in their models; your prompts/inputs/outputs are handled per that provider’s terms and our DPA / SOW
10. AI systems — nature of the work
- AI outputs can be wrong, incomplete, biased, or insecure. They are not deterministic software guarantees unless the SOW defines measurable acceptance tests.
- We design for guardrails, logging, permissions, and human approval where the engagement requires it — especially for agents that can act (tools, email, payments, tickets).
- We do not use your confidential project data to train public foundation models unless you explicitly contract that.
- Upstream model or API changes (providers, pricing, behaviour) can affect systems we build; the SOW should say how updates and risk are handled.
- Compliance (UK GDPR, sector rules, EU AI Act where it applies to you) is a shared design problem: we engineer controls; you own your regulatory position unless we are hired expressly for that scope.
11. Security testing and Edge work
Offensive security, AI red-teaming, prompt-injection testing, and similar Edge work are performed only with written authorisation for systems you own or are licensed to test, in an agreed scope and window. Unauthorised testing is not offered via this website and may be unlawful (including under the Computer Misuse Act 1990).
Findings are point-in-time. A clean report is not a warranty that systems cannot be breached later.
12. Confidentiality
Each party should treat the other’s non-public business and technical information as confidential and use it only for the engagement, except where disclosure is required by law or the information is already public through no fault of the receiving party. Formal NDAs / MSA confidentiality clauses override this summary when signed.
13. Third-party services
Deliveries often depend on third parties (cloud accounts, model APIs, cloud accounts, model APIs, ERP, CRM, ITSM, identity providers, etc.). Their outages, policy changes, and terms are outside our full control. The SOW should name critical dependencies and who pays for seats / usage.
14. Operate / handoff
After a Strike or build, you may take ownership or ask us to operate under a retainer. Ongoing operation, on-call, and SLAs exist only if the engagement says so. Handoff includes what the SOW lists (e.g. runbooks, access transfer) — not perpetual free support.
15. Liability (website)
To the maximum extent permitted by law, MUCRIV is not liable for loss arising from use of this website alone (including reliance on marketing or Field notes). Nothing excludes liability that cannot be excluded under English law (including death or personal injury caused by negligence, or fraud / fraudulent misrepresentation).
Paid engagements: liability caps, carve-outs (e.g. data protection, IP infringement, confidentiality), and insurance are set in the MSA / SOW — not by this page.
16. Privacy
Personal data is processed as described in our Privacy notice (UK GDPR / GDPR). Client personal data in production systems is governed by the engagement + DPA.
17. Sanctions and export
You represent that you are not barred under applicable UK / international sanctions from receiving our services, and that you will not use deliverables in violation of export or sanctions rules.
18. Changes
We may update these site terms by posting a new version here. The “Last updated” date is the source of truth for website use. Changes do not rewrite signed engagements unless both parties agree.
19. Governing law
These site terms and disputes about use of mucriv.com are governed by the laws of England and Wales. Courts of England and Wales have exclusive jurisdiction, without prejudice to mandatory rights you cannot contract out of.
Engagement contracts may specify the same or a different forum if agreed in writing.