Overview
InnerSpace supports space utilization analytics using Wi‑Fi Real-Time Location System (RTLS) data from network infrastructure. Because device identifiers can raise privacy and security questions, this article explains how MAC address data is protected, how it is transformed for analytics, and what to expect with modern device privacy features like MAC randomization (“MAC tumbling”).
At a glance (privacy & security)
Encrypted in transit and at rest: MAC address data is protected using industry-standard encryption during transfer and while stored.
Non-reversible identifiers for analytics: InnerSpace further transforms MAC addresses upon ingestion by applying salted hashing so the identifiers used for processing are not stored or processed in a reversible form.
Designed for trends, not identity: The system is built to measure utilization patterns over time without identifying individuals.
How InnerSpace transforms MAC addresses
By default, InnerSpace receives Wi‑Fi RTLS data directly from the network infrastructure. Upon receipt, InnerSpace transforms MAC addresses for analytics by hashing them (SHA‑1) and salting the hash. This enables consistent, privacy-preserving identifiers for trend analysis while preventing the original MAC address from being stored or used directly in analytics workflows.
What is MAC tumbling (MAC randomization)?
Many modern devices periodically randomize the MAC address they broadcast to improve user privacy. This behavior is often called MAC tumbling (or MAC randomization). In practical terms, it can affect how reliably an unconnected device can be observed over time.
Impact on analytics: unconnected vs connected devices
Unconnected devices (most impacted): Devices that are not connected to the Wi‑Fi network may rotate randomized MAC addresses frequently. This can reduce the ability to link observations across time, which may lower apparent dwell time or continuity for those devices.
Connected devices (typically more stable): In office environments, employees commonly have at least one device (e.g., a laptop) connected to corporate Wi‑Fi. For many devices, the randomized MAC remains consistent for a given SSID over longer periods, which improves continuity for analytics.
How InnerSpace avoids double-counting (de‑duplication)
People often carry multiple devices (laptop + phone + tablet). To reduce the risk of double-counting, InnerSpace applies de‑duplication methods that look for signals indicating multiple devices likely belong to the same person and consolidates them so utilization metrics are more accurate.
Common questions
“Can InnerSpace identify individuals from MAC addresses?”
InnerSpace is designed to produce space utilization insights without identifying individuals. MAC addresses are protected (encrypted in transit and at rest) and are additionally transformed on ingestion using salted hashing so analytics rely on non-reversible identifiers rather than raw device identifiers.
“Does MAC randomization make the data unreliable?”
MAC randomization can reduce continuity for unconnected devices. In typical office deployments, connected devices provide more stable continuity (often consistent per SSID over extended periods). InnerSpace’s approach is designed to work in real-world enterprise environments where connection behavior is common.
“Will one person be counted multiple times if they have multiple devices?”
InnerSpace uses de‑duplication techniques to reduce multi-device double-counting and improve the accuracy of people-based utilization metrics.
Summary
InnerSpace provides flexible, privacy-preserving handling of MAC address data. Data is protected with encryption in transit and at rest, further transformed using salted hashing upon ingestion, and processed with techniques (including de‑duplication) designed to produce accurate utilization analytics while addressing common privacy and reliability concerns.