Privacy Policy

Updated February 20, 2018

Thank you for reading SignalFrame's Privacy Policy. Your use of SignalFrame websites and/or services (directly or through SignalFrame's partners and customers) constitutes your acceptance of this Privacy Policy and terms then in place.

The purpose of this Privacy Policy is to provide information about the data SignalFrame collects, how we collect it, how it is stored, and how SignalFrame may share or use that data. This document includes examples for illustrative purposes only.

Note that SignalFrame reserves the right to update this Privacy Policy at any time. Modifications and the most recent update date are posted on this page.

Please email us at with your questions or concerns.


SignalFrame collects informatinon about detectable WiFi, Bluetooth, and Bluetooth Low Energy (“BLE”) signals emitted by wireless devices through its customers using SignalFrame 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 SignalFrame 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.

How do I interact with SignalFrame?

As a mobile or wireless device and app user, you may interact with SignalFrame’s system in either or both of the following ways:

Data we collect

Wireless signal and device identifiers

Using its APIs and/or SDKs, and via customer mobile apps and fixed or moving wireless devices, SignalFrame 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.

Signal identifiers are tied to a wireless device, but not to an individual or person.

Generally, things from which SignalFrame 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).


SignalFrame is not a location provider, and our services do not require location information. We 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, SignalFrame may retrieve the freshest (most recent) available location information (a latitude and longitude pair of coordinates) as part of an observation. SignalFrame 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.

With location enabled on a user’s smartphone, we may collect the most recently available GPS lat/long information for that smartphone, and may use it to verify that we are correctly identifying the types of wireless signals (from shops, restaurants, landmarks and venues, and so on) nearby. We do not gather nor share any GPS location information if location is “off,” either in the smartphone’s system preference settings or for the reporting app. (A partner or customer app that reports wireless signal observations to Wirelesss Registry may also require and collect location information, in accordance with that app’s own permissions and privacy policy, and separately from SignalFrame’s activities.)

Identifiable information

Except as outlined in the next section regarding information provided by visitors to SignalFrame’s website, the company does not collect personally identifiable information, including names and contact information.

SignalFrame 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.)

SignalFrame 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. SignalFrame’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 SignalFrame. Please refer to your mobile apps’ privacy policies for details.

If a user signs into an app using an email address, for example, that app may link data provided by SignalFrame about that user’s Ad-ID to the sign-in email address, in accordance with the app’s own permissions and privacy policy, and separately from SignalFrame’s activities.

On our website

SignalFrame 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 SignalFrame 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 SignalFrame'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 SignalFrame’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 SignalFrame partner or customer.

How we store information

SignalFrame uses Amazon Web Services’ cloud-based database servers to store information. We use reasonable security measures to protect that information.

How we use and share information

General usage and sharing

SignalFrame 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.

Using signal identifiers

SignalFrame 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.

SignalFrame 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.

Sample services

The data and analytics SignalFrame produce and may deliver to our customers enable a wide variety of services and use cases, including, for example:

Additional uses

SignalFrame also reserves the right to use information outlined above for other purposes, notably to:

What are my choices / How do I opt out

SignalFrame honors a smartphone user's preference to “Opt out of interest-based advertising” directly in a smartphone’s privacy settings. When selected, SignalFrame no longer receives signal observations from that smartphone, but does not delete past signal observation information tied to that smartphone’s Ad-ID.

Additional information

We welcome feedback to SignalFrame 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.

Interested in learning more?

Contact Us