PDF Office Viewer
Privacy Policy
Last updated:
Your documents are processed on your device. PDF Office Viewer does not automatically upload your document contents to a server operated by us. We use Google Firebase services for app usage measurement, crash diagnostics, configuration, and notification delivery. These services process technical information as described below.
This Privacy Policy explains how PDF Office Viewer (the “App”) accesses, uses, stores, and shares information. References to “we,” “us,” and “our” mean the developer identified in the Contact us section. This policy describes the current Android App; we will update it when our data practices change.
1. Documents and local information
The App accesses documents and images that you select, import, or allow it to find on your device. This includes file contents and file details such as names, paths, formats, sizes, and modification times. We use this information to list, search, preview, convert, rename, save, encrypt, decrypt, delete, print, and share files when you use those features.
Document processing, including image-to-PDF conversion and PDF password operations, takes place on your device. Passwords you enter are used for the requested operation and are not intentionally included in our analytics events or manually recorded diagnostic reports.
The App stores preferences, bookmarks, recent-file references, and imported or generated files locally. You do not need to create an account. We do not ask you to provide your name, email address, contacts, or payment details to use the current App.
2. Technical information and Firebase
The App connects to services provided by Google. Technical information can include installation identifiers, app and operating-system versions, device information, language, timestamps, and network information. Service requests may expose your IP address to the service provider.
Google Analytics for Firebase
Analytics is enabled by default in the current App. We record startup and onboarding steps and permission-related actions and results, together with an entry source, outcome, and randomly generated flow identifier. The SDK also collects automatic app and session information, an app-instance identifier, and device information; Analytics may derive an approximate location from network information. Our custom events do not include document contents, file names, file paths, or document passwords.
Firebase Crashlytics
Crash reporting is enabled by default. Crashlytics processes installation and session identifiers, crash traces, device and app information, and diagnostic details to help identify failures. Our manually recorded error reports are limited to the error type, operation, and stack trace.
Firebase Remote Config
Remote Config uses installation identifiers and technical information to deliver app configuration, such as feature switches and notification limits.
Firebase Cloud Messaging
Cloud Messaging processes installation identifiers and registration tokens to support push delivery. Registration can occur even if you decline notification permission; that permission controls notification display. The current App does not send its registration token to a separate backend operated by us.
For more information, see Firebase Privacy and Security, Google Analytics data collection, and the Google Privacy Policy.
3. Permissions and scanning
- Files and storage: file access, including “All files access” on supported Android versions, is used to discover and manage supported documents. You can also import files through the system file picker. Declining broad access limits file discovery.
- Notifications: notification permission allows the App to display notifications. You can decline it or change it in Android settings.
- Scanning: document and code scanning use Google Play services. Scanning image processing runs on your device, and the scanner returns the results you choose to provide. These integrations use the scanner’s camera interface without the App requesting its own camera permission. Google Play services may download scanning components and process technical service information.
- Internet access: the App uses network access for the Google services described in this policy. It does not require you to upload documents for local PDF processing.
The App does not request access to your contacts, microphone, or precise device location. You can review and revoke available permissions in Android settings.
Google provides further details about its document scanner and code scanner.
5. Advertising
The current App does not display third-party advertisements and has no advertising SDK integrated. Advertising-related storage, advertising user-data processing, and personalized advertising are disabled by default in its Firebase consent configuration. If we introduce advertising or additional data processing, we will update this policy and provide any required disclosures and choices.
6. Storage, retention, and deletion
Imported and generated files in the App’s private storage remain until you delete them, clear the App’s storage, or uninstall it. Temporary files may remain in its cache until cleared by the App, Android, or you. Local preferences and recent-file references remain until removed or the App’s storage is cleared. Device backup and restoration may preserve or restore local app data according to your Android and backup settings.
Files saved outside the App’s private storage, including original files and exported or shared copies, may remain after uninstalling. Delete those copies through the relevant file manager, recipient app, cloud provider, or print service. Deleting a file inside the App can delete the underlying file; it is not only removal from a list.
Technical data sent to Google is retained according to the relevant service’s retention rules and our project settings. Clearing local app data or uninstalling does not automatically erase previously transmitted analytics or crash reports. We use such information for the operational purposes described in this policy, and deletion requests are subject to the provider’s available controls and applicable obligations.
For questions about retained information or to make a deletion request, use the privacy contact below. We may need information sufficient to identify the relevant records; we cannot necessarily link a technical installation identifier to a person.
7. Your choices and privacy rights
You can choose which files to import or share, revoke permissions, disable notifications, delete files, and clear local app storage. Turning off notifications does not disable Analytics or Crashlytics. The current App does not provide an in-app toggle for those two services.
Depending on your location and applicable law, you may have rights to request access, correction, deletion, or a copy of personal information, to object to or restrict certain processing, or to withdraw consent where processing relies on consent. Contact us to make a request. Requests will be assessed according to applicable law and the information and technical controls available to us. You may also have the right to contact your local data-protection authority.
8. Security and international processing
We use the Android application sandbox for private app files, system-mediated file selection and sharing, and encrypted network connections for Firebase services. No storage or transmission method can guarantee absolute security. You remain responsible for protecting your device and deciding where to save or share documents.
Google may process technical information in countries outside your country of residence. Its applicable privacy policies and data-processing terms describe how it handles that information.
9. Children’s privacy
The App is a general-purpose document utility and is not designed specifically for children. If you are a parent or guardian and believe a child has provided personal information to us, contact us so we can review the concern and take appropriate action.
10. Changes to this policy
We may update this policy when the App or our data practices change. The revised version will be posted on this page with an updated date. Where required, we will provide additional notice or request consent before applying the relevant change.