Terms of sale and use

Each listing sells a software product delivered as a downloadable archive containing source code, a build configuration, a README and a licence file. Some listings also include a compiled binary. What a given listing includes is stated on its own page.

Every order carries a licence, shown on the listing before you buy and included as LICENSE.txt in your archive. It sets how many deployments are permitted, whether you may deploy for clients, and whether you may present the product under your own branding.

The licence terms are fixed at the moment of purchase. If a listing's licence changes afterwards, your terms do not change with it. Where this page and your delivered LICENSE.txt differ, that file governs.

You may not resell, relicense, sublicense or publish the source itself — in whole or in substantial part — as a competing product, template, course or code library. Distributing a compiled binary within the limits of your licence is permitted; redistributing the sources is not.

You are responsible for keeping your credentials secure and for activity under your account. Provide an email address you control: it is how your purchases are identified and how downloads are released.

Prices are in US dollars and payment is handled by Stripe. Access to a download is released once Stripe confirms the payment has settled.

See the refund policy, which forms part of these terms.

The software is provided "as is", without warranty of any kind. You are responsible for evaluating it before production use.

Some listings are trading or market software. That category carries real financial risk: it can lose money, and past measurements do not predict future results. Test on paper or in staging, with limits you can afford, before committing live capital. You are solely responsible for every order your deployment places and for compliance with the rules of any venue you connect to.

Some products can optionally link third-party libraries, named in the licence file shipped with them. Those components are not distributed with the archive and remain under their own licences, which you are responsible for reviewing. At least one such option is copyleft and is disabled by default; enabling it places obligations on any binary you then distribute.

Our products may include OpenSSL Toolkit (Apache 2.0). OpenSSL attribution is included in product NOTICE files. Customers distributing binaries must retain attribution. Customers are responsible for compliance with applicable export control and cryptography laws in their jurisdiction.

Each archive carries a NOTICE file and a THIRD_PARTY_LICENSES.md listing every component it can link and the licence that governs it. Those files are the authoritative list for the version you received.

These terms may change. The version in force for your order is the one published on the date of that order, together with the licence file delivered with it.

Zacharee Jordan Burchfield, trading as BotStudio9, Yulee, FL, United States. Email zachareeburchfield0909@gmail.com.