Terms and Conditions

These Terms and Conditions apply to the Elmhurst Codecraft website and explain the general framework for its web development services. Visiting the website does not itself create a paid engagement. A project begins only after the parties agree in writing on its scope and commercial terms, and any agreed conditions for commencement are met.

An accepted project proposal, statement of work or service agreement may contain more specific terms. If a specific agreed term conflicts with this general website text, the specific agreement controls for that project, subject to rights that cannot lawfully be excluded.

A person who accepts a proposal must be legally able to contract and have authority to act for the client. Business representatives should identify the business they represent and the contact authorized to give instructions and approve work.

Clients must provide accurate project and billing information and notify us of material changes. We may decline work that is outside our service scope, requires unavailable resources or involves unlawful content or activity.

Our listed services are Business Website Development, Landing Page Development, Website Redesign, CMS & Website Integrations, and Website Maintenance. The displayed project prices apply to the limited scope described with each service, rather than to an unlimited build of any size or complexity.

Business Website Development is $3,500 for up to 6 core pages; Landing Page Development is $1,250 for 1 page with up to 7 sections; Website Redesign is $2,750 for up to 5 existing pages; CMS & Website Integrations is $950 for the stated content setup and up to 2 standard integrations; Website Maintenance is $250 per month for up to 2 hours of agreed work. Prices are in USD before any applicable taxes.

The accepted proposal confirms the exact pages, functions, revision rounds, assumptions and exclusions. Custom applications, custom API work, copywriting, major migrations, paid software, hosting and domain registration are included only if the written proposal expressly includes them.

Before work begins, the parties agree on the deliverables, the client materials needed, planned milestones, feedback rounds, payment stages and any relevant access requirements. A website enquiry or local brief confirmation is not acceptance of a proposal or a promise that a particular start date is available.

A proposal is valid for the period stated in it. If that period expires, pricing and availability may need to be reconfirmed. Instructions to proceed should come from the authorized client contact and should identify the proposal being accepted.

The on-page project brief checks entries in your browser and shows a completion message. It does not submit an enquiry, send an email, reserve a slot or create a support ticket. Its temporary reference does not establish receipt by the company or a service contract.

To begin a business discussion, contact projects@elmhurstcodecraft.com separately. Do not rely on a local confirmation as notice of a cancellation, complaint, contractual approval or other action that requires us to receive a communication.

The client is responsible for supplying approved text, logos, images and other materials by the agreed milestones. The client must hold the necessary rights and permissions for those materials and for the products, services and claims described on the website.

The client must provide appropriate access, appoint an available decision maker and review work at the agreed checkpoints. Legal notices, product claims, industry-specific statements and the lawful operation of a client’s business remain the client’s responsibility unless a separate professional service is expressly agreed.

Where access to personal information is necessary, the parties should agree on appropriate handling instructions. Clients should not send unrestricted administrative credentials or live customer datasets through a general project enquiry.

Included revision rounds are stated in the accepted proposal. A revision adjusts work within the agreed direction and scope. A new design direction, additional page, replacement content after approval, new integration or changed functional requirement may constitute a change in scope.

We explain the effect of a requested change on cost and timing before undertaking the additional work. Additional fees require approval. Feedback should be consolidated by the authorized client contact to avoid contradictory instructions and repeated rework.

A schedule is based on the agreed scope, access, content delivery and timely feedback. The proposal identifies the intended checkpoints or launch window. Estimates should not be interpreted as a guarantee of an outcome that depends on unavailable client materials or an external provider.

If a dependency is delayed or a material change is requested, the parties should document a revised schedule. We will communicate a known material delay and its expected effect. A client should disclose any genuinely time-critical event before accepting a proposal so that feasibility can be discussed.

Payment amounts, invoice due dates, deposits if any, and release milestones are set in the accepted proposal. The website itself does not take payment or collect payment card details. A quoted price does not automatically include taxes, domain renewal fees, hosting, application subscriptions or third-party transaction charges.

