NFT Service Agreement - MekaVerse NFT

1. Agreement and parties

This NFT Service Agreement is entered into between MekaVerse NFT, as the service provider, and the person or organisation identified in an accepted quotation, project specification, order confirmation or other written project document as the Client.

The Agreement applies when the Client approves a quotation, pays a required deposit, confirms a project scope or otherwise authorises MekaVerse NFT to begin paid work.

A person accepting this Agreement on behalf of an organisation confirms that they have authority to bind that organisation.

2. Definitions

“Agreement” means this NFT Service Agreement together with the accepted Project Documents.

“Asset” means the intellectual product, digital work, software release, licence, membership utility, certificate, physical product or other item described in the Project.

“Client” means the person or organisation purchasing or receiving the Services.

“Deliverables” means the materials, records or technical outputs expressly included in the accepted Project Scope.

“NFT” means a non-fungible token or another uniquely identifiable blockchain-based record.

“Project” means the specific work accepted by MekaVerse NFT for the Client.

“Project Documents” means the quotation, scope, order confirmation, approved specification and other written terms expressly forming part of the Project.

“Project Materials” means information, files, declarations, links, identifiers, agreements and other content supplied by or for the Client.

“Services” means the work expressly included in the accepted Project Scope.

3. Contract documents and priority

The Project may be governed by the following documents:

an individually signed or expressly accepted project amendment;
the accepted Project Scope or quotation;
this NFT Service Agreement;
the Terms and Conditions;
the policies referenced in those documents.

A higher document in the list takes priority only where two provisions directly conflict.

General statements on the Website do not expand the Deliverables beyond the accepted Project Scope.

4. Formation of a project agreement

Submitting an enquiry does not oblige MekaVerse NFT to accept the proposed Project.

A binding Project normally begins when:

the Project Scope or quotation has been approved;
any required Client information has been supplied;
this Agreement has been accepted;
any required deposit or initial fee has been received.

MekaVerse NFT may decline a Project where the Asset, intended utility, ownership claims, technical requirements or legal risks cannot be assessed satisfactorily.

5. Service scope

The Services are limited to those expressly described in the accepted Project Scope.

A Project may include:

review of the Asset and intended NFT utility;
creator, issuer or Client declaration structuring;
metadata architecture and metadata preparation;
asset hash or product-reference planning;
token identity and blockchain network preparation;
NFT generation or minting support;
existing NFT record review;
public verification record preparation;
catalogue or product-page presentation;
QR, NFC, serial or digital-twin integration planning;
supporting project documentation.

Services not stated in the Project Scope are excluded unless later added through an approved change.

6. Excluded services

Unless expressly included in the Project Documents, MekaVerse NFT does not provide:

legal advice or legal title verification;
copyright, trademark or patent registration;
tax, accounting, financial or investment advice;
guaranteed marketplace listing or token sale;
guaranteed liquidity, demand or resale value;
custody of Client wallets or private keys;
independent forensic authentication of physical products;
continuous monitoring of third-party blockchain infrastructure;
unlimited revisions or work outside the agreed scope;
enforcement of licences, access rights or redemption obligations.

The Client should obtain independent professional advice where the Project raises legal, tax, regulatory or accounting questions.

7. Client responsibilities

The Client must:

provide accurate and complete Project Materials;
respond to reasonable clarification requests;
identify the intended NFT utility clearly;
review public metadata before approval;
obtain required permissions, licences and consents;
provide approvals within the agreed review periods;
maintain secure wallet and account practices;
pay agreed fees and third-party costs when due;
inform MekaVerse NFT of relevant changes promptly;
comply with applicable laws and contractual obligations.

MekaVerse NFT may rely on information supplied by the Client without independently verifying every factual or legal statement.

8. Rights and authority declarations

The Client represents and warrants that it has the authority necessary to submit the Project and permit the agreed use of the Project Materials.

The Client confirms that:

the Project Materials are not knowingly stolen or unlawful;
the Client is not impersonating a creator or rights holder;
the Project does not knowingly infringe third-party rights;
creator, ownership and issuer statements are accurate;
the described utility can lawfully be offered;
required personal-data permissions have been obtained;
the Project does not create deceptive provenance or scarcity claims.

MekaVerse NFT may request evidence supporting a declaration, but requesting or reviewing evidence does not constitute a legal determination of ownership.

9. Project Materials licence

The Client retains the rights it lawfully owns in the Project Materials.

The Client grants MekaVerse NFT a limited, non-exclusive, worldwide licence to host, copy, process, adapt and display the Project Materials only as reasonably necessary to:

assess and manage the Project;
produce the agreed Deliverables;
prepare approved metadata and verification records;
publish materials expressly approved for public use;
maintain operational and legal records;
comply with applicable law.

This licence does not transfer ownership of the Project Materials to MekaVerse NFT.

10. Metadata and public records

The Client must review and approve metadata intended for a public blockchain, decentralised storage system, NFT marketplace, catalogue page or verification record.

The Client acknowledges that:

