Modern phones do not always join Wi-Fi with a permanent factory MAC address. Apple and Android devices can use private or randomized Wi-Fi addresses to reduce cross-network tracking. This privacy feature is beneficial for guests, but legacy hotspot systems that treat a MAC address as a permanent identity can create repeat-login loops, fragmented analytics, incorrect device limits and unclear session relationships.
HotSpot manages session continuity, guest access and the lawful record chain when devices use private Wi-Fi addresses. Guests are not asked to disable a privacy setting. The proprietary method used to produce this outcome is confidential and is not described.
What is MAC address randomization?
A MAC address identifies a network interface on a local network. Modern operating systems can present a private address instead of the factory address when joining Wi-Fi. Apple calls this Private Wi-Fi Address, while Android commonly calls it MAC randomization or randomized MAC.
The goal is to reduce persistent tracking across different networks. The practical behavior can vary by operating system version, network security and device policy.
Why captive portals are affected
A legacy hotspot may use the MAC address alone to recognize a device, continue a session or count a returning visitor. When that address changes, the system may believe it has found a new device.
Common symptoms include repeated authentication, inflated device counts, reset quotas, fragmented returning-visitor analytics and difficulty relating a lawful record to its authentication context.
A modern guest Wi-Fi service should accept private-address behavior as normal rather than asking guests to turn it off.
What matters for lawful records
The objective is not merely to produce a row containing a MAC address. A defensible record process maintains a clear relationship among the authenticated user, assigned network information, session time and relevant traffic records while preserving integrity and exportability.
A randomized address is one technical value observed during a session. It should not be treated as a permanent personal identity on its own. HotSpot preserves the session context and timestamped export chain without disclosing its proprietary correlation method.
Warning signs in an existing hotspot
- Guests repeatedly see the login page after reconnecting.
- Device counts grow much faster than plausible visitor counts.
- Time and quota policies unexpectedly reset.
- Returning-visitor metrics become unreliable.
- Support requests increase after mobile operating-system updates.
- Audit exports do not clearly relate sessions to authentication events.
What HotSpot delivers
- No instruction to disable Private Wi-Fi Address.
- Captive portal flows compatible with current mobile behavior.
- Session continuity and analytics not left dependent on a MAC address alone.
- More consistent device and user policies.
- Session-aware lawful logging and timestamped exports.
- Central visibility across locations and SSIDs.
The correct validation is a pilot across current iOS and Android versions, reconnect scenarios, SSID transitions, authentication methods and exported session records.
Questions to ask a hotspot vendor
- What happens when a guest reconnects with Private Wi-Fi Address enabled?
- Does the system treat a MAC address as a permanent person identifier?
- How do rotating addresses affect returning-visitor analytics?
- Must users disable a phone privacy setting?
- How are authentication, session and lawful records related?
- How are new iOS and Android versions tested?
- How are multi-SSID and multi-location transitions handled?
- Can a specific session evidence package be exported quickly?
Explore hotspot management or request a pilot review.
Frequently asked questions
Must guests turn off Private Wi-Fi Address?
No. HotSpot is designed to work without requiring guests to disable this privacy setting.
Does a randomized MAC invalidate lawful logging?
No. However, a legacy design that treats the MAC alone as an immutable identity can weaken session relationships. Authentication, session and network records should be managed together.
Does an iPhone use a new MAC on every connection?
Behavior varies by operating-system version, network type and selected private-address mode. Fixed and periodically rotating private-address scenarios can occur.
Is randomized MAC the default on Android?
Many devices running Android 10 or later use per-network randomized MAC by default. Names and behavior can vary by manufacturer and version.
How does HotSpot solve it?
HotSpot delivers the outcome at product level: session continuity, policy consistency, analytics and record relationships. The proprietary implementation is not disclosed.
Can it be tested with our current network?
Yes. A pilot can validate current firewalls, wireless controllers, SSIDs, authentication methods and representative iOS and Android devices.