Privacy for
your PDF files.

1. Overview

PDF Toolkit, package name com.nexdevlab.pdftoolkit, is provided by NexDevLab. PDF Toolkit helps you scan, read, edit, sign, convert, organize, protect, search, use document tools from another device through xAccess, and optionally sync PDF documents.

2. Local processing and document content

PDF Toolkit can create and handle PDFs, scans, images, text files, office conversion outputs, OCR text, barcodes, watermarks, page edits, document passwords, and signatures. These workflows run on the Android device, including when you control them from a browser through xAccess, using Android, Google ML Kit, Tesseract OCR, PDFBox, and local app code.

PDF Toolkit stores working copies, scan pages, crop/edit settings, OCR text, saved signatures when you choose to store one, document library details, thumbnails or previews, and app preferences in app storage on your device. Saved outputs are also written to Documents/PDF Toolkit so you can find them outside the app.

NexDevLab does not sell your document content and does not use your PDFs, scans, OCR text, or signatures to train AI models.

3. Device files and indexing

The Files tab can request Android all-files access so PDF Toolkit can find PDFs across shared device storage and organize them by folder. If you grant this access, PDF Toolkit creates a local SQLite index with PDF file paths, file names, folder paths, file sizes, modified times, and a local touched flag.

This device-wide file index remains on your device. PDF Toolkit does not upload PDFs found by the Files tab to NexDevLab. Explicit imports use Android document pickers and are limited by app file-size safeguards.

4. xAccess local-network server and file transfers

xAccess is optional and starts only after you select Start xAccess in the app and, where required, receive timed access. While it is running, PDF Toolkit opens a TCP port on the Android device and displays a local HTTP address for use in a browser. It normally uses port 8080; if that port is unavailable, Android assigns another available port and the app displays that port in the address.

A browser device that can reach the displayed address can send selected PDFs, images, office documents, text, editing instructions, signatures, drawings, and other tool inputs to the Android device. The Android device may return page previews, extracted content, converted files, edited files, and other requested results. These xAccess transfers go directly between the browser device and the Android device; they are not routed through or stored on a NexDevLab document server.

The open port closes when you stop xAccess from the app or its persistent notification, when timed access expires, or when Android ends the service. Closing the browser alone does not stop xAccess. Uploaded inputs, previews, edits, and generated results may be held temporarily in the app cache and removed during app cleanup or by Android. Files uploaded with the main xAccess uploader or saved with a Send to Device action are written to Documents/PDF Toolkit and remain until deleted. Files downloaded in the browser are stored and controlled by that browser device.

5. Cloud Sync and Google Drive

Cloud Sync is optional. When you connect a Google Drive account, PDF Toolkit requests the narrow Google Drive file scope needed to create and manage files the app creates or opens in Drive. PDF Toolkit creates or uses a PDF Toolkit folder in your Drive and can upload, rename, download, compare, or resolve conflicts for PDF Toolkit-managed files.

To support Cloud Sync, PDF Toolkit stores local sync records such as the connected account name, display name, provider account ID, Drive folder ID, Drive file IDs, remote file names, hashes, modified times, sync status, queued operations, and recent sync errors. Google account authorization is handled through Google Play services. PDF Toolkit does not store your Google password.

Disconnecting Cloud Sync stops future syncing and revokes PDF Toolkit's Drive access for that account. It does not automatically delete files that were already saved in Google Drive.

6. Ads, consent, and Remote Config

PDF Toolkit may show banner, native, or interstitial ads through Google AdMob and Meta Audience Network. Google User Messaging Platform may show a consent or privacy-options form where required. Firebase Remote Config may be used to choose the active ad network or turn ad delivery off without shipping a new app version.

Advertising and related SDKs may process ad identifiers, IP address, approximate location derived from network data, device and app information, ad interactions, diagnostics, and consent signals. NexDevLab does not receive your PDFs, scans, signatures, or OCR text through these ad services.

7. Premium subscriptions

