Midcontract Terms of Service

Last Updated: February 5, 2025

1. INTRODUCTION

Welcome to Midcontract ("Platform", "we", "us", "our"), a blockchain-enabled escrow payment and contract management platform operated by Midcontract OÜ, a company registered in Estonia. These Terms of Service ("Terms") govern your access to and use of our platform, services, and features, including our website, applications, and any related content, functionality, or services offered. By accessing or using the Platform, registering an account, or clicking to accept or agree to these Terms of Service when this option is made available, you agree to comply with and be bound by these Terms. If you are using the Platform on behalf of a business or legal entity, you represent that you have the authority to accept these Terms on behalf of that entity.Please read these Terms carefully before using the Platform. These Terms incorporate by reference additional policies and agreements, including but not limited to the Payment Terms, Privacy Policy, KYC/AML Policy, and Dispute Resolution Policy. If you do not agree to these Terms or any related policies, you must not access or use the Platform.For any questions or assistance, our Support Team is available to help. You can contact us at support@midcontract.com.

2. REPRESENTATIONS AND WARRANTIES

This Platform is offered and available to users who are at least 18 years of age to form a binding contract. If you are under 18 you are not permitted to use the Platform or the Midcontract services. 

The Platform is available only to users who are not subject to any economic sanctions or trade restrictions imposed by the United States, European Union or any other applicable jurisdiction.

By accessing and using the Midcontract platform, users represent and warrant that they will not engage in any prohibited activities outlined in Section Prohibited Activities. Any violation of this provision constitutes grounds for immediate suspension or termination of the user's account.

By using the Platform, you represent and warrant that you meet all of the foregoing eligibility requirements. If you do not meet all of these requirements, you must not access or use the Site.

3. DEFINITIONS

"Platform": means Midcontract's website, applications, smart contracts, and services collectively

"Client" means any individual or entity that contracts for services through the Platform

"Agency" means an organization representing one or more freelancers, operating as a single contractor entity.

"Freelancer": An independent contractor providing services through the Platform

"Agency": An organization representing one or more Freelancers

"Contractor" means either:

  • An individual freelancer, or
  • An agency providing services through the Platform under an agreed contract

"Smart Contract" means self-executing contracts with terms directly written into code deployed on the Polygon blockchain

"Blockchain Transaction": means any operation recorded on the Polygon blockchain related to Platform activities

"Wallet": A digital wallet for cryptocurrency transactions

“Supported Cryptocurrencies”: USDT, USDC, DAI (operating on the Polygon blockchain)

"Embedded Wallet": A wallet integrated into the Platform, powered by Alchemy, for seamless transactions

"External Wallet": A cryptocurrency wallet owned and managed independently by the user (e.g., MetaMask)

"On-Ramp/Off-Ramp": Services that enable users to convert fiat currency to cryptocurrency (on-ramp) or cryptocurrency to fiat (off-ramp)

"Hourly Rate": The agreed-upon payment amount per hour for services provided in an hourly contract

"Weekly Limit": The maximum number of hours a freelancer can log and be compensated for within a week

"Escrow": means funds held in smart contracts until specified conditions are met

"Platform Fee": means the percentage fee charged by Midcontract for provided services

"Gas Fee": means the computational cost required to perform transactions on the Polygon network

"Contract": A binding agreement between a Client and a Freelancer/Agency outlining the terms of service, payment, and deliverables

"Contract Value" means the total agreed payment amount for services, excluding fees

“Escrow Return Request”: A formal request initiated by the client to recover escrowed funds when contract deliverables remain unfulfilled or do not meet specifications

“Dispute”: A formal disagreement raised by either party regarding contract terms, deliverables, or payments

“Dispute Manager”: A representative responsible for overseeing dispute processes and making final determinations

“Manual Review”: A verification process where submissions flagged for further inspection are manually reviewed by Midcontract’s legal specialists

“Evidence Submission”: Supporting documentation or proof provided by parties during a dispute, including screenshots, files, or correspondence

“Prepayment”: An advance payment for hourly contracts subject to potential return requests

“Resolved’ Status”: A contract status update indicating the conclusion of a dispute or return request

“Withdrawn’ After Dispute”: A status indicating partial funds were released after dispute settlement

4. USER ROLES AND RESPONSIBILITIES

Clients, freelancers, and agencies agree to comply with all applicable laws and regulations and refrain from activities detailed in Section Prohibited Activities. Users are responsible for ensuring their actions do not breach the rules on prohibited activities and may face penalties for non-compliance, including suspension of services and legal action.

4.1 Clients
  • Must be at least 18 years old and legally able to enter into contracts
  • Responsible for:
    • Providing accurate project requirements
    • Funding escrow accounts before work begins
    • Reviewing and approving deliverables within specified timeframes
    • Maintaining confidentiality of project information
    • Completing KYC/AML verification as required
    • Ensuring their profile details, such as email addresses and wallet information, are accurate and up-to-date to avoid service interruptions
4.2 Freelancers
  • Must be at least 18 years old and legally able to provide services
  • Responsible for:
    • Delivering services as specified in Contracts
    • Maintaining professional standards and meeting deadlines
    • Protecting client confidential information
    • Completing KYC/AML verification
    • Accurately representing skills and experience
    • Ensuring their profile details, such as email addresses and wallet information, are accurate and up-to-date to avoid service interruptions
4.3 Agencies
  • Individual or organization representing one or more Freelancers
  • Responsible for:
    • Managing contracts on behalf of associated Freelancers
    • Delivering services as specified in Contracts
    • Maintaining professional standards and meeting deadlines
    • Protecting client confidential information
    • Completing KYC/AML verification
    • Accurately representing skills and experience of their team
    • Managing communication with Clients
    • Ensuring fair distribution of payments to associated Freelancers
    • Maintaining transparency with associated Freelancers regarding contract terms
    • Ensuring their profile details, such as email addresses and wallet information, are accurate and up-to-date to avoid service interruptions

5. CONTRACT TYPES AND PROCESSES

5.1 Fixed-Price Contracts
5.1.1 Contract Creation and Modification

Initial Setup:

  • Either the client or contractor (freelancer/agency) can initiate the creation of a fixed-price contract.
  • The contract requires both parties to be registered, logged in, and KYC/AML-verified.
  • Initial terms include:
    • Project name and description
    • Total agreed payment amount
    • Delivery deadline (optional)
    • Payment structure: single payment or by milestones

Modification Process:

  • Parties may request updates to contract terms before it is accepted.
  • Changes after activation require mutual agreement and an update request via the platform.
5.1.2 Prepayment and Deposit Requirements
  • Fixed-Price Contracts:
    • The full payment amount must be deposited into the escrow account before work begins.
  • Milestone-Based Contracts:
    • The first milestone's payment must be deposited before work begins.
    • Subsequent milestone payments are deposited and approved incrementally.
5.1.3 Submission and Approval Process

Work Submission:

  • Contractors submit completed work or deliverables via the platform.
  • Contractors may attach relevant files as links and descriptions.
  • The system logs the submission in the activity history for transparency.

Approval Process:

  • Clients have a review period (default: 5 days) to approve or request changes to the submitted work.
  • If no action is taken within the review period, the system automatically approves the work.

Request for Changes:

  • Clients may request revisions, specifying the necessary changes.
  • Contractors must address feedback and resubmit work within the agreed timeframe.
