Privacy Policy for PDF Pro AI

Draft updated: September 4, 2026. This version becomes effective when published with the corresponding Android app update; it has not yet replaced the policy on our website.

App: PDF Pro AI
Android package: com.pdflauncher
Google Play developer display name: FurryCurry
Privacy contact: privacy@mkit.ai

This policy explains how information is handled when you use PDF Pro AI. “We” refers to the publisher of PDF Pro AI. The app provides PDF tools, optional on-device AI, and an optional Android Home experience called Quick Home. You do not need an account to use it.

1. The essentials

• Our PDF processing and AI inference run on your device. We do not operate a document-upload, cloud-conversion, cloud-AI, or document-sync service in this app.
• The optional AI model is downloaded on demand through Google Play Asset Delivery. Once the model is installed, supported questions and summaries are processed on the device. Downloading a model does not upload your PDF to Google Play.
• The app contains advertising. Advertising and measurement SDKs can send identifiers, interaction records, and technical information to their providers. Local document processing does not mean the entire app makes no network requests.
• On a new installation, usage measurement and operational updates are enabled by default and start when the app starts, without waiting for the introduction screens to finish. Saved opt-outs are respected. You can change these settings as described below.
• Crash-report uploads are off by default. Advertising privacy choices are handled separately from the usage-measurement setting.
• Choosing a cloud document provider, sharing, printing, using network-based text-to-speech, or contacting support may send information outside the device at your direction.

2. Documents and local processing

The app accesses PDFs, images, folders, and output locations that you select using Android's document pickers or an “Open with” action. It may process document names and content URIs, page images, extracted or recognized text, annotations, signatures, form entries, search terms, passwords for requested PDF operations, and generated files.

These data are used to open, read, annotate, sign, fill compatible forms, scan, recognize text, merge, organize, compress, protect, export, save, and share documents. Document processing performed by our app occurs on the device. Some operations create temporary app-private files or flattened output copies.

Our application-defined analytics events and advertising requests do not attach PDF contents, document names or URIs, signatures, passwords, form entries, AI questions or answers, or your recent-document list. Custom handled-error reports use technical categories rather than document text. Automatic crash reports, if enabled, can include exception messages and stack traces produced by Android or a library; those are not a guarantee that every report is free of incidental sensitive information.

If you choose a cloud-backed provider in Android's file picker, that provider may download or upload the selected document under its own policy. A PDF link-to-QR operation encodes the link you supply locally; it does not upload, fetch, or change access to the linked file. Anyone who receives the QR code can read its embedded link.

3. Recent files, Quick Home, and device storage

We store recent-file references and titles, reading position, preferences, onboarding progress, tool-use counters, model status, and other operational state in app storage. This supports reopening files and continuing tasks. Android document grants determine whether a saved file reference can still be opened.

When you enter or use Quick Home, including its preview before choosing a default Home app, the app reads launchable app entries to display names, icons, and launch actions. Our Quick Home implementation does not upload that list as an analytics payload. Advertising SDKs have their own device-information processing, described in section 6; this statement is not a blanket claim that every included SDK is unable to access app information.

Quick Home is optional. Entering its interface does not itself grant the Android Home role: the system controls your default-Home choice. You can change the default Home app through Android Settings.

Android backup or device-transfer services may copy eligible app data according to your device and account settings. The app permits Android backup; local-only processing should not be interpreted as disabling Android's backup services. The local flags used to avoid repeating Adjust milestone events are excluded from app backup and device transfer.

4. AI, scanning, OCR, and read aloud

AI: When you request an AI feature, the app can ask Google Play to download its optional model. Google processes delivery and technical information under its policies. After installation, the app uses extracted PDF text and your question or summary request locally. We do not send that content to a publisher-operated AI service. Model availability, device capability, and supported document text affect whether a request can be completed. AI output may be inaccurate and should be checked against the document.

Scanning and OCR: The document scanner uses Google Play services and may require a first-use component download. Scans and ML Kit text recognition are processed on the device. Google components may separately transmit SDK usage, device, and diagnostic information; see ML Kit terms and privacy information.

Read aloud: When you select this feature, extracted text is passed to your chosen Android text-to-speech provider. Some voices operate locally; others use the provider's network service. Review that provider's settings if the document must remain offline.

5. Usage measurement, attribution, and operational updates

Firebase Analytics

Usage measurement is enabled by default. We use Firebase Analytics for product-operation and onboarding outcomes and for advertising delivery and revenue events. Records may include operation or journey identifiers, feature and outcome categories, ad placement and provider information, request or impression identifiers, revenue values, and technical error categories—not document content.

The service also processes app-instance identifiers and technical context such as app version, device model, operating system, language, and approximate geographic context. We disable Firebase Analytics advertising-ID collection and advertising-personalization consent in this integration. Those Firebase settings do not disable identifier processing by Adjust or advertising SDKs.

Adjust

Adjust follows the usage-measurement setting and starts by default. It measures installations, sessions, attribution, three first-success milestones, and valid per-impression advertising revenue records. The milestones are the first confirmed ad impression, the first successful document-tool operation, and the first observed successful default-Home setup. No custom document fields are attached to these milestone events.

Adjust may process advertising or other attribution identifiers, installation-referrer information, IP/network information, device and app details, timestamps, and the measurement records above. Our integration disables Adjust App Set ID reading and Adjust partner forwarding. This does not disable the separate advertising services or mean Adjust receives no personal data.

Firebase Remote Config

Operational updates are enabled by default and fetched asynchronously at startup. Remote Config supplies feature-availability settings, AI limits, measurement safety switches, and advertising mediation, placement, and timing configuration. It may use a Firebase installation identifier and request-related device, app, and network information. It does not upload your documents or perform AI inference remotely.

