Image & PDF Toolbox Privacy Policy
Last updated: September 16, 2026
In short: Core image, PDF, and OCR processing happens on your device. No account is required. The app does not upload your documents, images, OCR text, filenames, or file paths to a developer server. The free tier uses Google Mobile Ads, and subscriptions are handled by the Apple App Store or Google Play.
1. Scope
This policy applies to the Image & PDF Toolbox mobile application (the “App”) and explains how the App and its integrated third-party services handle information. The App currently has no account system and no developer-operated backend that receives user files.
2. Data processed locally
2.1 Files and camera content you choose
When you select an image or PDF, scan a document, run OCR, edit, convert, compress, split, merge, or export, the App reads and processes that content on your device. The camera is used only after you open the scanner and grant permission. Audio is not captured.
2.2 Local files and job history
To provide the Files screen and job status, the App stores processing history and necessary metadata in private app storage. This can include job type, options, progress/result state, timestamps, file URI, filename, format, size, and output location. Generated files are stored in a location you choose or in the App's storage area.
2.3 Preferences
Language, theme, default image quality, output behavior, filename preferences, and ad-frequency counters are stored locally on the device.
3. Data that third parties may process
3.1 Advertising
The free tier may display native, interstitial, or app-open ads through Google Mobile Ads. Depending on your region, device settings, and consent choices, Google and its advertising partners may process IP address, device or advertising identifiers, coarse location, ad interactions, diagnostics, and anti-fraud information to serve ads, limit frequency, measure performance, and prevent invalid traffic. The App does not provide document content or OCR text to advertising services.
See the Google Privacy Policy (https://policies.google.com/privacy) and How Google uses advertising technologies (https://policies.google.com/technologies/ads).
3.2 In-app purchases
Weekly and monthly subscriptions are processed by Google Play Billing or Apple StoreKit. The store handles payment and account information; the App does not receive your card number. The App receives product ID, transaction status, purchase proof/token, and transaction time to verify subscriptions locally and restore purchases. Each store's privacy policy governs its handling of data.
3.3 Operating-system services and sharing you initiate
File pickers, save panels, and system share sheets are provided by Android, iOS, or the receiving app you choose. A selected file is provided to another service only when you initiate sharing or saving to a third-party location. That service's terms and privacy policy then apply.
3.4 OCR components
Text recognition is performed with on-device ML Kit components. Recognized content is not sent by the App to a developer server. The operating system or app store may provide and update underlying components under the platform's rules.
3.5 Usage analytics
Firebase Analytics is enabled by default when the App has a valid Firebase configuration. The App records screen views, taps in coarse screen regions, tool opens, processing starts/completions/failures, paywall and purchase actions, ad impressions and clicks, and verified in-app purchases. Parameters are limited to fixed screen names, coarse tap regions, tool type, subscription plan, failure category, ad format, store-provided price and currency, and transaction identifiers for verified purchase events when available. Google may process app-instance and device information under its Firebase privacy terms (https://firebase.google.com/support/privacy). No filenames, paths, document contents, OCR text, or exact tap coordinates are included.
3.6 Android crash diagnostics
Android release builds use Firebase Crashlytics to diagnose application crashes and errors. Google processes crash reports, app and operating-system versions, device characteristics, installation identifiers, and related diagnostic information. Dart reports sent by the App contain the exception type and filtered code stack frames; the App omits exception messages, Flutter diagnostic context, document names, document paths, document contents, OCR text, and purchase credentials from these reports. Native Android crash and ANR diagnostics are collected by the Firebase SDK. We do not set a user identifier or attach user documents or custom content logs. See Firebase privacy information (https://firebase.google.com/support/privacy). Crash reports require network transmission to Firebase; local document processing remains on-device.
4. What the App does not collect
- No name, email address, phone number, or account registration is required.
- Images, PDFs, scans, and OCR text are not uploaded to a developer server.
- The App does not sell your document content. Advertising-related data handling is described in section 3.1.
5. Permissions and your choices
- Camera: used only for document scanning. You may revoke it in system settings; other import and processing tools remain available.
- Files/photos: the App prefers system pickers and accesses only items you select and output locations you choose.
- Ad privacy: use system advertising privacy settings and, where applicable, the advertising privacy entry in App settings to reopen Google consent options. Declining personalization does not disable core local tools.
- Sharing: sharing is always initiated by you and can be cancelled before sending.
6. Retention, deletion, and security
Private documents and job metadata are excluded from operating-system cloud backups. Android device transfer also excludes the App's private data. Files you explicitly save outside the App follow the backup settings of that destination. Keep a separate copy of files you need before uninstalling or changing devices.
Local job history and preferences remain until you delete history, clear the App's data, or uninstall the App. Deleting history does not automatically delete files that you saved elsewhere; delete those files with your device's file manager. Apple or Google determines retention of store purchase records.
Third-party analytics, advertising, and diagnostic records follow the applicable provider policies and configured retention settings. Uninstalling the App does not automatically erase records already transmitted to those providers. Contact us for questions or requests relating to those records.
The App relies on operating-system sandboxing to protect private data and minimizes permissions and network access. No storage or transmission method is absolutely secure, so protect your device and share files only with services you trust.
7. Children's privacy
The App is a general-audience utility and is not directed specifically to children. We do not knowingly collect children's personal information through a developer-operated service. Users below the local age of digital consent should use the App and purchase features with a parent or guardian.
8. International processing
Advertising, analytics, crash-reporting, and app-store providers may process the data they collect outside your country or region and apply safeguards described in their policies. Core file processing and local records are not uploaded to a developer server as a result.
9. Changes to this policy
If data practices materially change, we will update the date and content of this policy and provide in-app notice or renewed consent where required by law. Material changes will not retroactively authorize earlier processing.