Pynqr
VANTH Studio / Guides / Private scanning
Privacy by architecture

Why Keep Network Scan Data On Device?

A local network inventory can describe the technology inside a home or office. Processing it locally limits how many systems need to receive and retain that information.

5-minute readReviewed August 10, 2026
Quick answerOn-device scanning keeps device discovery, labels, history and reports on the iPhone unless you deliberately export or share them. That reduces unnecessary server-side collection, though purchases, optional analytics and support communications remain separate data flows.

What a network inventory can reveal

None of those facts is automatically catastrophic, but together they form a detailed technical map that deserves deliberate handling.

Local processing changes the trust model

A cloud-backed scanner may offer synchronization, remote alerts or aggregated intelligence. Those features can be useful, but they also require data transfer, server security, retention rules and account recovery. A local-first scanner can perform ordinary discovery and analysis without uploading the inventory.

On-device does not mean “no data flow anywhere”

Purchase validation requires store and entitlement information. Optional analytics can measure product usage when enabled. Support messages contain whatever the user chooses to send. A precise privacy claim separates these flows from the actual device list and scan history.

Pynqr’s modelDevice discovery, history, tags, reports and diagnostics are processed and stored on the device. RevenueCat handles purchase validation. Optional anonymous analytics use PostHog when enabled, and support receives information the user chooses to provide.

Questions to ask any network scanner

  1. Is the discovered device list uploaded?
  2. Is an account required for local scanning?
  3. Where are labels and scan history stored?
  4. Are analytics optional, and what fields do they contain?
  5. Does an export leave the app only when I initiate it?
  6. Can I delete local history and support data?

When cloud features may be worth it

Remote monitoring, multi-user administration and cross-device synchronization can justify a service component. The right choice depends on the job. The important part is knowing which data enables the feature and choosing the smallest exposure that meets the need.

Share reports carefully

Exports can contain addresses, names, ports and notes. Review the file before emailing it, posting it publicly or attaching it to a support ticket. Remove anything the recipient does not need.

Related guides

Understand device evidence · Secure the network · Compare scanner priorities

Keep the inventory close

Pynqr is designed around local discovery and on-device storage.

Download Pynqr