Legal Center

Pilot Program Terms

Terms for evaluating Ziantrix HRMS during pilot, beta, early-access, proof-of-concept, and limited enterprise onboarding programs.

Last updated: May 25, 2026Security OverviewPrivacy Policy
Pilot Program Terms

Pilot programs are collaborative, evolving evaluations of Ziantrix HRMS. Pilot customers should expect feature iteration, reasonable-effort support, careful review of AI-assisted outputs, and customer responsibility for critical HR, payroll, compliance, and employment decisions.

1. Introduction and Scope

These Pilot Program Terms govern participation in pilot, beta, preview, early-access, proof-of-concept, evaluation, or limited deployment programs for Ziantrix HRMS provided by Ziantrix AI Technologies Private Limited ("Ziantrix", "we", "us", or "our").

These terms are intended to set practical expectations for customers evaluating an actively evolving AI-assisted HRMS and workflow platform. They supplement our Terms of Service and any signed pilot agreement, subscription agreement, data processing agreement, order form, or written statement of work.

Written agreements control

If a signed agreement between Ziantrix and a pilot customer conflicts with these public Pilot Program Terms, the signed agreement controls for that customer.

2. Purpose of the Pilot Program

The pilot program allows selected organizations to evaluate Ziantrix in realistic HRMS, payroll-adjacent, employee support, workflow automation, and AI-assisted operational contexts before broader production adoption.

  • Validate fit for employee operations, HR support, onboarding, attendance, leave, document workflows, and payroll calculation support.
  • Evaluate customer-specific workflows, access models, knowledge sources, integrations, and review processes.
  • Collect structured feedback from HR, payroll, finance, IT, managers, employees, and administrators.
  • Improve product reliability, usability, governance, and operational maturity before broader deployment.
  • Identify configuration, onboarding, and support needs for enterprise readiness.

3. Eligibility and Participation

Pilot participation is limited to organizations accepted by Ziantrix. We may consider operational fit, implementation readiness, data readiness, workflow scope, support capacity, integration complexity, and mutual pilot goals when accepting or continuing a pilot.

  • Customers must designate appropriate administrative, HR, payroll, IT, and business contacts.
  • Customers must provide accurate information needed to configure and evaluate the pilot.
  • Customers are responsible for ensuring Authorized Users follow these terms and internal policies.
  • Pilot access may be limited by feature scope, user count, data volume, integration availability, geography, support capacity, or agreed evaluation period.

4. Pilot Nature and Evolving Functionality

Pilot programs are collaborative and evolving. Some functionality may be incomplete, change rapidly, be reconfigured during evaluation, be subject to usage limits, or be removed or replaced as the platform matures.

  • Pilot workflows may be adjusted based on customer feedback, product learnings, security needs, reliability needs, or implementation constraints.
  • Screens, terminology, reports, AI-assisted behavior, notifications, integrations, and workflow steps may change during the pilot period.
  • Pilot functionality may not represent final generally available functionality.
  • Ziantrix may prioritize changes based on safety, reliability, customer impact, and product direction.

5. Feature Availability and Experimental Features

Pilot features may include experimental, preview, beta, or limited-release functionality. These features are provided for evaluation unless a written agreement says otherwise.

Feature type
Pilot expectation
Core pilot workflows
Configured around the agreed pilot goals and available platform capabilities.
Experimental features
May change, be limited, produce errors, or be discontinued before general availability.
Integrations
May depend on customer systems, third-party availability, credentials, configuration, and scoped implementation effort.
AI-assisted features
May require human review and may behave differently as knowledge sources and workflows improve.
Reports and analytics
May be refined over time and should be validated before business-critical use.

6. Customer Responsibilities

Customers remain responsible for how the pilot is configured, used, reviewed, and governed within their organization. Ziantrix provides tools and support, but customers retain responsibility for operational HR, payroll, compliance, legal, and employment decisions.

  • Provide appropriate notices, consents, legal bases, and internal approvals before submitting employee or organizational data.
  • Configure roles, access, workflow ownership, review steps, and escalation paths appropriately.
  • Validate outputs before relying on them for payroll, compliance, HR, finance, legal, or employee-impacting decisions.
  • Use realistic but appropriate pilot data, avoiding unnecessary sensitive data unless needed for the agreed pilot scope.
  • Maintain downstream systems, records, approvals, filing, and payment processes outside Ziantrix where applicable.
  • Train pilot users to understand that pilot outputs may evolve and should be reviewed carefully.