5.1.4 Payment and Notifications

Approved Work:

  • Upon approval, funds in the escrow account are unlocked and made available for the contractor to claim and withdraw via their connected wallet.
  • The system sends payment confirmation notifications to both parties once the funds are unlocked.

Rejected Work or Revisions:

  • The contract status remains active while revisions are in progress.
  • Notifications inform both parties of requested changes and submission updates.

Auto-Approval Notifications:

  • In-app notifications are sent 3 days, 1 day before, and on the due date to remind users about pending approval.
5.1.5 Contract Status Updates and Completion
  • Contracts move to "Completed" status after:
    • The client approves the final milestone.
    • The platform confirms payment transfers.
  • Both parties receive notifications when a contract is marked as completed and archived.
5.2 Milestone-Based Contracts

Note: The key processes for milestone-based contracts align with those for fixed-price contracts, but with the following specific considerations for milestones:

5.2.1 Key Features of Milestone-Based Contracts:
  1. Individual Milestone Payments:
    • Each milestone’s payment must be deposited into escrow separately before work on that milestone begins.
    • Funds are unlocked and made available for the contractor to claim and withdraw upon approval.
  2. Sequential or Parallel Completion:
    • Milestones can be completed sequentially (one after the other) or in parallel (multiple milestones worked on simultaneously), depending on the agreed project terms.
  3. Deliverables:
    • Contractors submit deliverables through the platform, specifying the associated milestone.
  4. Approval and Auto-Approval Process:
    • Clients have 5 days to review and approve or request changes after submission.
    • If no client action is taken within this period, the system automatically approves the milestone.
    • Once auto-approved, funds are unlocked for the contractor to claim.
  5. Auto-Approval Notifications:
    • In-app notifications are sent 3 days, 1 day before, and on the due date to remind users about pending approval.
5.3 Hourly Contracts
5.3.1 Contract Creation and Modification

Initial Setup

  • Both the client and contractor (freelancer/ agency) can initiate the hourly contract creation process
  • The contract requires both parties to be registered, logged in, and KYC/AML-verified
  • Initial terms include:
    • Hourly rate
    • Maximum weekly hours limit (optional)
    • Prepayment amount (optional)

Rate Modifications

  • Contractor Rate Adjustments:
    • Contractors may only decrease their hourly rate
    • Rate decreases will take effect from the beginning of the next calendar week (Monday, 00:00 UTC)
    • Contractors cannot increase their rates
  • Client Rate Adjustments:
    • Clients may only increase the contractor's hourly rate
    • Rate increases take effect immediately upon implementation
    • Clients cannot decrease rates

Weekly Limit Modifications

  • Only clients have the authority to modify the maximum weekly hours limit
  • Weekly limit increases take effect immediately upon implementation
  • Weekly limit decreases take effect from the beginning of the next calendar week (Monday, 00:00 UTC)
5.3.2 Time Tracking and Approval Process

Timesheet Submission

  • Contractors record their working hours and relevant notes in the timesheet
  • System automatically locks timesheet editing at 00:00 UTC on the first day of the following calendar week
  • Locked timesheets are automatically submitted for client review

Approval Process

  • Clients have 3 days to review and approve/reject submitted timesheets
  • Auto-approval occurs if no action is taken within the 3-day review period
5.3.3 Payment and Prepayment Management

Prepayment Enabled Contracts

  • System automatically processes payment when sufficient prepaid funds are available
  • Both parties receive payment confirmation notifications

Insufficient Prepayment Handling

  • Contract status changes to "On Hold" when available balance is insufficient
  • System alerts client to refill prepayment
  • Contract remains on hold until sufficient funds are deposited

No Prepayment Contracts

  • Contract status remains "On Hold" until client deposits initial funds
  • System requires payment of any pending timesheets before contract reactivation
5.3.4 Notification System

Review Period Notifications

  • Upon timesheet auto-submission: Both client and contractor receive notification that the timesheet is locked, submitted, and ready for review and payment
  • Upon auto-approval: Both parties receive confirmation notification

Payment Notifications

  • Insufficient funds alert sent to client
  • Prepayment successful confirmation to both parties
  • Contract status change notifications
5.3.5 Contract Reactivation
  • Clients may deposit additional funds at any time
  • System presents modal for pending timesheet payment
  • Contract status updates to active upon sufficient fund deposit

6. MIDCONTRACT KYC/AML POLICY

This Know Your Customer (KYC) and Anti-Money Laundering (AML) Policy outlines the procedures and requirements Midcontract OÜ implements to prevent financial crime, ensure regulatory compliance, and maintain platform integrity. 
All users must undergo basic verification, which includes ID verification, liveness checks, and face-to-document matching using Identomat.

6.1 Regulatory Framework
  • Midcontract operates under:
    • Estonian Money Laundering and Terrorist Financing Prevention Act
    • EU Anti-Money Laundering Directives (AMLD)
    • Financial Action Task Force (FATF) Recommendations
    • Applicable international sanctions and regulations
6.2 Verification Levels
6.2.1 Basic Verification (All Users)
    • ID verification (via Identomat)
    • Liveness check
    • Face-to-document matching
6.3 Verification Procedures
6.3.1 Identity Verification through Identomat 
  • Midcontract partners with Identomat for secure and compliant KYC processes.Verification Flow:
    • User Initiation:
      • Redirect to Identomat's secure verification interface
      • Mobile and desktop support
      • Multi-language verification process
    • Document Verification:
      • AI-powered document authenticity checks
      • Support for international ID documents
      • Real-time validation
    • Biometric Verification:
      • Liveness detection
      • Facial matching with ID
      • Anti-spoofing measures
    • Verification Results:
      • Real-time verification status updates (approved/rejected)
      • For cases requiring manual review, Identomat sends a "Manual Check" status, and Midcontract's legal specialist reviews and makes the final approval or rejection decision.
6.4 Manual Verification Process
6.4.1 Additional Verification Steps:
  • Midcontract's legal specialist may request additional information if needed.
  • The review process includes checking submitted documents for accuracy and ensuring compliance with regulatory standards.
  • The legal specialist verifies that documents meet Estonian regulatory guidelines and EU AMLD requirements.
  • Identified discrepancies or missing information will be communicated promptly to the user.
  • Manual review decisions are logged for auditing and compliance reporting.
  • Users will receive notifications if manual review is initiated, including instructions for further steps.
6.5 Profile Update After Verification
  • Upon successful verification, user profiles are updated with verified information such as full legal name and verification status.
  • Verification statuses include: "Unverified," "In Review," "Verified," "Rejected."
6.6 User Responsibilities
6.6.1 Information Updates:
  • Users must notify Midcontract of changes to their legal name, address, or other relevant information.
  • Prompt updates ensure uninterrupted use of the platform.
6.6.2 Cooperation Requirements:
  • Timely response to verification requests.
  • Submission of accurate and clear documentation.
  • Compliance with requests for additional information.
6.7 Data Processing and Storage
6.7.1 Secure Data Handling:
  • Encrypted data transmission and storage.
  • Limited retention periods.
  • Data minimization principles in line with GDPR.
6.7.2 Retention Policy:
  • Verification records are retained only as long as necessary for compliance.
  • Data is deleted within 30 days of expiration unless required for regulatory purposes.