Where an external service is needed, its cost and account responsibility should be identified before purchase or activation. Clients should normally own business domains and production subscriptions in their own accounts. We do not purchase an unapproved paid subscription on a client’s behalf.

If an undisputed invoice is overdue, we may pause further work after reasonable notice, subject to the agreed contract and applicable law. Any disputed amount should be raised promptly with a clear explanation so that it can be reviewed.

The project includes a review against the agreed scope before launch or handover. The client should inspect the supplied work and identify specific in-scope issues during the review period stated in the proposal. Approval should be recorded through the agreed communication channel.

We address confirmed deviations from the agreed deliverables under the project terms. New preferences or functions discovered during review are handled as changes rather than defects. Launch occurs only after the necessary approvals, access and agreed payment conditions are satisfied.

The proposal should state any initial period for correcting defects in the delivered work. This is distinct from ongoing maintenance or later changes to content, platforms or external services.

The project agreement specifies ownership of the final deliverables and when any agreed transfer takes effect, including whether it depends on full payment. Client-supplied materials remain the client’s property or the property of their licensors.

Pre-existing tools, general development techniques, reusable code and third-party materials are not automatically transferred as exclusive property. Open-source software, fonts, platforms, plugins and stock assets remain subject to their respective licenses. Any limits relevant to future editing or redistribution should be explained in the handover.

The client should receive the agreed production access and deliverable files. A project does not grant either party permission to publish confidential material or claim the other party’s work as its own. Any public project credit or portfolio use requires the relevant permission.

The published maintenance package covers up to 2 hours of agreed work per month on a supported website. Examples include minor content changes, routine update checks and review of reported bugs. Unused hours do not roll over unless a written agreement states otherwise.

Major redesigns, new pages, custom development, emergency response, continuous monitoring and third-party subscription fees are outside the standard package. Availability, communication method and any response commitments are confirmed in the maintenance agreement. There is no implied 24-hour support service.

A maintenance arrangement has its own start, billing and cancellation terms. A one-time build does not automatically enroll a client in monthly maintenance.

Information designated confidential, or reasonably understood to be confidential in the project context, should be used only for the relevant business purpose and disclosed only to people or providers who need it for that purpose. Information already public, independently developed or lawfully obtained without restriction is not treated as confidential solely because it also appears in a project.

You must not use this website to distribute malicious software, attempt unauthorized access, interfere with its operation or submit content you are not permitted to share. Normal reference and browsing are allowed; copying the entire site or branding for another business requires permission.

A website may depend on hosting, a CMS, a browser, an application or an integration provider. Those providers control their own services and terms. An external change can affect functionality after launch and may require separately scoped work.

We do not promise a specific sales volume, search ranking, advertising result or uninterrupted availability from a website build. Performance and accessibility work are assessed against the requirements actually agreed in the proposal. No broad certification is implied by a general service description.

Cancellation and complaints are handled under the Cancellation and Complaints Policy and any specific project agreement. The parties should distinguish completed work, unstarted work and approved third-party commitments when calculating a cancellation settlement.

If you believe delivered work does not meet the agreed scope, contact us with the project reference and specific examples. We aim to review the issue and agree on an appropriate remedy. These terms do not remove consumer or other statutory rights that cannot lawfully be waived.

Each party remains responsible for obligations it has accepted and for its own unlawful conduct. Any limitation of liability must be set out in the accepted project agreement and applied only to the extent permitted by law. These website terms do not exclude liability that applicable law prohibits excluding.

The parties should first attempt to resolve a disagreement through direct written discussion and an exchange of the relevant records. The project agreement should identify the applicable law and dispute process. Where no specific choice has been agreed, the law and forum are determined by applicable legal rules; this page does not impose compulsory arbitration on a website visitor.

We may update the website terms to reflect changes in services or the website. The last updated date identifies the posted version. A later website update does not silently rewrite an already accepted project agreement.

If a material change to an active service is proposed, it should be communicated and agreed where required. If one provision cannot be enforced, the remaining provisions continue to apply to the extent permitted by law.