What Guardian actually transmits

Guardian's own network egress monitor will show Guardian itself making a request to bachao.ai. We'd rather you see that and know exactly what it is than wonder. This page is a complete, exact account — not a marketing summary — of what that request contains. If anything here doesn't match what you observe in the app, that's a bug and we want to know about it at ceo@bachao.ai.

Every field below maps directly to the server-side contract at POST /api/apps/telemetry, which rejects any request containing a field not on this list — so this list can't quietly go stale.

Sent — the complete list

Six possible fields, five always present, one only when you're signed in. Nothing else.

Anonymous install ID

A random UUID generated by the app the first time it runs. It identifies an app installation, not you or your device — it is not your IMEI, not your Android ID, not an advertising ID, and it is never combined with those.

App version

The Guardian app version you're running (e.g. "1.0.0") — lets us know which build reported an event.

Android version (API level)

Your device's Android SDK level (e.g. 33 for Android 13) — used to understand which OS versions our users are actually on.

Which app sent the event

"guardian" — distinguishes this app's telemetry from the separate BachaoPe app's telemetry.

Event name

A short label for what happened — currently: app_open, scan_completed, monitor_started, block_added. Nothing else rides along with the event; it's the label, not a description of what you did or saw.

Your Bachao user ID — only if you're signed in

If you're logged in, an internal user ID (not your email, not your phone number) is attached so we can count signed-in usage. If you haven't signed in, this field is simply absent.

Never sent — deliberately, and enforced server-side

Not "we choose not to send this today." The server rejects the request if it's present.

The domains or servers your other apps contact — the network monitor's findings stay on your device and are shown to you, never uploaded.
Your list of installed apps.
Anything scanned or decoded by the BachaoPe app (QR content, UPI IDs/VPAs, payee names, amounts).
Your precise location, or any location at all.
Your contacts, messages, call log, photos, or files.
Your phone number or IMEI.
Raw request content beyond the six fields listed on the left — the server rejects any payload containing a field it doesn't explicitly expect, rather than silently accepting and storing it.

Why we're disclosing this instead of hiding it

Guardian's network monitor is built to show you exactly this kind of thing — which app is talking to which server. It would be inconsistent, and frankly untrustworthy, to build that feature and then hope you don't notice Guardian doing the same. We'd rather you see the connection, come here, and find the truth matches what you saw.

The anonymous install ID exists so we can count "how many devices used this feature" without needing to know who you are. It is never joined with your email, phone number, or any other identity signal in our systems, except the one explicit, opt-in exception above: if you're signed in, your internal (non-identifying) user ID is attached so we can separate signed-in usage from anonymous usage.

Questions about this page, or think something doesn't match what you observed? Tell us.

ceo@bachao.ai