For developers

Legal pages and contracts for developers.

You build things people rely on. Put the acceptance rules, bug-fix window and hand-over in writing before the first commit.

Hand-painted illustration: a paper-document character beside a stack of ribbon-tied contracts.

How it plays out

You build a feature for a client and a month after launch they report a bug. Your agreement says what counts as a defect, how long you fix them for free and what happens after that. It also says who owns the code, who owns any open-source parts and who pays for hosting and outside services.

A web development contract and a statement of work cover most projects. Add terms and a privacy policy if you sell a product.

Pages you will want

These are the pages most developers reach for first. Not every one will apply to you.

Contracts that fit

Common problems

  • Requirements that change weekly with no change in price.
  • Promising a bug-free product.
  • Clients who think the code and hosting accounts are theirs from day one.

Questions

Who owns the code?
Whatever your contract says. Many agreements pass custom code to the client on full payment while the developer keeps reusable tools.
Should I give a warranty?
A short fix-it window for defects against agreed requirements is common.
Hand-painted illustration: a paper-document character at a round wooden door holding up a brass key.

Ready when you are.

Start with a free privacy policy. No card needed, and you can upgrade whenever you like.