PRIVACY POLICY
Application: All-in-One PDF Viewer & Editor
Japanese store name: オールインワンPDFビューアー&エディター
Android package: com.beautydream.imagetopdf.pdfconverter.pdfmaker
Developer: Beauty Dream Studio
Contact: contact@yuzhensoftware.com
Last updated: November 17, 2026
Effective date: November 17, 2026
Beauty Dream Studio ("we", "us" or "our") provides All-in-One PDF Viewer & Editor (the "App"). This Policy explains the information we access, collect, use, retain and disclose, the services involved, and your choices. We are responsible for personal information we process for our own purposes. Providers may act on our behalf or for their own disclosed purposes, depending on the service and applicable law.
1. Scope and Key Points
This Policy describes the App as provided with version 1.3.1 and its current document-reading features. The same Android package identifies the App if its display name differs by language or installed version. An older installed version may not contain all of the features or integrations described here. This Policy does not state that a newly added practice existed in every earlier version.
- Current document reading, scanning, recognition, editing, conversion, image viewing and local MP3 playback take place on your device. We do not upload your document or audio contents to our servers to perform these features.
- The App does not require a Beauty Dream Studio account and does not provide a cloud document-backup service.
- Local file processing does not mean that the App is offline or collects no personal information. Advertising, analytics, attribution, crash reporting, remote configuration, messaging, model downloads and subscriptions use connected services.
- An active subscription removes App-served advertisements. It does not disable all analytics, diagnostics, messaging or subscription processing.
- Files you deliberately share, export to a cloud destination or attach to support messages are handled by the destination you select.
2. Files and Other Information Processed on Your Device
With the permissions or individual file access you grant, the App processes:
- PDF, Word, Excel, PowerPoint and TXT documents, images and MP3 files that you select, open, scan, edit, convert, save or play;
- File names, local paths or content URIs, formats, sizes, timestamps and thumbnails needed for discovery, search, sorting, file-location links and document management;
- Recent-viewing records, favorite status and times, new-file markers, local folder and recycle-bin records, and reading preferences;
- Camera images, crop areas, page order, rotation, image adjustments, recognized text, edits, drawings, signatures, watermarks and output settings;
- Passwords entered for supported PDF protection or opening operations;
- Temporary working copies, rendered previews, conversion results, audio playback state and file metadata used for local playback controls; and
- App settings, permission-guide state, default-reader guidance records, local task and navigation state, subscription-prompt counters, purchase-state caches, and notification scheduling and deduplication records.
These records support the features you use. Browsing a device file does not by itself mean it has been imported into the App-managed PDF library. Reading or converting may create a temporary local copy. Editing or saving may create a new result or update an App-managed document according to the selected operation. Supported DOCX text editing saves an edited copy to a selected destination.
Text recognition runs locally. Some models must first be downloaded through Google Play services; downloading a model is separate from uploading a document for recognition. PDF passwords are used for the relevant local operation and are not deliberately included in our custom analytics or sent to a developer document-processing server. We cannot recover a forgotten password.
3. File Discovery, Background Observation and Permissions
All-files access lets the App discover and work with supported documents, images and audio in accessible shared-storage locations. It supports the document lists and file-management features. Android grants this through special-access settings. Refusing or revoking it limits automatic discovery; available system document-picker and external-sharing flows can still provide access to individually selected supported files.
When relevant access and background services are available, the App observes changes to accessible files through Android's media index and filesystem notifications, as well as changes to its own PDF library. It uses local information about file additions, deletions and likely screenshots to update file availability and decide whether to offer a related reminder, such as opening a document or converting an image to PDF. Screenshot recognition can use file and folder names in multiple languages. This is file-change detection, not continuous screen recording, and does not capture the screen or read the interface of other apps. Monitoring can continue when you are not actively using the App, subject to Android restrictions. It does not upload the local file index or screenshot contents for notification selection.
The App may request or declare the following access, depending on Android version and the feature:
- Camera: to capture pages in the App's scanner. Some supported flows may use Google's scanning interface. Imported images can be used instead of the camera.
- Photos and selected visual media: to show accessible albums and thumbnails and select images. On supported Android versions, selected-photo access is available.
- All-files access and legacy external-storage read/write permissions: to discover and manage supported files and save outputs where the Android version permits.
- System document access: to read or write the particular file or location you select, including a cloud document provider you choose.
- Notifications: for reminders, remote messages, shortcuts and task or playback status.
- Foreground and background services: to support document tasks, audio playback, file observation and notification features, subject to Android restrictions.
- Wake locks, boot reception and network access: to support active processing or playback, recheck and reschedule applicable background work, and communicate with the connected services described below.
- Billing, install-referrer and advertising-related permissions: for subscriptions, attribution, advertising identifiers and supported Android advertising services.
The current release does not request microphone recording, contacts, SMS, call-log or precise-location access. MP3 playback does not require recording microphone audio. Advertising providers may still infer approximate location from an IP address. You can review and revoke permissions through Android settings. Permissions do not authorize unrelated use of your file contents.
4. Notifications and Messaging
Notifications may include document and conversion reminders, document shortcuts, a saved-PDF count, processing progress and MP3 playback controls.
Reminder eligibility can use locally observed signals such as App foreground/background transitions, leaving the App, screen-on or unlock events, elapsed time, file additions or deletions, and newly detected screenshot files. Locally stored counters, last-reminder type, install age, subscription status, attribution group and remote rules affect selection and frequency. Some configurations may allow notifications while the App is in the foreground. Operating-system restrictions may prevent or delay delivery.
Some reminders may show locally generated image or screenshot previews. Shortcut, reminder or playback information may appear on the lock screen, including a file count, preview or media title, depending on the notification type and your Android settings. People who can see your screen may see this information. Use Android notification and lock-screen controls to limit visibility.
Firebase Cloud Messaging (FCM) and Firebase Installations process installation identifiers, registration tokens, message identifiers, topic subscriptions and technical delivery information. Our code uses Firebase topic registration and does not upload FCM tokens to a separate Beauty Dream Studio token backend. Receiving a message may lead to a local eligibility check and reminder. A notification payload received while the App is in the background may instead be displayed by the Firebase SDK, without passing through the same local reminder-frequency checks. Sound, vibration, banners and grouping depend on the channel, permission and system settings. Receipt does not guarantee visible delivery.
Disabling App notifications or a channel in Android settings controls visible notifications but is not a general opt-out from Firebase technical services, analytics, diagnostics or subscription checks. Clearing a notification is not necessarily the same as disabling the underlying service.
5. Advertising and Privacy Choices
The App uses Google Mobile Ads and AdMob mediation, including Pangle, Unity Ads and Liftoff Monetize (Vungle). Depending on configuration, available inventory and privacy choices, the App may display app-open, interstitial, native or banner advertisements. Not every integrated provider or format is used for every request.
Advertising providers may process IP addresses and approximate location inferred from them; Android Advertising ID, App Set ID or other applicable identifiers; App and SDK versions; device model, operating system, language and network information; ad requests, impressions, views, clicks and attribution information; consent signals; and diagnostic, performance and fraud-prevention information. Processing supports ad delivery, measurement, personalization where permitted, security and fraud prevention. Providers may disclose information to their advertising partners or affiliates under their policies. We do not deliberately provide document contents, recognized text, signatures, PDF passwords or local audio contents to advertising networks.
Google User Messaging Platform (UMP) presents applicable privacy messages and stores choices. When UMP requires a privacy-options entry, Settings → Privacy choices lets you review the available choices. Android also provides advertising-ID controls where supported. Available options depend on region, provider and system settings. There is no separate in-App switch for every ad network. The Pangle integration uses a non-personalized setting when an affirmative personalization decision is unavailable. Permission to request an ad is not, by itself, consent to personalized advertising.
Non-personalized advertising can still involve identifiers, network communication, measurement and security processing. Declining personalization does not necessarily remove advertisements or stop all provider data processing. An active ad-free entitlement, including an eligible activated trial or introductory period, suppresses App-served advertisements; it does not erase previously processed data or disable all connected services.
We do not sell your document contents. Some privacy laws classify certain advertising disclosures as a "sale", "sharing" or targeted advertising even without payment for the data. Where applicable, use the available privacy controls or contact us and the relevant provider to exercise your rights.
6. Analytics, Attribution and Remote Configuration
Firebase Analytics and Amplitude help us assess App use, reliability, retention, acquisition performance, subscriptions and advertising. Events can include launches, page visits, feature entry and exit, task success or failure, coarse input-count and processing-duration measures, permission and reader-guide interactions, subscription-screen and purchase outcomes, notification delivery attempts and clicks, and destination arrival. Advertising events may include format, network, placement, the triggering business-function category, revenue, currency and derived revenue ranges. These categories describe the feature used, not the contents of your document.
Session, task, flow and interaction identifiers associate related events. A pseudonymous analytics user identifier is derived by hashing the Android ID together with the App's package identity using SHA-256. Our code supplies this derived identifier to Firebase and Amplitude rather than sending the original Android ID as that user identifier. It remains a persistent device-related identifier, not anonymous information. Amplitude also uses an installation-related device identifier and session records. The services may process App and device characteristics, language, general country or region and technical connection information according to their configurations and policies.
Our current Amplitude configuration uses its EU server zone, limits automatic capture to application lifecycle events, and disables SDK collection fields for advertising ID, App Set ID, precise coordinates, IP-address event properties, city, region, DMA and carrier. We do not enable session replay or document-screen recording through Amplitude. Disabling an IP-address event property does not prevent a server from receiving the network address needed to handle a connection, and the EU configuration does not mean every other provider stores data in the EU.
Install attribution: Google Play Install Referrer supplies an installation-referral string. Current versions can retain a local snapshot and report the referral string, extracted UTM fields, a valid campaign ID and related technical metadata to analytics. The full string can contain advertising click identifiers or other parameters supplied by the referring campaign. Amplitude can receive the complete value, split into fields when necessary; Firebase receives a length- and field-limited representation. A campaign ID may be associated with later analytics events to measure channel retention and revenue. This differs from earlier versions that only retained a broad attribution category. It does not include document contents, but it is advertising and installation-related information associated with pseudonymous analytics records.
Our custom document-use events are designed to exclude file contents, file names, paths, content URIs, recognized text, search queries, signatures and PDF passwords. The installation-referrer payload described above is a separate attribution data source. System or library exception messages may contain contextual information as explained in Section 7.
Firebase Remote Config supplies settings for features, advertisements, notifications, subscriptions and experiments. It may process installation identifiers, App and SDK information, language, country, time zone and relevant user properties. Local or derived groups can affect feature presentation, reminder frequency or advertising settings. Remote configuration does not upload document contents.
Analytics may be exported to our Google Cloud BigQuery project for the same usage, retention, reliability and revenue analyses. Where Google signals is enabled and permitted by the relevant settings and consent, Google may use eligible signed-in activity for aggregated audience and advertising insights; we do not receive Google account credentials. The App does not currently provide a general user-facing switch that disables every analytics destination. Advertising privacy choices and notification permission should not be understood as such a switch. You may contact us about applicable privacy rights.
7. Crash Diagnostics
Firebase Crashlytics processes technical crash reports such as stack traces, exception messages, installation-related identifiers, device and operating-system characteristics, App version and diagnostic events. We use these to investigate failures and improve reliability. The current App does not provide a separate in-App Crashlytics switch.
We do not deliberately attach documents, images, audio, recognized text, signatures or passwords to crash reports. However, exception messages produced by Android or libraries may contain contextual information such as a local file path. The exclusions applied to custom analytics do not guarantee that every diagnostic message is free of file-related information.
8. Subscriptions and Payments
Google Play processes payment credentials and transactions. We do not receive or store your full payment-card or bank-account details. RevenueCat provides subscription-screen delivery, purchase validation, entitlement checks, restoration and subscription analytics.
Google Play and RevenueCat may process product and offering identifiers, purchase tokens or receipts, purchase history, entitlement status, billing phase, renewal and expiration information, price, currency, transaction metadata and relevant technical information. RevenueCat assigns an App User ID without requiring an App account; this is a pseudonymous identifier, not a guarantee of anonymity. Our code does not deliberately set RevenueCat customer attributes containing your name or contact email.
Local caches help determine subscription status and avoid duplicate purchases. A pending-purchase record can associate a RevenueCat App User ID with a pending product. Local subscription-prompt records may include task and reading counts, timestamps and hashed document identifiers for reading deduplication. Those local document identifiers are not included in our custom analytics events. Clearing App data does not cancel subscriptions or automatically delete transaction records held by providers.
9. Support and User-Selected Destinations
When you choose feedback or a feature request, the App can prepare a message in your selected email or sharing application. It may include your entered text, selected attachments, App version, device model, Android version, screen size, language and time zone. You can review, edit or cancel before sending. We may receive your sender email and information you deliberately include. Do not send passwords or unnecessary sensitive documents.
When you share, export, print through an available system destination, open a file location or choose a cloud document provider, Android and the selected application handle the transferred file, metadata or access permission. App-managed PDFs may be made available through Android's document-provider interface, subject to system access grants. Destination providers can synchronize or retain copies according to their own settings and policies.
10. Purposes and Legal Bases
We use information to provide requested file tools and playback; maintain local preferences and file lists; deliver applicable shortcuts and reminders; display and measure advertising; analyze acquisition, retention and feature performance; validate subscriptions; diagnose failures; prevent fraud and abuse; respond to support requests; and comply with legal obligations.
Where a legal basis is required, it may be performance of the service or contract you request, consent for processing that requires it, legitimate interests in operating, securing and improving the App where those interests are not overridden by your rights, or compliance with legal obligations. We do not treat acceptance of this Policy as consent to all processing. Where processing relies on consent, withdrawal does not affect the lawfulness of processing already completed. Applicable objection and other rights are described in Section 14.
11. Recipients and International Processing
Recipients include:
- Google and its affiliates: advertising and consent services, Firebase, Google Cloud analytics exports, Play Billing, Install Referrer, model delivery and relevant platform services;
- Pangle and the applicable ByteDance/TikTok group entities: advertising, measurement and security;
- Unity Technologies and relevant affiliates: Unity Ads delivery, measurement and security;
- Liftoff and relevant affiliates, including Vungle entities: Liftoff Monetize advertising, measurement and security;
- Amplitude, Inc.: product analytics and attribution analysis;
- RevenueCat, Inc.: subscription processing and analytics; and
- Email, sharing, storage or other destinations you deliberately choose.
We may also disclose information when lawfully required, to protect rights or security, investigate abuse, or carry out a business transfer, with safeguards and notice where required. Providers may operate in countries different from yours, including the United States, countries in Europe and Singapore. Where required, appropriate transfer safeguards must apply, such as applicable adequacy decisions or contractual protections. You may contact us for information about safeguards relevant to your request. A provider's location is not determined by the location of your local files.
12. Storage, Retention and Deletion
Local files and records: App-managed documents, local databases, preferences, cached attribution records, notification counters and other local state remain until removed or updated by the relevant feature, App cleanup, clearing App data or uninstallation. Recycle-bin items are not necessarily deleted when removed from an active list. Temporary files may remain after an interrupted operation until later cleanup. Android backup and device-transfer rules for App-owned documents, databases, preferences and temporary files are disabled in the current release.
Some operations save results directly to shared device storage. PDF-to-image conversion can publish images to the photo gallery. Other results may remain only in the App-managed PDF library until exported. Public copies, external originals and files copied to another provider may remain after clearing App data or uninstalling; delete them separately where appropriate. Uninstallation is not a reliable backup or recovery method, and restoring a subscription does not restore local documents.
Remote records: Analytics, attribution, diagnostics, messaging, advertising and subscription information is retained according to the purposes described here, the relevant service settings, contractual obligations and legal requirements. We retain information under our control only for as long as reasonably needed for those purposes, including investigating problems and fraud, measuring retention, resolving disputes and meeting accounting or legal obligations, and then delete or aggregate it. Analytics exports and support correspondence follow the same necessity-based approach. Provider-controlled transaction, security or backup records may have different retention periods. We do not promise a fixed deletion date for data independently controlled by another provider.
To request deletion of personal information we control, email contact@yuzhensoftware.com. We may need limited information to locate a pseudonymous record and verify your request. We may not be able to identify a record that cannot reasonably be linked to you. Where a provider controls information independently, its request process may also be needed. Clearing local data or disabling notifications does not automatically delete previously transmitted information or cancel a subscription. Legally required retention and valid legal claims may limit deletion.
13. Security
We use reasonable technical and organizational measures, including Android access controls, permission-based file sharing, restricted access to analytics and support records, and encrypted transport for connected services. No device, system or transmission can be guaranteed completely secure. Protect your device, maintain backups and share sensitive files only with trusted destinations. Password-protecting a particular PDF does not mean every local file, cache or exported copy is encrypted.
14. Your Choices and Rights
You can use Android settings to review permissions, manage notification channels and lock-screen visibility, restrict available background activity, and manage advertising identifiers. Where shown, Settings → Privacy choices provides the applicable advertising choices. You can choose individual files and sharing destinations, delete local files, clear App data, uninstall the App, and manage subscriptions through Google Play. Some choices limit the corresponding functionality.
Depending on your jurisdiction, you may have rights to access, correct, delete or receive a copy of personal information; restrict or object to processing; withdraw consent; opt out of targeted advertising, sale or sharing; or appeal a decision and complain to a data-protection authority. Send requests to contact@yuzhensoftware.com with the subject "Privacy Request — All-in-One PDF Viewer & Editor". We will handle requests according to applicable law and will not discriminate against you for exercising a privacy right. Any verification should be proportionate to the request.
15. Children and Accounts
The App is intended for adults aged 18 and over and is not designed or promoted for children. We do not knowingly seek personal information from children. If you believe a child has provided information to us, contact us so that we can investigate and take appropriate action.
The App does not create a Beauty Dream Studio account or require App sign-in. This does not make SDK identifiers or subscription records anonymous. Google Play purchases remain associated with the applicable Google Play account. Privacy requests can be made by email without creating an App account.
16. Provider Information
Google Privacy Policy: https://policies.google.com/privacy
Google Mobile Ads data disclosure: https://developers.google.com/admob/android/privacy/play-data-disclosure
Firebase privacy and security: https://firebase.google.com/support/privacy
Pangle regional privacy policies: https://www.pangleglobal.com/privacy
Unity Game Player and App User Privacy Policy: https://unity.com/legal/game-player-and-app-user-privacy-policy
Liftoff Privacy Policy: https://www.liftoff.ai/privacy-policy/
Amplitude privacy information: https://amplitude.com/privacy
Amplitude security and privacy information: https://amplitude.com/security-and-privacy
RevenueCat Privacy Policy: https://www.revenuecat.com/privacy
Provider documentation describes broader services and does not mean the App enables every feature a provider offers. This Policy describes the App's use of those services.
17. Changes and Contact
We may update this Policy when features, integrations, data practices or legal requirements change. We will revise the date and provide notice or obtain consent where required. Updating this Policy does not replace any required in-App disclosure or permission request.
For privacy questions, requests or complaints:
Beauty Dream Studio
Email: contact@yuzhensoftware.com
Privacy Policy: https://pdf.yuzhensoftware.com
Terms: https://pdf.yuzhensoftware.com/terms
This Policy explains our data practices and does not limit rights granted by applicable law.