public blockchain information may be permanent;
decentralised records may be difficult or impossible to delete;
third parties may copy or index public metadata;
changes may require a replacement record or clarifying update;
personal or confidential information should be minimised;
token metadata does not automatically prove legal ownership.

The Client must not approve confidential source files, private personal information or commercially sensitive material for public blockchain publication unless that publication is intentional and lawful.

11. Blockchain networks and wallets

The selected blockchain network, token standard, wallet requirements and transaction method will be stated or approved during the Project.

The Client is responsible for checking public wallet addresses and maintaining control of its wallet credentials.

MekaVerse NFT will not request the Client’s private key, recovery phrase or wallet password.

The Client accepts risks including:

irreversible blockchain transactions;
incorrect wallet addresses;
network congestion and variable transaction fees;
protocol updates, forks or discontinued standards;
wallet incompatibility;
third-party contract or infrastructure failures;
loss of access caused by compromised credentials.

12. Fees and payment

The Client must pay the fees stated in the accepted quotation or Project Documents.

Fees may include:

a non-refundable initial assessment or reservation fee;
a deposit before work begins;
milestone payments;
a final payment before delivery or publication;
blockchain network costs;
third-party platform or infrastructure costs;
fees for approved additional work.

Unless expressly included, network fees, taxes and third-party charges are separate from the MekaVerse NFT service fee.

Work may be paused where an invoice remains overdue.

13. Project stages and delivery

A Project may be divided into assessment, architecture, metadata, technical preparation, review and delivery stages.

Stage	Typical activity	Typical output
Project intake	Reviewing the Asset, Client and intended utility.	Project summary and information requirements.
Verification design	Mapping hashes, identifiers, records and declarations.	Verification architecture.
Metadata planning	Structuring asset, utility, rights and limitation fields.	Metadata draft.
Technical preparation	Preparing token identity, references and network scope.	Generation-ready structure.
Delivery	Providing approved records and documentation.	Final agreed Deliverables.

Any delivery date is dependent on timely Client cooperation, third-party availability and blockchain network conditions.

14. Client review and acceptance

The Client must review drafts and Deliverables within the review period stated in the Project Documents or, where no period is stated, within a reasonable period.

Feedback must identify specific errors, omissions or requested changes within the approved Project Scope.

A Deliverable may be treated as accepted when:

the Client provides written approval;
the Client instructs MekaVerse NFT to publish or use it;
the Client begins using the Deliverable operationally;
the review period expires without a material objection.

Acceptance does not remove the Client’s responsibility for approved public metadata or supplied declarations.

15. Revisions and scope changes

The Project Scope may include a specified number of revision rounds.

A revision means a reasonable adjustment to work already included in the approved scope. It does not include a new Asset, new utility, different blockchain architecture or complete redesign.

A scope change may arise when the Client requests:

additional NFT records or token variants;
a new blockchain network;
new metadata categories;
new licensing or access functionality;
additional QR, NFC or physical integration work;
substantial changes after approval;
urgent or accelerated delivery.

Additional work may require a revised quotation, new payment and updated delivery stages.

16. Delays and Client dependencies

MekaVerse NFT is not responsible for delay caused by:

late Client information or approvals;
incomplete or contradictory Project Materials;
changes requested by the Client;
delayed payment;
third-party service unavailability;
blockchain congestion or network interruption;
legal, ownership or compliance concerns requiring review.

Where the Client becomes inactive for an extended period, MekaVerse NFT may archive the Project and require a restart fee or revised schedule before work resumes.

17. Third-party services

A Project may depend on independent blockchain networks, wallets, storage systems, hosting providers, marketplaces, explorers, payment services or hardware suppliers.

Third-party services are governed by their own terms and may change or discontinue features without MekaVerse NFT’s control.

MekaVerse NFT does not guarantee:

continuous third-party availability;
marketplace approval or listing;
continued support for a token standard;
permanent storage by an independent provider;
specific transaction confirmation times;
third-party security or regulatory compliance.

18. Confidentiality

Each party must protect confidential information received from the other party and use it only for the Project.

Confidential information does not include information that:

is publicly available without breach of this Agreement;
was already lawfully known to the receiving party;
is lawfully received from an independent third party;
is independently developed without using confidential information;
must be disclosed under law or a valid authority request.

Public blockchain metadata and information expressly approved for publication are not confidential after publication.

19. Data protection

Each party must comply with applicable data protection requirements when processing personal information for the Project.

The Client must not provide unnecessary personal information for publication in NFT metadata or blockchain records.

Where the Client provides personal information relating to another person, the Client confirms that it has an appropriate lawful basis and has provided any required privacy information.

Additional information about MekaVerse NFT’s processing practices is available in the Privacy Policy.

20. Intellectual property in deliverables

20.1 Client materials

The Client retains ownership of intellectual-property rights it lawfully holds in the original Project Materials.

20.2 MekaVerse NFT materials

MekaVerse NFT retains ownership of its pre-existing methods, templates, systems, design elements, documentation formats, know-how and reusable technical components.

20.3 Project-specific deliverables

Rights in custom Deliverables will be allocated as stated in the Project Documents. Where no express transfer is agreed, the Client receives a non-exclusive licence to use the paid Deliverables for the approved Project purpose.

