Home / Privacy
Privacy

Privacy Policy

Last updated: 16 August 2026
No Diagnostix360 diagnostic cloud.

The current production app does not require a Diagnostix360 account and does not automatically upload your combined diagnosis, local history, monitor history or generated PDFs to a Diagnostix360 application backend.

Important: “Processed on device” does not mean “no network traffic.” A network diagnostic must contact gateways, resolvers and selected third-party targets. Those parties can receive ordinary network metadata such as your public IP address.

1. Scope and contact

This Privacy Policy applies to the Diagnostix360 Android application, diagnostix360.com and support communications. Privacy questions may be sent to support@diagnostix360.com.

2. No account and no remote diagnostic storage

The app does not require a Diagnostix360 account. Diagnostix360 does not operate a cloud service that automatically receives or stores your completed diagnostic record, local diagnostic history, Internet Monitor sessions or generated reports.

Android application backup is disabled for the app. Local app data remains controlled by the device and can be removed through available in-app controls, Android app-data controls or uninstalling the app, subject to copies you separately save or share.

3. Information processed locally on your device

Depending on your connection, Android version, permissions and the features you use, Diagnostix360 may process locally:

  • Wi-Fi radio information such as signal level, network name, BSSID where available, band, channel, negotiated link information, security and nearby Wi-Fi scan results.
  • Mobile radio and operator information where Android exposes it, including signal metrics, network technology, roaming and available cell information.
  • Local/public network addresses, gateway, configured resolver, ISP/ASN and other active-connection identity information.
  • Delay, jitter, reply/no-reply, DNS, TCP/TLS/HTTPS, route, traceroute, service-setup, radio and other diagnostic measurements.
  • Run identifiers, timestamps, scores, findings, readiness estimates, confidence information and local history.
  • Approximate location when permission is granted and the relevant feature or report option uses it.
  • Generated Customer, Technical and monitor/availability reports.
  • Bounded local operational events and crash metadata used only for user-initiated support exports.

This information is used to run the feature you requested, display the result, build local history, generate reports and support troubleshooting. It is not automatically sent as a combined diagnostic record to a Diagnostix360 backend.

4. Android permissions and special access

Android may require network-state, Wi-Fi-state, nearby-Wi-Fi, location, notification, foreground-service or other permissions to expose the information needed by a feature. You can deny or revoke permissions; some measurements or fields may then be unavailable.

Diagnostix360 does not use these permissions to read message content, typed text, contacts, passwords, authentication tokens or unrelated personal files.

5. Network traffic created by diagnostics

When you start a diagnosis or the Internet Monitor, the app sends ordinary test traffic to the active network's gateway and/or configured resolver and to selected public, regional or service endpoints. Requests may include normal network metadata such as source public IP, protocol information, DNS query names used for the test, TLS/HTTPS setup metadata and timing.

Targets, network providers and intermediate networks are third parties and may log or retain traffic under their own policies. Diagnostix360 does not control those third-party logs.

6. Customer and Technical reports

Each completed full diagnosis creates local Customer and Technical PDF reports from the same finalized run. The Customer report is intentionally simplified and omits sensitive technical identifiers such as SSID/network name, IP addresses, location and operator identity. The Technical report is the advanced evidence package and can contain sensitive diagnostic identifiers, including public/local IP addresses, ISP/ASN, active network name, configured DNS addresses, approximate location, nearby Wi-Fi names, device information, mobile-operator/cell information, traceroute hop addresses and exact timestamps when those fields are available.

The current production report build does not include per-application traffic analytics or application-name lists. Before selected sensitive reports are shared, the app presents a confirmation explaining that the PDFs may contain sensitive identifiers and requires an acknowledgement. You are responsible for previewing the report, choosing a trusted recipient and selecting the sharing channel. Once a report leaves your device, the recipient and the selected email, messaging, storage or cloud provider control their copies.

7. Report IDs and local linking

A report ID is used to identify a report and, where available, link it to the saved run on the same device. It is not a cloud retrieval key and does not let an ISP or other third party remotely fetch your diagnostic data.

8. Internet Monitor

The Internet Monitor starts only after the user starts monitoring. It runs visibly for the selected duration and can be stopped by the user. Session times, probe results, outages/gaps and generated monitor reports are stored locally. The monitor is not scheduled automatically and is not intended to restart itself after reboot.

