Home / Privacy
Privacy policy

Privacy Policy

Effective: 19 November 2026 (updated)
The core app works without optional sharing.

Diagnostic Data Sharing and Usage Analytics are separate choices. You can use Check, Live Monitoring, History and Reports without enabling either one.

At a glance

1. What this policy covers

This policy explains how Diagnostix360 handles information in the Android app and on diagnostix360.com. Diagnostix360 is operated by the developer/publisher identified for the app on Google Play. Privacy questions can be sent to support@diagnostix360.com.

2. Diagnostics processed on your device

Speed Test and local history. When you start the optional Speed Test, the app exchanges download and upload test traffic with Diagnostix360's Cloudflare-hosted endpoints. It measures download and upload throughput, ping, jitter, loaded latency, duration and the transferred byte count. Recent results can be stored locally on the phone, with a Wi-Fi name when Android makes it available. Speed testing uses real bandwidth and may use mobile data.

Reminders and notifications. The app can remind you to check your connection again: once at a time you choose (for example “Check again tonight?” at 9 pm), and, if you have not opened the app for 3 days, a friendly reminder (then one more 7 days later and a last one 14 days after that; never between 9 pm and 10 am). These reminders are scheduled on your phone by Android; nothing is sent to us to set them and they never start a measurement. They appear only if you allow notifications; you can turn them off at any time in Android’s settings for the app. Opening the app resets the 7-day reminder.

When you run a feature, Diagnostix360 may read or calculate network and device-side diagnostic information such as Wi-Fi signal and channel data, local network details, gateway and DNS information, mobile radio measurements, public-IP/ISP information, route and service results, and technical timestamps. Android may require Location or Nearby Wi-Fi permissions to expose some Wi-Fi scan information. If a feature uses device location, Diagnostix360 reads it locally only; from version 3.40.0 no report shows a location, and the Customer report does not show the Wi-Fi name. Optional diagnostic telemetry is designed to exclude GPS coordinates and location fields.

Detailed diagnostic results, local History and generated reports are primarily processed and stored on your device. Clearing app data or uninstalling the app can remove local data.

3. Optional Diagnostic Data Sharing

Optional speed-result telemetry. When Diagnostic Data Sharing is enabled, a summarized speed result may be uploaded to the separate diagnostic service: download and upload speeds, idle and loaded latency, jitter, test duration and amount transferred, broad network type, test time, app version, Cloudflare test-region code and the app-scoped Privacy ID. Network-derived ISP/ASN may be included. The diagnostic payload is designed not to include Wi-Fi SSIDs, raw IP addresses, exact GPS coordinates or hardware identifiers.

Speed comparison (app 3.41.0 and later). The app can show how your download speed compares with other Diagnostix360 users, for example “Download faster than 74% of all Diagnostix360 Wi-Fi users”, with a short badge such as “Top 25%” and a tip. The comparison is built only from results shared through Diagnostic Data Sharing in the last 30 days, with one test per device per day and network and one typical value per device; tests held back by the phone’s Wi-Fi link, a VPN, a data limit, a weak signal or automation are left out (a test held back by your own Wi-Fi link is still placed for you on your screen, with a note, but never used for others). To show it, the app asks our server for these group figures; the request carries only the network type (Wi-Fi or mobile data), never your result or Privacy ID, and the server stores nothing about it. Your own result is placed on your phone. If Diagnostic Data Sharing is on, the server also reads your provider from the connection, as any website sees your network, so you can compare with users of the same provider; a provider is shown only when at least 20 devices contribute (as a percentage from 50 devices). Wi-Fi is compared only with Wi-Fi, and mobile data only with mobile data. If it is off, you are still compared with all Diagnostix360 users: the app asks for the all-users figures only and the provider is not looked up. The app never shows the typical speed of a provider. The comparison is kept on your phone with that check or speed test and appears in its reports. A ranking image or an invitation leaves your phone only if you choose to share it.

If you enable Diagnostic Data Sharing, Diagnostix360 may send a privacy-minimized diagnostic summary for product improvement, calibration, abuse protection and aggregate ISP analysis. The summary may include broad test timing, transport type, app/scoring versions, result/problem codes, generic symptom category, ISP/ASN, summarized radio, Internet, DNS and readiness measurements, and a random app-scoped Privacy ID.

The diagnostic payload is designed to exclude raw IP addresses, Wi-Fi names, BSSID/MAC addresses, GPS coordinates, Android/Advertising IDs, account IDs, IMEI, hardware identifiers, cell identity, nearby-network identities, traceroute/resolver address lists and the full per-second raw timeline.

The Privacy ID is randomly generated for the app installation. It is not derived from Android ID, Advertising ID, IMEI or an account. Turning Diagnostic Data Sharing off stops future diagnostic uploads. The ID may remain in app-private storage so you can quote it in a later privacy request; it is lost if app data is cleared or the app is uninstalled/reinstalled.

4. Optional Usage Analytics

Speed Test usage events, such as start, completion and coarse duration/status, may be included in optional Usage Analytics. These events are not intended to include measured throughput, ping, SSID, IP addresses or the diagnostic Privacy ID.

If you separately enable Usage Analytics, Diagnostix360 may send broad product events to Google Analytics for Firebase, such as feature opened, diagnosis or Live Monitoring started/completed, broad transport/mode and duration buckets, report generated and whether the network changed during Live Monitoring.

Diagnostix360 does not add raw diagnostic measurements, score values, ISP/ASN, report/run IDs, Wi-Fi/cell identifiers, GPS coordinates or the Diagnostix360 Privacy ID to Firebase Analytics event parameters. Google may process its own app-instance, device, session and network-derived information under its own terms. Advertising-ID collection and ad-personalization signals are disabled in the app configuration.

5. Core network requests and third parties

AI Diagnosis (“Explain my result”). When a check finishes with “Explain my result with AI” ticked in the Start a check window (ticked by default from app 3.41.0; untick it and the app remembers your choice and sends nothing), or when you tap the AI button under a finished check, the app sends a summary of that check to Diagnostix360’s AI service, which runs on Cloudflare (Cloudflare Workers AI). The summary contains the result and problem codes, the app’s own result text and suggested steps, the activity ratings shown on screen, the status of each step of the report’s connection path (good, watch or problem), figures such as Wi-Fi or mobile signal strength and quality, the Wi-Fi channel number, delay, jitter, packet loss, website-lookup time and speed-test results, the broad connection type and the app language. It does not include Wi-Fi names, IP addresses, operator names, location or any report. Only if you turned on Diagnostic Data Sharing, it also carries the diagnostic Privacy ID, so that AI use can be studied together with the anonymous statistics.

To apply the free daily limit, the request also carries a device key: a one-way code calculated on the phone from Android’s app-specific device ID. It cannot be turned back into that ID and it stays the same if the app is reinstalled; it is linked to the Privacy ID only when Diagnostic Data Sharing is on. The AI service stores only a daily counter per device key and which checks were explained that day (kept for up to 90 days), and, without any text or device key, whether the AI found the app’s score consistent with the measurements (kept 90 days, to review the scoring), plus a per-network daily counter keyed by a salted, one-way code of the network address (kept for 2 days). It also keeps, for 90 days and without any text, a record of each request’s outcome (whether an answer was given, which AI model answered or why an answer was rejected, how long it took and the language), and your optional helpful / not helpful rating, linked only to the check’s one-way code. If you turned on Diagnostic Data Sharing, the measurements sent to the AI and its answer are kept for 30 days so we can check and improve the quality of the answers. Without it, nothing the AI wrote is stored.

The answer is shown in the app and kept on your phone. If you created reports for that check, the AI explanation and next steps are used in them, so it is included when you choose to share a report, for example with your provider. AI Diagnosis is separate from Diagnostic Data Sharing: with the option unticked, nothing is sent unless you tap the AI button. When the Start a check window opens, the app asks the AI service how many free explanations you have left today; that request carries only the device key and counts nothing. The AI forms its own diagnosis from the measurements, and its answer becomes the conclusion shown for that check; AI answers can contain mistakes, and the measurements remain the reference. Share result creates an image of the AI answer on your phone and shares it only when you choose to. If the first request fails quickly (within 20 seconds, for example after a brief network drop), the app sends the same summary once more by itself; a check is counted only once. To answer faster, the AI service may ask a second AI model at the same time when the first is slow, and uses the first answer that passes its checks; both models run on Cloudflare Workers AI and receive the same summary. As with any Internet request, Cloudflare receives normal connection information such as your IP address to deliver the request.

Speed Test infrastructure. A speed test is performed only when you choose it. Cloudflare and networks routing those connections necessarily process normal network information, including your source IP, to deliver test traffic and provide service-security/rate-limiting functions. The Speed Test endpoint is not designed to publish individual measurements as a public dataset. Diagnostic telemetry, if enabled, is a separate optional processing flow.

Network diagnosis requires ordinary Internet requests. The services contacted, and the networks carrying those requests, necessarily receive normal connection metadata such as the public source IP needed to route traffic. These requests can occur even when optional Diagnostic Data Sharing is off because they are part of the test you asked the app to perform.

Providers used by the app or website may include Cloudflare, Google/Firebase, public-IP lookup services, ISP/profile lookup services, DNS resolvers, regional reference targets and common Internet-service endpoints. Providers and endpoints can change as the product evolves. Third-party services process data under their own terms and privacy policies.

6. Reports, sharing and invitations

Depending on the tests run, Customer and Technical reports may also include optional speed-test values. Live Monitoring can produce a separate report containing session periods, quality categories, delay, jitter, packet loss, available network information and exact measurement times. Review every export before sharing; Customer reports normally expose fewer identifiers than full Technical reports.

Ranking images and invitations. “Share” under the speed comparison creates an image on your phone (your result, the comparison and a QR code to Google Play; never a Wi-Fi name, IP address or location). “Invite a friend” opens Android’s share sheet with a short message and a Google Play link; you choose the app and the person, and the app does not read your contacts. These Google Play links carry only a campaign name (such as “share_rank” or “invite”), so Google Play can tell us how many installs came from shared links, never who shared or who installed.

Customer and Technical reports are generated locally. The Customer report is the safer default for ordinary support. A Technical report can contain network names, IP/ISP/ASN information, configured DNS, approximate area, nearby Wi-Fi details, traceroute information, mobile operator/cell information and exact timestamps depending on report privacy settings. If you choose to share a report, email, screenshot or support log, the information you share leaves your device through the method you choose.

7. Retention and security

Where optional Diagnostic Data Sharing is enabled, summarized speed-result rows are included in the diagnostic retention policy below. Local Speed Test history follows Android app storage behavior and can be cleared using app settings where offered.

  • Diagnostic rows, including the random app-scoped Privacy ID, may be retained for up to 365 days when Diagnostic Data Sharing is enabled. This supports longitudinal calibration, deduplication, abuse protection, aggregate ISP analysis and privacy requests.
  • At the end of the retention period, those rows are deleted or irreversibly de-identified. Limited information may be retained longer only where required by law or reasonably necessary to establish, exercise or defend legal claims.
  • AI Diagnosis: daily counters per device key, request outcomes and ratings are deleted after 90 days, per-network counters after 2 days. Measurements and answers are kept only with Diagnostic Data Sharing on, and are deleted after 30 days. To reset or delete your AI data, send us the AI code or the Privacy ID shown in the app.
  • Local reports, History and caches remain subject to your device, app settings and normal Android storage behavior.
  • Firebase Analytics retention is controlled by the Analytics property and Google service rules; Google may retain aggregated or service data under its own policies.

