Local file processing in the Android app
The Private PDF Android app uses the same browser-first processing model as the website. For normal supported workflows, files are handled locally on the device rather than being sent to a remote PDF conversion server for processing.
That local-first design reduces unnecessary document exposure, but it does not remove the need to secure your own phone, downloads, and any cloud storage destination you choose when saving or sharing an output file.
What the app may store on your device
The app may keep runtime assets, preferences, consent state, and offline-capable files in local device storage so the interface and supported tools can load more reliably. Generated files are saved only when you explicitly export or share them.
This storage behavior supports offline-ready usage and faster relaunches. It is not a hidden document-upload system.
Network access and third-party services
The app includes internet access because the web runtime, optional analytics configuration, support routes, and related assets may require network connectivity. Core document processing is still designed to happen locally for normal workflows.
If analytics or similar measurement are enabled, they are intended for broad product understanding rather than inspection of document contents. Do not treat analytics as part of the document-processing pipeline.
Permissions and file export
The app uses Android file and share capabilities so you can choose source files and save or share finished outputs. Those actions are initiated by you. The app does not need an account to complete the normal local workflow.
When you export, the final file name is branded for consistency. The destination remains under your device and chosen app controls.
Contact for privacy questions
For privacy questions about the Android app, contact DayFiles support through the support page on this site. The best requests are specific about local processing, file handling, cached assets, analytics, or export behavior.