AYON1XW COMMISSION TERMS

Limited availability

SMALL PROGRAMMING COMMISSIONS

CommissionTerms

These Commission Terms apply to small programming and development commissions requested through this website or linked contact methods. By accepting a quote and commissioning a project, you agree to these terms.

Last updated: August 11, 2026 // Clear boundaries protect both sides.

EFFECTIVE AUG 11, 2026
PAYMENT EUR / PAYPAL
Explore 17 clauses

SCENE 02 / ENGAGEMENT

Intake &
Agreement.

Ground rules governing request evaluation, strict boundary definitions, individualized quotes, payment arrangements, and active development.

01

INTAKE / EVALUATION

1. Commission Requests

Index ↑

Submitting a commission request does not guarantee that your project will be accepted.

I mainly accept small, clearly scoped programming requests. I do not accept full startup builds, complex infrastructure, large platforms, payment systems, or ongoing maintenance-heavy projects unless explicitly agreed otherwise.

I may accept or decline a request at my discretion, including if the project is outside my skill set, availability, or the services I offer.

Before accepting a commission, we will discuss the project’s requirements, expected functionality, estimated delivery time, and price.

02

BOUNDARY / CRITERIA

2. Scope

Index ↑

The agreed scope defines what will be built. Only explicitly agreed features, deliverables, and work are included.

Extra features, major changes, redesigns, or new directions may require a new quote.

Suitable requests ACCEPT
  • Small websites and landing pages
  • Portfolio pages
  • Small scripts and tools
  • Bug fixes and UI cleanup
  • Discord or Telegram bot features
  • README / GitHub setup
  • Small automation tools
  • Focused edits to existing code
Unsuitable requests DECLINE
  • Full SaaS or startup builds
  • Large apps and complex infrastructure
  • Login and payment systems
  • Crypto, gambling, or banking systems
  • Malware, spam tools, or private scraping
  • Vague requests without clear scope
03

COMMERCIAL / ESTIMATE

3. Quotes

Index ↑

Once the project requirements are sufficiently clear, I will provide a quote.

The quote will specify the agreed scope, price, and, where applicable, an estimated delivery time.

A quote only covers the features and work explicitly agreed upon. Additional features or significant changes requested afterward may require an additional payment or a new quote.

04

FINANCIAL / PROTOCOL

4. Payment

Index ↑

Payment arrangements are handled manually after a quote has been accepted. There is currently no automatic checkout on this website.

Depending on the size and nature of the project, I may require either full payment upfront or an initial deposit with the remaining balance due before final delivery.

PAYMENT FLOW

Small projects: No upfront payment. Built to preview; paid in full prior to asset handoff.
Larger projects: 50% deposit before development begins; remaining 50% upon approved preview prior to delivery.

Development will normally begin only after any required initial payment has been received.

The complete source code, unrestricted project files, repository ownership, or other final deliverables may be withheld until the full agreed amount has been paid.

05

EXECUTION / TIMELINE

5. Development

Index ↑

I will develop the project according to the requirements agreed upon before development begins.

Any delivery date or development duration provided is an estimate unless explicitly agreed otherwise.

If a significant delay occurs, I will inform you as soon as reasonably possible.

SCENE 03 / DELIVERY

Handoff &
Warranty.

Provisions outlining revision allowances, interactive preview examination, file and repository handoff, post-delivery bug fixes, and refund guidelines.

06

ITERATION / REVISION

6. Changes and Revisions

Index ↑

Reasonable revisions to the agreed project may be requested during the review process.

Unless otherwise agreed, a commission includes up to two revision rounds.

DEFAULT ALLOWANCE

Two revision rounds within agreed scope are included. Substantial new features, redesigns, or pivots require an additional quote.

A revision means an adjustment to functionality or design already included within the agreed scope.

Requests for substantial new functionality, redesigns, or other work outside the original scope are not considered revisions and may result in an additional quote.

07

INSPECTION / APPROVAL

7. Review and Approval

Index ↑

Before final delivery, you may be provided with a demonstration, preview, screenshots, video, hosted version, test build, or another reasonable method of reviewing the project.

You should use this review period to report issues or request included revisions.

Access to a preview does not grant ownership of or permission to copy, extract, redistribute, or otherwise obtain unreleased source code or project assets.

