Terms

Who this is

HatchTag is a one-person web design and development practice based in Florida, United States. "I" and "me" mean HatchTag; "you" means whoever is reading this or hiring me.

Because it is one person rather than an agency, these terms are written in the first person. They are no less binding for it.

Using this website

Read it, click through the previews, send me an email. Please do not attack it, scrape it wholesale, or try to get into the parts that are not yours.

Found a flaw? Tell me at sales@hatchtag.dev. A report made in good faith — nothing taken, nothing broken, no demand attached — gets thanks and a fix.

The site is provided as it is. I keep it accurate and up, but I am not promising it will never be wrong or never be down.

Client previews

The previews page is the point of this business, so it gets its own section.

If you are looking at someone else's preview

Those are real sites, running live, hosted here on this domain. They belong to the businesses they were built for. Some are finished, some are still being worked on, and what you see today may not be what launches. Treat them as demonstrations, not as anybody's finished product, and do not copy them.

If the preview is yours

• You do not pay to see it. I will often build a working preview before any money changes hands, so you can click around a real site instead of squinting at a mockup.
• It stays mine until it is paid for. A preview is a demonstration, not a delivery. Until the agreed invoice is settled, the design and the code remain my property and no licence to use them transfers to you.
• It is not permanent. I host previews as a courtesy and can take one down — with reasonable notice where I can give it — if a project goes quiet, is cancelled, or simply ages out.
• It is not the final site. A preview shows the direction and how it behaves. Content, images and details change before launch, and a preview is not a promise about the finished thing.
• Tell me if you would rather it were not public. Previews sit on a public page by default because that is how new clients see what I do. Ask and I will keep yours unlisted.

Nothing here is a quote

This site carries no prices, and nothing on it is an offer capable of being accepted. What a site costs depends on how many pages it has, what it has to do and who has to be able to edit it afterwards.

A price arrives in writing after we have talked, and there is no agreement between us until you accept that proposal in writing. No payment is taken on this site — there is no card field and no payment processor anywhere on it.

How a project runs

The written proposal governs the work: what is being built, what it costs, when it is due and how it is paid for.

Where the proposal and this page disagree, the proposal wins. These terms fill the gaps; they do not override something we both signed. If the proposal is silent on a point, what is on this page applies.

Work outside the agreed scope — extra pages, a shop where there was not one, a feature that appeared after we started — gets quoted separately before it gets built, rather than absorbed quietly and argued about later.

Who owns what

• On final payment, the site is yours. The design, the page templates and the custom code written for your project transfer to you, along with the content you supplied, which was always yours.
• Before final payment, it is mine. That is what makes it possible to build you something before you have committed to anything.
• Third-party parts keep their own licences. Fonts, stock images, plugins and libraries come with terms set by whoever made them, and some of them are subscriptions. I will tell you which ones your site depends on. Keeping those licences current after handover is yours to do.
• My own tooling stays mine. The starting templates, build setup and techniques I reuse between projects are not part of what transfers — your site is, the workshop is not.

Showing the work

I may show the sites I build — on the previews page, in a proposal, or to someone asking what I do — including a screenshot, a link and the client's name.

If you would rather I did not, say so and I will not. No explanation needed, and it changes nothing about the price. If you tell me later, I will take it down.

The content you give me

Text, photographs, logos, testimonials — when you hand them over you are confirming you own them or have the right to use them.

That matters more than it sounds. A photograph pulled off a search results page is how small businesses end up with a demand letter from a stock agency, and the claim lands on the site owner. If a claim comes from content you supplied, it is yours to deal with, and you agree to cover me for it.

If you would rather not take that risk, tell me and I will source licensed images and tell you what they cost.

Domains, hosting and accounts

• Accounts should be in your name. Where I set up a domain, a host or an email service for you, I set it up as yours. A business that cannot get into its own domain registrar is one argument away from losing its website.
• Renewals are yours to keep paying. Domains and hosting expire. If a renewal lapses and the site goes down, that is not something I can fix retroactively.
• Credentials I hold get handed over on request, promptly and without conditions, once the work is paid for.
• Change the passwords after handover. I would rather you rotated them than left mine lying around in a project folder.

What I need from you

• Content and images, or a clear decision to have me write and source them.
• Feedback in reasonable time. A project waiting on approval is a project not being built, and long gaps push the launch date.
• One person who can make decisions. Design by committee is slower and worse.
• Payment to the terms in the proposal.

What I will not promise

I will build you a fast, accessible, well-made site. I will not promise you a position in Google's results, an amount of traffic, or a number of sales — because nobody can, and the people who do are charging you for a guess.

Equally: no site is bug-free on day one and no site is secure forever. I fix what I broke. Things that break later because software moved on, a plugin updated or a host changed something are maintenance, and maintenance is either in your proposal or it is a separate conversation.

Stopping a project

Either of us can stop. If you do, work completed up to that point is payable and anything already paid for what has been done is not refundable. If I do, I will refund what you have paid for work I have not delivered, and hand over what is finished.

A project that goes silent for 60 days is treated as paused. I will chase it first; I will not hold a finished site hostage over a forgotten email.

Liability

I do not limit liability for anything the law does not let me limit, including fraud and personal injury caused by my negligence.

Beyond that, and so far as the law allows: my total liability for a project is capped at what you paid me for it, and I am not liable for indirect or consequential loss, lost profit, lost data or business interruption. If something I did causes a problem, tell me early — there is usually a fix and there is always a conversation.

Changes and governing law

I update this page when the business changes, and the date at the top changes with it. A change applies to what happens after it is published; a project already agreed stays under the terms in force when you agreed it.

These terms are governed by the laws of the State of Florida, and the courts of Florida have jurisdiction. If part of this page turns out to be unenforceable, the rest of it stands.

Contact

Anything on this page: sales@hatchtag.dev. See also the privacy notice, which covers what happens to information rather than to work.

This page is written in plain English for people who have to live with it. It is not legal advice and it has not been through a lawyer. Before you rely on it for a project worth real money, have your own counsel read it.