Legal

Privacy Policy

Effective date: November 1, 2026 · AppLabs, LLC

AppLabs, LLC (“we”, “us”) makes PingBill (“the App”), an Android app that shows which outside companies another app contacts. This policy explains what PingBill reads, what it stores, and what we receive.

The short version: PingBill analyzes everything on your phone. Nothing is sent to us unless you choose to share a receipt, and a shared receipt is about the app you monitored, not about you.

What PingBill reads, and why

• Your installed apps that have a launcher icon (names, icons, versions and Android's app category) — so you can pick one to monitor. PingBill can only see apps with a launcher icon; it doesn't ask for access to all installed packages.
• During a session you start, the network activity of the one app you chose — to make its receipt. PingBill reads only metadata: the names that app looks up (DNS), the answers, the addresses and ports it connects to, the server name an HTTPS connection announces (TLS server name), the Host of plain-HTTP requests, and when each happened.

PingBill never reads message or page contents, passwords or anything inside encrypted connections. It doesn't decrypt traffic, install certificates, or watch apps you didn't choose.

How monitoring works

PingBill uses Android's VPN service on your phone. Only the app you chose is routed through it, and only while a session runs; every packet is passed on to its destination unchanged. The VPN runs on your phone — it doesn't send your traffic to us or to any server of ours. A notification shows while a session runs, with a Stop button. If you turn on tracker blocking (PingBill Pro), PingBill refuses connections to known tracker domains for that app during the session and pauses its HTTP/3 (QUIC) traffic so it uses regular HTTPS.

PingBill asks for permission to show notifications so the session notification can appear. Android shows its own VPN consent dialog before the first session; you can revoke it any time in Android's VPN settings.

What PingBill stores

• During a session, in memory only: each lookup and connection with its time. They are discarded when the receipt is made.
• Receipts: the monitored app's name, package and version, the session's start and end time, and totals per domain (domain, connections, lookups, blocked), with the companies they belong to.
• Your settings (theme, demo mode, tracker blocking, automatic sharing), whether you've seen the introduction, and whether Pro is unlocked.
• A random ID, created the first time you open “Share with AppLabs” (see below).

All of this stays in PingBill's private storage on your phone. Android backups and device-to-device transfers are turned off for PingBill. Settings → Data management → Delete all data removes your receipts and monitoring records and resets your settings and the random ID; uninstalling PingBill deletes everything.

Sharing receipts with AppLabs (optional)

You can share a receipt with us — one at a time, after a preview of exactly what will be sent, or automatically if you turn that on in Settings. Demo receipts are never shared. A shared receipt contains:

• the monitored app's package name, version and display name;
• the session's day (not the time) and length in minutes, and whether blocking was on;
• PingBill's version, its company database's version and your Android version number;
• each identified company with its connection, lookup and blocked counts, and its εxodus Privacy tracker IDs;
• those companies' domains, with random-looking parts masked (for example “*.example.com”), and, for domains PingBill doesn't know, only the site name (for example “example.com”);
• the random ID mentioned above. It's created by PingBill, isn't linked to your device, Google account or advertising ID, and is reset when you delete your data. We use it to limit how many reports one phone can send and to count how many different phones reported an app.

A shared receipt never contains times of day, other apps, contents of any connection, your name, email, location, contacts, device identifiers or advertising ID. Your internet address reaches our server, as with any connection, but we don't store it.

How we use shared receipts: for research into which companies apps contact, and to publish data about apps — for example, “this app contacted Google AdMob in 82% of reported sessions” — through our website and a public API for developers and researchers. We publish an app only once several different phones have reported it, and only totals across reports; we never publish an individual report or the random ID. Published data is licensed under the Open Database License 1.0.

Where it's kept: our API runs on Fly.io and its database on Neon (Amazon Web Services, United States). These providers process the data only to run our service. We keep shared reports until we decide they're no longer useful, or until you ask us to remove them. Because reports don't identify you, tell us the app and the day of the session (and the receipt's ID if you can) and we'll remove what we can match. We don't sell shared receipts or use them for advertising.

PingBill Pro and Google Play

PingBill Pro is sold through Google Play. Google processes payments under Google's Privacy Policy; we don't receive your payment details. PingBill checks your purchase with the Play Store app on your phone and remembers whether you have Pro, so it works offline.

Images, exports and links

Share cards and data exports go only where you send them. Links in PingBill (this policy, the terms, our other apps) open in your browser or the Play Store under their own privacy policies. Links to our other apps tell Google Play that PingBill sent the visit; PingBill itself records nothing.

Crash reports

PingBill contains no crash-reporting, analytics or advertising code. If you've allowed it in your phone's settings, Google may share basic crash statistics with us through Google Play Console; these don't identify you.

Tracker data

Company and tracker data: AppLabs' company database, built from εxodus Privacy's tracker list (exodus-privacy.eu.org, Open Database License 1.0) and AppLabs' list of company domains. It's built into the App; PingBill never downloads it.

Children

PingBill isn't directed to children under 13. It doesn't collect personal information from anyone, including children; shared receipts contain no personal information.

Your choices

Monitoring only happens when you start a session. Sharing only happens when you tap Send or turn on automatic sharing, and you can turn that off any time. You can delete everything PingBill stores from Settings, and ask us to remove shared reports at the address below. Depending on where you live, you may have other rights over your data; contact us to use them.

Changes

If this policy changes, we'll update it in the App (and on PingBill's website once it exists) and change the effective date. If a change affects what shared receipts contain or how we use them, we'll ask again before sharing more.

Contact

Questions about this policy or requests about shared receipts: mail@applabs.llc

AppLabs, LLC · Newark, Delaware, USA