Terms of Service

1. About these terms

These terms govern this website and educational digital content offered by Pavlo Ishchenko (the "Provider"), based in Tower Hamlets, United Kingdom. The Provider's email, telephone and postal address appear below and on the contact page. The version shown before an order forms part of that order.

2. What is sold

Products may include:

• prerecorded Roblox Studio, Luau and indie game-development lessons;
• PDF manuals, worksheets, diagrams, checklists and reference documents;
• original starter, milestone and completed example place files; and
• corrections or updates where the product page expressly includes them.

The product page and checkout state the exact deliverables, price, access period, supported technical baseline, delivery method, support boundary and exclusions.

3. Educational scope

Products provide general technical education. They are not custom game development, private code review, security certification, managed publishing, moderation representation, legal, privacy, tax or financial advice. No product guarantees platform approval, discovery, players, retention, ranking, Robux, revenue, employment or commercial success.

4. Orders and payment

Prices are one-time payments in US dollars unless checkout clearly says otherwise. Stripe will process the payment for the selected product. An order is accepted when payment is confirmed and an order confirmation is issued. If a material pricing or description error is discovered before access is supplied, the Provider may cancel and refund the order.

5. Delivery, access and compatibility

• Digital content is delivered by the method stated at checkout.
• Access is personal, non-transferable and limited to the published period.
• The buyer is responsible for compatible hardware, Roblox Studio, accounts, connectivity and storage.
• Some exercises may require test accounts, local clients or third-party tools identified before purchase.
• The published Roblox Studio, Luau and supporting-tool baseline defines what was tested.

6. Cancellations and refunds

Digital-content cancellation rights may depend on whether supply has begun with any legally required consent and acknowledgement. The Cancellation Policy and Refund Policy explain the practical process and voluntary flexibility. They do not remove rights that cannot lawfully be excluded.

7. Licence and intellectual property

Purchased videos, manuals, worksheets, source examples and project assets are licensed for the buyer's personal education and own lawful project work. Access must not be shared, republished, resold, uploaded or used to create a competing course. Example code may be modified for the buyer's own project, subject to notices and third-party licences included with the files.

8. Buyer responsibility

The buyer remains responsible for code, data, security, permissions, age and content settings, disclosures, community features, assets, audio, fonts, licences, accounts and release decisions in their own game. Current official Roblox documentation and specialist advice should be checked where appropriate before testing with real users or publishing.

9. Tool and platform changes

Roblox Studio, Luau, platform APIs, policy and publishing processes change. Verified errors affecting the stated technical baseline are handled under the Quality Policy. A lesson cannot promise indefinite compatibility with future platform versions.

10. Liability

Nothing excludes liability that cannot lawfully be excluded. Subject to those protections, the Provider is not responsible for platform decisions, third-party outages, later software changes, project defects, data loss or indirect commercial loss arising from applying general educational material. Buyers should keep independent backups and test changes before distribution.

11. Governing terms and contact

These terms are governed by the law of England and Wales, without removing mandatory consumer protections that apply where a buyer lives. Questions or complaints about an order should be sent to pavloivchenkoboos@outlook.com with the buyer name, order email, product and Stripe receipt reference. Do not send complete card details.