Privacy Policy

1. About this policy

This policy covers PDFWonderly for Android, package com.pdfwonderly.app, including its optional home-screen launcher, PDF tools, wallpaper browser, flashlight, advertisements and related measurement services. It describes the current implementation rather than features offered by Tinly or other apps.

PDFWonderly can be used without creating an account. Its current PDF features do not require a cloud document-processing account.

2. Your documents and selected photos

When you choose a PDF or image using an Android file or photo picker, the app receives access to the items you select and copies them into its private working storage. It uses that copy to merge, split or compress PDFs, convert images to PDF, export PDF pages or embedded images, and extract available PDF text as Markdown.

These operations run on your device. The PDF processing code does not send document contents or selected photos to our event endpoint, advertising providers, Adjust or Firebase Analytics. PDF thumbnails, filenames, output files and recent-task history are kept locally for the related tools.

When you choose Download, View or Share, the selected output is written to a location you select or made available to the app you choose. That destination or app has its own privacy practices. Files you export remain outside our private storage and are not removed by deleting an in-app history entry.

3. Launcher, wallpapers and permissions

• Home-screen apps: PDFWonderly queries launchable apps, labels and icons so it can display shortcuts and the all-apps list. It also checks which app handles the Android home screen and whether the promoted Tinly app is installed. The custom SDK-initialization event does not include a list of installed apps.
• Default launcher: changing the default home app uses Android’s settings and your confirmation. You can choose another launcher in system settings at any time.
• Photos and documents: the Android system file or photo picker grants access to the items you select so the app can read and process them. To save an output, you select a destination using the system picker. The current PDF flow does not request broad access to all files or the entire photo library; access to a selected item is different from a broad storage permission.
• Camera permission: the flashlight requests this permission to control the camera flash. The flashlight implementation does not take photos or record video. You can deny or revoke this permission.
• Wallpaper: the app uses bundled wallpaper assets and Android’s wallpaper service to apply your selection to supported home or lock screens.
• Internet: online access supports ads, attribution, technical event reporting and external destinations. PDF processing itself is local.

4. Technical events and identifiers

We record technical events when an advertising SDK initializes successfully and, where applicable, when launcher authorization prompts or advertising triggers, displays, failures and clicks occur. The app submits these events to our technical reporting service and Firebase Analytics. Depending on the event, information can include the SDK or ad network name, app package and version, UTC event time, a unique event ID, device brand and model, Android version, a country code from device-region settings, an attribution-channel value from Adjust or a host-provided setting (or an unknown value when unavailable), and a fixed business attribution label. Authorization and advertising events can also include the prompt or trigger context, prompt count or skip reason, ad placement identifier, format, network, estimated ad value when available, and failure details. The report can also include system language and the Android SDK version. Campaign, ad-group and site fields are currently sent as empty values; they are not populated from attribution data in this custom report. The receiving service can also receive the connection’s IP address and ordinary server-access information.

The custom report uses a randomly generated installation UUID, saved in app-private preferences. In the current event schema it is labelled oaid; this particular value is an app-generated installation identifier, not a hardware OAID or Google Advertising ID. It normally survives app restarts and in-place updates; clearing app data or a fresh installation normally creates a new value. Each event also has its own UUID for deduplication and retries.

Events are sent to tracker.wislingo.com over HTTPS with an encrypted request body. The event queue keeps the original event during retries, including its installation identifier and occurrence time. This report does not include PDF text, selected images, filenames or document thumbnails.

5. Advertising and attribution partners

Ads may appear at app entry, in selected launcher or PDF pages, or before certain actions. Availability and placement depend on configuration and successful loading. Advertising partners may process device and advertising identifiers where available, IP-based approximate location, device/network information, ad interactions and technical diagnostics for delivery, measurement and fraud prevention. Details depend on the active provider and mediation arrangement.

Google AdMob

Advertising and possible mediated sources. See Google’s Privacy Policy and its advertising explanation.

Pangle

Direct advertising and supported mediation paths. Pangle publishes region-specific end-user policies and controllers.

Adjust

Install attribution and session measurement may use advertising identifiers where available, install-referrer information, device/network data and attribution results. See Adjust’s privacy information.

Google Analytics for Firebase

