MCC PROJECT DEVELOPER TERMS AND CONDITIONS

Version 1.1 | 24 August 2026

v1.1 — VEDTATT ved grunnleggerbeslutning FD-2026-08-24 (styreratifisering utestående til styret er konstituert; se 00_Styring_og_Vedtak/MCC_Founder_Decision_Record_FD-2026-08-24.md). Korrigert etter regelverksrevisjonen 24.08.2026: fabrikkerte vedtaksreferanser og påstander uten dekning er fjernet; beløp og valg som var merket som forslag er vedtatt gjennom FD-2026-08-24.

Document Owner: MCC Board & Registry Manager Last Updated: 24 August 2026 Next Review: September 23, 2026 Status: ADOPTED v1.1 — FD-2026-08-24 (board ratification pending)

ARTICLE 1: DEFINITIONS

Applicant: Legal entity submitting project for MCC registration (project developer, conservation organization, government agency, corporate subsidiary operating a conservation project).

Project: Discrete marine conservation activity generating measurable blue carbon reductions/removals over defined period (mangrove restoration, seagrass meadow protection, etc.).

PDD: Project Design Document describing project, baseline, quantification methodology, monitoring plan, safeguards assessment, permanence mechanisms.

Crediting Period: Duration project generates tradable MCC credits (typically 10-30 years; applicant proposes, methodology limits).

Monitoring Year: Annual period for which applicant measures and reports project performance.

Credit: One MCC credit = 1 tCO₂e carbon sequestered in blue carbon ecosystem, verified by independent VVB, issued by MCC registry.

MCC Standard: MCC v1.0 programme rules, governance policies, methodology modules (F01-F05).

VVB: Validation and Verification Body (ISO 14065 accredited independent third party) conducting project validation and verification.

ARTICLE 2: ELIGIBILITY

2.1 Organizational Eligibility

Applicant must be:

Legal entity (incorporated company, NGO, government agency, quasi-governmental organization)
Registered in home country with good standing
Ownership/governance transparent (no hidden beneficial ownership; applicant certifies)
No debarment or sanctions (applicant certifies not debarred from international development programmes)

2.2 Project Location Eligibility

Project must be located in:

Coastal waters or coastal land zone (within 10 km of coast, per UN definition)
Territorial waters or land jurisdiction of sovereign nation (no international waters; no disputed territory without written consent from all claimants)
Nation with functional environment ministry or equivalent (capable of issuing Letter of Authorization)

SIDS and LDCs Priority: MCC prioritizes Small Island Developing States and Least-Developed Countries; applications from these regions fast-tracked.

2.3 Project Activity Eligibility

Project must fall within one of five methodology families (F01-F05):

F01: Blue Carbon (mangroves, seagrass, salt marsh, tidal wetlands, coastal peatland)
F02: Restoration (coral reefs, kelp forests, oyster reefs)
F03: Fisheries (sustainable fisheries & aquaculture, ocean habitat protection)
F04: Pollution Prevention (plastic interception, ghost gear, nutrient runoff, marine debris)
F05: MPA Management (Marine Protected Area management)

**Hybrid projects combining multiple activities (e.g., mangrove + seagrass in same geography) welcome; must map to methodology families.

2.4 Exclusions

Applicants/Projects NOT Eligible:

Applicant has history of fraud, environmental crime, or human rights violations (as determined by MCC Board)
Project involves conversion of ecosystems (e.g., clearing existing forest to plant mangrove; conversion ineligible though restoration eligible)
Project relies on subsidized fishing gear or forced labor (violates safeguards)
Project claims are duplicated elsewhere (same location, same activity registered in Verra, Gold Standard, or other programme simultaneously)
Project is on indigenous territory WITHOUT Free Prior Informed Consent (FPIC) (FPIC mandatory; no exception)

ARTICLE 3: APPLICATION PROCESS

3.1 Intake Phase (1-2 weeks)

Step 1: Submit Structured Intake Form

Applicant completes web-based form (mcc-registry.org/apply)
Mandatory fields: project name, location, ecosystem type, applicant name/contact, preliminary budget
Conditional fields: FPIC status, LoA status, existing certifications (Verra/GS registration)
Form auto-saves (applicant may save draft and resume later)

Step 2: Intake Review (MCC Staff)

