Refund Policy
Transparent terms outlining the structure of digital product ownership, licensing protections, and transaction dispute conditions.
Plain Language Rules
Because our products are premium, digital assets that are delivered immediately to your project directory via digital download, standard rules apply to licensing protection.
14-Day evaluation coverage window for technical discrepancies or unresolvable product exceptions.
Digital Asset Nature
All items listed on the Build Web platform are non-tangible, digital goods. Unlike physical assets, digital files cannot be physically returned or regular access definitively reversed once processed. Consequently, items remain functional within your scene libraries upon download initialization.
By executing an acquisition transaction at checkout, you acknowledge that all visual elements, assets, and source codes are instantly assigned to your studio workspace activation structure.
Eligible Refund Conditions
We review transaction adjustments explicitly within 14 days of purchase under verified structural exceptions. Review scopes include:
Defective Deployment
The core plugin asset displays terminal compilation breaks or missing system requirements that our support desk cannot resolve within 48 hours.
Asset Misrepresentation
The delivered bundle features distinct package discrepancies or fails to resemble explicit technical parameters advertised on the listing interface.
Double Purchase
Identical core licensing structures are acquired simultaneously via network transaction discrepancies or duplicate system calls.
Ineligible Conditions
Refund requests are systematically excluded from evaluation scopes under circumstances surrounding custom environment alterations. Examples include:
Change of mind
The asset package is functionally valid but is no longer needed due to shifting architectural project requirements.
Software mismatch
The asset fails to load correctly because your local engine version falls outside the explicitly detailed software baseline specifications.
Third-party friction
Conflicts arise from introducing custom, undocumented scripts or external unvetted plugins into the file structure.
Initiating an Evaluation
To request a file analysis or adjustment execution, reach out through our support ecosystem directly. Ensure you append your unique checkout identification reference number alongside technical diagnostics detailing the integration environment failure.
Once evaluated and authorized, credit reversals return directly to your primary routing accounts or connected provider wallets within 5 to 10 standard business banking cycles.