6.8. Compliance and Oversight
6.8.1 Responsibilities of Midcontract:
  • Ensure compliance with KYC/AML regulations.
  • Conduct periodic reviews of verification processes.
  • Address user queries related to identity verification.
6.8.2 Reporting:
  • Reporting of suspicious activity to relevant regulatory authorities.
  • Cooperation with law enforcement if required.
6.9 User Obligations
  • Users must maintain up-to-date identification records.
  • Cooperation during manual review is mandatory.
  • Users with expired documents cannot initiate new contracts but may complete active ones.
6.10 Policy Updates
  • Midcontract reserves the right to update this policy to reflect regulatory changes.
  • Users will be notified of any significant updates.
6.11 Contact Information
  • For any questions regarding this policy or verification procedures, users can contact our compliance team:
  • Money Laundering Reporting Officer (MLRO):
    • Email: compliance@midcontract.com

7. MIDCONTRACT PAYMENT TERMS

These Payment Terms govern all payment processes, fees, and escrow services on Midcontract. By using Midcontract, users agree to comply with these terms in conjunction with the Terms of Service.
7.1 ESCROW SERVICES AND CONTRACT STRUCTURE
7.1.1 Smart Contract Architecture
  1. Template-Based Contracts:
    • Each contract type (Fixed Price, Milestones, Hourly) operates through a dedicated smart contract template
    • Individual client contracts are derived from these templates
    • Each client receives a unique blockchain address for each contract type
    • Multiple contractors can be engaged under the same client's smart-contract address
  2. Wallet Management:
    • Contractors may use different wallet addresses for each contract
    • Clients may maintain separate wallets for different contract types
    • Wallet addresses can be updated through support in case of security concerns
    • Support verification is required for wallet address changes
7.1.2 Fund Deposit and Holding
  1. Deposit Requirements:
    • Clients must deposit funds before work commencement
    • Deposits are held in contract-specific smart contracts
    • No interest accrues on deposited funds
    • Real-time blockchain confirmation is required
  2. Release Conditions:
    • Funds release upon client approval or automatically in case of client’s inactivity
      • Default review periods:
        1. Fixed-price contracts: 5 days
        2. Milestone-based contracts: 5 days
        3. Hourly contracts: 3 days
      • All the details are in 5. CONTRACT TYPES AND PROCESSES
7.2 PAYMENT METHODS AND PROCESSING
7.2.1 Supported Currencies
  1. All contract values are calculated and displayed in United States Dollars (USD)
  2. Payments are processed exclusively in stablecoins:
    • USDT (Tether)
    • USDC (USD Coin)
    • DAI
  3. All stablecoins maintain 1:1 parity with USD
7.2.2 Wallet Options
  1. Embedded Wallets:
    • Provided through Midcontract's Alchemy integration
    • Platform covers gas fees
    • Simplified user experience
    • Users can export their embedded wallet from the platform for further usage by using their secret phrase
  2. External Wallets:
    • Support for MetaMask and other compatible wallets
    • Users responsible for gas fees
    • Advanced control options
  3. Fiat Conversion Services:
    • Integrated Transak services for fiat-to-crypto conversion
    • Available for both deposits and withdrawals
    • Subject to Transak's terms and fees
    • Fiat-to-crypto transactions facilitated by Transak are subject to Transak’s terms and fees. Midcontract is not liable for third-party service issues.
7.3 PLATFORM FEES
7.3.1 Client Fees
  1. The Platform charges a service fee of 1.9% ("Client Fee") in addition to the contract value
  2. The Client Fee is:
    • Calculated and added at the time of payment
    • Applied on top of the base contract value
    • Example: For a contract value of USD 100.00, the total client payment is USD 101.90
7.3.2 Contractor Fees
  1. The Platform deducts a service fee of 3.6% ("Contractor Fee") from the contract value
  2. The Contractor Fee is:
    • Automatically deducted during payment processing
    • Calculated based on the contract value
    • Example: For a contract value of USD 100.00, the contractor receives USD 96.40
7.3.3 Blockchain Gas Fees
  1. External Wallet Users:
    • Responsible for all blockchain gas fees
    • Fees determined by Polygon network conditions
    • Separate from Platform fees
  2. Platform-Embedded Wallet Users:
    • Platform covers all gas fees
    • No additional charges
    • Applies to standard platform transactions
7.3.4 Fee Adjustments
  1. The Platform reserves the right to implement promotional fee waivers
  2. Adjustments are:
    • Communicated in advance
    • Announced via email and platform notifications
    • Documented in transaction records
7.3.5 Dispute Resolution Fee Returns
  • In case of client victory:
    • Client Fee returned in full
    • Contractor Fee retained by platform
  • In case of contractor victory:
    • Client Fee retained by platform
    • Contractor Fee remains deducted
  • For split decisions:
    • Fees returned proportionally to the dispute resolution outcome
    • Return calculations based on the percentage awarded to each party
7.4 PAYMENT RECORDS AND DOCUMENTATION
7.4.1 Transaction Records
  1. Blockchain recording of:
    • Calculation of applicable fees
    • Fund transfers
    • Approval of token amounts
    • Escrow deposit transactions, including prepayments
    • Submission of completed work by the contractor
    • Approval of work or timesheets by the client
    • Automatic approvals triggered by system rules
    • Refill of deposit or prepayment balance by the client
    • Earnings claims submitted by the contractor
    • Withdrawal of escrow funds following an approved escrow return request
    • Creation of an escrow return request
    • Approval of an escrow return request
    • Cancellation of an escrow return request
    • Creation of a dispute
    • Resolution of a dispute
    • Deployment of a smart contract
  2. User Access:
    • Transaction details in Payments section
    • Complete fee breakdowns
    • Historical record access
7.4.2 Invoicing
  1. Available Documentation:
    • Viewable and downloadable invoices
    • PDF and CSV formats
    • Automatic generation upon completion
    • Accessible through user dashboard
7.5 MODIFICATIONS AND UPDATES

Midcontract reserves the right to modify these Payment Terms. Users will be notified of significant changes, and continued platform use constitutes acceptance of revised terms.For support contact: support@midcontract.com

8. ESCROW RETURN REQUEST AND DISPUTE MANAGEMENT

This section governs the procedures for managing Escrow Return Requests and disputes across all contract types on the Midcontract platform. These provisions ensure transparent and equitable resolution of contractual disagreements.

8.1 Escrow Return Request Process
8.1.1 Eligibility and Initiation
  • Clients may initiate an Escrow Return Request under the following conditions:
    • Undelivered work in fixed-price contracts.
    • Incomplete milestone deliverables (including partial refunds).
    • Unutilized prepayment in hourly contracts.
    • Unsatisfactory contract performance.
  • Validation checks ensure no conflicting active return requests exist for the same contract or milestone.
8.1.2 Request Statuses
  • New: Pending contractor response.
  • Approved: Request accepted, funds available for withdrawal.
  • Disputed: Request contested by contractor.
  • Canceled: Request withdrawn by client.
  • Withdrawn After Dispute: Funds partially released following dispute resolution.
  • Resolved: Indicates completion of return or dispute process.
8.2 Response Timeline and Options
8.2.1 Contractor Response Period
  • Contractors must respond within 7 calendar days of request submission through one of the following actions:
    • Approve the request, releasing funds to the client.
    • Open a formal dispute with substantiated justification.
  • Auto-Approval:
    • If no contractor response is received within 7 days:
      • The system automatically approves the request.
      • Funds become available for client withdrawal.
      • Both parties receive notification of auto-approval.
