Terms of service

These terms cover your use of muxover.com and its subdomains (the "site") and any freelance work I do for you (the "services"). The site and services are run by Jax ("I", "me"), an independent developer working under the name muxover. By using the site or asking me to do work for you, you agree to these terms. If you don't agree, please don't use the site or the services.

They work together with the privacy policy and the payment and refund policy. Questions go to contact@muxover.com.

1. Using the site

You can read, link to and share anything on the site. When you use it, you agree not to:

break any law, or use the site to help someone else break one;
attack, overload or disrupt the site, or try to get around its security, rate limits or spam protection;
scrape it at a rate that affects other visitors, or copy it wholesale to present as your own;
send spam, malware or misleading information through the contact form;
pretend to be me, or suggest I endorse you or your work when I don't.

I can block access for anyone who does any of these. If you find a security problem, report it through the security policy instead of testing it on the live site beyond what that policy allows.

2. Site content and the muxover name

The text, design, logo, the Crossover mark, the names "Jax" and "muxover", and the images on the site are mine. You can quote short parts with a link back, but you can't reuse the branding or present the site's content as your own. Project names and descriptions pulled from my GitHub repositories are covered by those repositories.

I keep the content accurate, but it's provided as it is. Versions, descriptions and availability can change without notice, and nothing on the site is professional, legal or financial advice.

3. Open-source projects

The projects listed on the site are open source. Each one is covered by the license in its own repository, and that license decides how you can use it and what warranty, if any, comes with it. These terms don't add to or replace those licenses. Support for open-source projects is through their GitHub repositories and is given voluntarily.

4. Other sites and services

The site links to services I don't run, such as GitHub, npm, the Go package index, X and Telegram. Their own terms apply there, and I'm not responsible for their content or availability.

5. Freelance services

Quotes and agreements

Every project starts with a written scope and quote, sent by email. Unless the quote says otherwise, it stays valid for 30 days. A project is agreed once you accept the quote in writing and pay the deposit. If a project has its own signed agreement, that agreement takes priority over this section.

Who can hire me

You need to be at least 18 and able to enter a binding agreement. If you hire me on behalf of a company, you confirm you're allowed to do that for it. I can turn down any project, including work I believe is unlawful, harmful, or meant to break another service's terms.

Scope and changes

The work I deliver is what the agreed scope describes. If you want something added or changed once work has started, I'll tell you how it affects the price and timeline, and nothing changes until you agree in writing. Small clarifications that don't change the effort are included.

Your part

You provide the information, access, accounts and feedback the project needs, in reasonable time. You confirm you have the right to give me any code, content, data or credentials you share, and that the project is lawful. Delays on your side can move the timeline.

Timelines

Timelines in a quote are my honest estimate. I tell you straight away if something is going to slip and why. Missed estimates don't by themselves entitle either of us to damages.

Payment

Payment follows the payment and refund policy: a 50% deposit before work starts and the remaining 50% before handover.

Handover, acceptance and fixes

At handover you receive the deliverables set out in the scope. They count as accepted once the final payment is made, or once you put them into use, whichever comes first. If something I delivered doesn't work as the scope describes, tell me within 30 days of handover and I'll fix it at no charge. New features, changes you make yourself, and problems caused by third-party services aren't covered.

Ownership

Once the project is paid in full, you own the code and materials I made specifically for you. I keep ownership of my own tools, libraries and general know-how that existed before the project or aren't specific to it. You get a permanent, worldwide licence to use any of them that are part of your deliverables. Open-source components stay under their own licenses. Until you've paid in full, you have a licence to review the work, not to use it in production.

Confidentiality

I keep your non-public information, code and credentials confidential, use them only for your project, and remove my access to your systems when the project ends. This doesn't cover information that's already public or that I'm required by law to disclose.

Portfolio

I don't name you or show your project publicly unless you give me permission.

Support and hosting

Ongoing maintenance, hosting, monitoring and support after the fix period aren't included unless the quote says so. They can be agreed separately.

Ending a project

Either of us can end a project by telling the other in writing. You pay for the work done up to that point, you receive that work once it's paid for, and the refund policy covers any money left over. I can also pause or end a project if payments are late or if these terms are broken.

6. Warranties

I do the work with reasonable care and skill. Beyond that, and beyond the fix period above, the site and services are provided without warranties of any kind, as far as the law allows. I can't promise that any software will run without errors or interruption, or that it will meet requirements that weren't in the agreed scope.

7. Liability

As far as the law allows, my total liability for anything relating to a project is limited to the amount you paid me for that project, and I'm not liable for indirect or consequential losses such as lost profits, revenue, data, or business. Nothing in these terms limits liability that can't be limited by law, such as for fraud.

Projects often depend on services run by others, such as hosting providers, APIs and payment processors. I'm not responsible for their outages, changes, fees or decisions.

8. Your responsibility for your materials

If a claim is made against me because of code, content or data you gave me, or because of how you use what I delivered, you'll cover the reasonable costs of that claim.

9. Events outside anyone's control

Neither of us is responsible for delays caused by events we can't reasonably control, such as outages of third-party services, natural disasters or illness. The affected side tells the other as soon as possible, and timelines move accordingly.

10. Governing law and disputes

These terms are governed by the laws of the United Arab Emirates. If we disagree about something, we'll first try to settle it in good faith by email within 30 days. If that doesn't work, the competent courts of the United Arab Emirates will decide.

11. General

These terms, the quote and any signed project agreement are the whole agreement between us for a project.
If part of these terms can't be enforced, the rest still applies.
Not enforcing a term straight away doesn't mean giving it up.
Neither of us can transfer a project to someone else without the other's written agreement.
Notices are sent by email: to me at contact@muxover.com, to you at the address you used for the project.
These terms are written in English, and the English version is the one that applies.

12. Changes

I may update these terms. The date at the top shows when they last changed. A project already agreed stays under the terms that applied when its quote was accepted.

13. Contact

Questions about these terms: contact@muxover.com.