Skip to content

Privacy policy

This is a courtesy translation. In case of discrepancy, the Spanish version of this document prevails.

Last updated: September 25, 2026

SignalScope is a read-only desktop application for WISP operators who manage wireless radios. This policy explains what data the application handles and how it is protected. The product owner is Materis ("we").

This policy covers what the application does: what it reads from your network, what it stores on your computer and the five situations in which it goes out to the internet. It does not cover your purchase. The data of the commercial relationship (what you provide when you buy, pay, get invoiced or ask for support) is handled by Materis under its own policy, published at https://materis.io/en/privacidad, which applies equally to all its products. Each product publishes its own policy because each piece of software handles different data: one reads the network where it is installed and another touches nothing of yours.

1. General principle: your data lives on your computer

SignalScope works locally. All the information about your network (IP addresses, MAC addresses, device names, signal metrics, locations you place on the map, projects, snapshots and your radios' credentials) is stored only on your computer (in the application's data folder) and is never sent to our servers. We do not use the cloud to store your data, we do no usage analytics or ad tracking, and we do not sell or share information with third parties.

Only one feature sends data about your network off your computer, and only if you turn it on: messaging alerts (WhatsApp or Telegram). It is off by default, you set it up with your own credentials, and what goes out is the alert text. Section 2 details exactly what that text contains and who receives it. If you don't turn it on, nothing about your network leaves your computer.

The application connects to the internet in five specific situations, all described in section 2: activating your license, checking for a new version, downloading map images when you open the Coverage map, measuring the References you add outside your network and (only if you turn it on) sending messaging alerts.