20.4 Token ownership

Control of an NFT does not automatically transfer copyright, trademark rights, design rights, commercial licences or ownership of a related physical product.

21. Portfolio and publicity

MekaVerse NFT will not publish confidential Project Materials as a case study without permission.

Where the Project, NFT record or verification page is already public, MekaVerse NFT may refer to publicly available information solely to identify completed work, unless the Project Documents state otherwise.

Use of the Client’s trade name, trademark or unpublished materials for promotional purposes requires appropriate permission.

22. Service warranties

MekaVerse NFT will perform the Services with reasonable care and skill consistent with the accepted Project Scope.

MekaVerse NFT does not warrant that:

the NFT will acquire or retain financial value;
the NFT will be accepted by every wallet or marketplace;
third-party networks will remain unchanged;
the Client’s legal ownership claims are valid;
a blockchain record will be accepted as legal title;
a physical item is authentic without additional verification;
the Project will satisfy undisclosed Client requirements.

23. Disclaimers and risk allocation

NFT and blockchain projects involve technical, legal, operational and market risks.

The Client is responsible for deciding whether the proposed NFT utility, blockchain network and publication model are suitable for its objectives.

MekaVerse NFT does not provide investment recommendations and does not guarantee liquidity, market demand, price stability or return on expenditure.

Additional risks are described in the NFT and Blockchain Risk Disclosure .

24. Limitation of liability

Nothing in this Agreement excludes liability that cannot lawfully be excluded, including liability for fraud or another matter that applicable law prevents the parties from limiting.

Subject to that restriction, MekaVerse NFT will not be liable for indirect, consequential or special loss, including:

lost profit, revenue or opportunity;
loss of anticipated token value;
loss caused by compromised wallets or credentials;
incorrect or irreversible blockchain transactions;
third-party platform or network failures;
loss resulting from inaccurate Client information;
unauthorised copying of public metadata;
marketplace rejection or delisting.

Where liability may legally be limited, MekaVerse NFT’s total aggregate liability arising from a Project will not exceed the amount paid to MekaVerse NFT for the part of the Services giving rise to the claim.

25. Indemnification

To the extent permitted by law, a business Client will indemnify MekaVerse NFT against reasonable claims, losses and costs arising from:

infringing or unlawfully submitted Project Materials;
false creator, ownership or issuer declarations;
the Client’s breach of this Agreement;
unlawful NFT utility, licensing or redemption promises;
the Client’s misuse of Deliverables;
failure to obtain required permissions or consents.

This indemnity does not apply to the extent a claim was caused by MekaVerse NFT’s own unlawful conduct or breach.

26. Suspension and termination

MekaVerse NFT may suspend or terminate the Project where:

required fees remain unpaid;
the Client materially breaches this Agreement;
the Client supplies unlawful or misleading materials;
essential Client information is not provided;
continuing would create material legal or security risk;
the Client requests prohibited or deceptive activity;
the Client becomes insolvent or ceases business;
continuation becomes impossible due to external circumstances.

The Client may request termination by contacting MekaVerse NFT. Refunds and remaining fees will be determined under the completed work, committed costs, Project Documents and Refund Policy.

27. Consequences of termination

Following termination:

the Client must pay fees due for completed work;
non-refundable third-party costs remain payable;
unfinished Deliverables may be withheld where payment remains due;
each party should return or delete confidential information where appropriate;
public blockchain records already created may remain available;
provisions intended to survive termination will continue.

Termination does not reverse an irreversible blockchain transaction or remove information from an independent network.

28. Force majeure

Neither party is responsible for delay or failure caused by events outside its reasonable control.

Such events may include:

internet, hosting or infrastructure outages;
blockchain network failures or protocol incidents;
cyberattacks not caused by the affected party’s negligence;
government restrictions or legal changes;
natural disasters, war or civil disturbance;
failure of critical third-party suppliers;
industrial action or widespread utility failure.

The affected party should notify the other party where reasonably possible and take reasonable steps to reduce the effect.

29. General terms

29.1 Entire agreement

The Agreement contains the complete agreement regarding the accepted Project and replaces earlier discussions relating to the same scope.

29.2 Assignment

The Client may not assign the Agreement without written consent. MekaVerse NFT may use qualified subcontractors while remaining responsible for its contractual obligations.

29.3 Severability

If a provision is unenforceable, the remaining provisions continue to apply.

29.4 No waiver

Failure to enforce a provision immediately does not waive the right to enforce it later.

29.5 Electronic communications

Project approvals, notices and agreements may be communicated electronically where legally permitted.

29.6 No partnership

The Agreement does not create a partnership, employment relationship, fiduciary relationship or joint venture.

30. Governing law and contact

This Agreement is governed by the laws applicable to MekaVerse NFT in the United Kingdom, subject to mandatory rights that cannot lawfully be excluded.

The parties should first attempt to resolve a dispute through good-faith written communication.

Questions about this Agreement or an active Project may be submitted through:

Contact MekaVerse NFT

Do not submit wallet private keys, recovery phrases, passwords or authentication codes.