Telemetry is sent over HTTPS and the app/server use allow-list and validation controls intended to reduce unnecessary data collection. No Internet-connected system can be guaranteed completely secure.

8. Your choices and requests

You can turn Diagnostic Data Sharing and Usage Analytics on or off independently, revoke Android permissions, clear local app data, and choose not to share reports. Turning a setting off stops future collection through that setting; it does not necessarily erase data already processed by third-party services.

If you previously enabled Diagnostic Data Sharing and want us to check whether current pseudonymous rows remain linked to your installation, email support@diagnostix360.com and include the Privacy ID shown in Settings. If matching rows still exist and can be identified, we will handle the request as required by applicable law. After rows are deleted or irreversibly de-identified, or if the Privacy ID is no longer available, we may no longer be able to associate older rows with you.

9. Children and international processing

Diagnostix360 is a general-purpose network utility and is not directed specifically to children. Where local law requires parental or guardian consent for optional data sharing, that consent should be obtained before enabling it. Cloud and network providers may process data in different countries under their own legal and contractual safeguards.

10. Website interest and pilot forms

If you submit an iOS availability form or a provider-pilot form, we receive the information you choose to send, such as your email address and, for provider enquiries, company, role and message. The website stores these submissions in our Cloudflare-hosted lead database so we can send the requested iOS notification or respond to the provider enquiry.

We do not use these form submissions to add raw diagnostic measurements to a marketing profile. You can ask us to delete a website form submission by contacting support@diagnostix360.com from the same email address.

11. Website, changes and contact

Free online test. The test on the Speed test page runs in your browser and contacts our speed-test server (speed.diagnostix360.com). When a test ends, the page sends its result to that server: download and upload speed, ping, jitter, the delay when the line is busy, which popular services opened, the data used, the page language and whether data saver was on. The server adds the kind of device (phone, tablet or computer), its system and browser (worked out from what your browser reports, which is not kept), and the country and internet provider as Cloudflare sees them. We use these records, kept for 365 days, to see how the online test is used and to improve it. They contain no IP address, no city and no identifier. To limit each person to 25 online tests a day, the server also keeps a one-way code made from your network address with a key that changes every day; it cannot be turned back into the address and is deleted the next day. To check whether popular services open, your browser contacts those services directly (Google, YouTube, WhatsApp, Facebook, Instagram, TikTok, Netflix, Microsoft, Cloudflare and ChatGPT), without cookies; they receive an ordinary request from your browser. If you tap Share, you choose where your result goes.

Google Play buttons and the troubleshooter. When you press a Google Play button on this website, it goes through diagnostix360.com/get/… and we add one to a daily counter for that button. The counter keeps only the day, the name of the button (which includes the page language) and the kind of device (Android, iPhone or iPad, or other), worked out from what your browser reports, which is not kept. It keeps no IP address, no cookie and no identifier, and the counts are kept for 400 days. Google Play then shows which of our pages sent the visit (a campaign name in the link) and the kind of place you arrived from (for example Google search, Facebook or a direct visit), not who you are. That last label is kept only in this browser tab while you browse (session storage, cleared when the tab is closed) and is passed on to Google Play without being stored by us. The troubleshooter pages run nothing on your device and send nothing. The Report for your provider in the online test is built in your browser from the result on screen: we do not receive it, and you choose whether to print, save or send it.

diagnostix360.com is delivered through Cloudflare. Normal request/security metadata may be processed to deliver and protect the site. Diagnostix360 does not use advertising cookies. If Cloudflare Web Analytics is enabled, it is used for aggregate website measurement without analytics cookies or localStorage, while Cloudflare may still use strictly necessary security/network mechanisms.

We may update this policy when the product, providers or legal requirements change. The effective date above will be updated when we do. Questions: support@diagnostix360.com.