Skip to content
Petal& CodeWeb design & build studio
Petal & Code

Legal

Terms of service

Version 1.2 · Updated 5 November 2026

Working with me. What to expect when you book a project, including payments, approvals, ownership and ongoing support.

1. About these terms

Petal & Code is the trading name of Petal & Code Ltd, run by me, Rosie Jaeger. These terms apply when you work with me on a project.

Company
Petal & Code Ltd, company number 17405589, registered in England and Wales
Registered office
71–75 Shelton Street, London WC2H 9JQ (also on every invoice)

Which document applies

  1. A signed services agreement, if you have one, applies first.
  2. If not, the proposal written for your project applies.
  3. This page covers anything neither of them does.

Below, “your agreement” means whichever of the first two applies to you.

Business and private clients

These terms are written for business clients. If you are hiring me as a private individual rather than for a business, your statutory consumer rights apply in full and nothing here takes them away.

2. Materials you provide

Copy, logos, photographs, brand assets and data you send me for the project stay yours. By sending them you confirm you have the right to use them and to let me use them. This matters most with photography and typefaces, where licences are easy to overlook.

I use those materials only to carry out your project. If anything turns out to be something you did not have the rights to, I will take it out of the work.

3. Working with specialists

I lead every project and I am your single point of contact throughout. Where a project calls for a particular skill, I may bring in a trusted specialist. I choose them, brief them and check their work, and you continue to deal with me. They are held to the same confidentiality I am, and I stay responsible to you for everything delivered, including their contribution.

Specialists only get the access their part of the work needs, agreed with you in advance where it involves your accounts or systems, and are bound by the same confidentiality.

4. Ownership and licences

Ownership of the designs, code and copy made specifically for you, including anything a specialist contributes, passes to you once the final invoice is paid. Until then, the work remains mine.

Some things I bring with me rather than make for you, such as my own components, snippets and tooling. Those stay mine, and you get a perpetual, irrevocable, royalty-free licence to keep using them as part of your project, including if someone else takes over maintaining it later.

Anything that came with its own licence, like a typeface or a stock image, is governed by that licence rather than by this page.

Unless you ask me not to, I may show finished work in my portfolio and on social media once it is live. Let me know if you would rather I did not, or if I should wait until a launch date.

5. Revisions and scope

Unless your agreement says otherwise, each stage of the work includes two rounds of revisions. A round means you send your comments together and I work through them in one go, rather than a running stream of individual changes.

If you want more rounds, or want to change direction after a stage has been approved, I will tell you what it adds before I start, and it goes on the next invoice.

Where your agreement names a date, that date assumes the included rounds are used and feedback arrives when agreed. Extra rounds move the dates that follow.

6. Payment

Projects are split 50/50: half to begin, half on delivery, unless your agreement sets out a different split. Larger projects are sometimes staged across more than two payments so they follow the work.

Your start date is the one set out in your agreement. Work begins on that date once the agreement is signed and the initial payment has cleared. Every later invoice is due within 14 days.

If an invoice is significantly overdue, I may pause work until it is settled, and unpaid work remains mine. If cash flow is tight, tell me early and we can agree a way forward.

7. Timings and approvals

Dates I give you assume feedback arrives roughly when we agreed. If a review takes a fortnight instead of a couple of days, the end date moves by about the same amount.

Each stage needs your approval in writing before the next begins. Please send feedback or approval within 5 working days, or tell me if you need longer. If I have not heard back, I will send a reminder. Silence is never treated as approval: the project pauses, and the schedule moves to match.

If the work is blocked for more than 30 days by something on your side, such as copy that has not arrived, a decision not made, or a system I cannot connect to, I may invoice for the work completed so far, and restarting is scheduled around my availability at the time. After 90 days the project is treated as ended, as set out in Ending a project.

8. Files and backups

Please keep your own copies of anything I send you. Store the deliverables and files that matter to you somewhere of your own.

Databases I host for your project are backed up, and where your project handles personal data, your data processing agreement sets out how. I keep other project files for a reasonable period after the project ends, but cannot guarantee to keep them indefinitely.

9. Confidentiality

Anything you tell me that is not public stays between us: your plans, your figures and how your business works. The same applies to my pricing and working files. Either of us can share it with people who need to see it, such as an accountant, a solicitor or a specialist working on the project, provided they are held to the same standard. This continues after the project ends.

10. Ending a project

Either of us can end the work by telling the other in writing. Either of us can also end it immediately if the other is in serious breach and has not put it right within 10 working days of being told.

However it ends, you pay for every stage already completed, for any stage under way in proportion to the work done, and for any third-party costs already committed on your behalf. Stages not yet started are not charged, and I return anything you have paid beyond that within 30 days. Payments are not refundable where they cover work already done, work under way or costs already committed.

11. Monthly plans

Monthly care plans run month to month, with no minimum term. Either of us can end a plan with 30 days’ notice by email.

Plans are billed monthly in advance. If the price of your plan changes, I will tell you at least 30 days beforehand.

A care plan covers the checks, security updates and backups set out in it, and hosting if you have chosen for me to host your site. Your plan sets out in writing the work covered and the time included for changes each month. Unused time does not roll over. Any additional work is priced and agreed with you before it starts.

When you send a request, I will reply within two working days and confirm when the work will be completed.

If we agree that I will manage your domain renewals, renewal charges are stated separately from your plan, and the domain stays registered in your name.

When a plan ends, I hand over the accounts and code, and export any data I hold for you, within 10 working days.

If a plan payment is more than 30 days late, I may pause updates and, after telling you in writing, suspend hosting I provide until it is settled.

12. Fixes and support

While a project is running, fixing a defect in my work, meaning anything that does not match the agreed scope or the designs you approved, is free and does not count as a revision round.

Fixes stay free for 30 days after your site goes live or your files are handed over, whichever comes first. After that, support is available pay as you go at my current hourly rate, with no retainer or minimum, or through a monthly plan. Your agreement sets the rate or plan, and I tell you what a piece of work will cost before I start.

I reply within two working days, and to anything urgent as soon as I can. I am not responsible for third-party services going down, such as hosting or payment providers, or for changes you or someone else makes to the site after handover.

13. Liability

My total liability for a project is limited to the fees you have paid me for it. I am not liable for indirect or consequential losses such as lost profit, lost business, lost data or lost goodwill.

Nothing on this page limits liability for death or personal injury caused by negligence, or for fraud or fraudulent misrepresentation.

Neither of us is liable for delay caused by something genuinely outside our control, provided the other is told promptly.

14. Changes to these terms

I may update this page from time to time. The version that applies to your project is the one in place when you signed your agreement, identified by the version number and date at the top of this page.

15. Law

These terms are governed by the law of England and Wales, and the courts of England and Wales deal with any dispute.

16. Questions

If anything here needs explaining, or you would like something changed for your project, email rosie.jaeger@petalandcode.com before we start.