Subprocessors & Third-Party Services

This Subprocessors & Third-Party Services document explains how Ziantrix AI Technologies Private Limited ("Ziantrix", "we", "us", or "our") uses third-party services to support Ziantrix HRMS, our websites, pilot environments, integrations, AI-assisted workflows, communications, support, security, reliability, and business operations.

Ziantrix handles employee data, payroll-adjacent workflow data, organizational HR data, documents, support requests, and operational metadata in sensitive enterprise contexts. We publish this page to provide high-level vendor transparency for customers, procurement teams, privacy reviewers, and security reviewers.

Third-party services help Ziantrix operate a reliable, secure, and useful enterprise SaaS platform. Depending on customer configuration, plan, geography, enabled modules, and operational needs, third-party services may support hosting, data storage, AI-assisted workflows, notifications, analytics, customer support, security, observability, and integrations.

• Operate cloud-based HRMS and workflow services.
• Support secure authentication, user sessions, and enterprise integrations.
• Enable AI-assisted retrieval, summarization, classification, and workflow support.
• Send customer-configured email, messaging, workflow, and operational notifications.
• Understand product usage, reliability, and website performance.
• Provide customer support, onboarding assistance, troubleshooting, and operational continuity.
• Maintain security, reliability, backups, monitoring, and incident readiness.

Ziantrix approaches vendor use through practical governance: selecting services that support legitimate product and operational needs, limiting use to appropriate purposes, considering privacy and security implications, and reviewing vendor suitability as the platform evolves.

• Use third-party services for defined operational, product, reliability, security, or support purposes.
• Consider the sensitivity of customer and employee data involved in a workflow.
• Apply access controls, customer configuration, and data minimization principles where appropriate.
• Review vendor categories as services evolve, new modules are introduced, or customer requirements change.
• Avoid publishing implementation details that would weaken security or reveal operational architecture.

Cloud infrastructure and hosting providers may support core service delivery, application hosting, databases, storage, networking, backups, logging, and reliability. These providers help Ziantrix deliver a cloud-native SaaS platform for HRMS and workflow operations.

We do not disclose detailed infrastructure architecture, exact deployment topology, operational configurations, or internal hosting dependencies in this public document. Enterprise customers may request appropriate security and trust documentation through their Ziantrix contact where available and subject to suitable confidentiality terms.

Ziantrix may use AI-assisted service providers to support features such as employee question answering, HR knowledge retrieval, document summarization, workflow classification, drafting assistance, payroll validation support, and operational routing.

• AI-assisted features are used to support workflows, not to replace customer judgment.
• Customer data is not used to train public AI models.
• AI provider usage may vary based on product module, region, availability, customer configuration, and operational requirements.
• Specific implementation details, model choices, routing logic, retrieval configuration, and internal safeguards are not disclosed publicly.

Communication and notification providers may support email, messaging, workflow notifications, security alerts, onboarding updates, support responses, and customer-configured employee communications.

Depending on configuration, these services may process limited contact details, message metadata, notification content, delivery status, and operational records needed to send or manage communications. Customers are responsible for configuring employee communications lawfully and appropriately.

Analytics and operational monitoring providers may help us understand website usage, product experience, service performance, errors, reliability, diagnostics, and operational health. These services support service improvement and platform reliability.

• Website analytics may be subject to cookie choices where applicable.
• Operational monitoring may be necessary to provide, secure, and improve the Services.
• Analytics and monitoring are not used to make automated employment, payroll, or employee-impacting decisions.
• We do not publicly disclose exact monitoring configurations, detection rules, thresholds, or tooling internals.

Customer support and operational tooling providers may help Ziantrix manage support requests, onboarding coordination, pilot feedback, customer communications, troubleshooting, documentation, and service operations.

Support workflows may involve customer contact information, issue descriptions, screenshots or documents provided by the customer, configuration context, and operational metadata needed to resolve requests. Customers should avoid sending unnecessary sensitive data through support channels unless needed for support and authorized by their internal policies.

Security and reliability-related services may support access protection, logging, alerting, availability, service diagnostics, abuse prevention, incident investigation, backups, and continuity planning. These services help protect HRMS, payroll-adjacent, document, and AI-assisted workflows.

• Security and reliability services may process operational metadata, logs, event records, or technical signals as needed to protect and operate the platform.
• These services are governed by purpose, operational need, and appropriate access controls.
• Detailed security tooling, monitoring internals, incident workflows, and anti-abuse logic are not disclosed publicly.

Subprocessors and third-party services may process limited customer data, employee data, technical data, account data, support data, or operational metadata where necessary to provide, secure, support, or improve the Services. The type of data involved depends on the service category, customer configuration, enabled modules, and operational context.

• Ziantrix uses third-party services for defined business, operational, security, product, or support purposes.
• Access to customer data is limited based on role, operational need, and service purpose where applicable.
• Customer data handling is also described in the Privacy Policy, Security Overview, Cookie Policy, and applicable agreements.
• Customers remain responsible for deciding what data they submit, which integrations they enable, and how employee notices or consents are handled.

Vendor and subprocessor obligations may vary based on customer location, user location, data residency needs, product configuration, and applicable privacy laws. Where relevant, Ziantrix considers data protection expectations such as GDPR-aware and India DPDP-aware principles when evaluating vendor use and customer requests.

International transfers, regional hosting, and data residency requirements may be addressed in customer-specific agreements, product configurations, or enterprise discussions. Public documentation does not replace a signed data processing agreement or customer-specific legal review.

Ziantrix services and vendor relationships may evolve as we improve the platform, add functionality, expand regions, strengthen reliability, or change operational needs. Subprocessor categories, service providers, and purposes may change over time.

• We may add, replace, remove, or change third-party services as the platform evolves.
• Material vendor-related changes may be communicated according to applicable agreements or legal requirements.
• Customers with contractual notice rights should refer to their signed agreements for specific notice procedures.
• This public page may be updated periodically to reflect current high-level service categories and trust information.

Customers, procurement teams, privacy teams, and security reviewers may contact Ziantrix with reasonable questions about subprocessors, third-party services, privacy posture, security posture, or trust documentation. The information we can provide may depend on confidentiality requirements, customer agreement status, sensitivity of the request, and operational security considerations.

• Customers may request additional high-level subprocessor or trust information through their Ziantrix contact.
• Enterprise security or privacy reviews may be supported through appropriate documentation and confidentiality terms.
• We do not provide information that would expose sensitive infrastructure, security internals, monitoring logic, or operational dependencies.

For subprocessor, vendor, privacy, or trust questions, contact privacy@ziantrix.com. For legal notices, contact legal@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.

This document may be updated as Ziantrix services, vendor categories, privacy practices, security practices, or operational requirements evolve. Material updates will be reflected by updating the version or last updated date.