7. AI-Assisted Workflow Disclosures

Ziantrix pilots may include AI-assisted features for knowledge retrieval, employee support, document workflows, summarization, classification, routing, payroll validation support, and operational workflow assistance. AI output may occasionally be inaccurate, incomplete, outdated, ambiguous, or unsuitable for a specific decision.

  • AI assists workflows but does not replace human judgment.
  • AI-generated or AI-assisted outputs should be reviewed before critical use.
  • Pilot customers are responsible for configuring knowledge sources and review paths.
  • Ziantrix does not use customer content to train public AI models.
  • Additional public guidance is provided in the AI Usage & Transparency document.

8. Human Oversight and Operational Responsibility

Human oversight is expected throughout pilot usage, especially for workflows that affect employees, compensation, payroll readiness, statutory obligations, compliance, workplace rights, or financial records.

  • Customers should review AI-assisted responses before sending sensitive employee communications.
  • Customers should review payroll-related outputs before downstream payroll lock, filing, or payment execution.
  • Customers should route uncertain, contested, or high-impact matters to qualified personnel.
  • Customers should maintain internal fallback processes during pilot evaluation.

9. Payroll and Operational Limitation Clarifications

During pilots, Ziantrix may support payroll calculation, payroll validation, exception surfacing, reimbursement context, approval routing, and audit documentation. These capabilities are intended to help customers evaluate operational control and readiness.

No autonomous payroll execution

Ziantrix does not currently execute salary disbursements, initiate bank transfers, move funds, hold customer money, provide banking services, or act as a financial institution.

Customers remain responsible for final payroll approval, statutory treatment, tax decisions, filings, employee communications, and payment execution through their chosen payroll, finance, ERP, banking, or payment systems.

10. Pilot Support Expectations

Ziantrix provides pilot support on a reasonable-effort basis unless a written agreement states otherwise. Pilot support is intended to help customers evaluate the platform, resolve onboarding issues, understand configuration, and provide feedback.

  • Support channels, response expectations, meeting cadence, and implementation scope may vary by pilot agreement.
  • Pilot support may prioritize issues based on severity, security, customer impact, product readiness, and available capacity.
  • Ziantrix may provide configuration guidance, troubleshooting, workflow review, and product education during the pilot.
  • Pilot support does not replace customer HR, payroll, legal, tax, finance, compliance, or IT responsibilities.

11. Feedback and Improvement Rights

Pilot programs work best when customers share practical feedback. Customers may provide comments, suggestions, issue reports, workflow observations, usability feedback, feature requests, and operational learnings.

Ziantrix may use pilot feedback to improve, develop, prioritize, market, support, and operate the platform, provided we do not disclose customer confidential information or personal data except as allowed by applicable agreements and privacy obligations.

12. Data Handling References

Data submitted during a pilot is handled according to applicable agreements, the Privacy Policy, product configuration, and customer instructions where Ziantrix acts as a processor or service provider. Customers should review data readiness and minimize unnecessary sensitive data during pilot setup.

  • Customers remain responsible for employee notices, consents, legal bases, and internal approvals.
  • Pilot data may be used to provide, secure, support, evaluate, and improve customer-specific pilot workflows.
  • Customer data protection, access control, tenant isolation, and auditability are described at a high level in our Privacy Policy and Security Overview.
  • Deletion, export, retention, and backup lifecycle handling may be governed by applicable agreements and platform capabilities.

13. Confidentiality Expectations

Pilot programs may involve non-public product information, early feature designs, workflow configurations, customer data, business plans, pricing, feedback, implementation discussions, and operational learnings. Each party should protect the other party’s confidential information with reasonable care.

Customers should not publicly disclose non-public pilot functionality, screenshots, benchmarks, roadmap information, implementation details, or performance observations without Ziantrix’s prior written consent, unless disclosure is required by law.

14. Acceptable Use Expectations

Pilot customers and users must use Ziantrix responsibly, lawfully, and within the agreed pilot scope.

  • Do not attempt unauthorized access to systems, tenants, accounts, APIs, data, or workflows.
  • Do not bypass access controls, approval flows, tenant boundaries, usage limits, or security controls.
  • Do not upload malware, unlawful content, or content that infringes third-party rights.
  • Do not use pilot features to make unlawful discriminatory, retaliatory, deceptive, or harmful employment decisions.
  • Do not use automated scraping, stress testing, probing, scanning, reverse engineering, or security testing without written authorization.
  • Do not submit production-critical workflows to experimental features without appropriate customer review and fallback controls.

