English Version
Last Updated: 2026-10-07
Effective Date: 2026-10-07
Welcome to PDF2IMG ("we", "our", or "the App"). This policy explains how documents are handled on your device, and which limited data the App sends to the service providers named below.
PDF2IMG opens PDFs and renders them to images on your device. PDF files, page images, and exports are not uploaded to us. The App does send limited usage analytics, crash diagnostics, push tokens, and purchase status to the third-party services listed in this policy.
1. On-device document processing
- PDFs are opened and rendered to images on the device with Apple PDFKit.
- PDF files, page images, and exports are never uploaded to us or to any of the services listed in this policy.
- Files stay in the app sandbox, and in the app-group container used by the Share Extension, until you delete them or uninstall the App.
- Passwords for protected PDFs are stored only on the device.
- The optional "Download" feature fetches a PDF directly from the URL you enter. That request goes to the third-party server at that URL, not to us.
2. Analytics, crash, push, and purchase data
The App sends limited usage analytics, crash diagnostics, push tokens, and purchase status to the services in Section 3. The App does not require an account.
- Analytics events include screen names and feature actions (for example, pages selected or merged, export format, DPI or quality, export preset, and page counts).
- Analytics events currently also include the names of documents you open or export. These are file names only. File contents are never included.
- Crash reports can include breadcrumb logs of recent screens and actions, and those logs may include document file names.
3. Third-party services
The providers below process the listed data on our behalf for the purposes stated.
- Google Firebase Analytics (Google LLC): Used for analytics and product improvement. Firebase Analytics receives an app-instance ID, IDFV, device model, operating system, language, coarse country derived from the IP address, app version, and the in-app events and screen views described above, including document file names and never file contents. Privacy policy: https://firebase.google.com/support/privacy.
- Firebase Crashlytics (Google LLC): Used for crash diagnostics and stability. Crashlytics receives crash stack traces, device and operating-system state, a Crashlytics installation ID, breadcrumb logs of recent screens and actions (which may include document file names), non-fatal errors, and the push token and push provider stored as a custom key.
- Firebase Cloud Messaging (Google LLC): Used outside mainland China to deliver push notifications. Firebase Cloud Messaging receives an FCM registration token and Firebase installation ID linked to the APNs token, plus device model, operating-system version, language, timezone, and app version.
- JPush 极光推送 (深圳市和讯华谷信息技术有限公司): Used only when the device region is mainland China, instead of Firebase Cloud Messaging, to deliver push notifications. JPush receives a JPush registration ID, the APNs device token, device identifiers including IDFV, device hardware information (model, screen resolution, manufacturer), operating-system information (version, name, language), network information (network type, carrier, IP address), and push delivery logs. The App uses the IDFA-free "noidfa" build of the JPush SDK and does not collect the IDFA. Privacy policy: https://www.jiguang.cn/license/privacy.
- PostHog (PostHog Inc.): Used for product analytics on the US cloud at us.i.posthog.com. The App generates a random anonymous ID that is not the IDFA. PostHog receives app lifecycle events (install, open, and background), screen views, the same in-app events (including document file names, never file contents), device model, operating system, locale, timezone, screen size, and app version. PostHog receives the IP address and uses it for coarse geolocation. A person profile holds the push provider and push token. Session replay and tap autocapture are off. Privacy policy: https://posthog.com/privacy.
- RevenueCat (RevenueCat, Inc.): Used for subscription validation and management, and for restoring purchases. RevenueCat receives an anonymous RevenueCat app user ID generated on the device, App Store receipt and transaction data (product, purchase, renewal, and expiry dates, price and currency, and trial status), country and locale, and app version. Requests may be routed via RevenueCat's api.rc-backup.com domain. Privacy policy: https://www.revenuecat.com/privacy.
- Apple App Store / StoreKit (Apple): Payment is processed by Apple. We never receive your card or billing details. Subscriptions are governed by Apple's Standard Terms of Use (EULA).
Third-party SDK directory / SDK information-sharing list
| SDK name | Company | Purpose | Personal information collected | Collection method | Privacy policy |
|---|---|---|---|---|---|
| Firebase Analytics | Google LLC | Analytics and product improvement | App-instance ID; IDFV; device model, operating system, language, and coarse country derived from IP address; app version; in-app events and screen views. Those events currently include the file names of documents opened or exported, and never include file contents. | Collected automatically by the SDK, together with events logged by the app | https://firebase.google.com/support/privacy |
| Firebase Crashlytics | Google LLC | Crash diagnostics and stability | Crash stack traces; device and operating-system state; Crashlytics installation ID; breadcrumb logs of recent screens and actions, which may include document file names; non-fatal errors; and the push token and push provider stored as a custom key. | Collected automatically by the SDK. The app sets the push token and push provider as a custom key. | https://firebase.google.com/support/privacy |
| Firebase Cloud Messaging | Google LLC | Deliver push notifications outside mainland China | FCM registration token and Firebase installation ID linked to the APNs token; device model; operating-system version; language; timezone; app version. | Collected automatically by the SDK | https://firebase.google.com/support/privacy |
| JPush SDK (including JCore) | 深圳市和讯华谷信息技术有限公司 | Deliver push notifications to users in mainland China | JPush registration ID; APNs device token; device identifiers (IDFV; the IDFA-free “noidfa” SDK build is used, and the app does not collect IDFA); device hardware information (model, screen resolution, manufacturer); operating-system information (version, name, language); network information (network type, carrier, IP address); push delivery logs. | Collected automatically by the SDK | https://www.jiguang.cn/license/privacy |
| PostHog | PostHog Inc. (US cloud, us.i.posthog.com) | Product analytics | A random anonymous ID generated by the app (not the IDFA); app lifecycle events (install, open, background); screen views; the same in-app events, which currently include document file names and never include file contents; device model, operating system, locale, timezone, screen size, and app version; IP address, which PostHog uses for coarse geolocation; and a person profile holding the push provider and push token. Session replay and tap autocapture are off. | Sent by the app. PostHog receives the IP address. | https://posthog.com/privacy |
| RevenueCat | RevenueCat, Inc. | Subscription validation and management, and restoring purchases | An anonymous RevenueCat app user ID generated on the device; App Store receipt and transaction data (product, purchase, renewal, and expiry dates, price and currency, and trial status); country and locale; app version. Requests may be routed via RevenueCat’s api.rc-backup.com domain. | Sent by the app | https://www.revenuecat.com/privacy |
4. Advertising and cross-app tracking
- The App shows no ads and contains no ad-network SDK.
- The App does not request App Tracking Transparency permission and does not access the IDFA.
- Data is not sold, not shared with data brokers, and not used for targeted advertising or for cross-app or cross-website tracking.
- The third-party providers named in this policy process data on our behalf for the purposes described above.
5. Device permissions
To import files, save exports, and show notifications, the App may ask for these iOS permissions:
| Permission | Triggered When | Purpose |
|---|---|---|
| Photo Library Additions | Tapping "Save to Photos" | Used solely to save generated long images or multiple image files directly to your iOS Photos app. We do not read, view, or scan your existing photo album. |
| Document Picker / Files | Tapping "+" or "Import File" | Used solely to load the PDF document you explicitly select from your local Files app or iCloud Drive. |
| Notifications | Asked at launch | Used only to show push notifications. You can turn notifications off in iOS Settings → PDF2IMG → Notifications. |
The App does not request location, camera, contacts, or microphone access. You can review or change these permissions at any time in iOS Settings → PDF2IMG, or in Settings → Privacy & Security. Turning off Photo Library Additions or document access only disables the related save or import action. You can turn notifications off in iOS Settings → PDF2IMG → Notifications.
6. In-app purchases and subscriptions
- Processed by Apple: Subscription payment is processed by Apple through StoreKit. We never receive your card numbers, billing addresses, or other billing details.
- RevenueCat: Subscription validation, subscription management, and restoring purchases use RevenueCat, as described in Section 3.
- Terms of Use: Subscriptions are governed by Apple's Standard Terms of Use (EULA).
7. Your choices
- Notifications: You can turn notifications off in iOS Settings. The push token remains registered, but no notifications are shown. Uninstalling the App invalidates the token.
- Local documents: Delete documents in the App, or uninstall the App, to remove all local data.
- Subscriptions: Manage or cancel subscriptions in your Apple ID settings (Settings → [your name] → Subscriptions).
- Access or deletion: To request access to or deletion of analytics, crash, push, or subscription data, email support@jiaqiang.cc and include the support information shown in the App. Because the App has no accounts, we may need the push token or the RevenueCat user ID to locate that data.
- There is currently no in-app setting to opt out of analytics.
8. Data retention
- Local files remain on the device until you delete them or uninstall the App.
- Analytics, crash, and push data are kept only as long as needed for the purposes in this policy, and according to each provider's retention settings. For example, Crashlytics crash data is kept for about 90 days, and analytics data is limited by our provider settings.
- Subscription records are retained as needed for purchase validation and for legal and accounting requirements.
9. International transfers
- Data handled by Google (Firebase Analytics, Crashlytics, and Cloud Messaging), PostHog, and RevenueCat is processed in the United States.
- JPush data for users in mainland China is processed in mainland China.
10. Children's privacy
PDF2IMG is not directed to children under 13. In mainland China, it is not directed to minors under 14. We do not knowingly collect personal information from them. If you are a parent or guardian and believe we have collected personal information from a child, email support@jiaqiang.cc and we will delete it.
11. Updates to this policy
We may update this Privacy Policy. The updated version will be published on this page with a new "Last Updated" date.
12. Contact us
If you have questions about this Privacy Policy, contact us at:
Support Email: support@jiaqiang.cc
© 2026 PDF2IMG. All rights reserved.