Privacy Policy for toPDF
toPDF is an offline PDF toolkit for Android. This policy explains what happens to your information when you use the app. The short version: your documents and photos are processed on your device and are never sent to us.
Our core promise: the documents and photos you process never leave your device, except the optional Office conversion that you choose to start (section 1a). Firebase receives only usage and crash data.
1. Your files stay on your device
All tools in toPDF (Image to PDF, Document scanner, Compress, Merge, Split, Photo and signature resizer, ID card on one page, PDF viewer) process your files on your device only. Your photos, scans, PDFs and the files you create are not uploaded to our servers or to any third party by the app. The one exception is the optional Office conversion described in section 1a.
- You choose the files to process. The app reads them only to perform the action you asked for.
- Files you create are saved to the Download/toPDF folder on your device using Android's MediaStore. They stay there until you delete them.
- The app keeps a history database on your device (file names, locations, dates and sizes of the files you saved) so you can find, open and share them again. This history is not sent to us.
- The document scanner uses the Google ML Kit Document Scanner. It is delivered through Google Play services and scans and processes pages on your device. Your scans are not sent to us. Google may collect limited usage and performance data for ML Kit as described in its disclosure.
- If you share a file from toPDF to another app, that app's own privacy policy applies to the copy you send.
1a. Office conversion (optional)
Word, Excel, PowerPoint, OpenDocument and RTF files cannot be converted on the phone, so Office conversion is the one toPDF feature that sends a file off your device. It is a Pro feature and it is opt-in: nothing is sent unless you pick a file and confirm "Upload & convert" in the consent sheet (you can tick "Don't ask again" to skip the sheet next time, and your Pro purchase is required to start it).
- What is sent: the document you chose, over an encrypted (HTTPS) connection, to our conversion endpoint (a Cloudflare Worker at office.mjandroid.dev). The endpoint passes it to our processor CloudConvert (Lunaweb GmbH, Germany), which converts it to PDF. The app uploads it under a generic name ("document" plus the file extension), not your real file name.
- What comes back and what is deleted: the PDF is returned to your phone and saved in Download/toPDF like any other result. Our endpoint stores no files, and it asks CloudConvert to delete the conversion job (your file and the PDF) right after the PDF has been delivered. CloudConvert's own retention and security are described in its privacy policy: https://cloudconvert.com/privacy.
- Also sent: a random install ID (a UUID the app creates; it is not linked to your name or account) used only to limit use to 10 conversions per day, and a shared app key. The install ID counter expires after 24 hours. Like any internet request, your IP address is visible to Cloudflare, which runs the endpoint, and to CloudConvert.
- What we log: only the file size, extension, duration and result of each conversion. Never file contents or names.
- Your choice: do not use this feature if the document is something you do not want to upload. The rest of the app keeps working offline.
2. Information we collect
We do not collect personal data. toPDF has no accounts or login, and we do not ask for your name, email address, phone number or location. We do not run a server that receives your data, except the stateless endpoint used by the optional Office conversion (section 1a), which keeps no files.
We do use Firebase Crashlytics (crash reports) and Firebase Analytics (basic usage statistics), which receive technical and usage data but never your files or file names. We set no user ID, so this data is not linked to your name or account. The app also includes other third-party services (section 3). These services may collect limited technical data directly from your device, as described by each provider. We do not receive your documents through them.
3. Third-party services in the app
| Service | Purpose | Data it may collect | Provider's privacy policy |
|---|---|---|---|
| Google AdMob (Google Mobile Ads SDK) | Shows ads in the free version | Advertising ID and other device identifiers, IP address (which can indicate approximate location), device and app information, ad interactions such as taps and views, diagnostics | https://policies.google.com/privacy and https://policies.google.com/technologies/partner-sites |
| Google User Messaging Platform (UMP) | Asks for your consent where the law requires it | Your consent choices and related device identifiers | https://policies.google.com/privacy |
| Google Play Billing | Handles the one-time "Pro" purchase that removes ads | Purchase information such as a purchase token and order status. Payment details are handled by Google Play and are not seen by us | https://policies.google.com/privacy and https://play.google.com/about/play-terms/ |
| Google Play In-App Review | Lets you rate the app without leaving it | Handled by Google Play; we do not receive your review data beyond what Play shows in the Play Console | https://policies.google.com/privacy |
| Google Play In-App Update | Lets the app check for and install updates through Google Play | Handled by Google Play; update status and device information are processed by Google Play | https://policies.google.com/privacy |
| Firebase Crashlytics (Google) | Crash reporting, so we can find and fix crashes | When the app crashes: stack trace, device model, Android version, app version, app state at the time of the crash, and a Crashlytics installation ID (a random UUID). We set no user ID | https://firebase.google.com/support/privacy and https://firebase.google.com/docs/crashlytics/android/customize-crash-reports |
| Firebase Analytics (Google Analytics for Firebase) | Understand which tools are used so we can improve the app | Automatic events and properties (for example first open, session start, screen views, app version, device model, Android version), country or region derived from IP address, the app-instance ID, and the advertising ID where available (AdMob is in the app). One custom event, file_saved, records only which tool made a file (such as image_to_pdf or compress) and whether it is a PDF or an image. It never records file names, sizes or contents. We set no user ID | https://firebase.google.com/support/privacy and https://firebase.google.com/docs/analytics/configure-data-collection |
| Google ML Kit Document Scanner | On-device document scanning | Runs on your device. Google may collect limited usage and performance data for ML Kit | https://developers.google.com/ml-kit/android-data-disclosure |
We use this data only for advertising, consent, processing your purchase, crash fixing and understanding which tools are used. We do not sell your personal data. Firebase processes data on our behalf as Google's service provider (see Google's Firebase data disclosure: https://firebase.google.com/support/privacy). Firebase is active only in release builds from Google Play, not in development builds.
4. Advertising and consent (GDPR, UMP)
The free version shows ads served by Google AdMob. If you are in the European Economic Area, the United Kingdom or another region that requires consent, the app shows a consent form from Google's User Messaging Platform the first time you open it. You can accept, decline or manage your choices. If you decline, you may still see ads, but they will not be personalized.
You can review or change your choice at any time from the privacy options entry in the app settings (where shown for your region). On Android you can also:
- Reset your advertising ID or opt out of ad personalization in Android Settings, under Google, then Ads.
- Manage Google ad personalization at https://adssettings.google.com.
The one-time Pro purchase removes ads from the app.
5. Legal bases (EEA and UK users)
Where the GDPR or UK GDPR applies, we rely on your consent for personalized advertising and for the use of identifiers by ad services. For crash reports and basic usage statistics we rely on our legitimate interest in keeping the app stable and improving it. Processing needed to complete your purchase relies on contract performance and is carried out by Google Play.
6. Children
toPDF is not directed at children under 13 (or under the minimum age required by the law in your country). We do not knowingly collect personal information from children. If you believe a child has provided personal information through the app, contact us at mjandroiddev@gmail.com and we will help resolve it. Parents can also use Android and Google Play parental controls and Google's ad settings.
7. Data retention
- Your files and history: stay on your device until you delete them or uninstall the app. We cannot access or delete them for you.
- Data held by third-party services: retained by those providers under their own policies. For example, Google retains advertising data as described in its policy.
- Crash data (Firebase Crashlytics): kept for 90 days, then removed (Google's Firebase data disclosure).
- Usage data (Firebase Analytics): event data is kept for 2 months by default, unless we change the retention setting in our Firebase console. Aggregated reports that do not identify you may be kept longer.
- Purchases: purchase records are kept by Google Play.
8. Security
SDK traffic between the app and Google services is encrypted in transit. Because your files are not uploaded (except in the optional Office conversion, section 1a), their security depends on your device. We recommend using a screen lock and keeping Android updated.
9. Your rights and choices
- Delete your files and history: delete files from the Download/toPDF folder using any file manager, delete entries in the app's History screen, or clear the app data or uninstall the app in Android settings.
- Ad personalization: change your UMP choice in the app, or use Android and Google ad settings as described in section 4.
- Advertising ID: reset or delete it in Android Settings, under Google, then Ads. Firebase Analytics also uses the advertising ID where available, so limiting it limits that use too.
- Analytics and crash reports: toPDF does not currently have an in-app switch to turn Firebase Analytics or Crashlytics off. Resetting or limiting the advertising ID is the only control available today. You can also write to mjandroiddev@gmail.com with questions.
- Data held by Google services: you can access, export or delete data associated with your advertising ID or Google account through Google's tools (https://myaccount.google.com/data-and-privacy) and request help from the provider's privacy contacts.
- Requests to us: since we do not hold personal data that identifies you, there is usually nothing to delete on our side. You may still write to mjandroiddev@gmail.com to ask a question or make a request. Depending on where you live (for example the EEA, UK, India, or California), you may have rights to access, correct, delete, restrict or object to the processing of your personal data, or to withdraw consent. We will reply within the time required by applicable law.
10. International transfers
Google services may process data in countries other than your own, including the United States. Where required, Google relies on lawful transfer mechanisms. Your documents are not part of these transfers because they never leave your device. The exception is a file you choose to convert with Office conversion, which is processed by Cloudflare and CloudConvert (Germany).
11a. Users in India (DPDP Act, 2023 and IT Rules)
For users in India, MJ Android Dev is the Data Fiduciary for the limited personal data described in section 2. We process it only for the purposes stated in this policy (running ads, measuring usage and crashes, processing your optional Office conversion and your Pro purchase), on the basis of your consent and legitimate uses permitted by the Digital Personal Data Protection Act, 2023. You can withdraw consent for personalised ads at any time in Settings → Privacy choices (where shown) or by resetting or deleting your advertising ID in Android settings, and you can ask us about, correct or erase personal data we hold by writing to us. You may also nominate another person to exercise your rights in the event of death or incapacity.
Grievance Officer (Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 and Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021): Manoj Singh Rawal, mjandroiddev@gmail.com. We acknowledge complaints within 24 hours and aim to resolve them within 15 days. If you are not satisfied, you may approach the Data Protection Board of India once it is operational.
We do not knowingly process personal data of children under 18 in India for tracking, behavioural monitoring or targeted advertising; see section 6.
11. Changes to this policy
We may update this policy, for example when we add or remove a service. We will post the new version at https://mjandroid.dev/topdf/privacy and change the "Last updated" date above. If a change is significant, we will also tell you in the app or in the Play Store release notes. Please review the policy from time to time.
12. Contact
Questions about this policy or your data: mjandroiddev@gmail.com
Sources
- Google Play User Data policy: https://support.google.com/googleplay/android-developer/answer/10144311
- Data safety form guidance (definitions of collect and share): https://support.google.com/googleplay/android-developer/answer/10787469
- AdMob Play data disclosure: https://developers.google.com/admob/android/privacy/play-data-disclosure
- Google ML Kit data disclosure: https://developers.google.com/ml-kit/android-data-disclosure
- Firebase data disclosure (Crashlytics retention, service provider terms): https://firebase.google.com/support/privacy
- Firebase Analytics data collection: https://firebase.google.com/docs/analytics/configure-data-collection
- Crashlytics data collection and reporting: https://firebase.google.com/docs/crashlytics/android/customize-crash-reports
- Google Analytics data retention: https://support.google.com/analytics/answer/7667196
- Content rating and ads guidance: https://support.google.com/googleplay/android-developer/answer/9859655