8.2.2 Automated Reminders
  • 3 days before the deadline: In-app and email reminders sent to the contractor.
  • 1 day before the deadline: Final reminder notification sent.
  • On the due date: System sends a final notice.
8.3 Dispute Resolution Framework
8.3.1 Dispute Initiation Rights
  • Contractors may file disputes for:
    • Disagreement with Escrow Return Requests.
    • Unjustified change requests.
    • Contract term violations.
  • Clients may file disputes for:
    • Inaccurate hourly logs.
    • Deviation from agreed contract terms.
    • Unsatisfactory deliverables.
8.3.2 Resolution Process
  • Initial Review:
    • Midcontract's dispute team examines submitted documentation.
  • Investigation Period:
    • Maximum 2 business days for standard resolution.
    • Additional information may be requested.
    • Mediation services provided if necessary.
    • A chat will be created in the support platform (based on ZenDesk) that includes all parties and Midcontract's dispute manager for clear communication.
    • The dispute manager will request all necessary details and provide periodic updates.
  • User Responsibilities During Evidence Submission:
    • Submit clear and accurate documentation supporting their claims (e.g., messages, timestamps, submitted deliverables).
    • Respond to requests for additional information within the specified timeframes.
    • Maintain respectful communication during the dispute process.
    • Ensure all evidence is provided in supported file formats and does not contain any malicious content.
  • Resolution Notification:
    • Both parties receive detailed resolution notifications, including next steps.
  • Resolution Outcomes:
    • Client Victory: Full return of disputed amount.
    • Contractor Victory: Release of disputed funds to contractor.
    • Split Decision: Proportional distribution of funds.
8.3.3 Communication During Disputes
  • A dedicated chat channel will be created within the support platform (powered by Zendesk).
  • This channel will include the client, contractor, and Midcontract's dispute manager.
  • The dispute manager will guide the process by requesting relevant details and providing periodic updates.
  • All parties will receive real-time notifications within the chat system to ensure responsiveness and transparency.
  • The final resolution and steps for fund release or withdrawal will be communicated within this chat.
8.3.4 Inclusion of Audit Logs:

All chat messages, evidence submissions, and communication records within the dispute channel will be securely logged and may be referenced in audits or regulatory checks.

8.4 Notification System
8.4.1 Mandatory Notifications
  • Request submission confirmation.
  • Response deadline reminders (3 days and 1 day prior).
  • Dispute status updates.
  • Resolution decisions.
  • Fund withdrawal confirmations.
8.4.2 Communication Channels
  • In-app notifications.
  • Email notifications.
  • Contract activity logs.
8.5 Fund Withdrawal Process
8.5.1 Withdrawal Eligibility
  • Funds become available for withdrawal upon:
    • Request approval by contractor.
    • Auto-approval after 7 days.
    • Final dispute resolution.
8.5.2 Withdrawal Execution
  • Initiated through connected wallet.
  • Transaction confirmation provided.
  • Wallet synchronization and validation before fund withdrawal.
  • Blockchain transaction record maintained.
8.6 Compliance and Enforcement
8.6.1 User Obligations
  • Adhere to specified timelines.
  • Provide accurate documentation.
  • Respond to official communications.
  • Follow dispute resolution decisions.
8.6.2 Non-Compliance Consequences
  • Account restrictions.
  • Platform access limitations.
  • Legal enforcement actions.
  • Forfeit of dispute rights.
  • Account suspension after repeated invalid disputes.
8.7 Amendments and Updates

Midcontract reserves the right to modify these terms with:

  • Prior notification to users.
  • Grace period for adaptation.
  • Preservation of ongoing dispute resolutions.
8.8 Governing Law

This policy operates under applicable contract and arbitration laws while maintaining platform-specific resolution procedures.

9. MIDCONTRACT PRIVACY POLICY

9.1 INTRODUCTION

Midcontract OÜ ("Midcontract," "we," "us," or "our"), a company registered in Estonia, is committed to protecting your privacy and ensuring the security of your personal information. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our blockchain-enabled escrow payment and contract management platform, including our website, applications, and related services (collectively, the "Platform").

9.2 KEY DEFINITIONS
  • Personal Data: Any information relating to an identified or identifiable natural person.
  • User: Any individual or entity accessing or using the Platform.
  • Platform: The Midcontract website, applications, and services.
  • Cookies: Small text files placed on your device to collect and store information about your browsing preferences.
  • Smart Contract: Blockchain-based automated agreements managing escrow and payments.
9.3 DATA CONTROLLER

Midcontract OÜ [Address] Estonia

Email: privacy@midcontract.com

9.4 INFORMATION WE COLLECT
9.4.1 Information You Provide
  • Account Information:
    • Email address
    • Password (encrypted)
    • Username
    • Profile information
  • Identity Verification Information (processed and stored by Identomat):
    • Full name
    • Date of birth
    • Identification document type
    • Document expiration date
    • Verification status and timestamps
    • Address (manually provided)
  • Contract-Related Information:
    • Contract details and specifications
    • Project descriptions
    • Payment information
    • Communication records
    • Wallet addresses
9.4.2 Information Automatically Collected
  • Usage Data:
    • IP address
    • Browser type
    • Device information
    • Operating system
    • Access times and dates
    • Pages viewed
    • Links clicked
    • Navigation patterns
  • Blockchain Information:
    • Public wallet addresses
    • Transaction records
    • Smart contract interactions
9.4.3 Cookies and Similar Technologies

See our Cookie Policy section below for detailed information about our use of cookies and similar technologies.

9.5 HOW WE USE YOUR INFORMATION

We use your information for the following purposes:

9.5.1 Essential Operations
  • Providing and maintaining the Platform
  • Processing transactions and payments
  • Managing user accounts
  • Facilitating contract creation and management
  • Ensuring compliance with KYC/AML requirements
  • Preventing fraud and maintaining security
9.5.2 Communication
  • Sending service-related notifications
  • Providing customer support
  • Sending updates about platform changes
  • Responding to your inquiries
9.5.3 Platform Improvement
  • Analyzing usage patterns
  • Improving user experience
  • Developing new features
  • Troubleshooting technical issues
9.5.4 Legal Compliance
  • Meeting regulatory requirements
  • Responding to legal requests
  • Enforcing our terms of service
  • Protecting our legal rights
9.6 LEGAL BASIS FOR PROCESSING

We process your personal data under the following legal bases:

  • Contract Performance: Processing necessary for the performance of our contract with you
  • Legal Obligation: Processing required to comply with our legal obligations
  • Legitimate Interests: Processing necessary for our legitimate interests
  • Consent: Processing based on your specific consent
9.7. DATA SHARING AND DISCLOSURE
9.7.1 Third-Party Service Providers

We share data with trusted service providers:

  • Identomat: For KYC verification services
  • Alchemy: For wallet services
  • Transak: For fiat-to-crypto conversion
  • Cookiebot: For cookie consent management
  • Cloud service providers: For hosting and storage
  • Analytics providers: For platform improvement
9.7.2 Legal Requirements

We may disclose information:

  • To comply with legal obligations
  • To protect our rights and property
  • To prevent fraud or illegal activities
  • In response to valid legal requests
9.8 DATA RETENTION

