Legal

Terms

Last updated: April 12, 2026

This page explains the ground rules if I agree to work with you.

Right now most of my time is going into open-source work, donation-supported work, and private local projects. If I take on a paid client project, the final scope, pricing, timeline, and delivery model are always confirmed in writing first.

What these terms cover

These terms apply to any paid or unpaid project, technical help, support, hosting, maintenance, training, or consulting work I choose to take on through muso.sk unless a separate written agreement replaces them.

How work starts

Before work starts, I need enough clarity to do the job properly.

That usually means:

  • a clear written task or project goal
  • access to the systems involved
  • one decision-maker or one person who can confirm the next step
  • an agreed budget, rate, or fixed scope
  • an agreed communication channel

If those basics are missing, I may pause the start, ask for a paid diagnosis first, or decline the work.

Communication

I prefer written communication and structured task handoff.

If a project is active, I usually want:

  • Basecamp/Plane or another agreed written tool
  • clear tasks instead of scattered messages
  • one thread per issue when possible
  • calls only when they help move the work forward

Voice-message chaos, last-minute pressure, and unclear instructions slow projects down. If communication becomes messy enough to waste time, I may bill the extra time, pause the work, or stop the project.

Scope and change requests

The agreed scope covers only what was actually agreed.

If the task changes, the estimate changes too. That can mean:

  • extra billed time
  • a revised fixed quote
  • a new milestone
  • a separate follow-up task

Small clarifications are normal. New features, bigger revisions, inherited cleanup, or extra environments are not free just because they appeared after the start.

Payments

Public pricing on this site is a baseline, not a promise that every job fits a fixed menu.

Depending on the work, I may use:

  • prepaid hour blocks
  • deposits
  • milestone invoices
  • monthly recurring billing
  • small fixed-scope quotes

If payment is late, I can pause work, hold delivery, or suspend support until the balance is settled.

Hosting, support, and maintenance

If I host or maintain something for you, that does not mean unlimited support.

Unless a separate arrangement says otherwise:

  • support is limited to the agreed scope
  • updates and fixes are usually handled in batches
  • emergencies are handled separately
  • third-party outages, provider problems, or platform changes can affect timelines

If I inherit a system I did not build, I may require a paid review before I agree to maintain it.

Delivery and responsibility

I do the work personally unless I say otherwise.

I use automation and AI tools in my workflow where they help delivery, but I stay responsible for what I ship.

I am not responsible for delays caused by:

  • missing access
  • unclear or changing requirements
  • third-party provider issues
  • client-side delays
  • content, approvals, or assets arriving late

Ownership

Unless a written agreement says something else:

  • your final paid deliverables become yours after full payment
  • my reusable methods, templates, tooling, and internal workflow stay mine
  • third-party software, services, and licenses stay under their own terms

Right to refuse or stop work

I can decline or stop work if:

  • payment is not made
  • the task changes beyond what was agreed
  • communication becomes abusive or chaotic
  • the project becomes risky for legal, security, or operational reasons
  • the working setup is no longer a fit

If that happens, I will usually close out the current state as cleanly as the situation allows.

Liability

I work carefully, but no technical work is risk-free.

To the maximum extent allowed by law:

  • I am not liable for indirect or consequential loss
  • I am not liable for third-party platform failures
  • my total liability is limited to the amount paid for the specific work that caused the issue

Backups, access control, and launch approval should always be treated seriously by both sides.

Changes

I may update these terms when the way I work changes. The current version on this page is the one that applies unless a separate written agreement says otherwise.

Contact

If you want to clarify anything before starting, use the contact page.