Sonar privacy policy
Effective 17 November 2026.
This policy covers Sonar, the Android app (one.adamkl.sonar) that measures your Wi-Fi and internet connection and reports it to a Chorus server. It says what the app collects, where it goes, who can see it, how long it is kept and how to have it deleted.
1. Who we are
Sonar is made and published by AdamKL, an individual developer and the developer named on Sonar's Google Play listing ("we" below). Questions, requests and complaints: sonar@adamkl.one.
2. How Sonar works: your data goes to one server
Sonar has no cloud of its own. When you enrol the app (by scanning a QR code or opening an enrolment link), you connect it to one Chorus server, and the app sends its measurements only to that server. Before you enrol, Sonar uploads nothing.
- During this beta, the Chorus server is run by us. It is a server in our home in Canada. Uploads reach it over HTTPS through a proxy on a virtual server we rent from OVHcloud in Canada, which passes them on over an encrypted tunnel.
- Anyone can run their own Chorus. If you enrol with a server someone else runs (yourself, your employer, a friend), that person decides how it is kept and used, and this policy doesn't cover their copy. Ask them.
One Chorus can serve several households. Each device's data is stored under that device. Other testers can't see your device's data: the app shows only its own device, and we give testers no accounts on our server.
3. What the app collects and sends
Sonar sends measurements continuously while it is enrolled, including in the background. The server receives:
About the phone
- manufacturer, model, Android version, kernel version and app version;
- a hardware id: a one-way hash of Android's
ANDROID_ID, never the raw value, so that reinstalling the app continues the same device record; - the phone's device name from Android's settings (often a person's name, such as "Alex's Pixel"). It is used as the device's default name on the server;
- the phone's Wi-Fi MAC address on the network it is connected to.
About your Wi-Fi connection
- the network's name (SSID) and its access point identifiers (BSSID and, on Wi-Fi 7, the AP MLD address);
- band, channel, channel width, Wi-Fi standard, security type, signal strength, link speeds and, for Wi-Fi 7, each link of the connection;
- the information elements the access point broadcasts (its advertised capabilities);
- connects, disconnects and roams, with the reason when Android reports one.
Nearby networks. Results of Wi-Fi scans: each nearby network's name, access point identifiers, band, channel and signal strength.
Connection tests
- round-trip times and lost replies to your router, to public DNS resolvers and to Echo (a test server run by the operator of your Chorus);
- hourly and twice-daily tests that time how long a few public websites take to answer (section 6);
- scheduled call, video, browsing and file-transfer tests, mostly against Echo (browsing tests also load a few public websites, section 6): about 1 GB a day by default, none on metered networks such as mobile data. The server's operator can schedule heavier tests for a device, up to a limit of 20 GB a day;
- your public IP address (as Echo and Cloudflare see it) and, looked up on the server, your internet provider;
- the phone's local IP addresses, the router's address and the DNS servers in use;
- the IP address each upload comes from, which the server records as it arrives.
Network state. Which network carries the phone's traffic, whether Android judged the network working, captive portals, whether a VPN is up, whether the network is metered, and the number of bytes and packets sent and received over Wi-Fi in total and by Sonar itself. Never the contents of your traffic, the sites you visit or which apps use the network.
Mobile network (if the phone has one): network type (such as LTE or 5G), operator name and signal strength. Not your phone number, IMEI or cell tower ids.
Power state. Battery level and charging, screen on or off, Doze, battery saver, Data Saver and temperature or thermal throttling, because they change how the phone uses Wi-Fi.
What the app detects and does. Events it detects (for example "Internet down" or "Wi-Fi disconnected"), the results of scheduled tests, and whether you are at home (section 4).
Diagnostic bundles. When a serious problem is detected, or when the server's operator asks, the app uploads a bundle: the last 15 minutes of measurements plus Sonar's own logs and, where Android allows it, Wi-Fi system log lines. By default bundles are redacted: every network name and hardware address except your own network's is replaced by a code that means nothing outside that bundle. The server's operator can turn redaction off. Chorus can also make a further-sanitized copy of a bundle for an internet provider or router maker; see section 6.
Advanced mode (optional, only if you set it up with Shizuku). Sonar then also reads Android's Wi-Fi diagnostics and Wi-Fi system logs. These can contain the names of apps that hold Wi-Fi locks or report connectivity problems, so app names reach the server. "Allow deep captures" (off by default) lets the server's operator turn on more detailed Wi-Fi logging for up to 30 minutes for one bundle.
4. Location
Sonar asks for precise location access, including all the time, even when the app is closed. Android requires it for two things Sonar does:
- Reading the Wi-Fi network's name and access point and scanning for nearby networks. Android hides these from apps without location access.
- Home location (optional, Settings › Home location). If you set your home on a map, the phone uses Google Play services' geofencing and occasional location fixes to tell whether you are home, leaving or away, so a phone leaving home isn't reported as a Wi-Fi outage.
Your GPS coordinates never leave the phone. The server gets only "home", "leaving" or "away".
Be aware, though, that some of what is sent reveals where you are:
- Access point identifiers (yours and your neighbours', from scans) can be looked up in public Wi-Fi location databases, which can place them within metres.
- Your public IP address and internet provider give an approximate location, usually the city or region.
5. Why we collect it
Only to diagnose your network: to tell you whether a problem is your phone, your Wi-Fi, your router, your internet provider or the far end, and to show it on graphs. There are no ads, no tracking, no analytics or crash-reporting SDKs, and we never sell your data or share it with anyone to market to you.
6. Other parties the app contacts
To take its measurements, the phone itself contacts these, which see your public IP address the way any website does:
- Cloudflare (1.1.1.1): ping and DNS timing, and a DNS query that tells the phone its own public address;
- CIRA Canadian Shield (149.112.121.10): DNS timing;
- public websites for timing tests: hourly,
www.google.com,www.cloudflare.comandwww.wikipedia.org; twice a day, the front page of a few popular sites (such as Google, YouTube, Wikipedia, GitHub or CBC). Only the page itself is fetched, without signing in; - LibreSpeed servers (the list at librespeed.org), only if the server's operator schedules public speed tests for your device (off by default);
- Echo, the test server named by your Chorus. During this beta it is ours, on the OVHcloud server in Canada. It counts the bytes each device sends it per day;
- Google Play services on the phone, for geofencing and location fixes if you set a home location. Google's handling of location data is covered by Google's privacy policy and your phone's location settings.
The server's operator can change which test targets and sites are used. On the server side:
- internet provider lookups use a database stored on the server; your address isn't sent anywhere to look it up;
- diagnostic bundles are shared with someone else only at your explicit request or with your explicit consent, for example to send your internet provider evidence of your own problem, and then only as the sanitized copy (names, IP addresses and other networks' identifiers replaced);
- if the server's operator sets up alerts, a short alert (device name, problem and time) goes to the notification service they chose;
- we sometimes use an AI assistant (Anthropic's Claude) to help read diagnostic data on our server. The data it reads for a question is sent to Anthropic to produce the answer.
7. How long it is kept, and deleting it
On our server:
| Data | Kept for |
|---|---|
| Detailed measurements | 14 days |
| Per-minute summaries | 13 months |
| Per-30-minute summaries, the device record (model, device name, hardware id) and detected events | until the device is deleted |
| Networks the device was on (names, access points, public IP, internet provider, home/away) | 13 months after last seen |
| Wi-Fi MAC addresses | 90 days after last seen |
| Upload addresses (the IP the uploads came from) | 14 days |
| Test runs | 13 months |
| Diagnostic bundles | 90 days |
| Alerts sent about the device | 90 days |
| Uploads the server couldn't store (kept for repair) | 30 days |
To have your data deleted, or to get a copy of it, email sonar@adamkl.one from the address you were invited with, and say which device. We delete the device and everything stored about it, usually within a week and always within 30 days. Uninstalling the app stops all collection but doesn't delete what is already on the server, so ask us.
On the phone, Sonar keeps measurements until they are uploaded (at most 50 MB), uploaded ones for 15 minutes, up to 5 diagnostic bundles waiting to upload, a list of problems for 8 days, and your settings and home location. Uninstalling the app deletes all of it. The app's data is excluded from Android backups.
8. Security
- Everything the app sends to Chorus goes over HTTPS; the app refuses unencrypted connections to the server.
- Each enrolled phone has its own secret device token. The server's operator can revoke it at any time.
- On the phone, data waiting to be uploaded is stored in the app's private storage, which other apps can't read.
9. Local API (off by default)
Settings › Local API lets a computer on your own Wi-Fi network read this phone's live status, protected by a token you copy from the app. It listens only on your Wi-Fi network, and it uses plain HTTP, so the status is unencrypted on your local network. Turning it on means you choose to share that status with that computer.
10. Children
Sonar isn't directed at children and is not meant for anyone under 13. We don't knowingly collect data from children. If you think a child's phone was enrolled, write to us and we will delete it.
11. Your choices
- Don't grant location: Sonar can't see network names or access points and works only partly.
- Leave Home location, Advanced mode, deep captures and the Local API off (they are off by default).
- "Pause monitoring while away" stops measuring when you aren't home.
- Ask us at any time to see, correct or delete your data.
12. Changes
If this policy changes, the new version is posted at this address with a new effective date. If a change means the app collects more, or sends data somewhere new, we will tell testers before it takes effect.