SkimGuard Security Monitoring: Device Privacy Notice
Effective: October 14, 2026
This notice explains how SkimGuard, Inc. ("SkimGuard," "we," or "us") handles wireless signal data collected by our security monitoring systems at business locations. It is separate from the privacy policy for the SkimGuard mobile apps, which is available at skimguard.io/privacy.
1. Scope
SkimGuard operates security monitoring devices, desktop software, and integrations with business Wi-Fi network equipment (Cisco, Meraki, Aruba, Ruckus and Juniper Mist), all deployed at the locations of our business clients. We call these, together, "SkimGuard Security Sensors." They run continuously to help detect payment-terminal tampering, unauthorized hardware attachments, and electronic card skimmers.
2. What we collect
SkimGuard Security Sensors receive the wireless signals that Bluetooth devices broadcast publicly within range of a protected location. For each device observed, we may record:
- a hashed identifier derived from the device's Bluetooth address (MAC address);
- the manufacturer prefix of that address, when it is a fixed address assigned by the manufacturer;
- the wireless protocol (for example, Bluetooth Low Energy or Bluetooth Classic) and the signal strength;
- which sensor observed the device, where that sensor is located, and when the observation was made;
- information the device itself broadcasts publicly, such as its advertised name, manufacturer data, and advertised service types.
Additional wireless protocols (v2 sensors). Some SkimGuard Security Sensors also observe two further public wireless signals near a protected location:
- 802.15.4 (the radio family used by Zigbee and similar low-power devices). The sensor listens passively. It does not join any network, is not given any network key, and therefore sees only the lowest-layer public information a device broadcasts: such as a hashed form of the device's hardware address, its manufacturer prefix, the network and channel identifiers in the air, and signal strength. It cannot and does not read the contents of any 802.15.4 network or device.
- NFC (near-field, a few centimetres). The sensor detects only the presence of an NFC field or transmitter in the immediate vicinity of a protected payment terminal, the kind of signal an illicit reader attached to a terminal would produce. It operates in listen / field-detection mode only: it does not poll, interrogate, or read payment cards or any other NFC tag or device, and it does not emit a reader field of its own for that purpose.
- Wi-Fi (802.11). The sensor listens passively for the Wi-Fi signals nearby equipment broadcasts in the open air, the kind an unauthorized Wi-Fi transmitter hidden in or near a payment terminal would produce. It does not join any network, is not given any password, and does not read the contents of any Wi-Fi traffic. It evaluates signals on the sensor itself and keeps a record only when a signal is relevant to a security event, not a log of the devices nearby. For a transmitter it records, it keeps only lowest-layer facts: a hashed form of the hardware address, its manufacturer prefix, the channel, and signal strength. It does not store network names (SSIDs), except briefly during a support diagnostic (described below).
Identifiers observed over 802.15.4 and Wi-Fi are hashed the same way Bluetooth addresses are (see "How identifiers are handled"); NFC field-detection records the fact and strength of a field, not the contents of any card or tag.
How identifiers are handled. A device's Bluetooth address is converted to a hashed identifier on the sensor itself, or as soon as we receive it in the case of network integrations. We do not store the original Bluetooth address, except briefly during a support diagnostic, as described below. A hashed identifier is not anonymous: the same device always produces the same hashed identifier, and it can be matched to a known address. We therefore treat hashed identifiers as personal information and protect them accordingly. Identifiers belonging to SkimGuard's own sensors are stored as-is, so that our sensors do not flag one another.
Support diagnostics. If a business client reports a device it believes our sensors did not detect, authorized SkimGuard staff may place a sensor at that location into a short diagnostic mode. A diagnostic session can be started only by SkimGuard staff, lasts no more than 10 minutes, and ends automatically. During a session, the sensor records the devices it observes in fuller detail: including, for Bluetooth, their original Bluetooth addresses, and, for Wi-Fi, network names (SSIDs), so that our engineers can identify the device in question and improve our detection. Diagnostic records that contain this fuller detail are kept separately from our other records, are accessible only to authorized SkimGuard staff, and are deleted automatically within 30 days. We may keep a hashed copy, which we handle like our other observation records. A diagnostic session follows the same limits as normal monitoring: the sensor does not connect to, pair with, or access the contents of any nearby device.
What we do not do. Our sensors do not connect to, pair with, join, or access the contents of any nearby personal device or network. They detect nearby devices by listening to the signals those devices broadcast publicly, using standard Bluetooth scanning (which may send brief discovery requests that nearby Bluetooth devices can receive), passive 802.15.4 listening, passive Wi-Fi listening (no network is joined and no password or key is used), and near-field detection that senses the presence of an NFC field without reading cards or tags. Our sensors do not read the contents of any Wi-Fi traffic, card, tag, or network; do not use these signals to count, track, or profile people; and do not store the original hardware address of any device, except briefly during a support diagnostic, as described under "How identifiers are handled."
3. Why we use it
We use this data for security, fraud prevention, and crime prevention. Specifically, we use it to:
- identify and locate payment skimmers and other unauthorized transmitting hardware;
- help our business clients and law enforcement agencies investigate tampering and related crimes;
- support the physical and transaction security of our clients' locations.
We do not sell, rent, or share security signal data for marketing or advertising.
4. Who we share it with
Original hardware addresses and Wi-Fi network names are kept only in short-lived support diagnostic records, as described in Section 2, and are used only by authorized SkimGuard staff. We disclose them outside SkimGuard only where we are legally required to do so. We do not disclose observation records about bystanders to our business clients in general. We may disclose observation records, identified only by hashed identifier and manufacturer, to the following:
(a) The business client where the sensor is installed. The client can see the devices observed at its own location, shown by manufacturer and a shortened identifier, so that it can verify security events there. The client may also receive exports of its own location's records.
(b) Law enforcement agencies. We provide access to law enforcement agencies that we have verified. Each agency's access is limited to its own jurisdiction, and every access is logged. An agency may also give us a device identifier and ask whether it matches any records we hold. Each requesting agency is responsible for ensuring it has the legal authority its request requires, such as a subpoena, warrant, court order, or other lawful basis.
(c) Service providers that host and operate our systems on our behalf, under confidentiality obligations.
5. Our role
When SkimGuard provides security monitoring to its business clients, including through client-owned equipment and enterprise Wi-Fi integrations, SkimGuard acts as a service provider to those clients.
6. Contact
SkimGuard, Inc.
Questions about this notice: privacy@skimguard.io