MegaScript.
[ Terms ]

Simple working terms for clear collaboration.

These terms outline how projects, payments, revisions, ownership, support, and responsibilities are handled when working with MegaScript.

Discuss a projectPrivacy policy

Terms summary

These terms outline how projects, payments, revisions, ownership, support, and responsibilities are handled when working with MegaScript.

01

Project scope

Every project starts with an agreed scope, timeline, deliverables, and responsibilities. Changes outside scope may require a revised estimate.

02

Payments

Payment milestones are confirmed before work begins. Late payments can pause delivery until the account is brought up to date.

03

Revisions

Reasonable revision rounds are included according to the proposal. New directions after approval may be treated as additional work.

04

Ownership

After final payment, approved deliverables are transferred to the client unless a separate license or third-party restriction applies.

05

Third-party tools

Hosting, plugins, SaaS tools, fonts, payment providers, and APIs may have their own terms and costs.

06

Liability

We work carefully, but MegaScript is not responsible for indirect losses, third-party outages, or client-side changes made after handoff.

How agreements stay clear

A written proposal or statement of work should always be the source of truth for a specific project.

01

Proposal

We define scope, price, timeline, and deliverables before work starts.

02

Approval

You confirm the direction and provide the content, access, and feedback needed.

03

Delivery

We build, review, revise, and prepare the work for launch or handoff.

04

Handoff

Ownership transfers after final payment and agreed deliverables are complete.

Terms questions

Short answers to help you decide without friction.

MegaScript

Where ideas become reality.

Navigation

Explore

Designed and developed with ❤️ by

© 2026 MegaScript. All rights reserved.