1. Contract documents
For a paid engagement, the binding agreement should consist of the accepted proposal, statement of work, order form or signed contract, together with any documents expressly incorporated there. If those project-specific documents conflict with these general terms, the project-specific documents prevail for that engagement.
2. Informational website
The public website, demonstrations, assistant, FAQs, portfolio descriptions, pricing indications and Guidance configurator are provided for general information and early project exploration.
They are not an automatic offer, acceptance, final specification, professional advice or commitment to deliver. Using the website or sending an enquiry does not create a client relationship, exclusivity obligation or duty to begin work.
3. How a project becomes binding
A project begins only when:
- both parties agree the scope, deliverables, assumptions, timetable, fees and other material conditions in writing;
- the proposal or contract is accepted using the method stated in that document; and
- any required deposit, onboarding information or access is received.
Until then, discussions, prototypes and estimates may be changed or withdrawn. No person may bind either party unless authorised to do so.
4. Scope, estimates and change control
Deliverables, exclusions, dependencies, acceptance criteria, milestones and support are defined in the accepted proposal or contract. Website or Guidance estimates are indicative and subject to discovery and technical validation.
Fees and timing may change when assumptions prove incorrect, requirements change, third-party systems impose constraints, client inputs are delayed or additional work is requested. Material changes should be documented through a written change request, revised proposal or agreed project record before the additional work begins.
Unless the project document says otherwise, dates are good-faith estimates rather than guaranteed deadlines. Both parties should promptly communicate risks that may affect delivery.
5. Responsibilities
Luvalia's responsibilities
- perform the agreed services with reasonable professional care and skill;
- communicate material blockers and seek approval for significant scope changes;
- use client materials only as needed for the engagement; and
- deliver the agreed outputs and handover items subject to payment and the project terms.
Client responsibilities
- provide timely, accurate requirements, decisions, content, access and feedback;
- appoint an authorised contact who can approve work;
- ensure supplied materials, instructions and data may lawfully be used;
- review deliverables and report material issues within the agreed review period; and
- pay fees and third-party costs when due.
Delays or rework caused by missing, late or inaccurate client inputs may require an updated schedule and fee.
6. Intellectual property and licences
The accepted proposal must state which deliverables transfer to the client, when transfer occurs and what licence applies. Unless expressly agreed otherwise:
- the client retains ownership of materials it supplies and grants Luvalia a limited licence to use them for the project;
- Luvalia retains ownership of pre-existing tools, know-how, methods, reusable components, templates and general-purpose code;
- third-party and open-source materials remain subject to their own licences; and
- rights in custom final deliverables transfer or are licensed only after full payment of the relevant fees.
Portfolio or case-study use requires the permission described in the project agreement and must respect confidentiality. No public disclosure should be assumed where the agreement does not permit it.
7. Third-party platforms, licences and costs
Projects may depend on hosting providers, domains, app stores, APIs, AI models, payment services, messaging tools, software licences or other third-party systems. Unless the proposal includes them, their fees, taxes, usage charges and account obligations are the client's responsibility.
Third-party services are governed by their own terms and may change, suspend features, increase prices or experience outages. Luvalia is not responsible for a third party's acts or omissions but will use reasonable care when selecting, integrating or recommending providers within the agreed scope.
8. Confidentiality and data protection
Each party should protect non-public business, technical and commercial information received from the other and use it only for the engagement. Confidentiality obligations, exceptions, duration and permitted disclosures should be set out in the proposal, contract or a separate non-disclosure agreement.
Each party is responsible for its own compliance with data-protection law. If Luvalia processes personal data on the client's behalf, the parties must put an appropriate data-processing agreement and security instructions in place before that processing begins.
Credentials and production data should be shared through agreed secure methods, not ordinary project messages where avoidable. The website's own privacy practices are described in the Privacy Policy.
9. Fees, payment, suspension and cancellation
Currency, taxes, deposit, milestone payments, invoicing schedule, expenses, late-payment consequences and accepted payment methods are governed by the accepted proposal or contract. No public website price overrides an individual written quote.
If payment is overdue, Luvalia may pause work after reasonable notice where legally permitted. The schedule may be adjusted to reflect the pause and resource availability.
Cancellation, rescheduling, refunds, non-refundable deposits, payment for work completed and committed third-party costs must follow the accepted proposal or contract. Any mandatory consumer withdrawal or cancellation right remains unaffected and must be addressed specifically if the final service model serves consumers.
10. Warranties and liability
Luvalia warrants that agreed services will be performed with reasonable professional care and skill. Any defect-reporting period, correction process, service level or additional warranty must be stated in the project documents.
Unless expressly agreed, Luvalia does not warrant that deliverables will produce a particular commercial result, remain compatible with every future third-party change, operate without interruption or be free from every defect. AI-assisted and automated systems may require human review, monitoring and appropriate safeguards.
Any liability exclusions, indirect-loss exclusions and financial cap must be agreed in the final contract and assessed against the operator and client context. Nothing may exclude liability that applicable law does not allow to be excluded, including mandatory consumer protections and liability for fraud or wilful misconduct.
11. Termination and handover
Termination rights, notice periods and cure periods are governed by the accepted project documents. A party should generally be able to terminate for a material breach that remains uncured after reasonable written notice, and immediately where continued performance would be unlawful.
On termination, the client must pay for accepted work performed and approved non-cancellable commitments up to the effective date, subject to applicable law and the contract. Luvalia should provide the handover items paid for and reasonably available, while each party returns or deletes confidential material as agreed.
Clauses that by nature should continue—such as payment, confidentiality, intellectual property, liability and dispute provisions—survive termination.
12. Changes and contact
These website terms may be updated prospectively. Changes do not rewrite an already accepted project agreement unless both parties agree in writing or the agreement itself provides a lawful update mechanism.
Questions may be sent to contacto@luvalia.com.