Private by architecture, not by marketing.

LocalPDF is built around on-device PDF workflows. Core document actions such as split, merge, rotate, reorder, sign, edit, compress, read, and OCR are designed to run locally on your device instead of sending the contents of your PDFs to a cloud processor.

Core Processing Handled on-device through the Android app, Kotlin bridge, and Rust PDF engine.

Account Model No LocalPDF account is required to use the app’s core PDF features.

Billing Pro purchase and restore flows use RevenueCat and the app store.

Last Updated

April 10, 2026

Your PDFs are selected by you.

Imported documents, temporary working files, OCR outputs, and exports are created locally to complete the actions you request.

Settings and history stay local.

LocalPDF stores preferences, local stats, operation history, and workspace state on your device.

Purchase status may involve network services.

When you buy or restore Pro access, store and billing providers may process transaction-related data required for that purchase flow.

Notifications are optional.

If you grant notification permission, LocalPDF may show local workflow progress or completion updates on Android.

What This Covers

How LocalPDF handles your information

This page reflects the current LocalPDF app in this repository: an Android-focused PDF utility that emphasizes local processing and local storage for document workflows.

1. Information We Handle

PDFs and related files you choose to import, read, process, share, or export.
Generated outputs such as split documents, merged files, signed exports, compressed copies, OCR results, and optional text sidecar files.
Local app data such as settings, operation counts, recent activity, and document workspace state.
Purchase and restore state needed to unlock Pro access when billing is used.

2. How We Use It

To perform the PDF action you requested inside the app.
To reopen documents you previously imported into the app’s local workspace.
To remember app preferences, local history, and local workflow state.
To show workflow progress notifications if you allow notifications on Android.
To validate, restore, or maintain a one-time Pro purchase when billing is used.

3. What Stays On Device

Core PDF processing is designed to run locally through the app’s Android and Rust components.
LocalPDF does not intentionally upload the contents of your PDFs to a cloud service for the app’s core PDF operations.
OCR processing is designed to run on-device, and OCR exports are written locally.
Settings, stats, recent operations, and workspace copies are stored locally on your device.

4. What May Use Network Services

Purchase, restore, and billing-related flows use RevenueCat and the app store infrastructure.
Android or store surfaces you choose to use, such as sharing, app updates, or payment flows, may involve third-party platform services outside LocalPDF’s on-device PDF engine.
Core PDF document processing is not described here as a cloud-upload feature.

5. Permissions

Permission	Purpose
Internet	Used for billing and store-related flows, including purchase and restore operations.
Post Notifications	Used for local workflow progress, completion, and retry notifications on supported Android versions.
Read/Write External Storage older Android versions only	Used to import and export user-selected files on older Android devices where those permissions still apply.

6. Retention And Control

Your local settings, history, cached working data, and exported documents remain on your device until you remove them, clear app data, uninstall the app, or delete files yourself.
Files you export are saved to user-visible locations you choose through Android file workflows.
If device backups are enabled through Android, backup behavior is controlled by your device and operating system settings.

Important Scope Note

This privacy page is written to match the current LocalPDF repository and app behavior visible in the project as of April 10, 2026. If you add analytics, crash reporting, cloud sync, accounts, server-side OCR, or other online services later, this page should be updated before release.