NUMEXS / LEGAL / 03
Terms of Service
How NUMEXS IT consulting, implementation, handoff, and support engagements are scoped and delivered.
Formation and service scope
NUMEXS Corp offers Business IT Consultation, Business Software Setup, Workflow Automation, API & Application Integration, Custom Business Dashboard, Cloud Workspace Setup, AI Tools Integration, Technical Documentation, Remote Technical Support, IT Systems Optimization, and Ongoing IT Support. A website enquiry is an invitation to discuss work, not an acceptance of a project. The service relationship starts when an identified scope and price are agreed.
A written proposal or statement of work should identify the systems, functions, deliverables, assumptions, exclusions, client responsibilities, schedule, and applicable support coverage. Descriptions on the website are broad service summaries. A project may require a feasibility review before a specific integration or technical result can be promised.
Discovery and client information
The client should provide accurate descriptions of its workflow, relevant system versions, subscriptions, existing configuration, data sources, and desired result. A designated contact should be authorized to make decisions and approve access, tests, and changes. NUMEXS may rely on information supplied by the client when preparing a scope or performing the work.
If a platform does not offer the assumed API, permission, data export, or license feature, the parties should reassess the plan. An undisclosed restriction or a material change to the environment can affect price and schedule. The client remains responsible for its business policies, the quality and rights of its data, and lawful use of its systems.
Access and project materials
Access to client accounts or remote systems should be authorized, suitable for the task, and limited to the agreed period and functions. The client should use its own account administration procedures to grant and revoke access and should avoid sending passwords through ordinary enquiry channels. Temporary credentials or approved remote access methods can be arranged in the project scope.
Before changes that could affect data or operations, the client should maintain an appropriate backup or recovery path unless backup work is expressly included in the scope. NUMEXS should be informed about maintenance windows, production restrictions, security controls, and other users or vendors who may change the same system during the engagement.
Implementation and changes
NUMEXS performs the services identified in the accepted scope using the agreed environment and client-authorized tools. A workflow or dashboard depends on specific input data and business rules; an integration depends on vendor interfaces and permissions. The work may include configuration, mapping, documentation, walkthroughs, or tests as described in that scope.
A requested addition, newly discovered dependency, platform change, or different acceptance criterion can require a written change to price, timing, or deliverables. NUMEXS should explain the impact and seek agreement before performing chargeable out-of-scope work. A minor clarification within the existing scope does not automatically become a separate project.
Testing, acceptance, and handoff
The parties should define representative test cases and an authorized reviewer. NUMEXS can demonstrate or document the agreed configuration, while the client checks that the result matches its business rules and sample data. Issues within the accepted scope should be reported with sufficient detail for investigation and resolution.
Final acceptance, any review period, and any included revision rounds should be specified in the project agreement rather than assumed from the website. Handoff may include administration notes, configuration details, or a walkthrough if listed as a deliverable. The client remains responsible for operating its accounts and keeping third-party subscriptions active after handoff.
AI, dashboards, and third-party systems
AI-assisted output can be incomplete, inaccurate, or unsuitable for a particular use. A client should define appropriate data restrictions, human review, and approval before relying on such output. NUMEXS does not make an AI model's output a substitute for a client's own judgment, compliance review, or professional advice in a regulated field.
Dashboards reflect the available source data, definitions, timing, and platform behavior. Cloud services and integrations remain subject to vendor terms, outages, rate limits, and product changes. NUMEXS can configure agreed connections but cannot guarantee the independent performance or continued availability of a third-party provider.
Fees, third-party costs, and support
The published service fees are in US dollars; Remote Technical Support is $150 per hour and Ongoing IT Support is $900 per month. The accepted scope governs the actual billing schedule, covered tasks, and any authorized extras. Third-party licenses, cloud usage, and vendor charges are separate unless explicitly included.
An ongoing support arrangement should define covered systems, request channels, hours or response expectations if any, monthly boundaries, and the process for work beyond coverage. The website does not promise 24-hour monitoring, instant response, or a service-level guarantee. See the Payment, Cancellation & Refund, and Remote Support policies for related general terms.
Ownership, confidentiality, and limits
Each party retains its pre-existing materials, methods, and systems. Rights to use custom deliverables after payment, third-party components, and any source files should be stated in the signed scope. A client does not acquire ownership of a vendor's platform merely because NUMEXS configures it.
Project information should be handled with appropriate confidentiality and access controls under the agreed terms. Any specific liability allocation, warranties, indemnities, data-processing duties, or governing law should be set in a contract reviewed for the particular engagement; this public description does not silently add unagreed commercial terms.
Ending an engagement
A project may be paused or ended as described in the accepted agreement and the Cancellation & Refund Policy. On termination, the parties should account for work performed, committed third-party costs, deliverables completed, and the return or removal of authorized access. The client should promptly rotate or revoke project credentials under its own account procedures.
A support subscription is distinct from a one-time project. Its renewal, cancellation timing, coverage, and outstanding requests should be confirmed in the applicable written arrangement. Questions about a current engagement should refer to its accepted scope and the contact details below.