We engage subprocessors only for defined operational purposes. The categories below describe the types of providers we may use and the functions they perform.
5.1 Infrastructure and Cloud Providers. Compute infrastructure, object storage, Data Backup storage, database hosting, and supporting cloud services. Primary production systems remain self-managed within India wherever practical.
5.2 Network Security and Content Delivery. Providers delivering DDoS protection, Web Application Firewall (WAF), DNS, TLS termination, bot protection, and edge caching. These providers necessarily process request metadata such as IP address, browser information, and requested URLs while protecting the Services.
5.3 Payment Providers. Providers responsible for subscription billing, payment processing, refunds, mandates, and invoicing. Payment credentials remain under the payment provider's control and are not stored by ZipZy®.
5.4 Email and Communication Providers. Providers responsible for transactional email, notifications, marketing communications (where permitted), and messaging services.
5.5 Analytics and Product Telemetry. Providers used for aggregated analytics, product usage measurement, and operational insights. Where possible, IP addresses are truncated or hashed.
5.6 Error and Performance Monitoring. Services capturing application errors, performance metrics, crash reports, and operational diagnostics while minimising personal data collection.
5.7 Customer Support Providers. Providers supporting helpdesk operations, support tickets, and customer communication.
5.8 AI Providers. AI model providers used solely for inference supporting AI Features. Customer Inputs and Outputs are processed only to generate responses and are contractually prohibited from being used to train foundation models.
5.9 Security Providers. Malware detection, phishing analysis, URL reputation services, and other security tooling used to protect Customers and the platform.
5.10 Identity Providers. Third-party authentication providers used only when Customers choose federated sign-in methods.