Draft prepared 10 October 2026. These terms are not legally approved or in effect. Commercial and legal clauses identified below require company approval before adoption; this page does not amend an existing customer contract.
1. Service identity and scope
Mentrox OneHR is developed by Mentrox Digital Solutions for HR and workforce administration. The contracting legal entity, registration details and registered address require verification before these terms are adopted.
The agreed order or customer contract should identify enabled modules, users/access scope, implementation arrangements and any custom work. Planned production or specialized maintenance functionality is not included merely because a public page discusses it.
2. Registration and authorized business use
Proposed account terms: a customer supplies accurate company and administrator information and authorizes users who may act for it. Accounts are for legitimate business administration and permitted employee self-service. Users must protect credentials and report suspected unauthorized access.
Customer approval required: the authority for accepting the agreement, account eligibility, administrator responsibilities and procedures for recovering or transferring account ownership must be set out in the final contract.
3. Subscription and billing
The application supports subscription and approved company/demo access states. The written quote or order should define the modules, term, charges, currency, taxes, payment method and access period. No universal free trial, fixed fee or unlimited-user commitment is created by this page.
Company approval required: billing dates, renewal method, price-change notice, cancellation, refunds, overdue charges and post-expiry data access. Technical access expiry is not a complete contractual termination or deletion policy.
4. Customer and employee data responsibilities
Proposed customer terms: customers are responsible for the accuracy and lawful provision of company/employee information, approved HR policies and user permissions. They should provide required notices and collect only information needed for the lawful business process.
Payroll configuration, statutory eligibility, rates, filings and payment execution need qualified customer review. A saved payslip is not proof of bank settlement. Historical changes and unpaid-claim adjustments should retain the authorized evidence and audit history.
5. Intellectual property and customer records
Proposed allocation: the provider retains rights in its software, branding and supplied product materials; the customer retains its rights in the records it lawfully supplies. Access to the software should be limited to the agreed subscription and authorized users.
Legal approval required: the precise licence grant, restrictions, customer-data processing permission, feedback terms, third-party component obligations and treatment of custom developments. This draft does not claim ownership of employee personal information.
6. Acceptable use
Proposed acceptable-use restrictions include credential sharing outside authorized access, attempted access to another company’s data, malicious uploads, interference with the service, unlawful processing and reverse engineering where lawfully restrictable.
Customer and legal approval required: investigation, suspension and notice procedures, emergency intervention grounds and appeal/reinstatement arrangements. Restrictions must be assessed under applicable law.
7. Availability, support and AI assistance
The service depends on its deployed application, infrastructure and configured providers. No uptime percentage, support response time, recovery objective or uninterrupted-availability guarantee is established by the inspected project. Any SLA must be separately agreed.
AI responses may be incomplete or incorrect. Supported state changes require the applicable confirmation and server authorization. Users must review important information against the underlying records; the assistant is not legal, tax or employment advice.
8. Termination and data handling
Company/legal approval required: termination grounds, notice and cure periods, the effects on outstanding amounts, and any continued duties. The final agreement must define customer export opportunities, retention/deletion and backup treatment.
An inactive account or expired subscription does not by itself establish irreversible deletion. Preserve financial audit history where required and reconcile authorized payment records before making destructive changes.
9. Warranties and limitations of liability
Legal approval required: any warranty standard, exclusions, liability cap, excluded losses, indemnities and exceptions for matters that cannot lawfully be limited. No monetary cap, refund remedy or waiver is invented in this draft.
The approved wording must reflect the actual service, negotiated customer agreement and applicable mandatory law. Product documentation should not be read as an absolute accuracy, security or statutory-compliance guarantee.
10. Governing law and dispute resolution
Proposed for legal review: assess Indian law as the governing-law basis for this India-facing service. The final choice of law, courts/venue, dispute escalation and any arbitration arrangement require explicit company and legal approval. No unverified city, tribunal or arbitration term is selected here.
The contract should identify how formal notices are served and which contact details are legally effective. The published general/support emails remain enquiry channels until that notice process is approved.
11. Changes, approval and contact
Before adoption, approve the contracting identity, commercial terms, support commitments, liability/warranty wording, termination/data arrangements, governing law and dispute process. Then publish an approved effective date and an agreed change-notification mechanism.
For questions about this draft, contact mentroxdigitalsolution@gmail.com. It is excluded from search indexing until legal/business review is complete and an authorized policy replaces it.