MangaFuru is a local-first manga reader for iPhone and iPad, with no MangaFuru account or commercial manga catalog. Library data, progress, and settings are primarily stored on your device; enabling iCloud backup or exporting a backup also stores selected data at that destination. Firebase product analytics, crash reporting, and performance diagnostics are enabled by default. They may transmit feature interactions, online manga titles and hashed identifiers, pseudonymous installation identifiers, and diagnostic data. You can turn Analytics off in Settings; Section 4 explains the data and controls. Analytics data is not provided to advertising SDKs or used for cross-app or cross-site advertising tracking. This policy also covers the website and issue reports.
1. Who We Are and Scope
This Privacy Policy is published by the MangaFuru Team ("MangaFuru Team", "we", "us", or "our"). The MangaFuru Team is a small independent team / individual developer and is not a registered company. For the limited personal data described in this policy, the controller is the MangaFuru Team, contactable at gomanga.support@gmail.com.
This policy explains how data is handled when you use MangaFuru, a local-first iOS manga reader for iOS 18 and later, when you visit our website, and when you report issues to us through GitHub Issues.
This policy applies to the following:
- the MangaFuru iOS application itself;
- the official website hosted at https://mangafuru.github.io;
- the issue and bug-reporting channel hosted at https://github.com/MangaFuru/MangaFuru/issues.
MangaFuru has no account system and does not operate a content server that stores your complete library or reading progress. We do, however, use Google Firebase for product analytics, Remote Config, crash reporting, and performance diagnostics, and are responsible for disclosing and managing the limited data listed in Section 4. Third-party or self-hosted sources you configure, and infrastructure providers such as GitHub, process the data they receive under their own policies.
2. Our Core Principle: Local-First, No Account
The fundamental design principle of MangaFuru is local-first. In practice, this means:
- There is no MangaFuru account system. No MangaFuru registration is required; individual sources, Komga servers, or Apple services may require their own accounts or sign-in.
- Your library, reading progress, and source configuration are primarily stored on your device. Section 3 covers backups and exports, and Section 4 covers analytics and diagnostics that may be sent to Google. Local-first does not mean that no data ever leaves your device.
- We do not host, upload, sell, or distribute manga pages and provide no official content catalog or recommended-source list. The internal popularity measurement described in Section 4 retains only a bounded title and hashed content key for eligible public sources, never manga pages or raw URLs.
MangaFuru is a manga reader plus a source-configuration framework. Acting solely on your instruction and configuration, the app requests and displays content from the sources you choose; all sources, files, accounts, credentials, and access rights are configured and controlled by you.
3. Data Stored on Your Device
The following data is primarily created and stored on your device, not transmitted wholesale to the MangaFuru Team. Backups and exports you enable, and the analytics and diagnostics in Section 4, may involve storage or processing outside your device:
- your library and imported content items;
- read-later / history lists and reading history;
- reading progress (including chapter and page position);
- installed-source records, repository configuration, and individual source settings;
- app preferences (such as language, appearance, reading direction, and cache settings);
- caches of cover images, page images, and metadata;
- local diagnostic logs.
You can delete individual items or clear caches in the app. Deleting the app does not also delete exported files, iCloud backups, previously transmitted analytics, or data held by third-party sources; manage those copies separately at their storage destinations.
The app includes a built-in Local source, which is a content-agnostic mechanism that lets you import or read files you already own and control on your own device or network. It provides no manga catalog or recommended sources; the app can build local library indexes and caches in response to your actions. Removing the Local source only removes its entry-point record and does not delete content you previously imported.
Backups, iCloud, and Exported Files
If you enable automatic iCloud backup, the app stores backup files in your Apple account's iCloud storage, not on a MangaFuru Team content server. Depending on the backup categories, files can contain your library and categories, read-later list, reading history and progress, source and repository configuration, and supported app preferences. Backup headers may also contain your device name, creation time, and app version. Apple processes iCloud data under its Privacy Policy.
Native app backups are not complete file backups: they exclude downloaded manga page images, rebuildable image caches, cookies, and Keychain credentials. Source configuration and content metadata may still include private server addresses or personal information; do not share backup files publicly. Turning automatic backup off stops future automatic backups but does not delete existing copies; delete those separately through backup management or Apple's iCloud storage controls.
Manual exports are handed to the location or service you choose in Files or the share sheet; retention and deletion depend on that destination. Restoring a backup writes supported data back into the app. Keep copies you need and review prompts for export, restore, and deletion. Apple's device-level backups are separately governed by your system settings and Apple's policies.
4. Information We Do and Do Not Collect
Analytics is enabled by default. MangaFuru uses Firebase Analytics to understand feature adoption, preference distribution, and the purchase funnel; Crashlytics and Performance to improve stability and performance; and Remote Config for safety switches and A/B tests. Firebase manages pseudonymous App instance and Firebase installation identifiers, but MangaFuru App code does not read or display those identifiers.
You can turn Analytics off under Settings → Advanced → Analytics. Turning it off immediately closes product events, applies the Firebase Analytics, Crashlytics, and Performance collection controls, resets local Analytics state, and deletes unsent crash reports. Under the Firebase SDK lifecycle, Crashlytics' persisted collection state becomes fully effective on the next App launch. Opting out does not delete data uploaded while collection was previously enabled. Remote Config may remain operational for safety and configuration, but it cannot override your choice to send product events.
Our App Store privacy dispositions are below. None of these data types is linked to a MangaFuru account or real-world identity, used for tracking, or shared with an advertising SDK:
| Data type | Collected | Linked | Tracking | Purposes |
|---|---|---|---|---|
| Device ID (pseudonymous Firebase installation / App instance identifier) | Yes | No | No | Analytics; App Functionality |
| Coarse Location (Firebase-derived city-level metadata) | Yes | No | No | Analytics; App Functionality |
| Product Interaction | Yes | No | No | Analytics |
| Purchase History | Yes | No | No | Analytics |
| Crash Data | Yes | No | No | App Functionality |
| Performance Data | Yes | No | No | App Functionality |
| Other Diagnostic Data | Yes | No | No | Analytics; App Functionality |
Product interaction includes app launches, screens and feature entries, coarse tap positions, setting categories, source installation/activation outcomes, paywall actions, and search-length buckets without query text. Reading usage data may also include active reading seconds, reader type, and the reason a reading session ended, to understand feature use.
Online manga interactions, such as opening the reader, completing a chapter, or adding or removing a library item, may include a manga title of up to 160 characters and hashed identifiers derived from the source identifier and content URL. These events use the general Analytics control and do not depend on the popularity safety switch. This path does not filter through a public-source allowlist, so titles from sources you configure may also be included. Local, EPUB, and PDF do not use this online-manga identity path. Hashing replaces raw URLs but does not guarantee anonymity or conceal a separately transmitted manga title.
A separate, independently gated popularity measurement accepts only eligible public sources and may include a public source code, hashed content key, bounded public title, and read or library-add signals. That measurement excludes private servers, custom repositories, and local documents; these exclusions are not a guarantee for all online manga events described above. Turning Analytics off stops both types of product events.
Purchase History uses closed categories for purchase start, cancellation/pending/unverified/failure, verified completion, restore request/result, and Terms or Privacy link actions. MangaFuru custom events contain no transaction ID, receipt, price, currency, storefront, payment method, account, or error text.
Coarse Location means only city-level metadata derived by Firebase/GA4 from network and device data. MangaFuru requests no Analytics location permission and sends no GPS coordinates or precise location. On August 5, 2026, direct read-back showed granular location and device collection enabled for all 307 regions.
Retention: on August 5, 2026, direct GA4 read-back showed event data retention of 2 months, user data retention of 14 months, and reset-on-new-user-activity enabled; Google's standard aggregate reports may persist longer under its service policies. Crashlytics crash records and associated installation identifiers begin deletion after 90 days. Performance retains IP-associated events for 30 days and installation-associated and de-identified performance data for 60 days before deletion begins. If BigQuery export is later enabled, raw event tables expire after 60 days and are restricted to the aggregation boundary; internal popularity snapshots expire after 400 days.
Our app analytics events do not include MangaFuru account credentials, IDFA/advertising identifiers, names, contacts, GPS coordinates, payment card details, raw search queries, or source login credentials, and do not upload your library or manga pages wholesale. This does not mean no content-related data is processed: titles, hashed identifiers, and reading interactions are disclosed above. Apple handles purchase transactions; the app uses StoreKit to verify purchases and restored entitlements. Support submissions and backups are covered separately in Section 7 and the backup explanation. App analytics data is not currently provided to advertising SDKs; any future advertising service will require updates to this policy, necessary consent flows, and App Store disclosures.
5. Sources and Network Connections
MangaFuru lets you add "Repositories" and install or enable "Sources". A source may be a third-party extension, a remote service, or a local service running on your own network or device. Acting on your instruction and configuration, the app then browses, searches, opens, and displays content from those sources you configure.
When the app connects to a source or source service, it does so as you have configured it. Any data sent over such a connection (for example, search terms, the content requested, or credentials you enter for that source) is sent, at your direction, to the source you have chosen. These third-party or self-hosted services are outside the MangaFuru Team's control and operate under their own privacy policies and terms.
Because some sources may run on your local network, or because the app itself may host a local server on your device, iOS may prompt you to grant Local Network permission. This permission is used to communicate with local source services on your device or local network, not to transmit your activity to us.
You are solely responsible for the legality and rights of whatever sources and content you configure and access, and for complying with applicable law and each source's own terms. The MangaFuru Team recommends no particular source and ships no curated source list; the built-in Local source described above is only a content-agnostic local mechanism and provides or points to no content.
6. Website and GitHub
Our website (https://mangafuru.github.io) is hosted on GitHub Pages. The website may use web analytics (such as Google Analytics) and display advertising (such as Google advertising); these third-party services may set cookies and collect usage data or device/browser identifiers, and operate under their own policies. Where applicable law requires prior consent, we will present a cookie-consent mechanism and obtain your consent before enabling them, and we will update this policy when we make material changes to advertising or analytics.
Bug and issue reports go through GitHub Issues at https://github.com/MangaFuru/MangaFuru/issues. When you visit the website or use GitHub Issues, GitHub, as the hosting and infrastructure provider, may process standard server logs, IP addresses, account/login state, and the contents of the issues you submit, under its own policies.
Please note: public issues submitted on GitHub Issues are publicly visible. Their contents can be viewed by others and may be indexed by search engines. Consider this carefully before submitting anything in a public issue.
GitHub's processing of data on its platform is governed by GitHub's own privacy policy and terms, not by this policy.
7. Diagnostics and Issue Reports You Choose to Submit
When you choose to report an issue to us, the information you provide may include the following:
- a text description of the problem and steps to reproduce it;
- screenshots;
- diagnostic snippets, such as excerpts of local logs, error messages, or device/app version information.
We use this information only to understand, diagnose, and fix problems and to respond to your report.
Retention: we retain support emails and issue-report contents only for as long as needed to diagnose and resolve the matter and to maintain a public record of the issue. Public issues submitted through GitHub Issues persist publicly under GitHub's model even after closure. Closing an issue does not delete it; deletion, editing, and retention are governed by GitHub policies and permissions.
Important security warning: do not submit passwords, private tokens, full cookies, paid content, personal data, or other secrets in public reports or diagnostics. Public issues submitted through GitHub Issues are publicly visible and may be indexed by search engines. Before submitting a screenshot or log, remove any sensitive or personally identifiable information.
8. Legal Bases and Your Privacy Rights
MangaFuru is local-first and has no account, but it still processes the pseudonymous analytics and diagnostic data listed in Section 4. We rely on legitimate interests in improving the app, understanding feature use, and maintaining reliability, and provide an in-app opt-out; legitimate interests or an opt-out cannot replace prior consent required by applicable law. This policy describes data handling and does not itself constitute your consent to optional data collection. We process issue reports and support emails you actively submit in order to respond to your request.
Depending on applicable law (for example, the GDPR, UK GDPR, CCPA/CPRA, or similar laws), and where the applicable conditions for each right are met, you may have the following rights regarding any personal data we hold:
- to access the personal data we hold about you;
- to correct inaccurate or incomplete data;
- to delete your data (the "right to be forgotten");
- to object to processing carried out on the basis of legitimate interests (GDPR Article 21);
- to restrict certain processing;
- to obtain your data in a portable format, where technically feasible and the applicable conditions are met.
Some rights apply only to certain processing bases. For example, GDPR data portability applies only to processing based on consent or contract and carried out by automated means. Access, portability, or deletion of pseudonymous Firebase data also depends on whether the relevant identifier can be located reliably; the right to object applies to processing based on legitimate interests.
Where the CCPA/CPRA applies, we will not discriminate against you for exercising your privacy rights. Purchasing Premium does not affect your ability to exercise these rights.
You can contact us at gomanga.support@gmail.com to exercise these rights. Local library data and progress can be managed or deleted on your device; manage iCloud and exported copies separately at their storage destinations. Firebase data is keyed by pseudonymous identifiers and subject to service-side retention, so we may need information capable of locating a record and cannot promise to identify a person's data from a manga title alone. We will respond within applicable statutory deadlines, and you may lodge a complaint with your local data protection authority.
9. International Users and Data Transfers
MangaFuru is available worldwide. Library data and progress are primarily processed on your device. Apple processes iCloud backups you enable, and your chosen services handle exported copies; storage locations depend on the service. The Firebase analytics, diagnostics, Remote Config, and gated popularity data listed in Section 4 may be processed by Google or its agents outside your country under Google's data-processing terms and applicable transfer mechanisms.
When you use our website or submit a report through GitHub Issues, that data is processed and stored by GitHub on GitHub's infrastructure, which may be located outside your country. Any cross-border processing by GitHub relies on the transfer safeguards GitHub maintains (for example, standard contractual clauses or applicable data-transfer frameworks) under GitHub's Data Protection Agreement, and such data is submitted by you on your own initiative. Such processing is governed by GitHub's own policies and safeguards, to which the MangaFuru Team is not a party. Any third-party or self-hosted source you configure may also process data in its own location. Consider this before submitting anything to us.
10. Children's Privacy
MangaFuru is not designed for or directed to children under 13. We do not knowingly create child accounts or collect direct identity data from children. The default analytics and diagnostics listed in Section 4 contain no age or account, but may still originate from a device using the app; this policy does not constitute child or parental consent or replace safeguards required by applicable law.
If we become aware that we have inadvertently received personal data from a child under the applicable age (for example, embedded in an issue report), we will delete it. You may also contact us at gomanga.support@gmail.com, and we will take reasonable steps to remove that information.
MangaFuru is a source-configuration framework and ships no content of its own. You are responsible for the age-appropriateness of content accessed through sources you configure, and for any appropriate supervision of minors.
11. Security
Local MangaFuru data is protected by iOS platform security. Once you enable iCloud backup or export a file, security of those copies also depends on your Apple account, destination service, and sharing settings. Backup compression is not content encryption.
You can further protect your data by keeping your device updated, using device-level protections (such as a passcode and biometrics), and carefully managing the credentials and access for the sources you configure.
For the limited Firebase data listed in Section 4 and content you actively submit, we use data minimization, closed parameters, opt-out controls, least privilege, and bounded retention. No internet transmission or electronic storage is completely secure, and we are not responsible for the security of third-party or self-hosted sources you configure. Nothing here limits data-protection obligations or rights that cannot be excluded under applicable law.
12. Third-Party Services and Links Disclaimer
MangaFuru uses Google Firebase for the analytics, Remote Config, crash, and performance services described in Section 4, and can connect to third-party or self-hosted sources you configure. This policy and website may link to external services such as Google and GitHub.
Google and each third-party or self-hosted service operate under their own privacy policies and terms. The MangaFuru Team does not endorse the content, operation, or security of a source you configure; your relationship with its operator is governed by that operator's terms.
Before using any third-party or self-hosted service, we recommend that you review its privacy policy and terms.
13. Changes to This Policy
We may update this Privacy Policy from time to time to reflect changes to the app, the website, or applicable law. When we make changes, we will update the "last updated" date at the top of the page.
For material changes, we will make reasonable efforts to provide notice, for example through the website or the app. For changes involving data processing that requires consent by law, publishing this policy or continuing to use the app does not replace that consent. We encourage you to review this policy periodically.
14. Contact Us
If you have any questions about this Privacy Policy, or wish to exercise any privacy right, please contact us as follows:
- Privacy and legal contact: gomanga.support@gmail.com
- Website: https://mangafuru.github.io
- Project home: https://github.com/MangaFuru
- Bug and issue reports: https://github.com/MangaFuru/MangaFuru/issues (note that public issues are publicly visible)
For requests involving personal or confidential information, please use the email address above rather than a public issue.
15. Controlling Language
This Privacy Policy is provided in Traditional Chinese and English. The Traditional Chinese version is the controlling and authoritative text; the English version is a convenience translation.
In the event of any difference or inconsistency between the Traditional Chinese and English versions, the Traditional Chinese version prevails.
This policy is effective and was last updated on September 13, 2026.