Privacy and Data Handling Pixelnetica™ Document Scanning SDK for Android

Documents are sensitive by nature — IDs, contracts, medical papers — so an SDK that touches them owes its integrators exact answers: where processing happens, what goes over the network, and where files end up. This page gives those answers in the form a privacy or procurement review needs.

Processing Happens on the Device

Every processing step — document detection, cropping, colour processing, text recognition, PDF composition — runs in the SDK’s engine on the user’s device. No image, no recognized text, and no document metadata is ever transmitted anywhere by the SDK. There is no cloud component, no telemetry, and no analytics: the scanning, camera, and support libraries contain no networking code at all.

License validation is also local: the key is checked on the device, with no activation call.

The Complete Network Behaviour

Exactly one SDK feature can use the network — downloading OCR language files, in the design library’s language manager — and it talks only to servers your application chooses:

• LanguageManager.requestServer(url, …) downloads language lists and language files from the URL you supply. The SDK ships no server address of its own; production applications host the files themselves (see Get started).
• LanguageManager.requestAssets(…) reads languages bundled inside your application, with no network at all.

The downloads carry no document data in either direction — they fetch recognition data files, nothing more. Skip the language manager (bundle your languages, or skip OCR) and the SDK performs no network activity whatsoever. That claim is verifiable from outside: run your application behind a proxy and observe the traffic.

Where Files Are Written

The SDK writes only where your application points it, in three places:

• Captured pages from the Smart Camera go to the outputDir you pass in CameraParams — or, left unset, to the activity’s own location in your application’s private storage. The URIs come back to your code, and the files are yours to keep or delete.
• Language files go to the directory your application designates (directly, or through the language manager’s storage in your application’s private files).
• Exported results — images, PDFs, text — go to the paths your code passes the writers.

Nothing is written to shared or public storage unless your application chooses such a path, and the SDK never deletes or uploads user documents on its own. Files in your application’s private storage are removed by Android with the app’s uninstall, like the rest of your app’s data.

What This Means for Your Disclosures

For a data-safety form or privacy policy, the SDK itself contributes no data collection, no data sharing, and no third-party endpoints. The one network flow — language downloads — targets infrastructure you control and transfers no user content, so its disclosure (if any) is about your server, not about a third party. Your application’s own handling of the scanned documents remains, as always, yours to declare.