Privacy Policy

How Pagelark collects, uses, and protects your information.

Effective date: September 12, 2026 · Application: Pagelark (com.pagelark.reader) · Developer: NetSoftTouch

Summary: Pagelark is designed with an on-device first architecture. Your documents, scanned texts, and reading files are processed entirely on your device. We do not operate a user account system, and your document content is never uploaded to any remote server or shared with third parties.

1. Information We Do NOT Collect

To ensure complete privacy for your reading materials:

Document Content & Text: All files you open or import (PDF, EPUB, DOCX, TXT), clipboard text you paste, and physical pages you scan are parsed, stored, and rendered strictly on your local device.
Text-to-Speech Audio: Voice synthesis is generated locally using your device's built-in Text-to-Speech (TTS) engine (such as Google Text-to-Speech). Speech audio is never streamed to or stored on external cloud servers.
User Accounts & Profiles: Pagelark does not require registration, login, email address, password, or profile creation.
Reading Habits & Search Queries: Your bookmarks, reading progress, playback speeds, and document search queries remain solely in your device's private local database (Room / SQLite).

2. Information Collected and Third-Party Services

Pagelark uses selected standard third-party services for advertising, payment processing, and application stability. These services may collect technical information as outlined below:

A. Advertising (Google AdMob)

The free version of Pagelark displays advertisements served by Google AdMob. To provide relevant ads and prevent fraud, Google Mobile Ads SDK may collect and process:

Device identifiers (such as the Google Advertising ID / GAID).
IP address and coarse (approximate) location.
Ad interaction data (impressions, clicks, and ad performance diagnostics).

Consent Management (EEA, UK, Switzerland, and US State Laws): We implement the Google User Messaging Platform (UMP) SDK. Users in covered jurisdictions are prompted on first launch to make their choices regarding personalized advertising, cookies, and device identifiers. You can change or withdraw your consent at any time inside the app via Settings → Privacy & telemetry → Privacy Options (Ad Consent).

Ad-Free Option: Users who upgrade to Pagelark Pro will have all advertising completely disabled, and no ad requests are made to AdMob.

B. Anonymous Analytics (Firebase Analytics)

We use Google Firebase Analytics to collect aggregated, non-personally identifiable usage statistics (such as screen navigation, general feature usage, and session duration) to help us understand app performance and improve user experience.

Strict Privacy Guarantee: Analytics events never include document text, document titles, file names, file paths, URIs, search terms, or personal identifiers.

You can disable anonymous analytics at any time by selecting DON'T SHARE under Settings → Privacy & telemetry.

Consent before collection, where consent is required. If you are in the EEA, the UK or Switzerland, analytics and crash reporting are switched off and collect nothing unless and until you choose SHARE under Settings → Privacy & telemetry. Answering the advertising consent form does not switch them on — advertising and analytics are separate purposes, and the form covers only the first.

Elsewhere, anonymous analytics and crash reporting start enabled and you may turn them off at any time in the same place. In every region, both are held off at app startup until the applicable rule has been determined, so nothing is collected before that point.

C. Crash Diagnostics (Firebase Crashlytics)

To diagnose and fix unexpected errors and crashes, Pagelark uses Firebase Crashlytics. When a crash occurs, Crashlytics collects technical diagnostics including device model, operating system version, memory state, and stack traces.

Crash logs contain only software execution stack traces and never contain your document content or personal data. Crash reporting is governed by the same single choice as analytics, described in Section 2B above — including being switched off by default where consent is required — and you can toggle it off at any time by selecting DON'T SHARE under Settings → Privacy & telemetry.

D. In-App Purchases (Google Play Billing)

If you purchase or subscribe to Pagelark Pro, the transaction is processed securely through Google Play In-App Billing. NetSoftTouch does not receive, store, or have access to your credit card, bank account, or billing details. All financial transactions are managed entirely by Google according to the Google Play Terms of Service.

For more details on how Google collects and uses information when you use apps integrated with Google services, please review How Google uses information from sites or apps that use our services and the Google Privacy Policy.

3. Web Articles and Network Requests

Pagelark makes network requests only for the following explicit purposes:

User-Initiated Article Fetch: When you share or paste a web article URL to read, the app makes a direct HTTP request to download the HTML content from that specific web page to parse the article text. No personal identifiers or other documents are sent.
Ad Serving & Telemetry: Communicating with Google AdMob and Firebase as described above.
Billing Verification: Verifying Pro entitlements with the Google Play Store.

4. Device Permissions and Why They Are Needed

Pagelark requests only the minimum permissions necessary for its functionality:

android.permission.INTERNET: Required for fetching web articles, displaying ads (free version), verifying Pro purchases, and transmitting crash/analytics diagnostics.
android.permission.CAMERA: Required solely when you choose to use the Camera OCR feature to extract text from a physical document via on-device ML Kit text recognition. Camera frames are processed in temporary memory and never stored or uploaded. This feature is optional.
android.permission.POST_NOTIFICATIONS & android.permission.FOREGROUND_SERVICE_MEDIA_PLAYBACK: Required on Android 13+ to show media player controls in the notification drawer and lock screen during background playback.
android.permission.WAKE_LOCK: Prevents the device from sleeping while reading audio is actively playing.
Storage / Document Access: Pagelark uses the standard Android Storage Access Framework (SAF) system picker, allowing you to select specific files without granting the app broad access to your entire storage.

5. Children's Privacy (COPPA Compliance)

Pagelark is not directed at children under the age of 13 (or under 16 in the European Economic Area). We do not knowingly collect or solicit personal information from children. If you believe a child has provided us with personal information, please contact us at nguyenminhthuanvnn@gmail.com so we can take immediate corrective action.

6. Data Retention and Deletion

Because your reading data and documents are stored exclusively on your local device:

You can delete any document from the Pagelark library at any time within the app.
Clearing the app's data in Android Settings or uninstalling Pagelark will permanently remove all locally stored documents, reading progress, and settings from your device.

7. Your Privacy Rights (GDPR & CCPA/CPRA)

Depending on your location, you may have statutory rights regarding your personal information, including the right to access, rectify, delete, or restrict the processing of your data, and the right to opt out of targeted advertising. You can exercise these rights via the in-app privacy controls (Settings → Privacy & telemetry) or by contacting us.

8. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated effective date. We encourage you to review this page periodically.

9. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy or Pagelark, please contact us at:

Developer: NetSoftTouch
Email: nguyenminhthuanvnn@gmail.com
Website: https://nguyenminhthuanvnn.github.io/pagelark/