Updated September, 14 2017
Please email us at Privacy@WirelessRegistry.com with your questions or concerns.
Wireless Registry collects informatinon about detectable WiFi, Bluetooth, and Bluetooth Low Energy (“BLE”) signals emitted by wireless devices through its customers using Wireless Registry Application Program Interfaces (“APIs”) and/or Software Development Kits (“SDKs”). We use these signal observations for the general purpose of building a database of relationships between wireless signals and devices over time, from which we provide data and analytics to our customers.
For example, a mobile app may integrate the Wireless Registry SDK to receive insights about the types of retail brands that app’s users encounter, or the devices (like wearables, smart home gadgets, and cars) they own, to help guide marketing and advertising strategies.
As a mobile or wireless device and app user, you may interact with Wireless Registry’s system in either or both of the following ways:
Using its APIs and/or SDKs, and via customer mobile apps and fixed or moving wireless devices, Wireless Registry collects, stores, and may share or use raw and/or processed detectable wireless signal and/or device identifier information. Identifiers include MAC addresses, SSIDs, UUIDs, and Ad-IDs.
- MAC address: the unique and persistent identifier tied to a wireless device’s signal hardware. Most wireless devices, like a wireless Bluetooth speaker, have just one MAC. Smartphones typically have both WiFi and Bluetooth signals, and so two MAC addresses (one MAC for each signal).
- SSID: a meaningful signal name that is not necessarily unique, like a home WiFi network name or a humanly readable name emitted from a wireless device.
- UUID: a commonly used BLE signal identifier. BLE devices with a UUID include beacons (like Apple™ iBeacon or Google Eddystone), as well as common wearables and item trackers. A BLE device may emit one or several UUIDs that are either constant or change over time.
- Ad-ID: a pseudo-random identifier provided by the smartphone’s operating system (iOS or Android) and used for the purposes of mobile advertising. The Ad-ID can typically be reset by the smartphone’s user.
Signal identifiers are tied to a wireless device, but not to an individual or person.
Generally, things from which Wireless Registry may observe signal or device identifier information include any wireless device with a WiFi, Bluetooth, or BLE signal. Such devices can be fixed (such as, for example, network routers, smart home appliances, and beacons) or mobile (such as, for example, smartphones, fitness wearables, and cars).
Wireless Registry is not a location provider, and our services do not require location information. We do not request a smartphone’s location from the mobile apps that report signal observations to our system via our signal observation APIs and/or SDKs, and do not gather nor share GPS location information if location services are disabled on the smartphone or for the reporting apps.
However, when location services are enabled on the smartphone and for the reporting app, and that app or another service on the smartphone is collecting GPS geolocation, Wireless Registry may retrieve the freshest (most recent) available location information (a latitude and longitude pair of coordinates) as part of an observation. Wireless Registry may share such information with the reporting mobile app, its customers, or partners. Our customers and app partners may use such information, or separately require location information, in accordance with their own permissions and privacy policies.
Except as outlined in the next section regarding information provided by visitors to Wireless Registry’s website, the company does not collect personally identifiable information, including names and contact information.
Wireless Registry does not collect, receive, or store any information that could identify you individually, such as a name, address, email, phone number, and so on. (The only exception to this is when you choose to provide such infomration to us through our website. Please refer to the “On our website” section below for details.)
Wireless Registry also does not link information about wireless signal and/or device identifiers it collects from devices to information that could identify an individual, including names and contact information. Wireless Registry’s mobile app partners and customers may link smartphone Ad-IDs to additional user information, in accordance with their own privacy policies and permissions, but do not share any such information or linkages with Wireless Registry. Please refer to your mobile apps’ privacy policies for details.
Wireless Registry may collect general analytics information about visitors to our website for the purposes of measuring web traffic and to improve or optimize the website and our services.
When you choose to contact Wireless Registry through our online contact form or by email, you may provide certain information that is personally identifiable, such as your name, contact details, and any other information you decide to share. This information gathered through Wireless Registry’s website is used to address your questions and to better serve you. To that end, we may share such information with third parties.
For example, you may use Wireless Registry’s online contact form to send us a question about our services and to request access to our API and/or SDK documentation, and provide your name, email address, and GitHub username. We use such information to respond to your query and to help us provide you with services, which may include connecting you with a Wireless Registry partner or customer.
Wireless Registry uses Amazon Web Services’ cloud-based database servers to store information. We use reasonable security measures to protect that information.
Wireless Registry uses the information we collect, as described above, for the general purpose of building and maintaining a database of relationships between wireless devices over time, through which we provide data and analytics to our customers as part of a variety of services and use cases.
Wireless Registry may group signal and/or device identifiers (including MAC addresses, SSIDs, and UUIDs) for the purpose of establishing proximity between devices, of establishing signal clusters for a wireless device, or of maintaining clusters for several devices within a physical space.
For example, we may gather signal identifiers around a space (like a shop or a train station) to distinguish it from other spaces, or to determine that a certain number of app users are in proximity to each other.
Wireless Registry does not link a smartphone's Ad-ID to either of that same smartphone's MAC addresses.
For example, we may link a smartphone’s Ad-ID to the MAC address of a fitness wearable to learn more about that smartphone user’s consumer preferences or to establish cluster relationships, but we do not link that information to either of the smartphone's MAC addresses.
The data and analytics Wireless Registry produce and may deliver to our customers enable a wide variety of services and use cases, including, for example:
Wireless Registry also reserves the right to use information outlined above for other purposes, notably to:
Wireless Registry honors a smartphone user's preference to “Opt out of interest-based advertising” directly in a smartphone’s privacy settings. When selected, Wireless Registry no longer receives signal observations from that smartphone, but does not delete past signal observation information tied to that smartphone’s Ad-ID.
We welcome feedback to Wireless Registry on our services, and may share that feedback with third parties without personally identifiable information.
We are not responsible for any third-party products or services you access via our websites or services.
Our services are not intended for children under 13 years of age, and we do not knowingly or intentionally collect or store data from children under 13.