SSIDekick privacy policy
SSIDekick has no account, no ads, no analytics and no tracking libraries. Your scans, measurements and saved results are stored on your phone and nowhere else. Data leaves the phone only when a tool has to talk to a server to do its job, and those servers are listed below. The only data we, Iceamp Labs, ever receive is a bug report or feedback that you choose to send.
Who we are
SSIDekick is made by Iceamp Labs, Sweden, which is the data controller for the information described here. Contact: play@iceamp.com.
Permissions and why the app asks for them
| Permission | What it is used for |
|---|---|
| Location (precise) | Android only gives apps Wi-Fi scan results, the connected network's name and mobile cell information when location access is granted. The GPS tool also shows your position and satellites, and the coverage log records your track, from GPS alone unless you turn on its “Wi-Fi and sensor positioning”: that uses Android's fused location, which, when Google Location Accuracy is on in your phone's settings, has Android send nearby Wi-Fi networks and cells to Google to work out the position (Google's processing, under your phone's settings, not the app's). Your location is never sent anywhere by the app itself; it only leaves the phone if you tap “Open on map”, turn on the coverage log's Map, or export a coverage recording (see below). |
| Nearby Wi-Fi devices | Scanning for Wi-Fi networks and reading their details. |
| Nearby Bluetooth devices | The Bluetooth tool's scan for devices advertising nearby (names, signal, maker). Declared to Android as never used for location. The device list exists only while the screen is open and is never sent. With Pro, tracker sightings are kept as described below: while the Bluetooth screen is open, and in the background whenever the long-term roaming log, the background cell watch or the background twin watch is on (the tracker watch has no switch of its own; it runs with those). On Android 11, Bluetooth scanning also needs location access. |
| Phone state | Reading the serving and neighboring mobile cells, the SIM's network and roaming status for the Cellular tools. The app never reads your phone number, call log, contacts or messages. Separately, and without any permission, the app reads the SIM's country code (or, without a SIM, the mobile network's) each time it starts, only to tell you that SSIDekick is not offered in Russia or Belarus; it isn't stored or sent. |
| Local network access | Discovering devices on your network, Wake-on-LAN, and bandwidth tests against your own equipment. |
| Change Wi-Fi state | Only for “Test through this AP”, on tap: the phone briefly joins the network you picked to test it, then returns. |
| Internet | The online tools listed below. |
| Notifications, foreground service, start at boot | Only used if you turn on the long-term roaming log, a background watch (cell, twin or host watch) or new-device alerts, or record coverage: Android requires a visible notification for anything that keeps running, and alerts arrive as notifications. Host watch resumes after a restart. |
| Foreground service (location type) | Only if you turn on the optional long-term roaming log, let the cell watch or twin watch run in the background, or record coverage. Android shows the connected access point's address and the GPS position to a service that keeps running only when it is of this type, and only when you start it from the app. It runs with a permanent notification. The roaming log and twin watch record no position; the cell watch keeps the rounded area described below, as it does with the screen open; a coverage recording keeps your GPS track until you delete it. |
Every permission is optional. A tool that needs a permission you haven't granted is shown as unavailable; the rest of the app works.
What stays on your phone
The app stores the following in its private storage, which other apps can't read:
- Wi-Fi scan history, saved scans, the names you give access points and your list of own networks.
- Saved bandwidth tests with your comments, speed test settings and custom servers, ping targets and Wake-on-LAN favorites.
- Cell watch history: the identities of mobile cells your phone has used, when they were seen, and the area they were seen in, rounded to about 1 km. This is what lets the app notice a cell that suddenly appears somewhere else.
- Widget state (current network name, addresses and a short traffic history) and which tools you use most, to order the home screen.
- Twin watch (if you use it): what your own Wi-Fi networks normally look like (their access points' addresses and settings, and the gateway and DNS server seen when connected), to notice copies.
- Tracker watch (Pro; see Nearby Bluetooth devices above for when it runs): for the last 24 hours, when a location tracker that is away from its owner was heard and which access point your phone was on at the time. No position is recorded; this is how the app tells whether a tracker moves with you.
- Coverage recordings (if you make them): your GPS track with the Wi-Fi access points and mobile cells heard along it. Each recording stays on the phone until you delete it, and is only exported when you choose to.
- Device history: for each local network you scan with LAN discovery (up to 20), the devices found there (up to 500 per network) with their addresses, the names and MAC addresses they gave, and when each was first and last seen. You can forget a device or clear a network's history in LAN discovery.
- Host watch (if you use it): the hosts you chose to watch and, for each, when it last answered and its outages (up to the last 100).
- If you turn it on, the long-term roaming log: the times your phone connected to, moved between or lost access points, with each access point's address, network name, band and signal. No position is recorded. Entries older than 30 days are deleted, and you can clear the log at any time.
Uninstalling the app, or clearing its storage in Android's settings, deletes all of it. Country lookups for traceroute use a database built into the app, so the addresses you trace are not sent to a lookup service.
Backups. If Android backup is turned on for your Google account, Android may include this app's storage in that backup, handled by Google under your account and settings; Iceamp Labs cannot access it. The roaming log, coverage recordings, tracker sightings, the cell watch history, device history and the twin watch's profiles of your own networks are always left out of backups and phone-to-phone transfers: they are collected automatically and amount to a history of where you have been. Saved scans and the access point names you gave are backed up like your other settings, because you chose to keep them; they contain access point addresses, which can indicate where a scan was made.
Exports. Reports, certificates and saved results are only written to a file or shared when you choose to, and go where you send them.
What leaves your phone, and where it goes
Network tools work by sending traffic to other machines. The servers involved see your phone's public IP address, as any server you connect to does. None of them receive an identifier for you or your device from SSIDekick.
| When | Sent to | What |
|---|---|---|
| Home screen, while connected | Cloudflare (stun.cloudflare.com), with Google (stun.l.google.com) as fallback | A standard STUN request, to learn your public IP address. Sent automatically when the network changes. |
| Internet checkup | Cloudflare (1.1.1.1), your network's DNS server, and the STUN servers above | Connection and name lookup tests, to measure whether and how well the internet connection works. |
| Speed test | Cloudflare (speed.cloudflare.com), a LibreSpeed server you pick (the list comes from librespeed.org), or a server you enter | Test data downloaded and uploaded to measure speed. |
| Ping, traceroute, HTTPS check, DNS lookup, port and LAN scans, Wake-on-LAN, bandwidth tests | The host, address or DNS resolver you choose, which may be Cloudflare or Google DNS-over-HTTPS | The probes, queries and test traffic of that tool. |
| Host watch, while you have it on | The hosts you chose to watch | A ping, a connection attempt to the port you chose, or an HTTPS request, at the interval you set, also while the app is closed. |
| New-device alerts, while you have them on | Devices on your local network | The same probes as a LAN discovery scan, about as often as you chose, while the phone is on a network you watch. Nothing leaves your network. |
| Port forwarding check, when opened or on tap | Your router, and other devices on your local network that answer the UPnP search | A UPnP search and requests that list the router's port forwards and its internet address, and a NAT-PMP/PCP probe. The app changes a forward only when you tap Remove or Add, and only on your router. Nothing leaves your network. |
| Latency monitor and “Test through this AP”, when started | Your router and DNS server, and Cloudflare (1.1.1.1) as the internet reference unless you change it | Pings, to compare where delays and losses happen. |
| Bandwidth server, while you have it on | Devices on your local network | The phone accepts bandwidth tests from devices on the same Wi-Fi or Ethernet network only (never mobile data or a VPN). Unless you turn announcing off, it also announces itself on that network under the name you set (by default “SSIDekick” and its model name). Nothing leaves your network. |
| “Look up owner” on a host page or in DNS lookup, on tap | IANA (data.iana.org), then the regional internet registry for the address (ARIN, RIPE NCC, APNIC, LACNIC or AFRINIC) | The address you are looking up, to fetch its public registration (whois/RDAP). |
| “Look up registration” in DNS lookup, on tap | IANA (data.iana.org, or whois.iana.org for domains whose registry has no RDAP), then that domain's registry (for example Verisign for .com, Internetstiftelsen for .se) | The domain name you typed, and if the registry doesn't know it, the same name without its first part (www.example.se, then example.se), to fetch its public registration. |
| “Look up site location” in Cellular, on tap | beaconDB (api.beacondb.net), an open, crowd-sourced location service | The identity of the selected cell (country and network code, area code, cell ID). Your own position is not sent, and the request asks beaconDB not to use your IP address. |
| Export of a coverage recording, on tap | Wherever you send or save it (for example Google Earth, Drive or email) | Your GPS track with the signal readings along it, in the format you chose (KML, CSV or WiGLE). Opening the KML file in Google Earth makes Google Earth load its standard map-pin icon from Google. |
| Coverage log map, only if you turn Map on | The OpenStreetMap Foundation (tile.openstreetmap.org) | Requests for the map images of the area shown on screen or in a PDF report, which reveal that area (for a recording, where you went) and your IP address. Images are kept on the phone so the same area isn’t downloaded again, deleted once not shown for 7 days, and all deleted when you turn Map off or delete a recording. When a kept image is older than the server allows, the app asks the server whether it changed, which again shows that area. Map is off until you turn it on. |
| Open on map, on tap | Your map app, or openstreetmap.org in the browser if you have none | The coordinates being shown. |
| Bug report or feedback, on tap | Iceamp Labs (iceamp.com) | See below. |
These services handle requests under their own privacy policies: Cloudflare, Google, beaconDB, the OpenStreetMap Foundation, and the operator of whichever LibreSpeed server you choose.
Bug reports and feedback
The same applies to the form on iceamp.com/ssidekick/support, which sends what you typed, the email address if you entered one, the app version and phone if you typed them, and your browser's user agent, window size and language.
When you send a report from the app's About sheet, we receive what you typed, the email address if you entered one, and a short context block that the form shows you before you send: app version, Android version, phone manufacturer and model, screen size, display density, font scale and language. The receiving server also sees your IP address. Reports arrive by email at Iceamp Labs and are used only to fix problems, improve the app and reply to you. We keep them as long as needed to handle them and no longer than two years. You can ask us to delete a report at any time.
The legal basis is your consent, given by sending the report, and our legitimate interest in fixing the app.
Purchases
SSIDekick Pro is bought through Google Play. Google processes the payment; we never see your payment details. The app only learns from Google Play whether Pro has been bought (and keeps that answer on the phone, so Pro works offline). The Google Play Billing library in the app talks to the Google Play Store app on your phone and sends Google its own diagnostic data, under Google's privacy policy.
What we don't do
- No advertising, and no advertising or analytics SDKs.
- No selling or sharing of personal data.
- No account, profile or device identifier.
- No collection of your location, network scans or measurements.
Children
SSIDekick is a technical tool for a general audience and is not directed at children under 13.
Your rights
Under the GDPR you can ask for access to, correction of or deletion of personal data we hold about you, which in practice means bug reports and feedback you have sent (how to ask for deletion). Write to play@iceamp.com. Everything else lives on your phone, under your control. If you think we handle your data wrongly, you can complain to the Swedish Authority for Privacy Protection (IMY) or the authority where you live.
Changes
If this policy changes, the new version is published here with a new effective date. If a change means more data leaves your phone, the app will say so before it happens.