PRIVACY POLICY PDF Reader: PDF Viewer

 PRIVACY POLICY

====================================


Privacy Policy  

App: PDF Reader: PDF Viewer  

Developer / Publisher: [SongNamLabs]  



====================================

1. INTRODUCTION

====================================


This Privacy Policy explains how PDF Reader: PDF Viewer handles information when you use the Android app. The app is designed to open PDF files selected by you through the Android system document picker, render pages on your device, remember recent documents, save bookmarks, and provide app settings. The app includes Google advertising and consent SDKs, so some advertising-related data may be processed by Google services when consent and regional rules allow it.


====================================

2. INFORMATION WE COLLECT

====================================


#Automatically Collected Data Via Detected SDKs


The codebase includes Google Mobile Ads SDK and Google User Messaging Platform. These SDKs may process advertising identifiers, device information, app interactions, diagnostics, approximate location, and consent signals depending on device settings, region, Google SDK behavior, and the consent choices shown to the user.


Evidence:

- app/build.gradle.kts: play-services-ads, user-messaging-platform

- ads/AdConsentManager.kt: UserMessagingPlatform.requestConsentInfoUpdate and loadAndShowConsentFormIfRequired

- ads/BannerAdView.kt: AdView and AdRequest

- ads/AdManager.kt: InterstitialAd.load


#Data Stored Locally


The app stores the following information locally on the device:


- Recent PDF metadata: display name, content URI, file size, page count, last opened page, last opened time, created time, favorite flag.

- Bookmark metadata: document ID, page number, optional note field, created time.

- Settings: theme mode, default view mode, keep-screen-on preference, recent sort mode, ad consent completion flag, opened document count, first launch/open time.


Evidence:

- data/database/PdfDocumentEntity.kt

- data/database/PdfBookmarkEntity.kt

- data/preferences/PreferencesRepository.kt


#Data Not Collected By The App Code


Based on the codebase scan, the app does not create accounts, collect names, collect email addresses, collect passwords, collect contacts, request location permission, request camera permission, request microphone permission, or upload PDF document contents to an app-owned server. PDF files are opened through Android's document picker and rendered locally using Android PdfRenderer.


====================================

3. PERMISSIONS USED

====================================


| Permission | Why Needed | Data Collection Involved? |

|---|---|---|

| android.permission.INTERNET | Required by Google ads and consent SDKs to request ads and consent information. | Yes, third-party ad/consent SDK processing may occur. |

| android.permission.ACCESS_NETWORK_STATE | Allows ad SDKs to check network availability before requesting ads. | No direct app content collection; supports ad network behavior. |

| com.google.android.gms.permission.AD_ID | Added by Google Mobile Ads in the merged manifest for advertising ID access. | Yes, advertising ID may be processed by Google SDKs. |

| android.permission.ACCESS_ADSERVICES_AD_ID | Added by Google ad/privacy sandbox libraries in the merged manifest. | Verify manually in Play Console and Play SDK Index. |

| android.permission.ACCESS_ADSERVICES_ATTRIBUTION | Added by Google ad/privacy sandbox libraries in the merged manifest. | Verify manually in Play Console and Play SDK Index. |

| android.permission.ACCESS_ADSERVICES_TOPICS | Added by Google ad/privacy sandbox libraries in the merged manifest. | Verify manually in Play Console and Play SDK Index. |

| android.permission.WAKE_LOCK | Added by a dependency in the merged manifest; app settings also include a keep-screen-on UI using window flags. | No personal data collection. |

| android.permission.FOREGROUND_SERVICE | Added by a dependency in the merged manifest, likely through AndroidX WorkManager transitively used by Google/AndroidX libraries. | No app-defined foreground service found; verify if Play Console flags it. |


The app does not request broad storage permission. PDF access is handled by Android's system document picker.


====================================

4. THIRD-PARTY SERVICES

====================================


| SDK | Data Collected | Purpose | Privacy URL | Compliance Basis |

|---|---|---|---|---|

| Google Mobile Ads SDK / AdMob | Advertising ID, app interactions, diagnostics, device information, approximate location depending on settings and consent. | Display banner and interstitial ads. | https://policies.google.com/privacy and https://policies.google.com/technologies/ads | Consent flow via UMP where required; app uses Google ad SDK. |

| Google User Messaging Platform | Consent status, region/consent information needed to show privacy forms. | Collect and manage ad personalization consent choices. | https://policies.google.com/privacy | Consent management for ad requests. |

| AndroidX Room | Local database rows for recent PDF metadata and bookmarks. | Local app functionality. | https://developer.android.com/jetpack/androidx/releases/room | Local-only storage in app database. |

| AndroidX DataStore | Local preference values such as theme and reading settings. | Local settings functionality. | https://developer.android.com/topic/libraries/architecture/datastore | Local-only storage in app preferences. |


====================================

5. DATA RETENTION

====================================


Recent document metadata, bookmarks, and settings remain on the user's device until the user clears recent files, removes items, uninstalls the app, or the Android system removes app data. The app does not operate a backend account system. Advertising and consent data handled by Google SDKs follow Google's own retention practices and user consent settings.


====================================

6. DATA SHARING

====================================


The app code does not upload PDF contents to a developer-controlled server. Advertising and consent SDKs may transmit advertising, diagnostics, device, consent, and interaction data to Google services for ad delivery, measurement, fraud prevention, and consent management. When the user chooses the Share action, Android opens a share sheet and the selected external app receives the PDF URI or app text chosen by the user.


====================================

7. USER RIGHTS & CONTROL

====================================


#United States: CCPA/CPRA


California users may have rights to know, access, delete, correct, and opt out of certain sharing or sale of personal information. This app does not sell account data and does not maintain user accounts. Advertising personalization choices may be controlled through the consent form, Android settings, and Google ad settings where applicable.


#EEA: GDPR


Users in the European Economic Area may have rights to access, rectify, erase, restrict, object to processing, and withdraw consent. The app uses Google User Messaging Platform to request and manage consent for advertising where required.


#UK: UK GDPR


UK users may have rights similar to GDPR rights, including access, rectification, erasure, restriction, objection, and consent withdrawal.


#Indonesia: Personal Data Protection Law


Users in Indonesia may request information about relevant data processing and request correction or deletion where applicable. The app stores recent document metadata and bookmarks locally; users can clear local history in Settings or remove app data through Android settings.


====================================

8. CHILDREN'S PRIVACY

====================================


The app is not designed for children as a primary audience. The app does not knowingly collect account information from children. The advertising consent request is configured with setTagForUnderAgeOfConsent(false), based on the current codebase. If the distribution target changes to children or families, the Play Families policy and ad configuration must be reviewed before release.


====================================

9. ACCOUNT DELETION

====================================


The app does not create user accounts. Account deletion is not applicable. Users can clear local recent-file history in Settings, remove bookmarks, uninstall the app, or clear app storage from Android system settings.


====================================

10. SECURITY

====================================


The app stores recent document metadata, bookmarks, and settings in local Android app storage. PDF files stay in their original device location unless the user shares them. Network communication is limited to Google advertising and consent SDKs detected in the codebase. No method of storage or transmission is completely risk-free, but the app avoids collecting account credentials or uploading PDF contents to an app-owned server.


====================================

11. CHANGES TO THIS POLICY

====================================


This policy may be updated when the app changes features, permissions, SDKs, or data handling practices. The updated version should be published at the same Privacy Policy URL used in Google Play Console.


====================================

12. CONTACT US

====================================


Developer / Publisher: [SongNamLabs]  

Email: [makando991@gmail.com]


Postingan populer dari blog ini

Privacy Policy

Privacy Policy Scanly

Privacy Policy