We retain your personal data for as long as necessary to:

  • Provide our services
  • Comply with legal obligations
  • Resolve disputes
  • Enforce our agreements

Specific retention periods:

  • Account information: While account is active plus 5 years
  • Transaction records: 7 years
  • Communication records: 3 years
  • Technical logs: 12 months
9.9 DATA SECURITY

We implement appropriate technical and organizational measures to protect your data:

  • Encryption of data in transit and at rest
  • Access controls and authentication
  • Regular security assessments
  • Employee training
  • Incident response procedures
9.10 YOUR RIGHTS

Under applicable data protection laws, you have the following rights:

  • Right to access your personal data
  • Right to rectification of inaccurate data
  • Right to erasure ("right to be forgotten")
  • Right to restrict processing
  • Right to data portability
  • Right to object to processing
  • Right to withdraw consent
  • Right to lodge a complaint with a supervisory authority

To exercise these rights, contact us at privacy@midcontract.com.

9.11 INTERNATIONAL DATA TRANSFERS

We may transfer your data to countries outside the European Economic Area (EEA). When we do, we ensure appropriate safeguards are in place through:

  • Standard contractual clauses
  • Adequacy decisions
  • Other legally approved mechanisms
9.12 CHILDREN'S PRIVACY

Our Platform is not intended for children under 18. We do not knowingly collect or maintain information from persons under 18 years of age.

9.13 DATA SUBJECT RIGHTS PROCEDURES
9.13.1 Data Subject Access Requests (DSAR)
  1. Request Submission:
    • Email to privacy@midcontract.com
    • Web form submission
    • Written request to registered address
    • Required identification verification
  2. Response Timeline:
    • Initial acknowledgment: 3 business days
    • Full response: Within 30 calendar days
    • Extension if needed: Additional 60 days with notification
  3. Information Provided:
    • Data categories held
    • Processing purposes
    • Recipients of data
    • Retention periods
    • Source of data
    • Automated decision-making details
9.13.2 Specific Data Retention Periods

Data Retention Periods:

  • Account Data: Active + 5 years (Legal obligation)
  • KYC Documents: 5 years from verification (AML regulations)
  • Transaction Records: 7 years (Tax/accounting requirements)
  • Communication Logs: 3 years (Contract disputes)
  • Login History: 12 months (Security monitoring)
  • Support Tickets: 3 years (Service improvement)
  • Failed Login Attempts: 90 days (Security monitoring)

9.13.3 Cross-Border Data Transfers
  1. Transfer Mechanisms:
    • EU Standard Contractual Clauses (SCCs)
    • Adequacy decisions
    • Binding Corporate Rules where applicable
  2. Transfer Safeguards:
    • Data encryption in transit
    • Access controls
    • Data minimization
    • Regular security assessments
10.1 ABOUT COOKIES

Cookies are small text files stored on your device when you visit our website. We use Cookiebot to manage cookie consent and provide transparency about our cookie usage.

10.2 TYPES OF COOKIES WE USE
10.2.1 Necessary Cookies
  • Essential for basic platform functionality
  • Cannot be rejected
  • Typically expire when you close your browser
10.2.2 Preference Cookies
  • Remember your settings and preferences
  • Improve your browsing experience
  • Can be rejected through cookie settings
10.2.3 Statistics Cookies
  • Help us understand how visitors use our Platform
  • Collect anonymous analytics data
  • Can be rejected through cookie settings
10.2.4 Marketing Cookies
  • Track your browsing habits
  • Enable targeted advertising
  • Can be rejected through cookie settings
10.3 COOKIE MANAGEMENT

You can manage your cookie preferences through:

  • Our cookie consent banner (powered by Cookiebot)
  • Your browser settings
  • Cookiebot's consent management platform
10.4 THIRD-PARTY COOKIES

Third-party services we use may set their own cookies:

  • Analytics services
  • Payment processors
  • Social media plugins
  • Marketing tools
10.5 UPDATES TO THIS POLICY

We may update this Privacy Policy and Cookie Policy at any time. We will notify you of any material changes by:

  • Posting the updated policy on our Platform
  • Sending an email notification
  • Displaying a prominent notice on our Platform
10.6 CONTACT US

For questions about this Privacy Policy or Cookie Policy, contact us at:

Email: privacy@midcontract.com

Data Protection Officer: dpo@midcontract.com

Effective Date: February 8, 2025

11. MIDCONTRACT INTELLECTUAL PROPERTY FRAMEWORK

11.1 DEFINITIONS
11.1.1 Intellectual Property

"Intellectual Property" includes but is not limited to:

  • Copyrights and copyrightable works
  • Patents and patentable inventions
  • Trademarks and service marks
  • Trade secrets and confidential information
  • Database rights
  • Design rights
  • Source code and object code
  • Documentation and specifications
  • Know-how and methodologies
  • All related rights worldwide
11.1.2 Work Product

"Work Product" means all deliverables, developments, inventions, innovations, improvements, modifications, discoveries, designs, processes, or other materials created by Contractor under a Contract, including:

  • Custom software and code
  • Designs and artwork
  • Written content and documentation
  • Data and databases
  • Audio/visual materials
  • All intermediate and final versions
  • Related intellectual property rights
11.1.3 Pre-Existing IP

"Pre-Existing IP" means any Intellectual Property:

  • Owned by either party prior to Contract execution
  • Created outside the scope of Contract work
  • Licensed from third parties
  • Independently developed without use of the other party's IP
11.2 OWNERSHIP AND TRANSFER
11.2.1 Work Product Ownership

11.2.1.1 Default Ownership

  • All Work Product created under a Contract is deemed "work-made-for-hire" where applicable
  • Client owns all right, title, and interest in Work Product upon full payment
  • Ownership transfers automatically upon final payment clearance
  • Smart contract confirms transfer timing on blockchain

11.2.1.2 Contractor Obligations

Contractor agrees to:

  • Execute necessary documents to perfect Client's ownership
  • Assist with IP registration if requested
  • Provide source files and documentation
  • Waive moral rights where applicable
  • Maintain confidentiality of Work Product
11.2.2 Pre-Existing IP Rights

11.2.2.1 Retention of Rights

  • Each party retains ownership of their Pre-Existing IP
  • Contractor must declare Pre-Existing IP before Contract start
  • Client's Pre-Existing IP remains Client's exclusive property

11.2.2.2 License Grants

  • Contractor grants Client perpetual license to Pre-Existing IP incorporated into Work Product
  • License is worldwide, non-exclusive, and royalty-free
  • Includes right to modify and create derivative works
  • Survives Contract termination
11.3 INTELLECTUAL PROPERTY WARRANTIES
11.3.1 Contractor Warranties

Contractor warrants that:

  • Work Product is original or properly licensed
  • No infringement of third-party rights
  • Full right to transfer ownership
  • No conflicting obligations
  • No open source software without approval
  • No malicious code or components
11.3.2 Client Warranties

Client warrants that:

  • Authorized to provide any Client materials
  • Client materials don't infringe third-party rights
  • Will respect Contractor's Pre-Existing IP
  • Will maintain required licenses
11.4. CONFIDENTIALITY AND TRADE SECRETS
11.4.1 Protection Requirements

Both parties must:

  • Maintain strict confidentiality
  • Implement security measures
  • Limit access to need-to-know basis
  • Return/destroy confidential materials
  • Report unauthorized disclosures
