Network Mediet Diagnostics Privacy Policy
App: Network Mediet Diagnostics
Developer: VEB LAIF PP
Privacy contact: info@veblaif.online
Privacy Policy for Network Mediet Diagnostics
About this policy
This policy describes the data handling supported by the current application source and Store description for Network Mediet Diagnostics. The developer identity is VEB LAIF PP. The privacy contact is info@veblaif.online.
Information accessed and processed
The app accesses Android network information to display your active connection type, connection status, Android’s internet validation status, local IPv4 and IPv6 addresses, network interface, MTU, DNS servers, and routes or gateways. It updates this information when your connection changes. The inspected implementation does not request network names, location, contacts, camera access, or microphone access.
The app processes hostnames, IP addresses, ports, attempt counts, and timeouts that you enter for diagnostics. Results can include resolved addresses, connection timings, success or failure messages, and timestamps. The subnet calculator and IP converter process your entered addresses and masks locally without requiring network requests.
No account is required. The inspected source does not implement developer-operated collection servers, analytics, advertising delivery, or automatic uploads of diagnostic history.
Why information is used
Information is used to show connection details, resolve hostnames, measure TCP connection latency, troubleshoot connectivity, calculate IPv4 subnets, convert address formats, and create reports. Saved settings provide your preferred defaults. Saved history and reports let you review, copy, and share results later.
Network requests and recipients
When you run DNS lookups or diagnostics that require hostname resolution, the app uses the active Android network’s system DNS resolver. Your configured DNS service may receive the queried hostname and associated network information.
TCP latency tests and TCP troubleshooting connect to the host and port you select. The destination and intervening network providers can observe connection information, including your network’s outward-facing IP address and connection timing. The test opens a TCP connection and closes it; the inspected implementation does not send saved reports or diagnostic history as an application payload.
These operations are necessary to perform the tests you request. DNS providers, destination operators, and network providers may handle connection information under their own policies. Their retention practices are not established by the app’s source.
Local storage and backups
On Android, diagnostic history, saved reports, and preferences are stored in the app’s private SharedPreferences storage. History saving is enabled by default. Diagnostic history can contain test types, targets, timestamps, statuses, resolved addresses, measurements, and result details. Calculator results enter history when you choose to save them. Reports can contain connection details and selected historical results. Local addresses are included in reports by default, with a setting to exclude addresses from report previews.
The app keeps up to 300 history entries and 100 saved reports, replacing older entries as these limits are reached. No automatic expiration period is implemented. Saved preferences remain until reset or removed. Some current inputs and displayed results also use Android’s saved screen state to restore the interface.
Android backup is enabled in the app manifest. Depending on your device, account, and operating-system settings, Android may back up or restore app data through its backup service. Such copies are controlled by the platform’s settings and practices.
Copying and sharing
Copy actions place the selected result or report on the system clipboard. Clipboard access and retention depend on your operating system and other permitted software.
Sharing opens Android’s share chooser and sends the report text to the app or destination you select. Review the report preview before sharing: reports may contain network addresses, hostnames, DNS information, routes, and diagnostic results. The receiving service handles the information under its own policies. Deleting local records does not delete clipboard copies or reports already shared elsewhere.
Permissions and third-party components
The app declares Internet and network-state permissions to perform diagnostics and read connection information. Its manifest also declares the Android advertising ID permission. However, the inspected code contains no advertising ID access, advertising SDK, or advertising behavior. The permission alone does not establish that advertising identifiers are collected.
The inspected dependencies include Kotlin, Compose, AndroidX, and coroutine libraries for app functionality. No analytics, advertising, or remote crash-reporting SDK is identified in the inspected configuration. Unexpected diagnostic exceptions may be written to Android’s local system log; the inspected code does not upload those logs.
The Android host also contains a WebView for displaying a configured terms/privacy page. The current startup path opens the diagnostic interface directly. If that WebView is displayed, loading web content can disclose ordinary connection information to the contacted website; JavaScript is enabled in that view. Website-side collection is not established by the inspected source.
Security
Android’s app-private storage provides operating-system access controls for saved data. The inspected implementation does not add its own encryption to stored history, reports, or preferences.
The app does not implement encrypted DNS itself; DNS transport depends on the active network and Android configuration. TCP latency measurements use a basic TCP connection without a TLS handshake, including when you select port 443. These tests should not be understood as encrypted application sessions. Security of exported reports and platform backups depends on the services and settings used. No storage or transmission method can be guaranteed completely secure.
Retention, deletion, and your controls
You can disable saving new diagnostic history in Settings. This does not remove existing history or saved reports. You can delete individual history entries and reports, clear diagnostic history, or use Clear local data to remove saved history and reports and reset saved preferences.
Android’s system controls also allow you to clear the app’s storage or uninstall the app. Backup copies and previously exported information may remain subject to the relevant platform or recipient controls.
No developer-side diagnostic database or automated remote deletion-request service is implemented in the inspected source. For privacy questions or deletion assistance, the designated contact is info@veblaif.online.
Browser preview
The browser preview stores history, reports, and preferences in browser local storage. It does not perform real system DNS lookups or TCP measurements and does not read Android connection details. Its share action copies text to the clipboard. Preview data can be removed through the app’s deletion controls or the browser’s site-storage controls.
Children’s privacy
No intended age groups were specified in the supplied information. The inspected app provides general network tools and does not implement accounts, age verification, or a separate collection flow for children. This draft does not assert a child-specific audience or age eligibility rule.
Changes to this policy
This policy should be updated when the app’s functionality, permissions, dependencies, or data practices change. Review the version made available with the app for current information.
Contact
App: Network Mediet Diagnostics
Developer: VEB LAIF PP
Privacy contact: info@veblaif.online