Privacy Policy

Your library

Honbako stores your library, reading history, bookmarks, preferences and downloaded pages on your device. The included original tutorial and local reading do not require a Honbako account.

Connections you choose

When you connect a personal library server, your searches, book identifiers, requested pages and any credentials you configure are sent to that server. External-source TestFlight builds can also contact source-list hosts and installed providers. The selected hosts and providers receive the requests directed to them, including source-list or package downloads, searches, requested pages and any credentials supplied for that connection. Providers receive network information such as your IP address and may collect data under their own policies. Only connect services you trust. Honbako does not operate those services.

iCloud synchronization

If you enable iCloud sync, library metadata, bookmarks and reading activity synchronize through your private Apple iCloud database. Reading records include a device name and identifier (identifierForVendor or a generated UUID) so Honbako can identify which device saved your position. Source connection details, including personal-server addresses and names, extension repository addresses, and approved extension identities and versions, also synchronize through your private Apple iCloud storage. Passwords, cookies, sign-in tokens, downloaded pages, imported files and extension packages remain on the device. Restoring a personal server may require signing in again; restoring an external extension requires your confirmation and the matching approved package. Your Apple account and iCloud settings govern access to this data.

Subscriptions and notifications

Apple processes Honbako Pro payments. Honbako uses StoreKit transactions and caches entitlement and verification dates to determine access. Honbako does not receive your payment-card details. Chapter alerts use local notifications, source checks and iOS background refresh. You control notification permission in system Settings. TestFlight uses Apple’s testing environment. A verified active subscription is still required for remote MCP hosting; test-environment purchases are kept separate from production purchases.

Optional iPhone Duo cover display

Showing a book cover on the optional outer display uses the system camera-capture accessory and requires camera permission. Honbako starts a video-only camera session for that accessory. It does not record or save photos or video, attach a microphone, or transmit camera frames to the developer. The session stops when the cover is hidden, the book closes, the device folds or the app moves to the background.

Optional MCP connections

MCP is off until you enable it, and Honbako asks before each connection what a connected AI can read. A local connection sends the information you allow to your chosen local server. Remote MCP uses Cloudflare-hosted storage and one private workspace per Pro purchase, shared by up to five of your devices that prove that purchase. Family Sharing members get their own workspace. Approved AI providers can use only the access you allow. Honbako does not provide the AI model or its subscription; your selected AI provider handles shared material under its own terms and privacy policy.

The remote service stores your latest shared library titles and identifiers, source and repository metadata, current reading position, and queued requests and results. When allowed, an AI can request your saved reading history, search your connected catalogs, and queue changes to your library, sources or repositories. These requests can retain search terms, reading-history records, source/repository addresses, results and errors. Source changes requiring confirmation are approved in Honbako.

When page access is allowed, the book, chapter and page identifiers of the page you’re reading are shared with your approved AI connections as you read. The manga-page image itself is sent only when your AI asks to see that page, and only while the book is open in Honbako; it is then stored with any annotations until you move to another page. This is manga-page content, not camera imagery. A page image already sent and the snapshot can remain available while Honbako is closed or offline. They do not have an automatic age-based expiry: later sync replaces the snapshot, a new shared page replaces the previous page, and turning off page access revokes the shared page. Turning MCP off on a connected device deletes that device’s shared snapshot, page and annotations. Queued work is bounded to 100 pending and 2,000 recent completed requests, with pruning on later requests.

Remote Pro verification sends a signed App Store transaction to Honbako, checks its authenticity and current subscription status with Apple, and retains purchase identifiers, hashed purchase bindings and entitlement dates. Honbako does not receive payment-card details. Installation identifiers, credential hashes, connection times and approved AI client/callback details support authentication and workspace isolation. Each device’s type (such as iPhone or iPad) and last-active time are shown in the Devices list on your other devices. Raw IP addresses are processed in real time; hashed network-address rate-limit records can remain for security windows of up to one day. Developer advertising and analytics services are not used.

Turning MCP off on one device while connected, or removing it from the Devices list, removes only that device: its snapshot, page and annotations are deleted, its credential stops working and its place among the five devices is freed. Your other devices and approved AI connections keep working. When the last device leaves, or when you choose Disconnect All Devices, the workspace’s shared library, jobs, pages, annotations and permissions are deleted and every AI credential is revoked. Minimal hashed records of each device and of your purchase’s workspace link remain without a fixed deletion date so that only your own devices can reconnect to it. Access credentials expire after 15 minutes and refresh credentials after 30 days; expired records are pruned during later operations, so logical expiry does not promise immediate physical deletion. If the server is unavailable, a local disconnect cannot confirm remote deletion: retry a connected disconnect or email jun@honbako.xyz privately. Removing the app alone does not delete remote information or copies held by your chosen AI provider.

Tracking, diagnostics and support

Honbako does not include advertising or a developer analytics service, and does not use the advertising identifier. Diagnostic logs remain local unless you choose to share them. Apple may process App Store or TestFlight diagnostics under its own settings and policies. If you contact support through GitHub, information you submit is used to respond and resolve the request. Public GitHub issues are visible to everyone; do not include passwords, contact details or private reading material.

Retention and deletion

Local reading data remains until you remove it through the app or remove the app and its local data. Removing the app does not automatically delete iCloud data or information held by connected providers. Manage cloud data using your Apple account and relevant service controls. Support discussions are stored by GitHub under its own privacy and retention controls. You can edit your own public issue content or contact GitHub about deletion of account information.

Contact and updates

Honbako is maintained by missingems, the maintainer of the linked public project. For privacy questions, deletion requests or private support, email jun@honbako.xyz. Public GitHub issues remain available for non-private bug reports. Do not post personal reading material, credentials or contact details in public issues; GitHub controls information stored on its service. We will update this page when our practices change and show the effective date above.