Zhadi

Privacy Policy

Zhadi · Privacy Policy

Applies to: 1.2.3 (build 23) · Effective: October 23, 2026

In one sentence: Recordings stay on the head unit or on the external drive you choose; the app does not upload footage and has no account. Update checks always run. Log upload, remote debugging, and status upload are off by default and send limited operational data only when you turn them on or press the button.

1. Where recordings are stored

Drive and Parking Guard recordings are stored in the head unit’s internal storage, or on the TF card / USB drive you plug in and select, and are overwritten in a loop according to the quota you set.

The Recent triggers clips on the Parking Guard page live only in the app cache, at most three at a time, and are deleted when you leave that page.

The app has no remote viewing, no cloud storage, and never sends footage or recordings to any server. To take recordings off the car, use a storage device or the head unit’s own file manager.

2. Network features at a glance

Version 1.2.3 accesses the network in the following situations. In every case, it does not upload recordings or images.

FeatureWhen it connectsWhat is sent / received
Update checkAt boot and about every 6 hours; always onSends device type, current version, and update-channel identifier; receives whether a new version exists
AI model downloadThe first time you enable Event AI CheckDownloads and verifies a model of about 4.7 MB; the model runs locally
Log uploadOff by default; about every 30 seconds after you enable itApp and daemon logs, device identifier, and status readings, about 2.5 MB/hour
Status uploadNot automatic; only when you press Status UploadA one-time snapshot of live readings and scan details
Remote debuggingOff by default; after you enable itReceives diagnostic commands and returns logs and command output over an encrypted connection; closing the switch ends it
Music castingWhen you use the featureSends track and artist queries to QQ Music / NetEase Cloud Music and similar services; receives album art and lyrics
Built-in emulatorWhen you use the emulatorFetches resources needed by the emulator; no recordings involved

None of these requests include recordings. Update checks and AI model downloads use encrypted connections. Log and status upload use UDP and carry logs and readings, not images.

3. Remote debugging and log upload (optional)

Remote debugging and log upload live in the debug settings. Both are off by default and must be enabled by you.

While remote debugging is on, maintainers can read logs and execute diagnostic commands (including shell commands) over an encrypted connection for troubleshooting; closing the switch ends the connection. While log upload is on, the app periodically sends runtime logs and status readings to help diagnose problems.

Both switches remember their last state, but neither turns itself on. Keep them off in normal use.

4. Permissions and why they are requested

PermissionPurpose
CameraRead the car’s four surround-view cameras for recording, live preview, and digital side mirrors
Storage / all files accessWrite recordings to internal storage, a TF card, or a USB drive
NetworkUpdate checks, optional log upload and remote debugging, AI model downloads, and music information queries
BluetoothUsed when the phone controller connects to the head unit; Android 11 and below also requires location permission to scan for Bluetooth devices
LocationOnly used for Bluetooth scanning on Android 11 and below (a system requirement); location is never read, stored, or uploaded
Start on bootStart automatically after the head unit boots so recording can begin while driving
Foreground service / wake lockKeep recording uninterrupted during driving and Parking Guard
Display over other appsShow the side-mirror view on the center screen when casting there
Battery optimization allowlistKeep Parking Guard from being killed by system power saving
Wireless debugging (ADB) / modify system settingsStart the daemon and grant its own permissions without root, so it can keep watching after the car is off
Install apps / read logsInstall app updates; read the app’s own runtime logs for troubleshooting
NotificationsThis head unit runs Android 10; notification permission only became required in Android 13, so it is not needed

The Permissions page in the app explains every requirement (and non-requirement) in the same terms.

5. What we do not do

  • · We do not create accounts or collect names, phone numbers, or email addresses
  • · We do not sell or share data with advertisers, and we do not include third-party ad SDKs
  • · We do not build user profiles or analyze behavior
  • · We do not upload footage or recording files to any server
  • · We do not use location for tracking; location permission is required by the system only for Bluetooth scanning on older Android versions

6. Data retention and stopping uploads

Recordings stay on the car and are managed by you; the app keeps no cloud copy.

If you have enabled log upload or remote debugging, uploaded logs are used by maintainers for troubleshooting, not for advertising or profiling. Once the switch is off, no new uploads occur.

Status upload is one-time and happens only when you press the button.

7. Other people in recordings

Recordings may capture pedestrians, other vehicles, and license plates, which may be protected by local law. The recordings stay in your car and under your control. Follow local laws on dashcams, and do not redistribute content that invades another person’s privacy.

Parking Guard is not a substitute for security measures; it is one more record.

8. Children and minors

This is a head-unit app. It is not directed at minors and does not intentionally collect any information about them.

9. Changes to this policy

If this policy changes, we will update this page and note the applicable version. The current version is 1.2.3 (build 23).

The current verified environment is BYD Tang EV / DiLink 4.0 / Android 10.

For permission setup and Parking Guard instructions, see the user manual.