PRIVACY POLICY

Scope of Data Autonomy

Your privacy is of the utmost concern to Virisa Icosys Technology Pvt Ltd. This Privacy Statement describes the types of information that we collect, use, share, and store through the use of Our Products and Services. By using any of Our Products and/or Services You agree to allow Us to collect, use, share, transfer, store, process and retain the information We collect in the manner described in this Privacy Statement or in Our Privacy Policy.

---

1. IMPORTANT DEFINITIONS

The following are used in this Privacy Statement in the manner defined below:

• 1.1. "Company," "Us," "We" or "Our": Virisa Icosys Technology Pvt Ltd, the provider of the Products and Services.
• 1.2. "Personal Information": Information specific to You or Your account that can be used to identify You. This encompasses:
  • Personally Identifiable Information: Name, physical address, telephone matrix destinations.
  • Registration Information: Payment card variables, username grids, and shipping paths.
  • User Content: Data, text, logs, or audio transmitted to or through the platform.
  • Web Behavior Information: Cookies, domain metrics, browser configurations, and page views.
• 1.3. "Products and Services": Individually and collectively, the hardware products, Icosys Mobile Apps, and associated cloud gateway network structures.
• 1.4. "Product Information": Operational metrics, hardware build variants, GIS coordinates, firmware versions, and log files.

2. TO WHOM THIS PRIVACY STATEMENT APPLIES

This Privacy Statement applies to all Virisa Icosys Technology Pvt Ltd.-owned websites, domains, services, applications, and products. This policy binds all company operators, technical employees, and customer nodes globally.

3. CORE PRINCIPLES & SYSTEM ACCESS

3.1. Safeguarding of Information: We take comprehensive electronic steps to insulate your telemetry logs. We will explicitly request your permission before sharing your data with auxiliary providers outside the standard operational scope required to execute system tasks.

3.2. Additional Authorized Users: Your master profile accounts offer the option to grant secondary device access clearances. Be advised that secondary account links can view logs, execution histories, and billing metrics. It remains your responsibility to guide added users on data privacy expectations.

4. WHY WE COLLECT INFORMATION

We capture, process, and align data arrays to: (A) configure, maintain, and upgrade performance metrics of the automation services, (B) deliver localized framework marketing, (C) insulate structural system nodes against malicious network attacks, and (D) remain entirely consistent with governmental regulatory guidelines.

5. WHAT AND HOW WE COLLECT INFORMATION

Data compilation occurs directly via your inputs (account registration, technician hotline queries, setting selections) and autonomously through environment use telemetry.

5.4.4. Network Synchronization Parameters: When connecting an Icosys automation device to a home network, the hardware tracks your Local area Wi-Fi network configuration name and access records. This information is secured in the local product storage matrix, allowing synchronization pipelines to keep device profiles alive. Note: Your local Wi-Fi router password parameters are never transmitted back to company servers.

6. DATA PROCESSING AND EXTERNAL LINKS

We do not sell, trade, or distribute your private profile markers to outside data brokers. Information is shared strictly with payment processing nodes, cloud database engineers, or legal oversight advisors bound by secure privacy metrics. If our websites include outgoing web links, their external domains operate under separate independent policies beyond our system control loop.

9. SYSTEM SECURITY ENFORCEMENT MEASURES

We enforce robust technical parameters to neutralize threat mechanics. All telemetry pipelines utilize Secure Sockets Layer (SSL) encryption protocols alongside enterprise firewalls to defend data blocks both in transit across active routes and while at rest inside storage partitions. Because no method of web architecture is entirely impenetrable, you must keep your profile pass-credentials insulated against third-party disclosure.

12. DATA TERMINAL COMMUNICATIONS

To update profile definitions, execute right-to-be-forgotten cleanups, or clarify system data loops, route a query directly to our compliance link: