Ongle Privacy policy
2026-10-20 · Android / iOSAndroid edition
The Android app has no internet permission and does not automatically send documents or personal data to developer servers. It has no accounts, advertising, analytics or tracking SDKs. User-selected documents are read and converted on the device.
Recent documents, access information, reading positions, bookmarks, settings, converted PDF/table/image files and preview caches are stored locally. Optional form autofill stores the name, phone number, birth date, email and address entered by the user locally for that feature. Use the available history/cache controls and profile editing, or clear app data, to manage local information. Exported files must be managed at their saved location.
Sharing, copying and opening external links happen at the user's request. An optional issue report previews the issue description, document format and page count, app/engine/OS versions and error details before handing them to a user-selected app. The original document is included only when the user opts to attach it. Transmission and file provider or receiving-service processing follow their policies.
Email addresses, messages and optional attachments received by support are used only for troubleshooting and responses, and deleted when no longer needed. Contact: h1.soft.x001@gmail.com. We update this policy and store disclosures if data practices change.
iOS privacy policy
The Ongle iOS app does not collect or transmit documents or personal data to developer servers. It has no accounts, analytics or tracking SDKs. Recent files, reading positions, settings and conversion results are stored on your device. You can clear recent history and cache in app settings. System backups and iCloud files follow your Apple settings and chosen file provider's policy. Sharing, copying and opening external links happen at your request and follow the receiving service's policy. Email enquiries disclose the sender address and message to support; we use them only to respond and delete them when no longer needed. We will update this policy and the store disclosures if data practices change.