Privacy Protocol.
01. Data Collection Ontology
When you interact with the HORIZON platform, we collect precise, minimal datasets required to establish rendering environments and verify identity:
- Operative Identifiers: Name, Corporate Relay (Email), and organizational metadata provided during the Inquiry phase.
- Spatial Telemetry: Interaction events, viewport rotation matrices, and hardware specs required to dynamically downscale or upscale the 3D rendering pipeline (WebGL metrics).
- Network Locators: IP addresses and edge-caching localities strictly for CloudFront DDoS mitigation and latency routing.
02. Processing Directives
Pursuant to Section 4 of the DPDP Act and Article 6 of the GDPR, processing of personal data occurs strictly on lawful grounds:
- Execution of Service Level Agreements and delivering requested 3D model streams.
- Security monitoring to prevent unauthorized injection attacks against our viewer infrastructure.
- Analytic telemetry to identify frame-rate drops and optimize our asset delivery systems.
03. Cross-Border Transfers
HORIZON utilizes a distributed, multi-region architecture. For clients interacting under Indian jurisdiction, all primary spatial data and Operative Identifiers are retained within Mumbai (`ap-south-1`) AWS availability zones as per MeitY guidelines. EU queries are localized and routed through Frankfurt (`eu-central-1`). Appropriate Standard Contractual Clauses (SCCs) govern all inter-node transfers.
04. Principal Rights (Data Fiduciary Obligations)
You possess absolute sovereignty over your entity records. You maintain the right to:
- Request Extraction: Obtain a portable, machine-readable export of all records we hold.
- Initiate Erasure: Purge your operational history from our active tables (subject to legal retention mandates).
- Revoke Consent: Terminate telemetry sharing, which may result in a degraded rendering experience.
To execute a request, transmit an inquiry to the Corporate Relay at legal@horizon-skynet.com.