If you buy or use PDF Toolkit Premium, payment, free-trial status, renewal, cancellation, refund handling, and subscription account management are handled by Google Play. PDF Toolkit may check whether Premium is active to remove ads and unlock Premium features such as Cloud Sync, Watermark, Edit PDF, and E-sign PDF.

NexDevLab does not receive your full payment card number from Google Play. You can manage or cancel subscriptions in Google Play.

8. Permissions PDF Toolkit may request

PDF Toolkit asks for permissions only when needed for PDF workflows:

• All files access / storage access: find existing PDFs, open selected files, import documents, and save outputs to Documents/PDF Toolkit.
• Internet and network state: run the optional xAccess local-network server, show its reachable address, transfer xAccess requests and files, use optional Google Drive sync and Google authorization, and support ads, consent, Remote Config, and subscription checks.
• Notifications: show completion or background sync/export alerts and the persistent xAccess-running notification with its stop action.
• Foreground data sync service: keep xAccess available while enabled and continue supported sync or transfer work while Android treats it as background work.

9. Sharing, transfers, printing, and other apps

When you share, print, export, open a file with another app, or upload a file to your own cloud account, the receiving app or service handles that copy under its own privacy practices. The same applies when you intentionally transfer a file through xAccess or download an xAccess result in another browser. PDF Toolkit cannot delete or control copies kept on another device.

10. Retention and deletion

Local app data remains on your device until you delete files in PDF Toolkit, clear app data, or uninstall the app. Files saved in Documents/PDF Toolkit may remain available in device storage until you delete them. Google Drive copies remain in your Drive until you delete them from Drive. Temporary xAccess working files may remain in the app cache until PDF Toolkit or Android clears them; xAccess outputs sent to the device remain in Documents/PDF Toolkit until you delete them.

You can remove a connected cloud account in PDF Toolkit, manage ad privacy choices from Settings when available in your region, turn off completion notifications, and manage Premium subscriptions through Google Play.

11. Request data deletion

To request deletion of PDF Toolkit-related data, email support@nexdevlab.com with the subject PDF Toolkit data deletion request. Include the Google account email used for Cloud Sync if your request is about a connected Google Drive account. Do not attach sensitive PDFs or personal documents to the email.

You can also use the dedicated PDF Toolkit data deletion page, which explains the request steps, types of data that can be deleted, and records that may be retained.

NexDevLab can delete support-request records and any PDF Toolkit-controlled records associated with your request. Most document data is stored only on your device or in your own Google Drive account, so you can delete it directly by deleting documents in PDF Toolkit, clearing app data, uninstalling the app, disconnecting Cloud Sync, or deleting synced files from Google Drive.

PDF Toolkit may keep limited records when required for security, fraud prevention, legal compliance, dispute handling, Google Play purchase records, or accounting. Third-party services such as Google Play, Google Drive, Google AdMob, Firebase, and Meta Audience Network handle their own records under their own deletion and retention processes.

12. Children

PDF Toolkit is a general productivity app and is not directed to children. Do not use PDF Toolkit to process another person's personal documents unless you have permission to do so.

13. Security

PDF Toolkit uses Android app storage, Android storage permissions, Google authorization, and HTTPS network calls for supported remote services. xAccess is an exception: it uses unencrypted HTTP on the local network, so another party with access to that network may be able to observe or alter xAccess traffic. Use a trusted network, control who has the displayed address, and stop xAccess when you finish. No app can guarantee perfect security, so avoid storing or sharing highly sensitive documents unless you understand where each copy is saved and how it is transferred.

14. Third-party services

PDF Toolkit may use the following third-party services depending on your device, region, settings, and app version: Google Play services, Google Drive, Google ML Kit document scanning/OCR/barcode tools, Google AdMob, Google User Messaging Platform, Firebase Remote Config, Meta Audience Network, and Google Play billing.

These providers may process information under their own terms and privacy policies. Review their privacy information if you use ads, consent, Drive sync, Google Play purchases, or Google-powered scanning features.

15. Changes and contact

This policy may be updated when PDF Toolkit features or service providers change. The date above shows the current version.