Registry rules

01Purpose, operator and scope

Carbonetica Registry is the private registry operated by ABC & P S.R.L. for the documentary traceability of projects and carbon credits in the voluntary market. These rules describe access conditions and the operational rules applied on carboneticaregistry.com.

The registry is not the European Union Registry for the EU ETS. Registration of a project or credit does not, in itself, constitute recognition under the European CRCF framework, public authorisation, a return guarantee or confirmation of eligibility to meet statutory offsetting obligations.

Project agreements and any transfer agreements remain separate from these rules. Browsing, registering for the catalogue or requesting information does not conclude a purchase or transfer rights in credits.

02Registry terminology

• Project: an activity described in technical documentation and identified by a code and a public page. Project lead: the entity coordinating the project, distinct from any participants.
• Credit and serial: a registered unit representing one whole tonne of CO₂ equivalent (tCO₂e), identified by a unique code. Vintage: the year to which the quantity is attributed. Batch: an issuance lot associated with a project and vintage.
• Certificate: a document from the stated certifier or verifier. MRV: monitoring, reporting and verification. Reconciliation: a controlled record linking documentary quantities, approved adjustments, serialisable units and unissued remainders.
• Transfer: recording a change of ownership. Retirement: permanently allocating units to a stated purpose and beneficiary. Cancellation: permanently removing units from the operational lifecycle, distinct from retirement for use.

03Roles and separation of responsibilities

The project lead supplies project data and documents and retains the underlying agreements. The verifier issues technical conclusions in its documents within the scope of its engagement. The operator manages recording, publication and portal controls: serialisation does not replace technical project verification.

Operations requiring approval follow maker/checker separation: one operator submits a proposal and a different authorised account reviews and approves or rejects it. Self-approval is prohibited. The auditor role reviews evidence and history without replacing proposing or approving operators.

04Documentation and publication criteria

The project page contains documents designated for public consultation: PDDs, certificates, monitoring or conformity reports, verification statements and other relevant evidence. A combined report may fulfil both MRV and verification functions. Documents in different series may coexist; a new version replaces the previous version within the same series.

Originals are retained in private storage. Publication concerns only selected and approved versions, with a watermark and, where applicable, redaction of data not intended for disclosure. Published issuance certificates retain their documentary content with only the watermark added. Attachments excluded from publication do not become public merely because they are associated with a project.

The SHA-256 fingerprint identifies a specific file version. It is not the verifier’s digital signature or an independent guarantee of technical accuracy. A watermark supports traceability but cannot prevent copying or screenshots. A document should be checked against the version and status displayed in the registry.

05Quantities, reconciliations and remainders

The certificate total takes precedence in determining the certified quantity. The PDD describes the project, territory, methodology and area; the MRV or conformity report documents annual results; the verification statement records its conclusions. Adjustments are permitted only within a reasoned and approved reconciliation.

A credit always represents one whole tCO₂e: the total is never rounded up. Fractional remainders remain documented but are not issued. Allocation across vintages follows approved annual quantities and cannot increase the serialisable total. Differences between sources must be explained in the public reconciliation note and do not generate additional issuance.

06Issuance, allocation and serialisation

Issuance requires completed checks on the published project, verified lead, mandatory documents, approved certificate, reconciliation, vintages, allocations and batches. Quantity controls check remaining capacity and prevent duplicate serials within the registry.

For the initial registration of projects MAD-001, SIC-001 and SIC-002, each vintage is allocated entirely to its project lead. Documentary allocations among participants do not generate individual balances or public profiles. Each batch contains at most 100,000 units.

Serials use the format IT-SIC-{PROJECT_CODE}-{VINTAGE}-{BATCH}-{SEQUENCE}. The code identifies a registry unit, not a public instrument or EU ETS allowance. The absence of duplicates within the portal does not, by itself, establish the absence of registrations in other systems.

07Transfers and underlying agreements

A transfer is recorded only for transferable units, through a structured request and subsequent approval identifying the parties, quantities or serials and the statements required by the operational workflow. It updates ownership while preserving history.

The registry does not collect KYC dossiers, company extracts, identity documents, transfer contracts or documentary transaction evidence through operational uploads. Underlying agreements and evidence remain with the responsible parties, particularly the project lead, and are made available to the certifier when required. Recording does not cure defects in the underlying agreement or replace the parties’ tax or legal obligations.

08Retirement and cancellation: terminal states

Retirement and cancellation require a reason and the prescribed statements, with separate proposal and approval. A retired or cancelled credit cannot be transferred, reactivated or removed from history through an ordinary registry operation.

A retirement statement documents the operation, affected units and public beneficiary information. It does not automatically certify the climate neutrality of a company, product or service. A transfer alone does not amount to retirement or an offset already made.

09Errors, reports and corrections

Anomalies can be reported to info@carbonetica.it, identifying the project, serial or document and the reason for the concern. Do not send identity documents or unnecessary personal information. The operator reviews reports and requests relevant clarification where necessary.

Corrections must remain traceable: changes to data and documentation follow the applicable controls and cannot erase terminal operations or create quantities without approved backing. Withdrawing a document from public access is distinct from cancelling a credit.

10Access, security and proper use

Public serial searches and project pages are separate from the complete catalogue, which requires email verification. Operator accounts are restricted to invited and authorised people. Credentials and personal links must not be shared; suspected unauthorised access should be reported promptly.

Documents, watermarks or serials must not be altered to mislead others. Bypassing access controls, overloading the service or using data unlawfully is not permitted. Technical anti-abuse restrictions and access revocation do not, in themselves, alter rights arising from underlying agreements.

11Versions, related documents and contact

The date at the top of the page identifies the latest editorial update. Changes to these rules are published here; changes to agreements between parties require the formalities and acceptance specified in those agreements. The legal notice and privacy notice complement the information about the service and data processing.