Privacy Policy

Privacy Policy

MihirakiPDFViewer is an app for reading PDFs comfortably on your device. This page explains what information the app handles and how that information is used.

Summary

The app's basic privacy approach.

PDF content is not sent out

Display, search, page detection, and related processing for selected PDFs are handled on the device.

No ads or analytics SDKs

The app does not include third-party SDKs for advertising delivery or behavior analytics.

Purchases are handled by Apple

In-app purchases are processed through Apple's StoreKit. The app does not directly receive payment information.

Information the App Handles

Information that may be used by each feature.

PDF Files

The app opens PDF files selected with the file picker. PDF text, metadata, and page information are used for viewing features.

  • PDF files are not uploaded to an external server.
  • PDFs in iCloud Drive are loaded according to Apple's system behavior.
  • Passwords for protected PDFs are used only for unlocking the document.

App Settings

Display settings, cover settings, two-page view, app icon settings, and similar preferences may be stored on the device.

  • Settings are used to restore app behavior.
  • Settings are not sent to a developer server.

Search Terms

Text entered in PDF search is used to search within the opened PDF. Search terms are not sent to external services.

In-App Purchases

Tip purchase status may be used for post-purchase UI and app icon changes.

  • Payment information is managed by Apple.
  • The developer does not receive credit card numbers or similar payment details.

Support Inquiries

If you contact support through GitHub Issues or email, the information you send may be reviewed as needed to reply or investigate the issue.

  • Do not send PDF files or their contents. Review the reporting and image instructions below before contacting support.
  • Device model, OS version, app version, and reproduction steps help investigation.

Sharing with Third Parties

Information you choose to share or send to support reaches the selected recipient and may be retained there. StoreKit purchases and iCloud Drive follow Apple's handling. Sample downloads and external links contact their service operators; those operators and your selected sharing destinations apply their own privacy practices. The app does not automatically send diagnostic reports to the developer.

Security

PDF files and settings are handled only as needed for the app.

Information You Manage

PDF files and passwords are managed by your device, iCloud Drive, or the storage location you use. If you handle sensitive PDFs, enable device passcode, biometric authentication, and iCloud account protection.

Policy Changes

This privacy policy may be updated when necessary.

Notice of Changes

Important changes will be announced on this page or in the app. The latest version is always available on this page.

On-device diagnostics and app logs

Diagnostic results are held in the current screen's memory. If you choose Share, the text includes the test time, model name and model identifier (not a unique device ID), OS and app versions, total and available memory, and non-storage check results. Logs contain event types, times, counts and elapsed processing times. The app's readable/shareable log is limited to 2,000 entries; entries older than 24 hours are removed when logs are read or recorded, not by a timer while the app is stopped. System logs follow OS retention rules. Reports and logs are not sent automatically.

Contact

For privacy questions or deletion requests, please contact support.

Privacy Policy

Open the Privacy Policy link at the top of Settings or in App Information. It is available before opening a PDF and while reading, without a purchase or login.

Available disk space is displayed only on this device. Shared diagnostic text excludes the storage check, its value, and its effect on the overall result. Logs may include elapsed processing times, but never raw system uptime.

Reading restoration stores the document bookmark, page, viewing settings, and search text locally; PDF passwords are not saved. Sample downloads contact GitHub Pages only when requested. Opening this policy or GitHub Issues also contacts an external website, whose operator may receive the IP address and request information. Shared reports go only to the destination you choose. These external services have their own privacy policies.

PDF viewing and search run on the device. Reading restoration stores a document bookmark, page positions, search text and viewing options locally; PDF passwords are not saved. Closing the document or resetting settings clears the restoration record, but does not delete the PDF or diagnostic logs. Some imported PDFs are copied into the app's Documents storage. To remove local app data, use the OS option to delete the app, not offload it. External originals and copies already shared are not deleted by that operation. There is no dedicated log-delete button.

Support information and retention

We use support information only to reply, investigate problems and make technical performance improvements. We do not request your real name. If your sender display name contains your real name, we retain it only in the original email for the period needed for replies and investigation; we do not copy it into case-specific Google Sheets or improvement notes.

Screenshots are accepted only at tyamada.support@gmail.com when text alone cannot reproduce the problem and an image is needed. Before sending, hide PDF contents, file names, names, notifications and other unnecessary information. Images are normally handled within the original email. Case-specific Sheets contain only the observations needed for the investigation, not the images.

We do not copy GitHub author names or handles into case-specific Sheets or improvement notes. Only when needed for a reply or investigation, we retain a link to the original Issue in the case Sheet. While the author can be reached through that link, the record remains linkable to them. Do not put personal information, PDF files or their contents, file names, or screenshots in public Issues.

Public GitHub posts and the email and case records we manage are distinct. Deleting our case link does not delete the public Issue. We cannot promise deletion of posts or service copies outside our control. Support reports and case references that lead back to a sender are not treated as anonymous.

Deletion schedule

A. Original emails (including displayed real names), investigation images and investigation copies: a case is complete when a reply or investigation conclusion exists and the developer confirms no work remains. Silence alone does not close a case. We check deadlines weekly, begin deletion around 60 days after completion, and confirm deletion of manageable records, including the relevant Trash, within 90 days. The 60-day point is not a minimum retention period; early deletion requests do not wait for the normal deadline.

B. Case-specific Sheets, observations, Issue links and intake/deletion records: we confirm deletion of the case file and related records and references within 90 days after deletion of the original information is completed. Deleting only rows or cells is insufficient. This does not extend A or allow originals to be moved into these records. A public Issue remaining online does not automatically extend our case-record deadline.

C. Generalized improvement notes may retain only causes and fix summaries, without names, images, post URLs, case IDs or other information leading back to the original report. They are not an alternative storage location for A or B records.

Exceptions are limited to continuing investigation or legal necessity. We record the reason, scope and end condition and review them at least every 30 days and when the investigation ends. Once the need ends, deletion is normally confirmed within 30 days, or by the original 90-day deadline if it remains and is earlier. Reopening or an exception does not automatically reset deadlines. Dates use calendar days in Asia/Tokyo.

These deadlines cover records the developer can manage. Deletion in a service interface does not guarantee physical erasure of provider-internal recovery copies or device backups within the same period. Such copies and their deletion limits are distinct from the records under our control. Deleting local app logs does not delete reports already sent.

For questions or deletion requests, contact tyamada.support@gmail.com. Provide only the information needed to identify the relevant case; do not post it publicly.