These Terms of Use & Service Terms ("Terms") govern access to the Archex website at https://www.archexweb.in and the general basis on which Archex ("Archex", "we", "us" or "our") provides software engineering, digital product development, AI integration and related technology services.
By accessing this website, you agree to comply with the provisions that apply to website use. If you engage Archex for professional services, the additional service terms below apply together with the relevant written proposal, Statement of Work (SOW), Master Services Agreement (MSA) or other agreement accepted by both parties.
1. About Archex
Archex provides digital product and software engineering services, including custom software development, AI integration and intelligent automation, web and mobile development, ecommerce solutions, business-system integrations, application modernization, quality engineering and ongoing technical support.
The precise services offered for an individual project will be described in the applicable proposal or project agreement.
2. Use of this website
You may use this website to learn about Archex, explore its services and submit legitimate business enquiries.
You agree not to:
- Use the website for unlawful, fraudulent or misleading purposes.
- Attempt to gain unauthorized access to the website, its infrastructure or related systems.
- Interfere with the website's availability, security or normal operation.
- Introduce malicious code or attempt to compromise the website.
- Copy, reproduce or commercially exploit website materials without permission, except where permitted by applicable law.
We may restrict access where reasonably necessary to protect the website, its users or our systems.
3. Website information and service descriptions
The information on this website is provided for general informational purposes. Service descriptions, technical explanations, examples and illustrations are intended to help visitors understand the types of work Archex may undertake. They do not, by themselves, constitute a binding proposal, technical specification, delivery commitment or guarantee of a particular outcome.
We make reasonable efforts to keep website information accurate and current, but we do not guarantee that every page or description will always be complete or up to date.
4. Enquiries, estimates and proposals
Submitting a contact form, project enquiry or other communication does not automatically create a client relationship or require Archex to accept an engagement.
Any preliminary discussion, indicative estimate or website information is subject to further assessment. Before work begins, the parties should agree in writing on the applicable project scope, deliverables, fees, timelines, assumptions and responsibilities.
A proposal or estimate is not binding beyond the period and conditions expressly stated in it.
5. Project scope and changes
Each professional engagement should be governed by a written proposal, SOW, MSA or other mutually accepted project agreement.
The applicable agreement should describe, as relevant:
- Project objectives and requirements.
- Features, deliverables and exclusions.
- Technical scope and integrations.
- Milestones and delivery expectations.
- Fees and payment arrangements.
- Acceptance criteria.
- Responsibilities of each party.
Requests that materially change the agreed scope may require revised fees, timelines or delivery arrangements. Such changes should be reviewed and agreed in writing before additional work is undertaken.
6. Client responsibilities
Clients are expected to:
- Provide accurate requirements, information and project materials.
- Appoint an appropriate contact for decisions and approvals.
- Provide authorized access to relevant systems, environments and services.
- Ensure that materials and data supplied to Archex may lawfully be used for the project.
- Review deliverables and provide feedback within agreed timeframes.
- Maintain appropriate backups and access controls for their own systems.
- Pay agreed fees according to the applicable project agreement.
Delays caused by missing information, access, approvals or other client dependencies may affect delivery schedules. The parties should discuss and document any resulting changes.
7. Fees and payments
Fees, payment schedules, taxes, reimbursable expenses and any applicable deposits will be set out in the relevant proposal, invoice or project agreement. Unless otherwise agreed in writing, payment obligations are governed by those project-specific documents.
Any changes to fees or payment arrangements should be communicated and agreed in writing.
8. Intellectual property and ownership
Ownership and permitted use of project deliverables should be expressly defined in the applicable project agreement. That agreement should distinguish between:
- Custom deliverables created specifically for the client.
- Materials, software, tools and components owned or developed by Archex before the engagement or independently of it.
- Open-source and third-party software.
- Client-provided materials, data and intellectual property.
No transfer or licence of intellectual property should be assumed beyond the rights expressly agreed by the parties.
Unless separately authorized in writing, Archex will not assume permission to publish confidential client materials, project details, screenshots or the client's identity in its portfolio or marketing.
9. Third-party services and software
Projects may depend on third-party platforms, cloud providers, APIs, libraries, payment services, content-management systems or other external products. Such services may be governed by separate terms, licences, pricing and usage restrictions.
Archex does not control independent third-party providers and cannot guarantee their uninterrupted availability, continued functionality, pricing or future compatibility. Any project-specific responsibilities for selecting, configuring, licensing or maintaining third-party services should be documented in the relevant agreement.
10. AI and automated systems
Some services may involve artificial intelligence, machine learning, language models, automated workflows or other probabilistic systems.
AI-generated outputs may be inaccurate, incomplete, inconsistent or unsuitable for a particular purpose. Their quality may depend on the available data, model behaviour, configuration and third-party services.
Where appropriate, systems should include evaluation, monitoring, validation and human review. Clients remain responsible for determining whether outputs are suitable for their intended business decisions and uses.
The parties should agree on relevant data permissions, security requirements, human oversight and operational responsibilities before deploying AI-enabled systems.
11. Confidentiality
Confidential information shared during a professional engagement should be handled in accordance with any applicable NDA, MSA or project agreement.
Where no separate confidentiality agreement exists, the parties should agree on appropriate confidentiality obligations before exchanging sensitive business, technical or personal information. Confidentiality arrangements should address permitted use, access, disclosure, protection and any required return or deletion of information.
12. Delivery, testing and acceptance
Project milestones, testing responsibilities, acceptance criteria and handover requirements should be defined in the relevant project agreement.
Clients should review submitted deliverables and communicate any material issues within the agreed review period.
Any warranty period, defect correction obligation, deployment responsibility or post-delivery support arrangement should be expressly documented rather than assumed.
13. Maintenance and support
Ongoing maintenance, monitoring, hosting, incident response, updates and technical support are not automatically included in every development engagement.
Where these services are required, their scope, availability, response expectations, fees and responsibilities should be agreed separately in writing.
14. Suspension and termination
The conditions for suspension or termination of a professional engagement should be specified in the applicable project agreement. That agreement should address outstanding fees, work completed, committed third-party costs, access to systems, transfer of deliverables and the return or handling of confidential information.
Archex may restrict or suspend access to its website where reasonably necessary for security, maintenance, legal compliance or protection against misuse.
15. Warranties and disclaimers
To the extent permitted by applicable law, website content is provided for general information without a guarantee that the website will always be uninterrupted, error-free or suitable for every purpose.
Any warranties relating to professional services, software deliverables, performance, security, compatibility or defect correction should be set out in the applicable project agreement.
Nothing in these Terms is intended to exclude a right or protection that cannot lawfully be excluded.
16. Limitation of liability
The allocation and limitation of liability for a professional engagement should be set out in the applicable MSA, SOW or other project agreement.
Any limitation should be reasonable, clearly drafted and reviewed for compliance with applicable law. It should address the relevant categories of loss, any agreed financial cap and any exceptions required by law.
Nothing in these Terms excludes liability to the extent that such exclusion is prohibited by applicable law.
17. External links
This website may contain links to third-party websites or services for convenience or reference. Archex does not control those external resources and is not responsible for their content, availability, security or privacy practices.
Accessing third-party websites is at your discretion and subject to their own terms.
18. Changes to these Terms
We may update these Terms to reflect changes to the website, our services or applicable requirements. The revised version will be published on this page with an updated revision date.
Changes to an existing professional engagement will be governed by the applicable project agreement and any mutually agreed amendments.