Turning operational updates off stops future app-initiated configuration fetches. Previously activated configuration or local defaults may remain in use. This switch is separate from usage measurement and is not a general network or advertising off switch.

Crashlytics

Crash-report uploads require you to enable Crash reports, operational updates to be enabled, and the applicable server safety switch to allow reporting. Reports can contain stack traces, exception details, app and device state, operating-system details, timestamps, and diagnostic installation identifiers. Some diagnostic information can be stored locally before upload. Custom handled reports avoid free-form document data.

6. Advertising and third-party providers

PDF Pro AI includes AdMob and TopOn mediation, with integrated ad sources including Unity Ads, Pangle, Liftoff/Vungle, and TopOn ADX (the Smartdigimkttech SDK). Which providers are used depends on the current mediation configuration, availability, and privacy state; every included source does not necessarily serve an ad in every session.

Advertising providers may process advertising and device identifiers, IP address and approximate location inferred from it, app and SDK versions, device and network characteristics, consent signals, ad requests, views, clicks, rewards, revenue, and diagnostics. Depending on the SDK and Android restrictions, technical information can also include sensor signals or information about installed or available apps. This processing supports ad delivery, measurement, frequency management, and fraud prevention. The app does not request precise-location permission.

Google's User Messaging Platform requests updated consent information and displays a privacy message when required by its configuration. Ad preparation and requests are gated by the resulting request-eligibility state. AdMob handles applicable advertising choices through that flow. Our TopOn adapter currently requests non-personalized advertising. Non-personalized advertising can still involve identifiers, network requests, measurement, and fraud-prevention data.

Turning off Optional usage analytics stops the app-controlled Firebase Analytics and Adjust measurement paths; it does not turn off all advertising SDK communications. Where available, use the separate advertising privacy options in Settings and the advertising controls provided by Android.

Provider information:

Providers may act as service providers or independently determine some processing purposes under their applicable terms. Disclosures for advertising may be treated as “sharing,” “targeted advertising,” or “sale” under some privacy laws even without a monetary sale of data. This policy does not claim that advertising involves no data sharing.

7. Permissions and other disclosures

The app uses Android's user-selected document grants instead of All Files access. It does not request MANAGE_EXTERNAL_STORAGE or QUERY_ALL_PACKAGES. Scoped package queries support launcher entries, PDF handlers, and text-to-speech services.

Included SDKs use network, network-state, advertising-ID, advertising-service, and delivery-related capabilities in the merged Android manifest. These are distinct from the system's user-selected document and default-Home grants. Scanning is provided through the Google Play services scanner flow rather than a broad file-access permission.

When you share, print, export, or open a file in another app, the selected recipient or provider processes it under its own terms. If you email support, we receive your email address and whatever you include. Please do not send passwords or confidential documents unnecessarily. Information we hold may also be disclosed when legally required or needed to address security incidents or protect legal rights.

8. Your choices, retention, and deletion

• Usage measurement: In Settings → Privacy & diagnostics, turn off Optional usage analytics and save your choices. This disables subsequent app-controlled Firebase Analytics and Adjust measurement. Firebase Analytics also resets its local analytics data. Already transmitted or in-flight records are not automatically erased by that action.
• Operational updates: Turn off Operational updates in the same screen and save. Usage measurement is independent. Crash-report collection is also paused when its operational-update prerequisite is off.
• Crash reports: Leave this off or turn it off and save. Disabling it also asks Crashlytics to delete unsent reports; it does not delete reports already received by the service.
• Advertising: Use advertising privacy options when offered and Android's advertising-ID and privacy controls. An analytics opt-out alone is not an advertising opt-out.
• Recent files: Settings offers a clear-recent-files action. This removes the app's recent-file history, not the underlying PDFs.
• App storage: Clearing app storage or uninstalling removes app-private data under Android's behavior. Android backups or device-transfer copies are managed separately. Exported PDFs, images, or text remain in their selected locations until you delete them there.

Local history and preferences are kept until cleared or removed. Temporary working files may remain until app cleanup or Android storage cleanup. Service-side measurement, attribution, advertising, and diagnostic records are retained according to the applicable service settings and the purposes for which they are needed, including reliability, fraud prevention, legal obligations, and dispute handling. Different providers have different retention and deletion practices; disabling a setting does not retroactively erase their records.

For access, correction, deletion, restriction, objection, withdrawal of consent, or other privacy requests available under applicable law, contact privacy@mkit.ai. We will assess requests and any applicable exceptions. Because the app has no account, locating a particular SDK record may require limited technical information. Do not send your PDFs to establish identity. You may also use providers' privacy-request channels and, where applicable, contact your local data-protection authority.

9. Security, international processing, and children

We rely on Android app isolation, scoped document access, and the security mechanisms of the integrated services. No storage, transmission, or processing method is completely secure. Local processing is not a promise that your device, backups, external providers, or generated files are immune to disclosure.

Although our document processing takes place on your device, service providers may process measurement, advertising, delivery, diagnostic, or support information in other countries. Their applicable processing terms and transfer safeguards govern those activities, together with the protections required by applicable law.

PDF Pro AI is a general-purpose document app and is not designed for children under 13. It does not ask users to create an account or provide an age. If you believe a child has provided personal information through the app or support, contact us so that we can assess and address it. Do not interpret the lack of an account or age field as the absence of SDK data collection.

10. Changes and contact

We may update this policy when our features, providers, or data practices change. The published version will state its effective date. Where required, material changes will be accompanied by appropriate notice and consent. This document does not replace any separately required in-app disclosure or consent process.

Privacy questions and requests: privacy@mkit.ai.