Service Level Agreement (SLA)

End-to-End Launch Service

Last Updated: January 22, 2026

1. Service Definition

This SLA defines support levels and responsibility boundaries for MakeMeACoin's end-to-end Solana token launch service, including:

  • Token mint setup and execution
  • Metadata preparation and on-chain writing
  • Liquidity pool creation and delivery
  • Authority configuration and management
  • Dashboard operations and logs

All transactions are signed through the user's wallet. The Platform never stores or controls user funds.

2. Service Workflow

  1. User provides project information via launch form
  2. Team prepares draft configuration based on provided information
  3. Configuration presented to user as final preview
  4. User approves configuration
  5. Platform executes technical workflow to write configuration on-chain
  6. Token + metadata + LP delivered live on Solana

3. Source of Truth: Final Approval

BINDING RECORD

The final structure displayed in the "Final Preview / Approved Configuration" screen is the official and binding record.

  • Approval timestamp and configuration hash are stored
  • This approved structure is what will be written on-chain
  • Telegram or other communication channels are for support only, not binding

4. User Changes and Responsibility Transfer

User may request changes before approving the final structure.

Changes requested by the user are applied by the Platform and presented as a new final structure.

Responsibility for outcomes resulting from user-requested parameters belongs to the user.

Platform is responsible only for the final structure created by the Platform and approved by the user without user modifications.

5. Support Levels and Response Times

These are initial response times, not resolution times:

Critical (P1)

  • Service cannot proceed despite payment verification
  • Platform-originated error preventing mint/metadata/LP operations
  • Critical infrastructure failure

Initial Response: 15 minutes

High Priority (P2)

  • Configuration or preview errors
  • Dashboard or automation workflow issues
  • Non-critical platform functionality loss

Initial Response: 2 hours

Normal (P3)

  • General information requests
  • Usage questions
  • Minor corrections or clarifications

Initial Response: 12 hours

6. Platform-Originated Error Definition

Platform-originated technical errors include:

  • Discrepancy between approved final structure and on-chain result
  • Technically incorrect configuration produced by the Platform (wrong metadata fields, incorrect authority status, wrong LP parameters)
  • Platform infrastructure failure preventing transaction initiation (backend/queue/worker failure)
  • Errors in platform automation logic

7. Out of Scope (Not Covered by SLA)

The following are NOT covered:

  • Token price, market movements, arbitrage, MEV, bot activities
  • Liquidity amount and LP-related economic outcomes
  • User wallet, device, browser, signature rejection, or user error
  • Incorrect information provided by user or user-requested changes
  • Third-party service outages (Phantom, Solana RPC, IPFS, Raydium, etc.)
  • Attacks, exploits, or market manipulation
  • Listing, marketing, community management
  • Revenue, success, or profit guarantees
  • Rug allegations or project reputation issues

8. Resolution and Remedy

For platform-originated technical errors, the Platform will:

  • Make reasonable efforts to resolve the error
  • Implement necessary technical corrections
  • Re-execute the service if needed

Remediation obligations are limited to the service fee paid for your selected package.

Platform does not cover indirect or economic damages, including user-added liquidity funds.

9. Insurance Coverage

  • Insurance covers platform-originated technical errors only
  • No separate reserve wallet for insurance
  • Coverage limited to direct service failures
  • Does not cover user funds added to LP
  • Does not cover market outcomes or economic losses

10. Authority and Security Defaults

• Mint authority is closed by default

• User can request authority to remain open (optional)

• Opening authority creates additional risk (user responsibility)

• No timelock system provided

• All authority configurations disclosed in final preview

11. Liability Limitation

UNDER NO CIRCUMSTANCES

Platform shall NOT be held liable for:

  • Loss of user funds or liquidity
  • Loss of profit or revenue
  • Price movements or market losses
  • Third-party attacks or exploits
  • Rug allegations or reputation damage

Maximum liability: the service fee paid for your selected package (see Pricing page).

12. Communication Channels

Support is available via Launch Center and Telegram during business hours. Response targets vary by package tier.

Final decisions and approvals are valid ONLY through the Platform dashboard.

Telegram conversations are for support purposes only and are not binding.

13. Delivery Timeline

Standard delivery: 24 hours from approval

Express delivery: 1 hour (if requested and feasible)

Timelines assume no user modifications and normal network conditions.

Acknowledgment

By using the end-to-end launch service, you acknowledge that you have read, understood, and agree to be bound by this Service Level Agreement. You understand that the Platform operates on a non-custodial basis and that final approvals through the Platform dashboard constitute the binding record for all service operations.