We use Firebase Analytics to understand app usage, including automatically collected installation, session and activity-screen events, app/device information and measurement identifiers such as an app-instance identifier. Advertising identifiers may be used where available and permitted by device settings. Google may process network information in connection with these services. This measurement operates separately from Adjust. We also submit SDK-initialization, launcher-authorization and advertising lifecycle events to Firebase, including relevant event context, advertising SDK and placement details, app and device-version details, language and attribution-channel information where available. The event includes its occurrence time and a randomly generated event correlation ID so that this event can be matched to our separate technical report; it is not used as a Firebase user ID. The custom event does not repeat the installation UUID or Google Advertising ID as Firebase event parameters. Our integration does not send PDF contents, selected photos, filenames, email addresses or the custom report’s installation UUID as Firebase event parameters or a Firebase user ID.

See Google’s Privacy Policy and Firebase’s privacy information. Analytics retention and controls depend on the configured Google Analytics property and applicable choices.

Other integrated adapters

TopOn and BIGO adapters are included but currently disabled in the local configuration. Their activation or material changes to data processing require an updated disclosure and any required privacy controls.

The custom initialization report may also include a separate Google Advertising ID when available and tracking is not limited by the device setting. Missing, zero or restricted advertising IDs are omitted; they are not replaced with another device identifier. The installation UUID remains a separate installation identifier. Third-party SDKs may independently use permitted identifiers. A notice about local PDF processing should not be read as a claim that the entire app works without network activity.

6. Why information is used and shared

Local information supports the launcher, selected-file processing, previews, recent results and your preferences. Technical events help measure and diagnose SDK initialization, launcher authorization prompts, advertising activity and upload failures. Advertising and attribution data support ad delivery, performance measurement, fraud prevention and understanding how installations originate.

Information may be received by our technical-reporting service and its hosting providers, active advertising or attribution providers, and destinations you explicitly open or share with. Information may also be disclosed when a binding legal requirement applies or to address misuse and security incidents. This policy does not grant permission to reuse the contents of your documents for advertising or model training.

7. Your choices and regional rights

You choose which files to import, whether to share an output, whether to grant flashlight permission, and whether to make PDFWonderly the default launcher. Android may provide advertising-ID and advertising-privacy settings; availability varies by device. Changing these settings does not necessarily remove all ads.

Depending on applicable law, you may have rights to access, correct, delete or obtain a copy of personal information, object to or restrict certain uses, withdraw consent, or opt out of certain advertising-related processing. You may also be able to complain to your local data-protection authority. Contact us at [email protected] to ask about these rights. We may request proportionate information to locate a record or verify your request.

This document itself is not an advertising-consent form. The current development build does not expose an active in-app CMP/privacy-choice flow; reading this page or continuing to use the app must not be treated as an affirmative choice for personalized advertising. Any regional consent or opt-out controls required for distribution must be provided separately.

8. Storage, retention and deletion

Completed local task history keeps up to the latest 30 tasks. Removing a task deletes its private result files; older results can also be removed as the history limit is reached. Private working copies and interrupted tasks are cleaned up by the app. Keep exported copies of important documents.

Pending technical events are stored in a bounded local queue. Confirmed stored or duplicate events are removed from that queue; invalid events can remain locally for troubleshooting. Clearing app data removes private local history, preferences and queued events, but does not erase exported files or information already received by servers or third parties.

Server-side retention: the operator must confirm and publish the retention periods or criteria for its technical-event database and access logs. Those periods are not specified in the current app implementation. Third parties apply their own published retention practices.

9. Security and international processing

The app uses private application storage and HTTPS for its custom event reporting. No storage or transmission method can be guaranteed completely secure. Local files are not described as encrypted at rest merely because they are in private app storage.

Advertising, attribution and hosting providers may process information in countries other than your own. The applicable controller, destination and transfer safeguards depend on the provider and region. See the linked provider notices or contact us for details. We do not claim that a specific hosting country or transfer mechanism has been verified where that information has not been supplied.

10. Children and changes

PDFWonderly is not designed as a child-directed service. We do not intend to solicit children’s personal information. If you believe a child’s information has been processed inappropriately, contact us so the situation can be investigated. This notice does not establish a verified parental-consent process or an age-verification feature.

We may update this policy when the app or its providers change. A revised date will appear at the top of this page. Material changes and any new choices required by applicable law should be communicated through an appropriate app or store notice; a policy update alone does not provide new consent.

11. Contact

App: PDFWonderly · Android package: com.pdfwonderly.app