08

HANDOFF / ASSETS

8. Delivery

Index ↑

After the project has been approved and all required payments have been received, the agreed deliverables will be provided.

Delivery may include source files, a downloadable archive, a Git repository, repository ownership transfer, deployment, or another method agreed upon for the project.

The exact deliverables depend on the individual commission.

09

SUPPORT / 7-DAY WINDOW

9. Bugs and Support

Index ↑

Unless otherwise agreed, I will provide a 7-day bug-fix period beginning on the date of final delivery.

7-DAY WARRANTY

I fix reproducible bugs in the original agreed scope at no extra charge for seven days post-delivery.

During this period, I will fix reproducible bugs that cause functionality included in the original agreed scope to not work as intended.

This does not include new features, changes in requirements, problems caused by modifications made by the client or third parties, external service changes, or issues outside my reasonable control.

Additional work after this period may require a new commission.

This support period does not affect any statutory rights that may apply.

10

SETTLEMENT / REFUNDS

10. Cancellations and Refunds

Index ↑

If a commission is cancelled before development begins, payments made for work that has not yet started may be refundable.

If development has already begun, any refund will depend on the amount of work already completed and any non-recoverable costs incurred for the project.

If I am unable to complete a commissioned project, I will communicate this and provide an appropriate refund for work that cannot be delivered.

Completed and delivered work is generally non-refundable, except where required by applicable law or where the delivered work materially fails to meet the agreed scope.

SCENE 04 / GOVERNANCE

Ownership &
Obligations.

Legal definitions governing intellectual property handoff, portfolio showcase rights, mutual responsibilities, third-party limitations, and direct communication.

11

INTELLECTUAL PROPERTY

11. Ownership

Index ↑

Unless otherwise agreed, rights to the custom final deliverables created specifically for your project are transferred to you after full payment.

IP TRANSFER

Full rights to bespoke deliverables transfer upon final payment. Pre-existing libraries, general tools, and third-party dependencies retain their respective licenses.

I retain ownership of pre-existing materials, general-purpose code, reusable components, libraries, development tools, templates, techniques, and other materials that were not created exclusively for your commission.

Projects may contain third-party software, libraries, fonts, assets, APIs, or other materials. These remain subject to their respective licenses and terms.

12

SHOWCASE / CREDITS

12. Portfolio Use

Index ↑

Unless confidentiality has been agreed upon beforehand, I may display non-sensitive portions of completed work in my portfolio or use them as examples of my development work.

I will not intentionally publish private credentials, personal information, confidential data, private source code, or other information that should reasonably remain confidential.

If you require the project to remain private, please communicate this before commissioning the project.

13

CLIENT RESPONSIBILITY

13. Client Responsibilities

Index ↑

You are responsible for providing accurate project requirements and any materials, access, information, or feedback reasonably necessary to complete the project.

You must have the necessary rights or permission to provide any assets, code, branding, content, or other materials supplied for use in the project.

You may not commission work intended for unlawful, fraudulent, malicious, abusive, or otherwise prohibited purposes.

14

DEPENDENCIES / INFRASTRUCTURE

14. Third-Party Services

Index ↑

Some projects may depend on third-party platforms, APIs, hosting providers, libraries, payment providers, or other external services.

I am not responsible for outages, pricing changes, account restrictions, API changes, discontinued services, or other actions taken by third-party providers that are outside my control.

Any recurring third-party costs will be the client’s responsibility unless explicitly agreed otherwise.

15

PRE-CONTRACT / STATUS

15. No Automatic Acceptance

Index ↑

A submitted request, message, or form entry does not create a commission by itself.

A commission only starts once the scope, price, payment terms, and delivery expectations have been discussed and accepted.

16

AMENDMENTS / POLICY

16. Changes to These Terms

Index ↑

These terms may be updated for future commissions.

The terms applicable to an existing commission will generally be the version accepted when that commission was agreed upon, unless both parties agree to different terms.

17

COMMUNICATION / INQUIRY

17. Questions

Index ↑

If you have questions about these terms or how they apply to your project, please ask before accepting a quote or making a payment.

NEXT STEP / INTAKE PROTOCOL

Ready to send
your brief?

If your project fits these parameters and you agree with these conditions, send your requirements through the private intake form.