Skip to main content

​
Credential Privacy

Are end-user home network credentials exposed to the venue operator, system administrator, or Wiacom? No. The user’s home WiFi SSID name and passphrase are never transmitted to, or stored by, the venue, the operator, or Wiacom. Horizon provisions a dedicated virtual SSID and associated credential set for the user at that venue. The user’s underlying home network credentials remain entirely within their own equipment and are not part of the provisioning flow at any point. Credentials stored on the wireless controller are encrypted at the configuration level. They are not readable in plaintext by venue staff or system administrators — access to the controller configuration does not expose credential values. The provisioning model is analogous to tokenised payment systems: the transaction is authorised using a derived, venue-specific token rather than the user’s real credential. The original credential is never shared, transmitted, or stored outside the user’s own environment.

​
Operational Complexity

What is the implementation and management overhead for the operator? Minimal. Horizon is cloud-managed and the provisioning lifecycle — SSID creation, credential assignment, expiry, revocation, and cross-location portability — is fully automated by the Wiacom platform. There is no manual configuration required per user, no new hardware, and no changes to the existing wireless infrastructure beyond the initial controller integration. Day-to-day management is handled through the Wiacom dashboard. Operators do not interact with the controller directly for credential operations. Does Horizon require a specific wireless vendor or proprietary hardware? No. Wiacom Horizon is vendor-agnostic. Integration is achieved through cloud API, local controller API, SSH/CLI agent, or a custom adapter depending on the vendor. This means Horizon can be deployed on virtually any supported wireless infrastructure without hardware replacement or vendor lock-in. See the WiFi Vendors section for the current list of supported platforms and integration modes.

​
Vendor Support & Compatibility

Will deploying Horizon affect the vendor support status for our wireless infrastructure? No. Horizon operates through vendor-supported API and configuration interfaces where available, and through non-invasive agent-based methods on platforms without a public API. It does not modify firmware, bypass security controls, or operate outside the vendor’s documented integration surface. Deployments using standard API integrations are fully within vendor-supported operational parameters.

​
Compliance & Data Protection

What data does Horizon process, and where is it stored? Horizon processes the technical identifiers required for SSID provisioning and session management — these are pseudonymous credential tokens, not personal identifiers in the regulatory sense. Personal data associated with the user’s identity (where captured through an onboarding channel) is handled in accordance with the platform’s standard data model and the applicable Data Processing Agreement. For deployments with strict data residency requirements, Horizon is compatible with both the standard cloud-hosted model and customer-hosted deployments. See Data Models and Deployment Options for further detail.