Privacy Policy

1. On-device processing and information you choose to send

Mihiraki: PDF Utility processes PDFs on your device. The app does not automatically upload PDF contents, diagnostics or logs to the developer. Source PDFs, working copies, settings and logs may be stored locally for the features you use.

You may choose to copy diagnostics, share logs with another app or submit a support report. Information you send can be received by your selected destination and, for reports to this project, by the developer. Review the content and recipient before sending.

2. In-App Purchases

This app includes optional in-app purchases (tipping) to support development. These transactions are handled exclusively by the Google Play Billing system. We do not have access to your payment details (such as credit card numbers).

3. Permissions

The app uses files you select to open, edit, save and export PDFs. It may retain a local copy of the last successfully opened source PDF to reopen after restarting. Unsaved edits and Undo history are not automatically saved. Sample downloads connect to GitHub, which handles connection data under its own policies.

4. Changes to This Policy

We may update our Privacy Policy from time to time. You are advised to review this page periodically for any changes.

5. Local logs and support copies

Local logs use a 24-hour cleanup threshold. Cleanup runs when the relevant logging functions run, using entry timestamps or file modification times. It does not guarantee deletion of every entry exactly 24 hours after creation, especially while the app is not running.

Local cleanup does not delete submitted reports, exported copies or copies held by other apps, service providers or backups. Their retention and deletion are separate.

For support copies managed by the developer, the deletion target is 90 days after the case is closed. Unnecessary copies are removed earlier. Open cases and limited exceptions are reviewed weekly. This target does not automatically delete public GitHub Issues or every external copy and backup.

6. Support reports and public posts

Send only what is needed to explain the problem. Support information received by the developer is used to answer the request and investigate the issue. Names, account handles, message bodies and attachments are not routinely copied into a separate tracking sheet. Where tracking is needed, keep only a case ID, issue link, dates, status and deletion record.

GitHub Issues are public. Profile information, posts and attachments are handled under GitHub policies. Editing or deleting your own comments is different from deleting an entire issue, which requires the repository owner or an authorized administrator.

To request removal of information in a report to this project, contact the developer through the original support channel. Do not repost sensitive information in a public request. Public posts, service records, caches and backups have separate controls; the app cannot guarantee erasure of all copies.