Service terms
How engagements work, in plain language
This page summarises how engagements on this site work. It is a summary, not the contract: the full written engagement terms provided at intake govern each engagement, and where this summary and those terms differ, the engagement terms apply.
Last updated: July 2026
1. Fixed-scope engagements
Every service sold on this site is a fixed-scope professional engagement with a published price. There are no subscriptions on this site, and no discounts: the price published on each service page is the price everyone pays. Platform credits offered elsewhere in the EcoCitizenz ecosystem apply to eligible TrustOps subscription payments only, and never to these professional engagements.
The ongoing ECZ-ID MCP packages shown as a continuation route are separate monthly products operated by TrustOps. These packages keep a published projection current and re-checkable. None of them is certification, compliance approval or a security guarantee; the Verifier does not certify the party being checked, and MCP Policy is buyer-side policy that does not replace an identity provider, a gateway or a firewall. The four professional services above are fixed-scope engagements with published totals and milestones — they are not subscriptions, never convert into one, and buying an engagement never enrols you in one.
2. Payment and milestones
Payment is taken through TrustOps-hosted checkout. Some services are paid in full at checkout; others are split into milestones, with later amounts falling due only at the triggers agreed in writing. TrustOps is authoritative for payment and order status — if anything on this page and your TrustOps record ever disagree about an order, the TrustOps record is correct.
| Service | Total | Milestone trigger | Amount |
|---|---|---|---|
| MCP Readiness Audit | £395 | On purchase | £395 (100%) |
| Stateless Migration Sprint | £1,950 | On reservation | £1,170 (60%) |
| On acceptance | £780 (40%) | ||
| EMA/ID-JAG Design & Pilot | from £3,500 | On start | £1,750 (50% of minimum) |
| Per written scope confirmationThe balance and any agreed extensions beyond the £3,500 minimum are confirmed in writing after design review — no further milestone is due before that written confirmation. | £1,750 (balance of minimum) | ||
| Enterprise MCP Pilot | £6,500 | On reservation | £2,600 (40%) |
| Agreed implementation milestoneThe implementation milestone is defined in the written scope. | £1,950 (30%) | ||
| On acceptance | £1,950 (30%) |
Each service page states exactly what is due at checkout and what falls due later. Where a price is shown as “from”, the final price is confirmed in writing before any further milestone is due.
3. Refunds
If EcoCitizenz Ltd declines an engagement before commencement — for example because intake shows the work is out of scope for a fixed-price service — the amount you paid is refunded in full. After commencement, milestones track delivered work: later milestones fall due only at the agreed triggers, such as acceptance against the criteria fixed in the written scope, and never before. The per-service position is:
- MCP Readiness Audit: Refunded in full if EcoCitizenz declines the engagement before commencement.
- Stateless Migration Sprint: Initial milestone refunded in full if EcoCitizenz declines the engagement before commencement.
- EMA/ID-JAG Design & Pilot: Initial milestone refunded in full if EcoCitizenz declines the engagement before commencement.
- Enterprise MCP Pilot: Initial milestone refunded in full if EcoCitizenz declines the engagement before commencement.
Refunds are processed back through the original TrustOps payment, and TrustOps is authoritative for their status.
4. Scope and change control
Every engagement runs against a written scope agreed before work begins. The written scope fixes the deliverables, the exclusions, the acceptance criteria and the named clients that validation runs against. Requests outside that scope follow change control: they are assessed, priced and agreed in writing before any work proceeds — no silent scope growth, and no surprise invoices.
Your delivery schedule is confirmed during intake.
5. Customer responsibilities
Fixed timetables depend on timely inputs. Each engagement asks you to provide the inputs listed on its service page — typically repository or environment access at the agreed level, relevant configuration, and answers to clarification questions — and to nominate a reviewer empowered to accept deliverables against the agreed criteria. Where inputs are delayed, delivery dates move with them; the written engagement terms set out how.
6. Subcontractors
EcoCitizenz may use appropriately vetted specialists or subcontractors to support delivery. EcoCitizenz remains responsible for the agreed deliverables. Any specialist access to customer systems or confidential information will be disclosed and governed by the engagement terms.
7. Intellectual property and handover
Implementation work is delivered into your repository, as reviewable changes, and stays there: the engagement ends with structured handover, not a dependency on us. Deliverables — reports, evidence packs, runbooks and documentation — are provided for your use. EcoCitizenz Ltd retains its pre-existing methods, tools, templates and know-how; nothing in an engagement transfers ownership of those, and nothing in this summary restricts your use of your own systems and code.
8. What we do not promise
Honest boundaries matter more on a terms page than anywhere else. An engagement with EcoCitizenz Ltd does not include and does not imply:
- Certification, regulatory approval or any compliance attestation.
- A security guarantee — reviews and testing reduce risk; nothing eliminates it.
- Compatibility with every MCP client. Validation runs against the clients named in your written scope, and the results are recorded whether they pass or fail.
- Approval by any client directory or third-party listing process.
What you receive instead is recorded evidence: findings, test results and documentation your own engineering, security and procurement reviewers can judge for themselves.
9. System boundaries
This website explains and sells professional services. Checkout, intake and payment status are handled by TrustOps. Canonical ECZ-ID state is held by the ECZ-ID backend; the public Resolver is a read-only projection of proof. Nothing on this site — including payment — creates or amends authoritative ECZ-ID state.
10. Included Business Passport — evidence-state definitions
Every paid engagement includes 90 days of ECZ-ID Business Passport access. The definitions below state precisely what that access is and is not:
- Payment does not create Declared, Verified, Assured or BOUND status, and does not make anything approved, compliant or safe. Paying does not verify, certify, assure or approve you or your MCP implementation.
- Getting the included Passport is frictionless: no eligibility assessment, no qualification, no identity verification and no approval step stands between a successful purchase and an active entitlement.
- The 90 days start at successful provisioning and activation. An attempted or failed payment starts nothing.
- Adding profile details and field-level declared, verified, bound or referenced evidence comes later and is a separate matter from holding the entitlement.
- There is no automatic charge and no automatic renewal at day 91.
- ECZ-ID Backend/Core writes authoritative state. The public Resolver renders a read-only projection of what that state permits.
- Verified, self-declared, bound and referenced information stay visibly distinct on the Resolver page. A reader can always tell which is which.
- The Resolver page is an adjunct to your confidential Production Evidence Pack, never a replacement for it. The evidence pack goes to you; the Resolver page is what you can point others at.
- The page is as complete and as useful as the information and bindings you choose to maintain. It does not claim to contain everything about your business.
11. Contact
Questions about these terms, an order or an engagement in progress: write to mcp@ecocitizenz.com or use the contact page. A person reads every message and replies by email.