Privacy Through On-Device Architecture
Many document applications advertise privacy while routinely uploading documents, user identifiers, and device telemetry to remote cloud servers. Their business models often center on cloud subscriptions, account registrations, and behavioral tracking.
MiygaL PDF follows a different model: Zero-Cloud Architecture.
Architectural Breakdown: On-Device Safeguards
The following safeguards ensure that your private documents remain strictly on your physical phone:
1. Zero Network Permissions for Document Processing
In the production Android build, the android.permission.INTERNET permission is omitted for core document processing. Android enforces permissions at the operating system level, ensuring the app cannot initiate network connections to transmit document data or telemetry.
2. Hardware-Backed On-Device Security
Sensitive user credentials—such as remembered PDF passwords and digital signatures—are encrypted using AES-256 encryption via the Android Keystore System (flutter_secure_storage). Encryption keys reside in your device's hardware security module (such as a Trusted Execution Environment or StrongBox keymaster where supported) and are accessible only after successful local biometric authentication.
3. Local Databases & Zero Third-Party Telemetry
Reading history, Smart Label tags, bookmarks, and full-text search indexes reside strictly in local SQLite and Hive database files inside the private app sandbox. No analytics or tracking SDKs (such as Firebase Analytics or commercial ad trackers) are embedded in the application.
4. In-Place File Access via Android SAF
MiygaL accesses documents directly in their original storage folders using Android's native Storage Access Framework (SAF) and ContentResolver. It does not copy or duplicate your files into a proprietary cloud repository.
5. Document Processing vs. Platform Store Services
To maintain complete clarity:
- Document Processing: 100% offline and on-device. No document content, passwords, or search queries ever leave your phone.
- Platform Store Services: When purchasing Pro access, transactions are processed directly by official Google Play Billing APIs under Google's standard billing framework. MiygaL Studio does not collect, receive, or store your payment card numbers, billing addresses, or bank details.
Product Page Summary vs. Architecture Guide
| Scope | Product Page Privacy Section | Dedicated Privacy Architecture Guide |
|---|---|---|
| Purpose | High-level summary of privacy commitments | In-depth technical explanation of system architecture |
| Audience | General users seeking trust and clarity | Security, legal, and privacy-conscious professionals |
| Coverage | Core promises: no ads, no accounts, offline | Manifest permissions, Keystore encryption, SAF, local databases |
| Verification | Simple feature highlights | Threat model, permission disclosures, and storage architecture |
User Perspective Use Cases
1. Legal Counsel & Compliance Officers
Reviewing privileged client communications, contracts, and regulatory filings under professional confidentiality obligations without third-party data processor exposure.
2. Medical Practitioners & Patients
Reading medical histories, diagnostic imaging reports, and lab results without transmitting patient data to external servers.
3. Financial Professionals & Executives
Protecting wealth management statements, tax returns, and strategic documents from cloud data breaches and credential stuffing attacks.
Capability Comparison: Document Security Models
| Security Dimension | MiygaL PDF (Offline On-Device) | Cloud-Tethered PDF Suites | Free Online Web Tools |
|---|---|---|---|
| Document Processing | 100% On-device CPU/GPU | Processed on cloud servers | Processed on cloud servers |
| Internet Permission | Omitted in manifest | Granted by default | Web browser connection |
| User Accounts | Zero accounts / No login | Required email / OAuth | Optional or required |
| Telemetry & Analytics | Zero tracking SDKs | Usage analytics SDKs | Ad network trackers |
| Credential Protection | Android Keystore (AES-256) | Server-side database encryption | Server storage |