Terms of Service
Last updated
About these terms
These terms describe how LexoraTech, a software development studio based in Sri Lanka, provides websites, custom software, and workflow automation. They apply alongside the written scope or engagement agreement for your project. Where a signed project agreement conflicts with these terms, that agreement takes precedence. Mandatory legal rights are unaffected.
Browsing this website or sending an enquiry does not commission a project. An engagement begins when both parties agree the scope and commercial terms in writing and any agreed initial payment is received.
Scope and milestones
The Lexora Working System is scoped around a defined business workflow. Before development, we agree deliverables, integrations, responsibilities, milestones, price, acceptance checks, and delivery assumptions. A post-launch review and any ongoing support are defined in the project scope.
Features, integrations, content, migration, subscriptions, and support are included only where stated in the agreed scope. Changes are assessed and agreed in writing, including any effect on price or schedule, before the additional work begins.
Pricing and payment
Project prices, currency, invoice due dates, payment method, applicable taxes, and any transfer or third-party charges are specified in your quotation or agreement. We issue invoices for the agreed payments. Complete business systems are quoted individually in fixed-price milestones.
The separate 5-Day Build is $1,500 USD for its agreed scope, with 50% payable on scope sign-off and 50% on delivery. This price does not apply to every website or Working System engagement. If delivery does not meet the agreed scope, the second half is not due until that scope is delivered.
Delivery and client responsibilities
You are responsible for providing the agreed content, permissions, access, test inputs, and timely decisions, and for having the rights to materials supplied for the project. Please use the agreed secure channels for credentials and confidential information.
For the 5-Day Build, the five working days begin once the scope is approved and the required access and inputs are ready. Other engagements follow their agreed milestones. We communicate the effect of delayed approvals, unavailable integrations, provider outages, or other dependencies on delivery dates.
Demonstrations and acceptance
Working System engagements include working demonstrations during development and a walkthrough against the agreed acceptance checks before handover. Acceptance requirements and any review period are recorded in the project agreement.
A defect is an agreed feature that is missing or does not operate according to the approved scope or acceptance criteria. New requirements and changes to previously approved work are assessed separately. Report an issue with enough detail for us to reproduce and investigate it.
Ownership and third-party services
Project source code is maintained in your repository from the first commit. Ownership of the bespoke code delivered for your project transfers on final payment, subject to the project agreement. Handover includes the agreed documentation, account access, and training.
Third-party software, open-source components, fonts, stock assets, and external services remain subject to their own licences and terms. Their subscription, usage, hosting, and renewal fees are distinct from our development charges unless expressly included in the quote.
Support and post-launch review
The 5-Day Build includes 30 days of defect fixes after handover for the agreed scope. For other engagements, warranty, support, review dates, and maintenance responsibilities are stated in the written scope.
New features, changes made by others, and issues arising from external service changes may require a separate quote. A review of actual usage does not guarantee a particular increase in sales, search rankings, conversion rate, or time saved.
Confidentiality and personal data
We use confidential project information to deliver and support the engagement and disclose it only to authorised people and providers needed for that work, or where legally required. Any additional confidentiality and data-processing obligations are agreed in writing.
Our Privacy Policy describes website enquiries, assistant use, and related information handling. Client-system access, permitted processing, retention, and handover or deletion instructions should be specified in the project agreement.
Pausing or ending an engagement
Cancellation, suspension, payments for completed work, any refunds, and handover arrangements follow the signed project agreement. Contact us promptly if you need to pause or end a project so that outstanding work and responsibilities can be recorded in writing.
Liability
To the extent permitted by applicable law and unless the signed agreement states otherwise, our liability is limited to the fees paid for the engagement giving rise to the claim. We exclude liability for indirect or consequential loss to the extent permitted by law. Nothing in these terms excludes liability or rights that cannot lawfully be excluded.
Updates
We may update these website terms and show the revision date above. Changes to an existing engagement require the agreement of the parties under its written change process; a website update does not automatically rewrite a signed project agreement.
Contact
Questions about terms of service can be sent to hello@lexoratech.com.