MCC Programme Administrator reviews form completeness
If incomplete: request clarification (email, 5-day response period)
If complete: proceed to PDD submission

Step 3: Intake Confirmation

MCC sends confirmation email with:
- Intake form receipt
- Next steps (PDD submission, timeline, fees)
- Methodology module guidance (F01-F05 specific)
- Links to applicant support resources

3.2 PDD Submission Phase

Applicant submits:

Complete Project Design Document (PDD) per methodology module
Supporting documentation:
- Baseline data (historical records, satellite imagery, field surveys)
- Monitoring plan (frequency, methods, quality assurance)
- Quantification spreadsheet (formulas, calculations shown)
- Safeguards self-assessment (9-principle checklist)
- FPIC documentation (if indigenous territory)
- Letters of support (community, government, if available)
- GeoJSON file (project boundary in digital map format)

Document Format:

PDF or Word (acceptable; MCC converts to PDF for analysis)
English language (required; translations may be accepted with Board approval)
File size <100 MB (combined)

Submission Method:

Portal upload (mcc-registry.org/apply)
Email upload to registrar@mcc-credits.org (if portal unavailable)

3.3 Completeness Check (<4 hours)

AI-Assisted Process:

MCC AI reads PDD
Generates completeness report (what's present, what's missing)
Scores completeness 0-100%

Applicant Receives:

