Payment, Final-Sale and Dispute Policy

Before payment, the listing and checkout identify the build, seller, price, Minecraft edition/version, file format, approximate size, included content, dependencies, preview, and license. The buyer requests immediate digital access and acknowledges that the purchase becomes final once access is supplied.

After access is supplied, there is no change-of-mind refund for disliking an accurately represented build, selecting the wrong clearly disclosed edition, or lacking ordinary tools needed to use ZIP or world files.

Support remains available for missing access, duplicate payment, corrupt or materially unusable files, material misdescription, undisclosed incompatibility, infringement, fraud, and mandatory legal remedies. A seller may not materially replace the purchase-specific file version after payment.

Where applicable, the buyer expressly requests performance and immediate delivery before the withdrawal period ends and acknowledges that the statutory withdrawal right is lost when digital performance begins, to the extent permitted by law.

The enforceable scope is the checkout brief, selected size and style, agreed price, and amendments clearly agreed in the order chat. Uncommunicated expectations are not part of the scope.

A buyer may open a support dispute within seven calendar days after delivery. The appeal must identify a material difference from the documented scope and provide relevant evidence.

BuildEx reviews the brief, agreed chat amendments, rates or listing, delivered file, preview, and evidence from both parties. Version 1 supports only a full release to the builder or a full buyer refund; no partial award is available.

A refund is not available for changed preferences, uncommunicated requirements, minor subjective aesthetic differences within scope, buyer modifications, or incompatibility disclosed before purchase. BuildEx records and communicates its reasoned decision.

A refund is complete only after the payment provider or authorized manual process confirms the outbound transfer. BuildEx records the provider reference, asset/network, amount, timestamps, and any failure. A database label alone is not proof that funds were returned.

Nothing in this policy excludes rights or remedies that applicable law does not allow BuildEx or a seller to exclude.