11.4.2 Trade Secret Protection

Special handling for:

  • Technical specifications
  • Business processes
  • Customer information
  • Proprietary methods
  • Development documentation
11.5. PLATFORM RIGHTS
11.5.1 Platform License

Users grant Midcontract limited license to:

  • Process and store contract materials
  • Use blockchain for ownership verification
  • Facilitate dispute resolution
  • Maintain transaction records
11.5.2 Platform IP Protection

Midcontract maintains rights to:

  • Platform features and functionality
  • Smart contract templates
  • User interface and design
  • Platform trademarks and branding
11.6 DISPUTE RESOLUTION
11.6.1 IP Dispute Process
  • Written notice requirement
  • Mandatory mediation period
  • Arbitration procedures
  • Interim relief availability
  • Cost allocation
11.6.2 Blockchain Verification
  • Smart contract audit trail
  • Ownership transfer records
  • Payment verification
  • Time-stamped documentation
11.7 COMPLIANCE AND ENFORCEMENT
11.7.1 Registration and Protection
  • IP registration assistance
  • Enforcement cooperation
  • Infringement notification
  • Blockchain verification
  • Documentation requirements
11.7.2 Violation Remedies
  • Contract termination
  • Payment withholding
  • Damage compensation
  • Injunctive relief
  • Platform access restriction
11.8 SPECIAL CIRCUMSTANCES
11.8.1 Multi-Party Projects
  • Joint ownership provisions
  • Contribution attribution
  • Decision-making authority
  • Exit procedures
  • Documentation requirements
11.8.2 Open Source Components
  • Approval requirements
  • License compatibility
  • Attribution requirements
  • Documentation needs
  • Risk assessment
11.9. TERM AND TERMINATION
11.9.1 Duration of Rights
  • Ownership transfer permanence
  • License term specifications
  • Post-termination rights
  • Survival provisions
  • Archive maintenance
11.9.2 Termination Effects
  • IP return requirements
  • Transition assistance
  • Continuing obligations
  • Blockchain record maintenance
  • Final documentation
11.10 IMPLEMENTATION AND UPDATES
11.10.1 Framework Updates
  • Change notification process
  • User acceptance requirements
  • Grandfather provisions
  • Blockchain record updates
  • Transition periods
11.10.2 Documentation Requirements
  • IP transfer records
  • License agreements
  • Assignment documents
  • Blockchain verification
  • Audit trails
11.10.3 Work-for-Hire Strengthening
  1. Explicit Assignments:
    • All intellectual property rights
    • Future exploitation rights
    • Modification rights
    • Distribution rights
  2. Documentation Requirements:
    • Assignment agreements
    • Rights transfer records
    • Copyright registrations
    • Patent applications
11.10.4 Open Source Compliance
  1. Usage Requirements:
    • Prior approval needed
    • License compatibility check
    • Documentation of components
    • Risk assessment
    • Attribution requirements
  2. Compliance Process:
    • Component review
    • License verification
    • Integration approval
    • Documentation maintenance
APPENDIX A: IP TRANSFER CHECKLIST
  1. Pre-Contract Phase
  • Pre-Existing IP declaration
  • Ownership verification
  • License documentation
  • Smart contract setup
  1. During Contract
  • Progress documentation
  • Component tracking
  • License compliance
  • Blockchain validation
  1. Completion Phase
  • Final deliverables
  • Source materials
  • Documentation transfer
  • Ownership confirmation
  1. Post-Transfer
  • Confidentiality review
  • Archive creation
  • Blockchain record finalization
  • Transfer documentation

12. ARBITRATION AND DISPUTE RESOLUTION

12.1 Binding Arbitration Agreement

By using the Platform, you agree that any dispute, claim, or controversy arising out of or relating to these Terms or the breach, termination, enforcement, interpretation, or validity thereof, shall be resolved by binding arbitration.

12.1.1 Arbitration Rules and Forum
  • Arbitration shall be administered by the Estonian Chamber of Commerce and Industry
  • The seat of arbitration shall be Tallinn, Estonia
  • The language of arbitration shall be English
  • One arbitrator shall be appointed unless the claim exceeds €100,000
  • For claims exceeding €100,000, three arbitrators shall be appointed
12.1.2 Arbitration Process
  1. Initiation:
    • Written notice of arbitration to the other party
    • Description of claim and requested relief
    • Payment of required filing fees
  2. Arbitrator Selection:
    • Parties have 15 days to jointly select arbitrator(s)
    • If no agreement, the Estonian Chamber of Commerce and Industry will appoint
  3. Proceedings:
    • Virtual hearings unless in-person hearing requested
    • Document submission electronically
    • 90-day resolution target from arbitrator appointment
12.1.3 Exceptions
  • Either party may seek emergency injunctive relief from a court
  • Small claims under €5,000 may be resolved through Estonian small claims court
  • Intellectual property disputes may be brought in courts of competent jurisdiction

13. SERVICE AVAILABILITY AND MAINTENANCE

13.1 Platform Availability
13.1.1 Uptime Commitment
  • Target uptime of 99.9% measured monthly
  • Excludes scheduled maintenance
  • Force majeure events excluded
  • Blockchain network downtime excluded
13.1.2 Scheduled Maintenance
  • Regular maintenance: Sundays 00:00-04:00 UTC
  • Notice provided:
    • 7 days for major upgrades
    • 48 hours for regular maintenance
    • Immediate notice for emergency maintenance
13.2 Service Level Agreements
13.2.1 Response Times
  • Critical issues: 1 hour response
  • High priority: 4 hours response
  • Normal priority: 24 hours response
  • Low priority: 48 hours response
13.2.2 Resolution Times
  • Critical issues: 4 hours target
  • High priority: 24 hours target
  • Normal priority: 72 hours target
  • Low priority: 5 business days target

14. LIABILITY LIMITATIONS

14.1 Blockchain Network Liability
14.1.1 Network Disclaimers

The Platform expressly disclaims liability for:

  • Polygon network congestion or failures
  • Gas fee fluctuations
  • Transaction delays or failures
  • Smart contract execution delays
  • Blockchain fork events
14.1.2 Smart Contract Limitations
  • No guarantee of smart contract security
  • Users acknowledge inherent blockchain risks
  • Platform not liable for smart contract exploits
  • Users responsible for wallet security
14.2 Third-Party Service Liability

Midcontract is not liable for disruptions, delays, or security incidents caused by third-party providers, such as Polygon, Transak, Identomat, Alchemy and The Graph.

14.2.1 Payment Services
  • Transak service interruptions
  • Fiat-crypto conversion rates
  • Payment processing delays
  • Third-party wallet service issues
14.2.2 Identity Verification
  • Identomat service disruptions
  • Verification delays
  • Document processing errors
  • Data transmission issues
14.3 User Error Liability
14.3.1 Platform Not Liable For:
  • Incorrect wallet addresses
  • Lost private keys
  • Unauthorized wallet access
  • Phishing or social engineering losses
  • User device security compromises
14.3.2 User Responsibilities:
  • Maintaining secure passwords
  • Protecting private keys
  • Verifying transaction details
  • Maintaining device security
  • Following security best practices

15. ASSIGNMENT OF RIGHTS

15.1 Platform Assignment Rights
  • Midcontract may assign rights to:
    • Subsidiary or affiliate companies
    • Acquiring entities
    • Successor organizations
  • Users will be notified of material assignments