15. Suspension or Termination Rights

Ziantrix may suspend, limit, or terminate pilot access if we reasonably believe continued access creates security risk, violates these terms, violates law, exceeds the pilot scope, threatens the Services or other customers, or may cause material harm.

Either party may end a pilot according to the applicable pilot agreement or, if no separate written term applies, by providing reasonable notice. Following termination, data export, retention, deletion, and backup lifecycle handling will follow applicable agreements, the Privacy Policy, legal requirements, and platform capabilities.

16. Service Modification Rights

Ziantrix may modify, improve, limit, suspend, rename, replace, or discontinue pilot features during or after a pilot. We may make changes to improve reliability, usability, security, compliance alignment, customer fit, or product direction.

We will make reasonable efforts to communicate material changes that affect active pilot workflows, but pilot customers should expect product behavior and feature availability to evolve.

17. Availability and Operational Limitation Disclosures

Pilot services are provided for evaluation and may not have the same availability, performance, support, or operational commitments as generally available production services unless a written agreement states otherwise.

  • Pilot access may be affected by maintenance, updates, third-party service issues, configuration work, customer systems, security events, or factors outside Ziantrix’s control.
  • Some pilot workflows may be rate-limited, manually reviewed, temporarily disabled, or changed during evaluation.
  • Pilot analytics, reports, summaries, and AI outputs should be validated before business-critical use.
  • Customers should maintain operational fallback plans for critical HR and payroll processes.

18. Warranty Disclaimers

Except as expressly stated in a written agreement, pilot services and pilot features are provided "as is" and "as available" for evaluation. To the maximum extent permitted by law, Ziantrix disclaims warranties of merchantability, fitness for a particular purpose, non-infringement, uninterrupted operation, error-free operation, and accuracy of AI-generated or system-suggested outputs.

Ziantrix does not warrant that pilot features will become generally available, remain unchanged, meet every customer requirement, identify every error, prevent every unauthorized action, or replace professional HR, payroll, tax, legal, financial, compliance, or security advice.

19. Limitation of Liability

To the maximum extent permitted by law, Ziantrix will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost goodwill, business interruption, loss of data, pilot configuration decisions, third-party services, or customer reliance on unreviewed pilot outputs.

Except as otherwise stated in a written agreement, Ziantrix total liability for claims arising out of or relating to a pilot program will not exceed the amounts paid by the customer to Ziantrix for the pilot giving rise to the claim during the 12 months before the event giving rise to liability. If no fees were paid for the pilot, Ziantrix total liability will be limited to the maximum extent permitted by law.

20. Governing Law and Dispute Resolution

Unless a signed agreement states otherwise, these Pilot Program Terms are governed by the laws of Telangana, India, without regard to conflict-of-law principles. Courts located in Hyderabad, Telangana, India will have exclusive jurisdiction over disputes arising from these terms or a pilot program, subject to any mandatory legal requirements.

The parties should first attempt to resolve pilot disputes in good faith through business and legal contacts before initiating formal proceedings, unless urgent injunctive relief or legal preservation steps are reasonably required.

21. Changes to Pilot Program Terms

We may update these Pilot Program Terms from time to time to reflect product changes, pilot practices, legal requirements, security needs, support practices, or operational learnings. When we make material changes, we will update the "Last updated" date and provide notice where required by law or agreement.

Continued pilot participation after updated terms become effective means the customer accepts the updated terms, unless a signed agreement provides otherwise.

22. Contact Information

For pilot program questions or legal notices, contact legal@ziantrix.com. For privacy questions, contact privacy@ziantrix.com. General inquiries may be sent to contact@ziantrix.com.

Ziantrix AI Technologies Private Limited, Plot No. 68, E/Part, Sri Ram Nagar Colony, Pasmamala, Rangareddy, Hyderabad, Telangana 501505, IN.

23. Last Updated and Versioning

Field
Value
Document
Pilot Program Terms
Version
1.0
Last updated
May 25, 2026
Owner
Ziantrix Legal, Trust, and Product Governance

These Pilot Program Terms may be updated as Ziantrix pilot programs, product capabilities, operational practices, or legal requirements evolve. Material updates will be reflected by updating the version or last updated date.