Local file processing in the mobile apps
The Private PDF Android and iOS apps use 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 product analytics, support routes, force-update checks, and related assets may require network connectivity. Core document processing is still designed to happen locally for normal workflows.
In the Android app, limited product analytics is enabled by default outside the European Economic Area, the United Kingdom, and Switzerland. In those regions, and if your country cannot be determined, analytics stays off until you accept. Your choice can be changed in Settings. The iOS app asks before enabling analytics in every region. Analytics helps DayFiles understand screen usage, feature outcomes, and reliability. It does not include filenames, document text, OCR or search content, passwords, document URLs, or free-form error messages. Advertising consent is managed separately.
The free Android version uses Google AdMob and Google User Messaging Platform consent tooling. These services may process advertising identifiers, device and app information, IP-derived approximate location, consent choices, and ad interaction or diagnostic data for advertising, fraud prevention, measurement, and compliance. They do not receive the PDF contents from the local document-processing workflow.
AdMob is limited to a non-blocking banner on a pre-action tool state. It is removed before upload, edit, export, or download work begins. Where required, the app asks for advertising consent and exposes a privacy-options control in Settings.
Google Play purchases and premium support
Android ad-free and Premium purchases are processed by Google Play Billing. Google handles payment credentials and returns purchase entitlement information to the app. DayFiles does not receive your full card or bank details.
The app checks the signed-in Google Play account for active lifetime and subscription entitlements so it can remove ads, restore purchases, and provide the applicable plan benefits. Before buying, each Premium-labeled tool can be tried multiple times on the device; those tries do not unlock ads-off or premium support. A premium-support request opens your email app with the plan type in the subject; you control the message and attachments before sending it to DayFiles.
Permissions and file export
The app uses platform 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 or iOS 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.