2. Data that is processed, and why

  • Paid license (Full version): to activate and validate your license, your email address, your license key and a device identifier (HWID) are sent to the Materis licensing system. They are used to verify the license and to control the number of activations allowed. This data is processed for that purpose only, and Materis is responsible for it: what it does with it and for how long is stated in its policy (https://materis.io/en/privacidad). Nothing about your network is sent in that request.

  • Trial version: it is 100 % local. It asks for no email or sign-up and sends no data to the internet.

  • Update notice: at startup, and every six hours while it keeps running, the application checks a publicly hosted version file (GitHub) to tell you whether a new version is available. If you installed it from the Microsoft Store, that check is made to the Store, and the update is only installed when you accept it in the Windows dialog. As with any download over the internet, the hosting provider may log standard technical connection data (for example, the IP address). No information about your network is sent in that request.

  • Coverage map images: the map is drawn on images the application downloads from public mapping providers: OpenFreeMap (with OpenStreetMap data) and, only if you turn on terrain relief, the open elevation model Terrain Tiles (AWS Open Data). As with any web browsing, those providers may log technical connection data, including your IP address and which area of the map was requested. No information about your network is sent to those providers: not the locations you have saved, nor the names, IPs, MACs or metrics of your devices. All of that stays in your project. If you don't open the Coverage map, the application makes none of these requests.

  • Satellite view with Google Maps (optional, off by default): the application does not include any Google key. If you want aerial imagery, you create an API key in your own Google Cloud account and register it under Preferences → Map; the account, the quota and the billing are yours. While Satellite is active, Google receives your IP address and the coordinates of the area you are looking at, and that use is subject to Google's terms and privacy policy. Nothing about your network is sent to Google either. The key is stored encrypted in your operating system's credential store, tied to that machine and that user: it does not travel inside the project file, it is not copied when you share it, and you can delete it at any time from the same screen.

  • References outside your network (optional): if you add a public IP address or a domain as a Reference (for example, your provider's) and watch it, the application sends it a ping (ICMP) from your computer every few seconds to measure whether it responds and how long it takes; if it is a domain, it resolves it through your system's DNS. That destination sees your public IP address, as with any ping, and receives no data about your network. It stops as soon as you remove it or turn off its watch.

  • Messaging alerts (optional, off by default): if you turn them on under Preferences → Messaging, the application sends the sentinel's alerts to your WhatsApp or Telegram through CallMeBot, a free third-party service. It is the only feature that sends information about your network off your computer, so it is worth knowing exactly what goes out:

    • What is sent: the alert text, which contains the project name, the name and IP address of the affected devices, the name of their access point and what is happening to them (for example, "session down"). No credentials, passwords, location or project are sent.
    • Who receives it: CallMeBot's servers, which deliver it to your own phone. You choose the recipient and you authorize the bot from your phone; if you choose a Telegram group, the whole group will read the alert. Materis is not involved in that delivery and receives no copy.
    • When: only when the sentinel detects a fault, and only while the application is running (also with the window closed, from the system tray). Off, which is how it ships, no request is made.
    • Where your activation details stay: the phone number, the Telegram user and the CallMeBot key are stored only on your computer, among the application's preferences. They are not part of the project: they don't travel in a .sscope, they don't travel in a snapshot and they never reach our servers. Sharing a project or a snapshot never exposes them, and when you open the application on another machine you have to set them up again.
    • They are not encrypted, and it is worth knowing what that means: unlike your radios' passwords (section 5), this data is stored in plain text, so anyone who can use your Windows session can read it. This was done on purpose (they are credentials for your messaging service, not for your network, and encrypting them under a project's key would tie them to that project), but looking after the computer is up to you. CallMeBot's terms make you responsible for all activity through your account, so whoever obtains your key could send messages to your phone in your name.
    • What relying on CallMeBot means: it is a free third-party service for personal use and its own terms govern that delivery (https://www.callmebot.com/terms-of-service/). In them it states that it does not guarantee that data will be available, that it accepts no liability for the loss of any content, and that although it claims no ownership of what you send, it may access it as needed to provide the service; in other words, the alert text passes through its systems. It also prohibits uses such as spam or any unlawful purpose, and the sender is you. Materis does not control that service or take part in the delivery.

3. Location

SignalScope does not access your device's location or request it from the operating system. You place the coordinates of your nodes and stations yourself, by hand, on the map; they are stored in your project and only leave your computer if you share that project or a snapshot. When sharing a snapshot you can leave them out with the privacy feature (section 6).

4. What the application does inside your network

None of the following goes out to the internet: it happens between your computer and the devices on your own network, and its results stay in your project.

  • Discovery: it sends pings (ICMP) to the address ranges you configure and reads the system's ARP table to learn the MAC address of the devices on your local segment. It installs no drivers and captures no traffic.
  • Sessions with the radios: it opens sessions over SSH, HTTPS or HTTP with the credentials you register, and only reads status information (see section 7).
  • Diagnostic tools: continuous ping, traceroute and the heartbeat of the devices you mark for watching generate traffic towards the devices you choose, and only while you use them. (If you watch a Reference outside your network, that heartbeat does go out to the internet: it is described in section 2.)
  • Finding devices that change IP: when a device with a saved session stops responding at its address, the application looks for it on your network: it asks your access points which address they see their stations at, asks the stations which address they see their access point at, and reads the ARP table. If it finds the device at another address, it opens the saved session there and checks that it is the same device (by its MAC) before updating anything.
  • SNMP (optional, off by default): only if you enter a community, the application asks over SNMP for the identity of devices outside your local network and of those whose manufacturer it doesn't recognize. That community is stored encrypted in your project, but bear in mind that the SNMP v1 protocol does not encrypt the communication: it travels in clear text over your network, as with any tool that uses it.
  • Speed test server (optional): when you turn it on, the application opens a listening port on the address of your computer that you choose, so that a radio on your network can connect and throughput can be measured. Windows will ask for firewall permission the first time. The server only measures the volume transferred: it does not read, store or forward the content, and it stops listening as soon as you turn it off or close the application.

5. Your devices' credentials

The passwords for accessing your radios are stored encrypted on your computer. The master key that protects them lives exclusively in your user's and machine's operating system credential store; it is never saved in files and never leaves your computer. Copying a project to another machine does not expose those credentials.

In transit, SSH and HTTPS encrypt the session with the radio. HTTP does not: if a device only supports that mode, the credentials travel unencrypted over your network, and the application warns you so that the decision is yours.

6. Sharing snapshots

SignalScope lets you export snapshots as files that you choose to share by your own means. These files do not pass through our servers. In addition, the snapshot privacy feature lets you trim sensitive data (IP, MAC, names, model, location, etc.) before sharing, permanently.

7. Security

The application is read-only: it never changes your radios' configuration. Sensitive data is encrypted at rest, and the app uses the internet only to validate the license, announce new versions, download the map images, measure the References you add outside your network and (if you turn it on) send messaging alerts (section 2).

8. Retention and control of your data

Local data is under your control: you can delete it by removing the application's files or uninstalling it. License data (email, key and device identifier) is kept in the licensing system while your license is valid, and your purchase data for the periods required by accounting and tax obligations: the Materis policy details this (https://materis.io/en/privacidad). To exercise your rights over either of them, write to us.

9. Changes to this policy

We may update this policy to reflect product improvements or legal changes. The current version is identified by its "Last updated" date.

10. Contact

For privacy questions or to exercise your rights over your data, write to us at support@materis.io.

← Back to home