9. Local Devices utility

The Local Devices/Full scan utility is user-started and limited to the active local Wi-Fi network. It may use local discovery methods and bounded local probing to identify devices that respond during the scan. Discovery-derived details can include local IP address, visible device names, opportunistically visible hardware addresses, model/service hints, responsive local services and last-seen information.

The utility is separate from the core diagnosis, does not affect the Health Score or readiness result, and is not uploaded as part of support telemetry. Use it only on networks you own or are authorised to administer.

10. User-initiated support and crash exports

The app can create a privacy-filtered support log or crash report locally. It does not transmit these automatically. When the user chooses Send support log or Send report, the app hands the generated file to the user's email/share application for review and sending.

The support export is designed to exclude or redact network names, BSSID, operator names, IP/MAC addresses, URLs, email addresses stored in app events, file-system paths, application names, device identifiers, report IDs, report content and individual target results. Crash payloads avoid including exception messages and instead use limited technical crash metadata. Because the message is sent through the user's own email/share application, the sender email address may still be visible to the support mailbox.

Opening a share/email app is not treated as proof that a message was sent. Local support/crash evidence is bounded by retention limits and pruned so it does not grow indefinitely.

11. Support communications

If you email support, Diagnostix360 and the email providers involved receive the message, sender address and anything you attach or write. Send only what is necessary. Do not send passwords, API keys, authentication tokens, payment-card information or unrelated private files.

Support communications may be retained as reasonably needed to respond, investigate defects, prevent abuse, maintain necessary records or comply with law, and may be deleted or anonymised when no longer needed where reasonably practicable.

12. Website data

diagnostix360.com does not require an account and the current site does not use Diagnostix360 advertising cookies, behavioural analytics pixels or third-party font services. The hosting/security provider may process standard request and security information such as IP address, browser/user-agent, requested URL, time and security events to deliver and protect the website under its own policies and configuration.

13. Advertising and payments

The current production source reflected by this policy does not use diagnostic results to build an advertising profile or for cross-app/cross-site tracking and does not include a Diagnostix360 diagnostic-data advertising backend. If advertising, analytics, cloud processing or paid features are added in a future release, this policy and the applicable Google Play Data safety disclosures will need to be updated to match the production behavior.

If Google Play processes a purchase in a future paid offering, Google controls payment-card processing under its own terms. Diagnostix360 would receive only the entitlement/purchase status required by the app, not full card details.

14. Retention and deletion

  • Local diagnosis, history and monitor data: retained locally until removed through available controls, Android app-data controls or uninstall.
  • Generated reports: retained wherever you save or share them. Diagnostix360 cannot delete copies it never received.
  • Local support/crash evidence: bounded by count, size and age and automatically pruned.
  • Support email: retained as described above and deletable on request where reasonably possible and legally permitted.
  • Website hosting/security logs: controlled by the hosting/security provider under its own settings and policies.

15. Security

The application is designed to minimize remote data collection and to keep diagnostic records local. No device, storage or transmission method is completely secure. You are responsible for device security, Android updates, screen locks, report recipients and the third-party services used to share files.

16. Children

The Service is not directed to children. A minor should use it only under appropriate adult supervision. Do not include a child's personal information in a support message or report unless necessary and lawfully authorised.

17. International processing

Network targets, hosting, email, app-store and sharing providers may process information in countries different from yours. Their terms, privacy policies and applicable safeguards govern their processing.

18. Your choices and rights

You can choose whether to run a test, start monitoring or a local-device scan, grant or revoke Android permissions, keep or clear local app data, and whether to share any locally generated report or support export. Completed full diagnoses create local Customer and Technical PDFs, but those PDFs are not transmitted to Diagnostix360 merely because they were generated. Where law gives you rights over information Diagnostix360 actually holds, such as support correspondence, contact us. We cannot access, provide or erase local diagnostic data that was never sent to us.

19. Changes

This policy may be updated when app behavior, providers or legal requirements change. The revision date appears above. The public policy and Google Play Data safety answers should remain consistent with the production build.

20. Contact

Diagnostix360
Privacy and support: support@diagnostix360.com