PingPeek / Privacy policy
Privacy policy
Updated October 2, 2026
These pages describe PingPeek and this website. Contact: jama33136@gmail.com.
1. Local traffic and records
PingPeek uses Android’s local VPN interface to process traffic on your device, without a remote proxy. Traffic counters, simulation settings and session records are stored locally, including in SQLite. PingPeek does not collect request payloads, visited URLs, account credentials, names or location as part of this monitoring.
2. Diagnostics and usage analytics
The current app integrates Firebase Crashlytics, Analytics and Remote Config for crash reporting, usage analytics and remote configuration. Reports, usage events, installation identifiers, app version and device/OS information may be sent to Google. Local traffic processing does not mean that all app data remains on the device. Google’s data handling is described in the Firebase privacy documentation linked below.
3. This website
This static site has no account system. This website uses Google Analytics 4 to measure page visits, Google Play button clicks and website interactions (such as navigation, language/theme choices and interactive demonstrations). Google may process browser/device information, cookie identifiers and usage events. Advertising personalization and Google Signals are disabled. Your theme choice is stored in your browser. Hosting infrastructure processes requests, including IP addresses, to deliver and protect the site. Google Play links include campaign parameters; opening Google Play is subject to Google’s policies.
4. Deletion and children
Clearing app data or uninstalling removes local records. This does not automatically delete diagnostic data already sent to Firebase; contact us about related requests. PingPeek is not intended for children under 13.
5. Updates and contact
Changes are published here. For questions about privacy or data, email jama33136@gmail.com.