15.2 User Assignment Restrictions
  • Users may not assign their rights without written consent
  • Platform accounts are non-transferable
  • Contract rights non-assignable without approval
  • Exceptions require Platform written authorization
15.3 Contract Assignment
  • Freelancers/Agencies cannot assign contracts
  • Clients may assign with Platform approval
  • Assignment process requires:
    • Written request
    • Assignee KYC/AML verification
    • Platform approval
    • Smart contract update

16. PROHIBITED ACTIVITIES AND USERS

16.1 Prohibited User Activities

Users are strictly prohibited from using the Midcontract platform for any of the following activities:

  1. Adult Content and Services:
    • Pornography, prostitution, escorting, or other adult-related services or obscene content.
  2. Illegal Substances and Products:
    • Sales or distribution of illegal drugs, controlled substances, drug paraphernalia, or substances designed to mimic illegal drugs.
    • Marijuana dispensaries or online pharmacies without legal compliance.
  3. Gambling and Lotteries:
    • Online gambling, lotteries, betting, sweepstakes, or offering prizes as an inducement to purchase goods or services.
  4. Weapons and Violence:
    • Sale, promotion, or distribution of weapons, munitions, explosives, or services that promote violence or harm.
    • Activities associated with terroristic organizations or illegal operations.
  5. Deceptive and Predatory Services:
    • Multi-level marketing (MLM), pyramid schemes, deceptive or predatory marketing services.
    • Extended warranties not backed by legitimate providers.
  6. Fraudulent Financial Services:
    • Check cashing, money transmission, currency exchanges, or sale of financial instruments.
    • Sale of video game or virtual currency that can be monetized, re-sold, or converted into physical or digital goods outside the platform.
  7. Copyright and IP Infringement:
    • Products or services that infringe on third-party copyrights, trademarks, trade secrets, or intellectual property rights.
  8. Age-Restricted Services:
    • Sale or promotion of age-restricted goods or services, including tobacco, alcohol, or e-cigarettes without legal compliance.
  9. Social Media Manipulation:
    • Sale or promotion of social media activity, such as buying followers, likes, shares, or views.
  10. Unethical Technology Use:
    • Sale or installation of spyware, malware, viruses, or any unauthorized software or program designed to compromise user systems.
  11. Hate Speech and Discriminatory Activities:
    • Services or content that promote hate, violence, bigotry, or discrimination based on race, ethnicity, religion, sexual orientation, gender, or other protected characteristics.
  12. Esoteric and Undefined Services:
    • Services such as astrology, psychic readings, or other undefined, vague, or non-verifiable services.
  13. Activities Encouraging Criminal Conduct:
    • Any activity that encourages behavior that could be considered a criminal offense, cause civil liability, or violate applicable laws.
16.2 Prohibited Uses of the Platform

Users may not access or use the Midcontract platform in any of the following ways:

  1. Unauthorized System Access:
    • Attempting to gain unauthorized access to other users’ accounts, data, or restricted areas of the platform.
    • Using another user's login credentials without permission.
  2. System Interference:
    • Using any device, software, or routine that may disrupt, damage, or overburden the platform or its services.
    • Attempting to bypass security controls, introduce malicious code (e.g., viruses, trojans, worms), or exploit platform vulnerabilities.
  3. Automated Data Collection:
    • Using bots, spiders, or crawlers to scrape or mine data from the platform.
    • Engaging in unauthorized monitoring, data extraction, or collection of information from other users or the platform.
  4. Circumvention of Controls:
    • Removing, altering, or bypassing security measures, including content protection or access restrictions.
  5. Illegal Activities:
    • Using the platform for any illegal, unethical, harassing, or disruptive purposes.
    • Violating any applicable law or regulation related to international sanctions, AML/KYC compliance, or financial services.
  6. Impersonation and False Representation:
    • Falsifying personal information, impersonating another person or entity, or misrepresenting affiliation with a company.
  7. Improper Use of Escrow Services:
    • Submitting false claims for refunds or creating fake contracts to manipulate escrow funds or payouts.
16.3 Penalties for Prohibited Activities:

The platform reserves the right to take appropriate measures against users involved in prohibited activities, including but not limited to account suspension, fund freezes, and reporting to legal authorities.Violations of these prohibited activities and uses may result in:

  • Immediate suspension or termination of the user’s account.
  • Forfeiture of escrowed funds if fraud is confirmed.
  • Reporting to relevant regulatory authorities for further action.
  • Legal action, including but not limited to claims for damages and penalties.

17. SANCTIONS COMPLIANCE

17.1 Sanctions Screening and Compliance Program

Midcontract maintains a comprehensive sanctions compliance program in accordance with applicable laws and regulations, including:

  • European Union sanctions regulations
  • Estonian financial services requirements
  • FATF recommendations
  • US OFAC guidelines where applicable
17.2 Restricted Jurisdictions
17.2.1 Geographic Restrictions

Access to and use of the Platform is strictly prohibited for persons and entities located in, organized under the laws of, or residing in the following jurisdictions:

  • Belarus
  • Central African Republic
  • Democratic Republic of the Congo
  • Iran
  • Libya
  • Myanmar (Burma)
  • North Korea
  • Russia (including Crimea, Luhansk People's Republic (LPR), Donetsk People's Republic (DPR))
  • Somalia
  • South Sudan
  • Sudan
  • Syria
  • Venezuela
  • Yemen
  • Any other jurisdiction subject to comprehensive sanctions
17.2.2 Access Controls

The Platform implements the following measures to enforce geographic restrictions:

  • IP address blocking
  • Geolocation verification
  • VPN and proxy detection
  • Device fingerprinting
  • Regular access pattern monitoring
17.2.3 Ongoing Monitoring
  • Continuous screening against major sanctions lists
  • Regular review of user activity for sanctions compliance
  • Automated alerts for suspicious patterns
  • Periodic review of compliance measures
17.3 Violation Consequences
17.3.1 Account Actions

Violations of sanctions compliance requirements may result in:

  • Immediate account suspension
  • Asset freezing
  • Contract termination
  • Reporting to relevant authorities
  • Permanent platform ban
17.3.2 Funds Treatment

In case of sanctions violations:

  • Funds may be frozen indefinitely
  • Regulatory reporting will be completed as required
  • Legal authorities may be granted access to relevant information
  • Release of funds subject to regulatory approval

18. FORCE MAJEURE

18.1 Force Majeure Events

Neither party shall be liable for any failure or delay in performance under these Terms resulting from:

18.1.1 Natural Events
  • Natural disasters
  • Earthquakes
  • Floods
  • Fires
  • Other natural catastrophes
18.1.2 Human Events
  • Wars
  • Terrorist actions
  • Civil unrest
  • Labor disputes
  • Government actions
  • Regulatory changes
18.1.3 Technical Events
  • Blockchain network failures
  • Smart contract vulnerabilities
  • Critical infrastructure outages
  • Cyber attacks
  • Third-party service provider failures
  • Internet backbone disruptions
  • Power grid failures
18.1.4 Market Events
  • Cryptocurrency market disruptions
  • Banking system outages
  • Payment network failures
  • Exchange rate volatility
18.2 Notification Requirements

The affected party must:

  1. Notify the other party within 24 hours of the force majeure event
  2. Provide regular updates on the situation
  3. Take reasonable steps to minimize impact
  4. Resume performance as soon as practicable
