Model 1 — Wiacom as Data Platform / Data Vault
This is the default operating model. In this model, Wiacom acts as a secure Data Platform and Data Vault for registration, consent, session, engagement, and WiFi usage data. Data is stored for a configured retention interval and used to provide analytics, reporting, audience activation, troubleshooting, and engagement capabilities. Data retention duration is configurable per deployment. After the retention interval expires, data is purged in accordance with the applicable data protection policy. Model 1 can also be configured so that selected personal data is pushed to customer systems — such as a CDP, CRM, PMS, or another approved platform — while Wiacom continues to operate the access control, onboarding, analytics, and reporting layers. Customer access to data held in Wiacom is provided through secure, controlled channels:Data Available
The following data may be exposed, subject to the configured consent, legal basis, and deployment rules:The platform does not expose raw guest names or email addresses in standard analytics views. Reports and dashboards are scoped according to the configured consent and data-processing rules for the deployment. Full PII export is available only through authenticated API or scheduled export, where permitted by the applicable consent and legal basis.
Who Holds the Data
In this model, Wiacom acts as a data processor on behalf of the customer. A Data Processing Agreement (DPA) governs this relationship. The customer remains the data controller and retains rights over guest data, including export and deletion requests, subject to the agreed processing terms and applicable law. Model 1 is designed for fast deployment and is typically the most suitable option for small and medium-sized customers that do not want to operate their own data platform, CRM, consent storage, or transactional messaging infrastructure. It provides a ready-to-use operating model with standard Wiacom terms, consent flows, data-retention controls, and portal documentation. Default terms and conditions templates are available and have been reviewed by reputable professional legal advisers, although customers remain responsible for validating their final deployment, notices, and lawful basis according to their own jurisdiction and internal policies. This model is available for deployments in multiple markets and is intended to provide broad operational coverage with minimal customer-side implementation effort.Model 2 — Wiacom as Middleware / Privacy-Minimised
This is a custom implementation available for customers with stricter data minimisation, data residency, or internal governance requirements. In this model, Wiacom acts primarily as an integration and enforcement layer. Personal data is pushed directly to the customer’s own CDP, CRM, PMS, or another approved external system at the point of collection. Wiacom retains only a unique pseudonymous user identifier and the technical data required for WiFi authentication, session control, reporting, SLA monitoring, security, and troubleshooting. Pseudonymous identifiers may still be considered personal data where they can be linked back to an individual by the customer or another authorised system.What Wiacom Retains
Customer Responsibilities
When to Consider This Model
This model is well suited for:- Enterprise or public-sector customers subject to strict data localisation requirements
- Customers who already operate a consolidated CDP or CRM and want to minimise the number of systems holding personal data
- Deployments where a PMS, such as a hotel property management system, is the authoritative system of record for guest identity
- Organisations seeking to reduce the personal-data footprint across third-party processors
- Customers with internal policies requiring privacy-minimised architecture by design