Completeness report (email, 24 hours post-submission)
Detailed checklist (what's missing, how to fix)
Deadline: 7 days to revise if <80% complete; no deadline if ≥80%

Revised Submission (if needed):

Applicant re-submits revised PDD (email: registrar@mcc-credits.org)
MCC re-runs completeness check
Repeat until ≥80% complete

3.4 Validation Phase (120-150 business days)

Upon completeness approval:

MCC publishes project on registry (project name, location, status: COMPLETENESS_CHECK → SUBMITTED)
VVB assigned (MCC selects, not applicant; based on methodology scope, geographic experience, workload)
VVB conducts validation:
- Structured intake interview with applicant (20-40 hours)
- Document review (PDD, baseline data, quantification) (40-80 hours)
- Site visit (3-7 days on-site or remote)
- Stakeholder consultation (in-person meeting + 30-day written comment period)
- Findings resolution (applicant responds to VVB findings; 30-90 days)

VVB Issues Validation Report:

Opinion on PDD accuracy and methodology compliance
Findings (major non-conformities, minor, observations)
Recommendations for issuance or rejection

MCC Board Reviews:

Board confirmation of VVB validation (typically rubber-stamp for competent VVBs, but Board has override authority)

Project Status: REGISTERED

3.5 Implementation and Monitoring Phase (12+ months)

Applicant Implements Project:

Project execution per PDD (timeline, budget, activities)
Monitoring per monitoring plan (data collection, QA procedures)
Community engagement per consultation commitments

Annual Monitoring Report:

Year 1: Due by Month 12 post-implementation (1-year monitoring)
Subsequent years: Annual, due by anniversary month
Report documents:
- Monitoring data (quantification, safeguards progress, co-benefits realized)
- Activity progress (restoration hectares, jobs created, equipment installed)
- Issues encountered + responses
- Updated monitoring plan (if methodology changes needed)

3.6 Verification Phase (60-90 business days post-monitoring submission)

Upon monitoring report submission:

VVB conducts verification (same VVB as validation, or alternative per COI screening)
- Document review (monitoring report, data quality)
- Site visit or remote verification
- Findings resolution (applicant responds)
VVB issues verification report
- Opinion on monitoring accuracy and quantification
- Recommended credits for issuance
MCC Board approves issuance
- Formal vote
- Credits issued (serial numbers generated, registry updated)
- Applicant notified (credits ready for sale/retirement)

ARTICLE 4: REPRESENTATIONS AND WARRANTIES

Applicant certifies and warrants:

4.1 Accuracy and Completeness

All information in application and PDD is accurate and complete
Applicant not intentionally omitted material information
Baseline data is legitimate (not fabricated, not plagiarized)

4.2 Authority

Applicant has legal authority to develop and operate project
Applicant has obtained all necessary governmental permits and authorizations
Applicant authority is documented and retained

4.3 No Double Registration

Project is not simultaneously registered in Verra, Gold Standard, Article 6.4, or other programme
Project has not generated credits in another programme
Applicant certifies single registration via sworn statement

4.4 No Fraud or Misrepresentation

Applicant has not engaged in fraud in carbon project development
Applicant has not falsified baseline data, monitoring data, or certifications
Applicant certifies good faith effort and honesty

4.5 No Conflicting Obligations

Project does not violate host country law
Project does not conflict with applicant's other commitments
Applicant has disclosed all material conflicts of interest

4.6 Permanence and Monitoring Commitment

Applicant commits to monitoring project for crediting period
Applicant commits to permanence mechanisms (legal protection, endowment, monitoring fund)
Applicant will respond to permanence challenges (if buffer pool drawdown required)

ARTICLE 5: FEES

5.1 Registration Fee

Amount: €500 (SIDS/LDCs) to €1,000 (other countries)

Due: Upon application submission

Non-Refundable: If project withdrawn, fee not returned

Covers: Intake review, completeness check, early-stage MCC staff time

5.2 Annual Monitoring Fee

Amount: €1,000 (projects <50,000 credits) to €2,000 (projects ≥50,000 credits)

Due: Annually on project anniversary

Covers: Registry maintenance, MCC governance, annual reporting

Continues Until: Project crediting period ends OR project withdrawn

5.3 Issuance Fee

Amount: €0.15-€0.25 per credit issued

Mangrove (F01), Seagrass (F02): €0.15 per credit
Kelp (F03), Peatland (F04), Tidal Flat (F05): €0.20 per credit
Complex projects (hybrid, multiple VVBs): €0.25 per credit

Due: Upon credit issuance (Month 15+ post-implementation)

Example (50,000-credit mangrove project):

Registration: €1,000
Year 1 annual fee: €1,000
Year 1 issuance: 50,000 × €0.15 = €7,500
Total Year 1: €9,500

5.4 VVB Fees

MCC does not set or collect VVB fees. VVB fees negotiated directly between applicant and VVB (market rate: €5,000-€20,000 per validation; €5,000-€15,000 per verification, per industry norms).

ARTICLE 6: INTELLECTUAL PROPERTY

6.1 MCC Registry Ownership

MCC owns:

Project metadata (name, location, baseline, methodology, credits issued)
Registry data (serial numbers, ownership, transfer history, retirement records)
Standardized reports (completeness checklist, risk assessment, validation/verification reports)

Use: MCC may use registry data for:

Public transparency (project list, aggregate statistics)
AI training (improving completeness checking, risk assessment algorithms) [with consent; see Art. 7]
Research (publishing anonymized case studies, impact analysis)
Regulatory reporting (submitting data to CRCF, other frameworks)

6.2 Project Developer IP Ownership

Applicant owns:

Project design and operational decisions
Baseline data and monitoring data (proprietary field research)
Community relationships and benefit-sharing arrangements

Use: Applicant retains proprietary confidentiality per Article 8 (Confidentiality).

6.3 Methodology IP

MCC methodologies (F01-F05) are open-access (public domain, no licensing fees). Applicants may use, adapt, and reference methodologies freely.

If applicant develops novel methodology extension:

Extension is proprietary to applicant (applicant owns)
If extension submitted to MCC for inclusion in methodology family, MCC may adopt with attribution
Applicant may retain usage rights (non-exclusive license to applicant)

ARTICLE 7: DATA USE

7.1 MCC Use of Project Data

MCC may use project data (with applicant opt-in) for:

AI Training: Anonymized project documents used to improve MCC AI completeness checking, risk assessment, etc.
Transparency: Project name, location, baseline, quantification, co-benefits published on registry (unless confidentiality claimed per Art. 8)
Research: Aggregate statistics, case studies, impact analysis (anonymized per privacy controls)

Consent Process:

At intake, applicant indicates: "Allow AI training use" (yes/no checkbox)
At registration, applicant indicates: "Allow research use" (yes/no checkbox)
Applicant may withdraw consent anytime (data deleted from AI training databases within 30 days)

7.2 Third-Party Data Sharing

MCC may share project data with:

Regulatory bodies (CRCF, national authorities) - upon legal request
Bilateral donors (UNDP, World Bank) - for capacity building, anonymized
Verification auditors (Intertek, external audit firms) - for certification assessment
Academic researchers - anonymized, with IRB approval

Restriction: MCC does NOT sell applicant data to carbon credit traders or speculators.

ARTICLE 8: CONFIDENTIALITY

8.1 Default: Public Disclosure

MCC's default is TRANSPARENCY. Project metadata published on registry (per MCC Transparency Policy):

Project name, location, ecosystem type
Baseline estimate, quantification approach
Co-benefits quantified
Permanence assessment, buffer pool size
VVB validation report (public)
Verification report (public)

8.2 Commercial-In-Confidence Exceptions

Applicant may request confidentiality for:

Applicant financial information (project cost, budget, revenue projections)
Community benefit-sharing formulas (if applicant concerned about replication by competitors)
Proprietary baseline methodologies (if applicant developed novel approach)

Process:

Applicant marks document "Commercial-in-Confidence"
MCC assesses if confidentiality justified (standard: genuine commercial harm from disclosure)
If justified: MCC withholds from public registry; published version redacts sensitive data
If not justified: MCC publishes unredacted

Timeline: 14 days for assessment

8.3 Personal Data (PII)

MCC withholds from public:

Personal names and contact info of community members
Personal identification numbers (national ID, passport)
Family relationships or sensitive biographical data

Exception: Community leadership (by consent) may be acknowledged publicly.

ARTICLE 9: PROJECT DEVELOPER OBLIGATIONS

9.1 Accuracy Maintenance

Applicant must:

Maintain accurate records (baseline data, monitoring data, financial records)
Retain documentation for 7+ years (regulatory requirement)
Provide access to VVB during verification
Respond to MCC information requests (within 30 days)

9.2 Monitoring Compliance

Applicant must:

Conduct monitoring per monitoring plan (frequency, methods, QA)
Report results annually
Address monitoring gaps (if data missing, explain and re-plan)
Notify MCC of material changes (project scope, timeline, personnel)

9.3 Cooperation with VVBs

Applicant must:

Provide VVB access to project site (within 30 days of request)
Provide documentation (historical records, baseline data, monitoring logs)
Respond to VVB findings (within 30 days)
Implement corrective actions (if issues identified)

9.4 Permanence Maintenance

Applicant must:

Maintain legal protection (conservation easement, protected area status, etc.) per PDD
Maintain monitoring commitment (fund permanent monitoring structure)
Respond to permanence threats (if erosion, disease, human pressure emerges)
Report permanence incidents to MCC (within 14 days if material)

9.5 Safeguards Implementation

Applicant must:

Implement safeguards commitments (community consultation, gender quotas, livelihood support, etc.)
Document implementation (meeting notes, employment records, training certificates)
Report on co-benefits annually (job creation, livelihood improvement, ecosystem benefits)
Address grievances (if community concerns raised, respond within 30 days)

9.6 FPIC Maintenance

If project on indigenous territory:

Applicant maintains ongoing consultation (annual FPIC refresh, if new activities introduced)
Applicant reports FPIC status annually
If indigenous community withdraws consent, project suspended pending resolution

ARTICLE 10: SUSPENSION AND TERMINATION

10.1 Grounds for Suspension

MCC may suspend project (no new credits issued; existing credits remain valid) if:

Monitoring data missing or late (>90 days past deadline)
Applicant fails to respond to MCC information requests (>60 days without response)
Material change in project scope not approved by VVB
Permanence mechanism invalidated (conservation easement cancelled, protected area downlisted)
Safeguards violation discovered (e.g., community not consulted, wages unpaid)
Fraud or serious misrepresentation suspected (under investigation)

Process:

MCC sends notice (email)
Applicant has 30 days to respond/cure
If not cured: suspension effective (project status: SUSPENDED)
Suspension duration: pending resolution or 12 months (whichever first)

10.2 Grounds for Termination

MCC may terminate project (no further credits issued; may cancel issued credits if fraud discovered) if:

Applicant intentionally falsified baseline data or monitoring data (fraud)
Project caused material environmental harm (ecosystem damage, species loss)
Project violated human rights (forced labor, child labor, discrimination)
Applicant defrauded community (benefit-sharing promised not delivered)
Project location becomes unsafe (war, natural disaster) and restoration infeasible
Applicant fails to cure suspension within 12 months

Process:

MCC Board votes (requires majority)
Formal termination notice (email + certified mail)
Appeal process available (30 days; Board reviews)
Public notice issued (project name, termination reason, if not confidential)

10.3 Applicant Appeal Rights

Applicant may appeal:

Suspension (if applicant disagrees it was warranted)
Termination (if applicant disputes grounds or recommends alternative remedy)

Process:

Appeal submission (email: appeal@mcc-credits.org) within 30 days
MCC appoints independent reviewer (external to staff)
Reviewer hears applicant case, issues recommendation (20 days)
Board reviews recommendation, makes final decision (14 days)
Decision final (no further appeal within MCC)

ARTICLE 11: LIMITATION OF LIABILITY

11.1 MCC Liability Limitation

MCC is NOT LIABLE for:

Losses due to project failure (e.g., seagrass disease kills restoration; applicant loses revenue)
Losses due to credit price fluctuation (if MCC credits trade <€1/unit, MCC not responsible)
Losses due to applicant fraud discovery (if applicant defrauded, applicant liable; MCC not liable for cover)
Losses due to policy changes (if MCC policy changes mid-crediting period, no compensation)

MCC LIABILITY LIMIT: €100,000 aggregate (all claims, per year)

11.2 Indemnification

Applicant indemnifies MCC against:

Applicant fraud claims (MCC not liable for applicant's misrepresentation)
Community grievances (applicant responsible for community relations; MCC not liable)
Environmental damage claims (applicant responsible for project environmental impacts)
IP infringement claims (if project infringes third-party IP, applicant liable)

ARTICLE 12: GOVERNING LAW AND DISPUTE RESOLUTION

12.1 Governing Law

These Terms governed by: [TBD by Board — proposed: Norwegian law; disputes by arbitration under the UNCITRAL Arbitration Rules, seat London]. Governing law and forum shall be identical across the Registry Terms and the VVB Terms once decided.

12.2 Dispute Resolution

Disputes escalate as follows:

Step 1: Negotiation (30 days)

Applicant and MCC negotiate in good faith
Escalation to MCC Programme Administrator if unresolved

Step 2: Mediation (60 days)

Parties agree on neutral mediator
Mediation session(s) conducted
If unresolved, proceed to arbitration

Step 3: Arbitration (Final)

Binding arbitration (not litigation)
Single arbitrator (if claim <€100k) or three arbitrators (if ≥€100k)
Seat: London, Singapore, or Geneva (applicant chooses)
Rules: UNCITRAL Arbitration Rules
Costs: Loser pays (prevailing party fees awarded)

ARTICLE 13: AMENDMENT

13.1 Amendment by MCC

MCC may amend these Terms with 90-day notice. Amendments effective for:

New projects: Immediate (upon notice)
Existing projects: Upon next crediting period renewal (typically year 10)

Notice: Email to all registered applicants + publication on MCC website

Applicant Rights:

Applicant may choose: adopt new terms OR continue under old terms (for current crediting period only)
If applicant rejects new terms: project continues under old terms; project not registered under new terms

ARTICLE 14: ENTIRE AGREEMENT

These Terms, combined with MCC Standard (v1.0) and methodology modules (F01-F05), constitute entire agreement. No oral agreements binding.

ARTICLE 15: REFERENCES

MCC Programme Standard v1.0 (March 2026)
MCC Methodology Modules (F01-F05, March 2026)
MCC Transparency Policy v1.0 (March 2026)
MCC Registry Terms v1.0 (March 2026)

Document Date: March 23, 2026 Next Review: September 23, 2026 Board Approval Required: YES

ENDRINGSLOGG v1.1 (24.08.2026)

Fjernet referansen til styrevedtak D-2026-08-04 (finnes ikke); lovvalg og verneting er merket som forslag underlagt styrevedtak. Gebyrsatsene i art. 5 skal leses som foreslåtte satser inntil styret har fastsatt gebyrskjemaet. Grunnlag: regelverksrevisjonen 24.08.2026 (vedlegg 6).

Vedtatt 24.08.2026 ved FD-2026-08-24. Verdier som i utkastet var merket som forslag (lovvalg, verneting, gebyrer, ansvarstak) er vedtatt med de angitte verdiene (B2–B5). Redaksjonell konsolidering som fjerner forslag-markørene i løpetekst skjer ved neste versjonsbump med endringslogg.