← MIYGAL STUDIO
Privacy Policy
MiygaL PDF: Offline Reader /// Productivity /// Live
MiygaL PDF
Developer: MiygaL Studio
Version: 2.1.0
Effective Date: November 1, 2026
Contact: miygal.connect@gmail.com
1. Introduction
This Privacy Policy describes how MiygaL PDF ("the App"), developed by MiygaL Studio ("we," "our," or "us"), accesses, collects, uses, and protects information when you use our mobile application on Android and iOS. We are committed to complete transparency and absolute user privacy.
The App is built on a strict local-only architecture. It operates without backend servers, without user accounts or registrations, and without any analytics, telemetry, or crash-reporting SDKs. All data created, accessed, or stored by the App remains exclusively on your physical device and is never transmitted to MiygaL Studio or any external party, except for native in-app billing transactions processed directly by Google Play or Apple App Store as detailed in Section 5.
2. Data the App Accesses and Stores Locally
The App processes and stores the following categories of data on your device only. None of this data is ever transmitted off your device or accessible to MiygaL Studio.
2.1 PDF Files and Document Content
- What is accessed: When you open a PDF document, the App reads the file directly from your device's storage (or authorized folders on iOS). When you annotate, fill forms, highlight text, sign, or modify a document, the App writes changes back to your local file upon your instruction. When using tools such as Organise, Merge, Split, or Smart Compress, the App creates temporary working copies in your device's local cache directory before presenting or saving the final file.
- Why it is accessed: To render, view, annotate, edit, reorganize, merge, split, and compress PDF documents as requested by you.
- Where it is stored: In your device's local storage in the location you originally chose, or within the App's temporary internal cache. Files are never uploaded to cloud servers or remote databases.
2.2 PDF Passwords (Secure Password Vault)
- What is collected: If you choose to enable "Remember Password" for a password-protected PDF, the App saves the password you entered for that document.
- Why it is collected: To auto-unlock password-protected files on future visits via biometric authentication (fingerprint or face unlock) or device PIN, eliminating repetitive manual password entry.
- How it is encrypted and stored: Passwords are encrypted using hardware-backed AES-256 encryption via the Android Keystore System (on Android) or Apple Keychain (on iOS). They are accessible only after successful device authentication.
- How long it is kept: Stored passwords remain in your secure vault until you individually delete them in Settings -> Manage Vault, clear them using the "Wipe Vault" option, or uninstall the App.
- Sharing: Saved passwords never leave your device and are never shared with anyone, including MiygaL Studio.
2.3 Saved Signatures (Secure Signature Vault)
- What is collected: When you draw a handwritten signature using the signature canvas or import an image signature and choose to save it, the App stores the signature graphic.
- Why it is collected: To allow you to reuse your digital signature across multiple documents and contracts with one tap, without redrawing or re-importing each time.
- How it is encrypted and stored: Signature entries are stored securely in hardware-backed encrypted local storage (Android Keystore System or Apple Keychain).
- How long it is kept: Signatures remain stored until you delete them individually in Settings -> Manage Vault -> Signatures, clear all saved signatures, or uninstall the App.
- Sharing: Saved signatures are strictly confined to your device and are never transmitted to external servers.
2.4 PDF Curator & Smart Collections (On-Device Categorization)
- What is accessed and stored: The App maintains category associations (such as Invoices, Bills, Tax, Identity, Medical, Receipts, and user-defined tags) to help organize documents.
- Why it is accessed: To power the PDF Curator feature, which groups related documents into convenient smart collections and suggests relevant categories.
- How it is processed: Categorization is calculated 100% on-device using local categorization rules and document attributes (with document text evaluated only if Content Search consent is explicitly granted). No cloud AI, no external machine learning APIs, and no remote language models are used.
- Where it is stored: Metadata tags and category mappings are stored in a private local database on your device.
2.5 Bookmarked Documents (Offline Private Library)
- What is accessed and stored: If you enable the "Secure Bookmarked Files" option in Settings, the App creates a secure, sandboxed local copy of your bookmarked PDF documents within the App's private internal storage directory.
- Why it is accessed: To ensure your essential documents remain intact and accessible in your private offline library, even if the original file is deleted or cleared from external folders (e.g., Downloads or messaging app caches).
- Where it is stored: In the App's isolated sandbox storage on your device.
- How long it is kept: Saved copies remain until you un-bookmark the document, delete it from the library, clear sandbox storage, or uninstall the App.
2.6 Deep Search Index (Content Search & User Consent)
- What is accessed and stored: If you explicitly enable Content Search in Settings, the App extracts textual content from your PDF documents and builds a local search index.
- User Consent & Control: Content Search is disabled by default until you grant consent in Settings or during search setup. You can toggle Content Search on or off at any time, or clear the search index immediately.
- Why it is accessed: To enable full-text "Deep Search," allowing you to find documents based on words and phrases inside the text of your PDFs across your library.
- Where it is stored: In a private, local search database index on your device. The extracted text is never sent off your device.
- How long it is kept: Until you tap "Clear Search Index" in Settings, clear app data, or uninstall the App.
2.7 File History and Usage Records
- What is collected: A local list of recently opened files, including file names, file paths, last-opened timestamps, page counts, and basic viewing statistics.
- Why it is collected: To display your Recent Files on the home screen, restore your reading position, and provide quick navigation.
- Where it is stored: In the local application database on your device.
- How long it is kept: Until you clear your history in Settings, until older records are automatically pruned according to your recent file limit, or until you uninstall the App.
2.8 Free Tier, Pro Passes, and Entitlement State
- What is accessed and stored: To manage free tier allowances and Pro upgrades (such as the Pre-paid 1-Month Pass and Lifetime Pro Access), the App stores local entitlement status, expiration dates, and activation timestamps.
- Why it is accessed: To validate Pro features locally without requiring remote user logins or account servers.
- Where it is stored: Entitlement state is stored in secure local storage protected by the device operating system's security architecture.
- Sharing: Entitlement data is strictly verified through native store APIs (Google Play Billing / Apple StoreKit) and is never transmitted to MiygaL Studio servers.
2.9 User Preferences and Settings
- What is collected: Local application settings such as App Lock preference, Session Timeout, Screen Security toggle, Content Search consent, Device Scan toggle, and language preferences.
- Where it is stored: In secure local storage and shared preferences on your device only.
2.10 Exported Image Files (Export to Image Tool)
- What is accessed: When you export PDF pages as images (JPEG, PNG, or ZIP), the App renders the pages locally using your device's graphics processor.
- Where it is stored: Temporary rendered images are written to your device's temporary cache directory and deleted when no longer needed or when system maintenance runs.
- Saving & Sharing: If you tap "Share," files are handed over to the OS Sharesheet. If you tap "Save," files are written directly to your chosen destination via the native system file picker.
3. Device Features and Permissions the App Uses
3.1 Biometric Authentication (Fingerprint & Face Unlock)
- Why it is used: To verify your identity before opening the App (when App Lock is enabled) or accessing credentials in the Secure Vault.
- Privacy Safeguard: The App never accesses, collects, or stores your biometric templates. Biometric authentication is handled entirely by the device operating system, which returns only an authenticated or unauthenticated result to the App.
- Permissions:
android.permission.USE_BIOMETRIC (Android) or NSFaceIDUsageDescription (iOS).
3.2 Storage & Folder Access
- Android (
MANAGE_EXTERNAL_STORAGE / All files access):
As a document management and PDF utility application, broad storage access is essential to discover, read, annotate, organize, and save PDF files located across your device's storage. Operating directly on existing files prevents unnecessary file duplication that wastes device storage.
- Why Storage Access Framework (SAF) is insufficient: SAF requires manual file-by-file or directory-by-directory user selection prompts every time a file is accessed, making seamless whole-device PDF library discovery and batch organization impossible.
- Why MediaStore API is insufficient: MediaStore focuses on photos, videos, audio, and the Downloads folder. It does not provide the broad access required to discover and manage PDF documents organized in diverse or custom folders across device storage.
- iOS (Folder Access & Security-Scoped Bookmarks):
On iOS, the App uses Apple's native Document Picker to allow users to select specific folders. The App uses Security-Scoped Bookmarks to retain authorized access to user-selected folders across app restarts, without requiring broad file system access.
- Absence of Internet Permission:
The Internet permission (android.permission.INTERNET) is completely excluded from the application manifest in production releases. On iOS, the App declares no network capabilities. The App cannot establish network connections in production releases.
3.3 Camera and Photo Library Access (Image & Signature Import)
- Why it is used: When adding an image annotation or importing an existing signature into a PDF, you may choose to take a photo using the device camera or select an image from your photo library.
- Permissions:
NSCameraUsageDescription and NSPhotoLibraryUsageDescription (iOS).
- Data handling: Selected images are processed and cropped strictly on-device, embedded into the target PDF, and are never uploaded or shared externally.
3.4 Screen Security & Window Privacy Protection
- Why it is used: When Screen Security is enabled in Settings, the App activates OS-level window privacy protection (
FLAG_SECURE on Android and privacy window masking on iOS).
- Privacy Safeguard: This prevents unauthorized screen captures, screen recordings, and conceals document contents in the device's Recent Apps / App Switcher view.
3.5 File Sharing
- Why it is used: When you tap "Share," the App passes the document to the system's native sharing mechanism (Android Sharesheet or iOS
UIActivityViewController) to send the file to an app you select (such as Email or messaging apps).
- Data handling: MiygaL Studio receives no copy of shared files. Delivery is handled entirely by the operating system.
3.6 In-App Review Prompt
- Why it is used: After significant usage milestones, the App may display the standard Google Play In-App Review dialog (Android) or StoreKit
requestReview dialog (iOS).
- Data handling: The App receives no information about whether you submitted a rating or review. All interaction occurs within the native app store framework and is governed by Google's or Apple's Privacy Policy.
3.7 System Time Verification (Android only)
- Why it is used: To verify local trial durations and license validity offline without relying on remote network time servers.
- Data handling: The App checks local system time configuration. No time, timezone, or location data is recorded, profiled, or transmitted.
3.8 Installation Lifecycle Verification (Android only)
- Why it is used: To determine local trial eligibility following a fresh installation or app update.
- Data handling: The App verifies standard local package installation timestamps in real time. These timestamps are evaluated ephemerally in memory and are never stored permanently or transmitted.
3.9 Play Store In-App Updates (Android only)
- Why it is used: To inform you when an update is available via the Google Play In-App Updates API.
- Data handling: The App does not connect to the internet directly. It queries the local Google Play Store service already present on your device. Any download traffic is handled securely by Google Play.
4. Data We Do Not Collect
To be completely explicit, MiygaL PDF and MiygaL Studio do not collect, transmit, store, or sell:
- Personal identifiers (name, email address, phone number, physical address).
- Account credentials or passwords.
- Location data or IP addresses.
- Analytics or usage metrics (no Google Analytics, no Firebase, no Mixpanel).
- Crash reports or diagnostics (no Crashlytics, no Sentry, no bug loggers).
- Advertising identifiers or profile data (no AdMob, no Meta Audience Network).
- The contents, text, or images of your PDF files.
- Decrypted password vault or signature vault data.
5. Third-Party Services
The App interacts with only one third-party service: official platform app store billing.
5.1 Google Play Billing and Apple App Store (StoreKit)
The App offers optional in-app purchases and passes for Pro features (e.g., Pre-paid 1-Month Pass, Lifetime Pro Access, and legacy subscription restoration).
- How purchases are handled: All transactions are processed directly by Google Play Billing (Android) or Apple StoreKit (iOS).
- Data received by MiygaL Studio: None. MiygaL Studio does not operate payment servers and never receives your credit card details, billing address, or payment credentials.
- Local purchase tokens: The App receives a cryptographic purchase token from Google Play or Apple on your device to unlock Pro features locally.
- Third-Party Privacy Policies:
5.2 Terms of Use (EULA)
6. Children's Privacy
Because the App operates on a local-only architecture with zero data collection, no network transmission, and no advertising, it is entirely safe for users of all ages and complies fully with the Children's Online Privacy Protection Act (COPPA) and GDPR Article 8. If you have any inquiries, contact us at miygal.connect@gmail.com.
7. Your Privacy Rights and Data Control
Because MiygaL Studio never receives, stores, or processes any of your personal data on remote servers, your statutory privacy rights under GDPR, CCPA/CPRA, DPDP Act 2023, and similar international laws are satisfied directly through native in-app controls.
7.1 Right of Access
All data stored by the App resides directly on your own device. You can view your document history, category labels, stored signatures, and active preferences directly within the App's user interface at any time.
Note regarding saved PDF passwords: For maximum security, saved passwords cannot be viewed in plain text. Passwords are hardware-encrypted by the Android Keystore System or Apple Keychain and can only be used by the App to unlock files upon authentication.
7.2 Right to Erasure (Right to be Forgotten)
You have absolute, immediate control to permanently delete all data stored by the App:
- Delete specific or all saved passwords: Open Settings -> Manage Vault -> Passwords to delete credentials individually, or select "Wipe Vault" to permanently erase all saved passwords.
- Delete specific or all saved signatures: Open Settings -> Manage Vault -> Signatures to delete signatures individually or clear all saved signatures.
- Clear Search Index: Open Settings -> Manage Content Search and tap "Clear Search Index" to delete all extracted text and search data.
- Clear File History: Open Settings and clear your document history and temporary file associations.
- Delete Bookmarked Library Copies: Un-bookmark files or clear offline library storage in Settings.
- Clear All App Data (System Settings): In Android or iOS device settings, clearing the App's data will immediately delete all local databases, vaults, indexes, and preferences.
- Uninstall the App: Uninstalling the App removes all internal databases, vaults, caches, and sandbox copies from your device.
7.3 Right to Data Portability
All your original PDF files remain in your device storage and are in your full possession. Exported images and modified PDFs can be saved to any location on your device or shared via the OS Sharesheet. Hardware-encrypted vault entries are cryptographically bound to your specific physical device security module and cannot be exported to another device, ensuring maximum credential protection.
7.4 Applicable Global Privacy Regulations
The architecture of MiygaL PDF inherently complies with:
- GDPR (European Union): Article 25 (Privacy by Design and by Default) and Article 5 (Data Minimization).
- CCPA / CPRA (California, USA): No sale or sharing of consumer personal data.
- DPDP Act 2023 (India): Strict purpose limitation and local data fiduciary containment.
- COPPA (USA): Zero personal data collection from children.
- Australian Privacy Act 1988 & Singapore PDPA 2012.
8. Data Security
The App protects your local data using industry-leading technical measures:
- Hardware-Backed AES-256 Encryption: Saved passwords and signatures are encrypted with AES-256 keys backed by the Android Keystore System or Apple Keychain.
- Biometric & PIN Gating: Access to stored credentials and app features is protected by your device's biometric authentication or PIN.
- Screen Security Protection: Optional window privacy masking blocks screen recording, screen capture, and recent app switcher previews.
- No Internet Permission: Production builds have the
INTERNET permission removed, making unauthorized remote data transmission technically impossible.
9. Changes to This Privacy Policy
We may update this Privacy Policy from time to time to reflect new features or platform requirements. When updates occur, the Effective Date and Version at the top of this document will be updated. We encourage you to review this policy periodically.
10. Contact Us
If you have questions, feedback, or concerns regarding this Privacy Policy or our privacy practices, please contact us: