Everything in writing before we start.

01What these terms cover

These terms apply to evancode.dev and every service Evan Code provides: websites and stores, apps, systems and dashboards, learning platforms, accounting systems and automation.

02Requests, consultations and proposals

• Sending the project form is free and commits neither side; consultations are paid at the price shown on the booking page.
• Once we understand the need, we send a written proposal with scope, stages, timeline, cost and payment schedule.
• Proposals are valid for 14 days unless stated otherwise.
• Prices on the site are planning ranges; the binding price is the one in the approved proposal.

03When the agreement starts

The agreement starts when you approve the proposal in writing and pay the first instalment. If documents conflict, a signed contract comes first, then the approved proposal and agreed change requests, then these terms.

04Scope and changes

• The scope is exactly what the approved proposal lists.
• Changes within the review rounds in the proposal are included.
• Anything added or changed outside the scope is costed and timed in writing, and we don't build it without your approval.

05Design and revision rounds

• Design is custom in every package: we build it from scratch in your brand and don't rely on ready-made templates.
• The price includes two revision rounds per stage (design, and each build stage).
• Extra revisions beyond those two, or changes to an agreed idea, are costed in writing before we make them.

06Prices and payments

• The first payment is 30% of the project value, due before we start.
• The rest is split across stages in the proposal; each payment falls due after a stage you can review.
• Prices exclude taxes and third-party fees unless stated.
• We fix the price in a reference currency so exchange-rate moves don't change it mid-project.

07Late payment

If a due payment is more than 7 days late after a written reminder, we may pause work and delivery dates shift by the length of the pause. Work resumes as soon as payment arrives.

08Your responsibilities

• Provide content, images, data and access on the agreed dates.
• Review each stage and send feedback within 5 working days.
• Make sure what you give us doesn't infringe anyone's rights or the law.

Late inputs or feedback move the schedule by the same amount.

09Accounts and third-party services

Domains, hosting, store accounts, WhatsApp Business, payment gateways and app-store accounts are registered in your name and email when they're part of the project. Their fees are paid to the providers or listed separately, and we're not responsible for their outages or price changes.

10Ownership and code handover

• Once paid in full, the source code, designs, database and content of your project are yours.
• We hand over the code in a repository on your account (such as GitHub) with run and deploy instructions.
• You can move the project to another developer at any time without our approval.
• We keep the right to reuse our general tools and libraries that aren't specific to your project.

11Who builds your project

The Evan Code team builds your project directly, and you have one named person to talk to from kickoff until after handover. You can follow the code yourself in a repository on your account while we build, not only at handover.

12Confidentiality

We treat your idea, data and project as confidential and never show your name, screens or details without written permission. We sign an NDA on request.

13Use of AI tools

We may use AI tools to write and review code faster; everything they produce is reviewed and tested by our team before delivery. We never put passwords, keys or your customers' personal data into them.

14Review and acceptance

Each stage is delivered on a test version you can try. If we receive no feedback within 10 working days of delivery, the stage is considered accepted. Final acceptance happens at launch or full handover.

15Testing, security and backups

• We test each stage before delivery and the whole project on phone and desktop before launch.
• Every project gets the security basics: encrypted connections (HTTPS), role-based permissions, and protected forms and sign-in.
• For systems that store data we set up backups and a restore process, detailed in the proposal.
• Independent penetration tests or managed hosting are add-ons listed in the proposal when needed.

16Post-launch warranty

We fix any bug in what we delivered free of charge, for a period starting at launch:

• Economy packages: 30 days.
• Professional packages: 60 days.
• Custom projects: 90 days.

We respond to any issue that takes the site or system down within 24 hours on working days and start fixing it right away.

A bug is something working differently from what we agreed. New features, changes to how something works, and problems caused by someone else editing the code aren't covered.

17Support after the warranty

After the warranty, maintenance and ongoing development are available under a separate agreement, hourly or as a monthly plan.

18Paid technical consultations

• A standard consultation is a 30-minute session, and a full consultation is a 60-minute session with written recommendations within 24 hours. Each costs the price shown on the booking page when you book.
• It's paid by transfer before the call, and the slot is confirmed once payment arrives.
• It's a standalone service that doesn't commit you to hiring us; the advice is yours to use with anyone.
• The intro call about your project (30 minutes) is always free.

19Security scans

We only scan sites and systems the client owns, or has written permission from the owner to test, after an authorisation that sets the scope and timing is signed. Any vulnerability we find is kept confidential and never used or shared outside the report delivered to the client.

20Cancellation and refunds

The cancellation and refund policy sets out what happens if a project is cancelled and how refunds are calculated.

21Projects we decline

We decline any unlawful or harmful project, such as fraud, gambling, breaking into others' systems, collecting data without consent or illegal content, and may stop any project that turns out to be one.

22Limitation of liability

Our liability for any project is limited to the amounts you paid us for that project. We're not liable for indirect losses, third-party outages or damage from using the system in ways we didn't agree.

23Resolving disputes

We aim to resolve any dispute directly within 30 days. If that fails, it goes to the forum and law named in the contract.

24Changes to these terms

We may update these terms. Ongoing projects stay on the version in force when they were agreed unless both sides agree otherwise.