What this site does not do
- No cookies are set by this site.
- No user accounts, sign-up forms, or login flows.
- No advertising pixels or third-party tracking.
- No session recording or heatmap tools.
- No contact forms that submit personal data.
Privacy Policy
How AppInspect handles data.
AppInspect is a local Android library, not a data service. This page explains what the documentation website collects (nothing) and what the library itself does with data on the device.
This website
No cookies. No personal data collected.
This documentation website uses cookie-free, privacy-respecting analytics (Cloudflare Web Analytics) to count page visits. No personal information about visitors is collected or stored. The AppInspect library itself contains no analytics — see the section below.
Third-party resources loaded
-
Cloudflare Web Analytics — a lightweight, cookie-free
analytics beacon (
static.cloudflareinsights.com/beacon.min.js) is loaded to count page visits and measure performance. It does not set cookies, does not track individuals across sites, and does not fingerprint visitors. Aggregated data (page views, countries, referrers) is visible only to the site owner. See Cloudflare's privacy policy for details. -
Google Fonts — Manrope and JetBrains Mono are loaded
from
fonts.googleapis.com. Google may log the request IP and user-agent per their own privacy policy. -
Maven Central links — Clicking "View Maven Central"
navigates to
central.sonatype.com, which has its own privacy policy and may set cookies on that domain.
AppInspect library
Runs entirely on your device. No cloud. No telemetry.
AppInspect is a developer and QA tool that runs inside the host Android application. It has no cloud backend, requires no account, and never uploads data to any AppInspect server.
What the library never does
- Does not require an AppInspect account or registration.
- Does not upload captured network events, crash reports, or storage data to any remote server.
- Does not send usage telemetry, crash telemetry, or analytics about how the inspector is used.
- Does not communicate with any AppInspect-operated infrastructure.
- Does not include any advertising SDKs or tracking libraries.
What the library stores on-device
- Captured OkHttp requests and responses are stored in an app-private SQLite database (
appinspect_storage.db) on the device. - Uncaught exceptions, and on Android 11+ ANR and native crash records, are captured and stored in the same private database, up to 50 recent events.
- Storage and WorkManager data is read from the host app on demand and is never persisted by AppInspect.
EncryptedSharedPreferencesfiles are automatically decrypted for read-only viewing inside the inspector, using the host app's own on-device Keystore key — decryption never leaves the device, and encrypted files cannot be edited or deleted from the inspector.- All on-device data is private to the host app and is not accessible to other apps without device root.
- Data is cleared when the user taps "Clear" inside the inspector, or when the host app is uninstalled.
Exports and sharing
Exports leave the device only when a person triggers them.
The library provides tools to export network logs as TXT or HAR files and to share crash details via the Android share sheet. These exports happen only when someone actively triggers the action inside the inspector.
Exports may contain sensitive data
Network log exports (TXT, HAR, cURL) include the full request and response headers from captured API calls. This may include:
- Authorization tokens and API keys from request headers.
- Session cookies from request and response headers.
- Request and response body content, up to the configured capture limit.
These exports are intended for internal debugging only. Treat them as sensitive internal artifacts and redact credentials before sharing with external parties or uploading to issue trackers.
The library's role in exports
- The library writes export files to
cacheDir/appinspect_exports/, scoped by aFileProviderthat cannot grant access to other paths. - Exports are only created when a user explicitly taps the export or share action inside the inspector.
- The library does not send exports anywhere automatically.
- Export files remain in the app cache until Android clears the cache or the app is uninstalled.
- For production builds, use
appinspect-no-opto ensure no data is captured or exportable.
Production builds
Zero inspection code in release APKs.
Use releaseImplementation("...appinspect-no-op") to ship only a
pass-through OkHttp stub in production — no UI, no database, no capture code,
no manifest entries. As a second independent layer, even if the full SDK
accidentally ships, it detects a non-debuggable build and self-disables
completely. End users are completely unaffected.
See the full security model →