Pulse Privacy Policy

Pulse is a local-first Android network diagnostics application operated by Sameer Malick (@KHILJI). This policy explains what Pulse accesses, what stays on your Android device, what may be sent to third parties when a network feature is used, and how you can export or delete your data.

Pulse does not provide user accounts, cloud synchronization, or an application backend. Pulse does not sell personal data.

1. Information Pulse accesses

• Wi-Fi connection and scan information, including SSID, BSSID, signal level, channel, frequency, link information, gateway, DNS servers, subnet, and local IP address.
• Nearby Bluetooth Low Energy broadcast information when you start BLE diagnostics.
• Approximate or precise Android device location after you grant Location access. Android requires Location-related access for some Wi-Fi information. Pulse can also use coordinates locally to select a nearby speed-test server.
• Local-network device information discovered through user-visible scans, including IP address, MAC address, hostname, vendor, and reachable services.
• Diagnostic input and results, including speed tests, ping, traceroute, DNS, URL checks, port checks, monitor samples, incidents, router observations, and floor-plan signal measurements.
• Remote connection profiles that you choose to save.
• Local application crash information, including error text, stack traces, and timestamps.

Pulse does not send precise Android GPS coordinates to its own server, because Pulse has no application server. Precise coordinates are not sent to the public network-identity providers used by the Speed screen.

2. Information stored on the device

Pulse stores settings, histories, monitor records, device history, router observations, floor-plan metadata, remote-profile metadata, and local crash reports in Android app-private storage.

Saved SSH passwords, private keys, passphrases, and non-public SNMP community strings use Android secure storage where supported. Other diagnostic records use the application sandbox and are not represented as end-to-end encrypted records.

Pulse does not upload saved diagnostic histories or the local crash-report archive. Separately, a diagnostics processor receives the limited, sanitized reliability data described below.

3. Network requests and third parties

Advertising delivery and privacy

Pulse may display banner, native, app-open, and optional rewarded advertisements on eligible screens. App-open ads are limited to later sessions and safe foreground returns. A user who voluntarily completes the rewarded ad can receive a 30-minute break from banner, native, and app-open ads on that device. Declining or skipping the offer does not block diagnostics or saved results. Advertising delivery and consent processors may collect or share the public IP address, app interactions, diagnostic information, and device or advertising identifiers for ad delivery, measurement, and fraud prevention.

Applicable privacy choices are collected through an advertising privacy form before Pulse requests ads where required. Pulse does not require an advertisement to unlock a diagnostic feature; the optional reward only suppresses eligible ads temporarily. Available choices can be reviewed from Settings > Ad Privacy.

Product measurement, app notices, and reliability

Pulse uses external processors to measure fixed screen visits and diagnostic-type completions, select and deliver app notices, and investigate uncaught application errors, native Android crashes, and application-not-responding events. These processors may receive app interaction events, fixed screen and diagnostic-type labels, sanitized error types, stack traces, app/build metadata, device and Android stability information, and per-installation identifiers.

Pulse does not attach SSIDs, BSSIDs, IP addresses, host names, URLs, credentials, saved diagnostic histories, discovered-device records, or diagnostic measurements to this telemetry. Application exception messages are replaced with the exception runtime type before upload; the local on-device crash archive retains the original detail for local troubleshooting.

Remote notifications

A remote-notification delivery processor may assign an app-installation token and handle message-delivery metadata needed to route app notices to the device. Pulse does not include scan history, diagnostic results, destination hosts, network addresses, or credentials in notification registration data.

Public network identity services

The Speed screen may contact public network-identity processors over HTTPS to identify the public IP address, network provider, and approximate network location. These processors receive the public IP address as part of normal internet communication. Pulse does not send precise Android GPS coordinates to them.

Speed-test servers

A speed test connects directly to the selected measurement server. The server receives the public IP address and generated download/upload traffic. Upload tests use generated bytes and do not upload personal files. Some measurement servers use HTTP; generated speed-test payloads sent over HTTP are not confidential data.

User-selected diagnostic destinations

Ping, DNS, traceroute, URL checks, port checks, monitors, SNMP, SSH, SFTP, Telnet, and raw TCP tools communicate directly with the destination selected by the user. The destination and intervening network providers can observe traffic according to the protocol used. Pulse does not proxy these sessions through a Pulse server.

Android sharing

When you share a diagnostics report, Android displays available share targets. Report content is transferred only to the app or service you select. That recipient controls its own handling of the shared content.

4. Android permissions

• Location and Nearby Wi-Fi Devices: read Wi-Fi identity and nearby wireless scan data as required by Android, and optionally select a nearby speed-test server locally.
• Bluetooth Scan and Connect: run nearby BLE diagnostics that you start.
• Notifications: show monitor outage, degraded-performance, and recovery alerts that you enable.
• Foreground service and wake lock: continue user-configured monitoring with a visible Android notification.
• Biometric access: unlock protected SSH credentials when you enable biometric protection.

You can deny a permission. Features that do not need the denied permission remain available.

5. Advertising choices

Where required, Pulse presents an advertising privacy form before ads are requested. If a privacy-options form is required for your device or region, reopen it from Settings > Ad Privacy. You can also reset or delete the Android advertising ID in Android privacy settings.

6. Security

Pulse uses Android app-private storage, Android secure storage for supported credentials, TLS for supported public identity and advertising requests, and SSH encryption with host fingerprint verification for SSH/SFTP sessions.

Some diagnostic protocols are not encrypted by design, including ICMP, traditional DNS, SNMP v1/v2c, Telnet, raw TCP, and user-configured HTTP endpoints. Use them only on networks and systems you trust and are authorized to administer.

7. Retention, export, and deletion

Local data remains until you delete it, clear Android app storage, or uninstall Pulse. Several histories use bounded retention.

Settings > Data Controls lets you export a diagnostics report, clear selected histories, or erase all Pulse local data, saved profiles, cached floor-plan files, local reports, and protected credentials.

Because Pulse has no user accounts or cloud storage, there is no remote account record to delete.

8. Children's privacy

Pulse is a technical network-administration utility and is not designed for children. The intended Google Play audience is adults. Pulse does not knowingly create profiles for children.

9. International use

Network destinations and advertising providers may process requests in countries other than the country where the device is located. Third-party providers control their own infrastructure and legal obligations.

10. Changes to this policy

The policy may be updated when Pulse features, external processors, or legal requirements change. The effective date identifies the current version. Material changes will be reflected in the in-app policy and this page.

11. Contact

Developer: SAMEER MALICK (@KHILJI)

Privacy and support email: adeelkhan04789@gmail.com