18.3 Extended Duration

If a force majeure event continues for more than 30 consecutive days:

  1. Either party may terminate affected contracts
  2. Platform may suspend services
  3. Alternative arrangements may be proposed
  4. Funds in escrow will be handled according to emergency protocols

19. RISK DISCLOSURES

19.1 Cryptocurrency and Blockchain Risks
19.1.1 Market Risks

Price Volatility

  • Cryptocurrency values can experience significant and rapid price fluctuations
  • Changes may occur within minutes or seconds
  • No guarantee of stable value even for stablecoins
  • Market conditions may affect ability to execute transactions
  • Potential for complete loss of deposited value

Liquidity Risks

  • Market conditions may prevent immediate execution of transactions
  • Delays in converting between cryptocurrencies and fiat
  • Possible limitations on withdrawal amounts or frequency
  • Risk of insufficient market depth for large transactions
  • Potential impact of market makers or large traders

Exchange Rate Risks

  • Fluctuations between cryptocurrency and fiat currencies
  • Cross-rate risks between different cryptocurrencies
  • Impact of global market conditions
  • Potential losses during conversion processes
  • Settlement timing risks

Market Manipulation

  • Susceptibility to pump and dump schemes
  • Impact of whale accounts and large holders
  • Risk of artificial market manipulation
  • Effect of false or misleading information
  • Impact of social media and market sentiment
19.1.2 Technical RisksBlockchain Network Risks
  • Network congestion and delays
  • Transaction confirmation delays
  • Fork events and chain splits
  • Network upgrade impacts
  • Consensus mechanism failures
  • Mining or validation issues
  • Network attack vulnerabilities

Smart Contract Risks

  • Programming errors or bugs
  • Security vulnerabilities
  • Upgrade and maintenance impacts
  • Integration failures
  • Gas price fluctuations
  • Execution failures
  • Unintended contract behaviors

Wallet Security

  • Private key loss risks
  • Phishing attacks
  • Social engineering threats
  • Hardware wallet malfunctions
  • Software wallet vulnerabilities
  • Backup failure risks
  • Recovery phrase security

Transaction Risks

  • Irreversible transactions
  • Incorrect address inputs
  • Failed transaction handling
  • Gas fee complications
  • Stuck or pending transactions
  • Double-spending attempts
  • Replay attack risks
19.1.3 Operational Risks

Platform Risks

  • System downtime
  • Maintenance interruptions
  • Database failures
  • API disruptions
  • Integration issues
  • Performance degradation
  • Backup and recovery risks

Third-Party Service Provider Risks

  • Payment processor outages
  • KYC provider issues
  • Wallet service disruptions
  • Infrastructure provider failures
  • Cloud service interruptions
  • API service problems
  • Data provider inaccuracies

Security Risks

  • Cybersecurity threats
  • Data breach risks
  • DDoS attacks
  • Account compromise
  • Infrastructure vulnerabilities
  • Internal security threats
  • System access risks
19.2 Regulatory and Legal Risks
19.2.1 Regulatory Compliance Risks

Jurisdictional Risks

  • Varying regulatory requirements across jurisdictions
  • Changes in regulatory frameworks
  • New licensing requirements
  • Regulatory enforcement actions
  • Cross-border compliance challenges
  • Regulatory conflicts between jurisdictions
  • Impact of international sanctions

Operational Compliance

  • KYC/AML requirement changes
  • Reporting obligation updates
  • Record-keeping requirement changes
  • Audit requirement modifications
  • Privacy law compliance
  • Data protection requirements
  • Operating license maintenance

Financial Regulations

  • Banking relationship risks
  • Payment processing restrictions
  • Currency control regulations
  • Securities law implications
  • Tax regulation changes
  • Financial reporting requirements
  • Capital control impacts
19.2.2 Legal and Contract Risks

Contract Enforcement

  • Cross-jurisdictional enforcement challenges
  • Smart contract legal status
  • Digital signature validity
  • Evidence admissibility
  • Dispute resolution limitations
  • Jurisdiction determination
  • Applicable law conflicts

Intellectual Property

  • Copyright infringement risks
  • Patent violation claims
  • Trademark disputes
  • Trade secret protection
  • License compliance
  • Open source obligations
  • IP ownership conflicts

Data Protection

  • Privacy law compliance
  • Data transfer restrictions
  • Data localization requirements
  • User consent management
  • Data breach responsibilities
  • Right to be forgotten
  • Data portability obligations
19.3 Business and Operational Risks
19.3.1 Business Model Risks
  • Revenue model sustainability
  • Market competition impacts
  • Pricing model viability
  • Customer adoption challenges
  • Partnership risks
  • Technology obsolescence
  • Market demand changes
19.3.2 Service Delivery Risks
  • Performance guarantee challenges
  • Service level maintenance
  • Quality assurance issues
  • Customer support capacity
  • Technical support limitations
  • Feature deployment risks
  • Platform scaling challenges
19.3.3 Reputation Risks
  • Public perception impacts
  • Media coverage effects
  • User feedback influence
  • Platform reliability concerns
  • Security incident impacts
  • Compliance violation effects
  • Brand value protection
19.4 Risk Acknowledgment

By using the Platform, users acknowledge and accept:

  1. Understanding of all disclosed risks
  2. Responsibility for due diligence
  3. Independent assessment requirement
  4. Risk of total loss possibility
  5. Technical complexity understanding
  6. Regulatory uncertainty awareness
  7. Market volatility acceptance
19.5 Risk Mitigation
19.5.1 Platform Security Measures
  • Multi-factor authentication
  • Encryption protocols
  • Access controls
  • Monitoring systems
  • Backup procedures
  • Incident response plans
  • Security audits
19.5.2 User Responsibilities
  • Security best practices adherence
  • Private key protection
  • Regular security updates
  • Suspicious activity reporting
  • Account monitoring
  • Password management
  • Device security maintenance
19.5.3 Platform Commitments
  • Regular security assessments
  • Compliance monitoring
  • Risk assessment updates
  • Security feature improvements
  • User education
  • Transparent communication
  • Incident response readiness

20. ACCEPTANCE AND CONTACT INFORMATION

20.1 Acceptance of Terms

By accessing or using the Midcontract Platform, you acknowledge that you have read, understood, and agree to be bound by these Terms of Service and all incorporated policies and agreements, including:

  • Privacy Policy
  • KYC/AML Policy
  • Payment Terms
  • Escrow Agreement
  • Intellectual Property Framework
  • Arbitration and Dispute Resolution Terms
  • Service Availability And Maintenance
  • Liability Limitations
  • Assignment of Rights

If you do not agree with any part of these terms, you must not use the Platform.

20.2 Last Updated

These Terms of Service were last updated on January 6, 2025. The current version supersedes all previous versions.

20.3 Contact Information
Midcontract OÜ
  • Registered Address: Harju maakond, Tallinn, Kesklinna linnaosa, Vesivärava tn 50-201, 10152
  • Registration Number: 17137097
General Inquiries:
Specific Departments:
  • Legal: legal@midcontract.com
  • Privacy: privacy@midcontract.com
  • Compliance: compliance@midcontract.com
  • Data Protection Officer: dpo@midcontract.com
  • For urgent assistance during business hours (Monday-Friday, 9:00-17:00 EET), you can reach our support team through the platform's chat feature.