Privacy at a glance

Your stories stay yours.

In Firebase-enabled releases, the limited product analytics and crash diagnostics described below are collected by default. MoKi does not provide an in-app switch to disable either service.

01

Default telemetry

Product analytics and crash diagnostics are collected by default as described below.

01 · Scope

Who and what this policy covers

This policy applies to the MoKi short-comics application for iOS and Android and to MoKi’s public legal pages. HONG KONG TOPtoFUN NETWORK TECHNOLOGY LIMITED (“we”, “us”, or “our”) publishes MoKi and is responsible for this policy. Apple, Google, and Firebase operate separate services under their own policies.

02 · Analytics

Understanding reading and purchase journeys

In releases connected to live Firebase services, Product analytics is on by default from the first use, without a separate telemetry prompt. Google, as the Firebase Analytics provider, receives an app-instance identifier, device and app information, session and lifecycle events, coarse location inferred from an IP address, app-store purchase events, and the MoKi activity described below. MoKi configures Analytics without advertising-ID collection or ad-personalization signals.

MoKi records subscription-screen views, purchase results, and reading activity, including time spent actively reading, the comic viewed, and its access status. We use this information to understand reading and purchase journeys and improve the app. Reading activity is measured while a comic is visible and you are interacting with the app; it is not eye tracking or proof that content was understood. These events do not include comic dialogue, free-form user text, or payment credentials.

MoKi does not provide an in-app switch to disable Product analytics. Collection occurs by default while you use a Firebase-enabled release and the service is technically available. Uninstalling MoKi ends new app-generated collection from that installation while the app is no longer installed, but it does not delete data that Google already received.

03 · Crash diagnostics

Keeping MoKi reliable

Crash diagnostics is also on by default from the first use in Firebase-enabled releases, without a separate telemetry prompt. Google receives reports through Firebase Crashlytics to help us identify crashes, non-fatal technical errors, and, where supported, app-not-responding events. Reports may include Crashlytics and Firebase installation identifiers, session and event identifiers, timestamps, app version, operating-system and device information, relevant app and thread state, and stack traces.

For errors sent through MoKi’s custom reporting path, the app replaces the original exception message with a stable error code and runtime type, redacts restricted custom context, and keeps context to small technical fields such as environment or error type. Firebase may still generate its own platform-level report details needed for crash processing. MoKi does not intentionally add comic dialogue, transaction credentials, receipts, JWS values, purchase tokens, transaction IDs, or other free-form user text to reports.

Analytics breadcrumbs

Because Product analytics and Crash diagnostics are collected by default, Firebase can automatically attach recent Analytics events as breadcrumbs to a crash, non-fatal, or app-not-responding report. Breadcrumbs can include automatically collected screen events and the subscription, purchase, and reading activity described above to help diagnose what happened before an error.

MoKi does not provide an in-app switch to disable Crash diagnostics. Collection occurs by default while you use a Firebase-enabled release and the service is technically available. Uninstalling MoKi ends new app-generated reports from that installation while the app is no longer installed, but it does not remove reports Google already received.

04 · Purchases

Apple and Google process payment

MoKi VIP is purchased through the Apple App Store or Google Play. The storefront processes your account, payment, tax, subscription, cancellation, refund, and purchase-history information. MoKi receives storefront callbacks needed to display access and offer purchase restoration. It does not copy complete receipts, JWS values, purchase tokens, or transaction objects into its own preference storage.

06 · Sharing and transfers

Google, storefront, and support providers

The technical data described above is disclosed to and processed by Google as the provider of Firebase Analytics, Crashlytics, and Hosting, and purchase data is processed by Apple or Google as the applicable storefront. Support correspondence is processed by our email and infrastructure providers on our behalf. We do not use this data for third-party behavioral advertising. These providers may process data in countries outside the country where you use MoKi, including countries where they or their subprocessors operate, under applicable terms, policies, contracts, and transfer mechanisms. Google explains how it uses information from apps that use its services on its partner sites and apps page.

07 · Retention

Kept only for the relevant system

  • Firebase Analytics user-level and event-level data follows the active retention setting for the Firebase property. Google states that this setting does not affect standard aggregated reports, which may therefore remain available under different rules.
  • Google currently states that Crashlytics keeps crash stack traces, extracted minidump data, and associated identifiers for 90 days before it starts removing them from live and backup systems. It states that Firebase Hosting retains incoming IP address data for a few months.
  • Apple and Google retain storefront and transaction records under their policies and applicable legal obligations.
  • Support and privacy-request correspondence is kept only as long as reasonably needed to answer the request, maintain an appropriate request record, resolve disputes, and meet legal obligations, then deleted or de-identified when no longer needed.
08 · Choices and rights

Telemetry and privacy requests

Product analytics and Crash diagnostics are collected by default in Firebase-enabled releases, and MoKi does not provide in-app switches to disable them. Uninstalling ends collection from that installation while the app is no longer installed.

Uninstalling MoKi does not cancel a subscription, erase storefront history, or automatically delete Analytics events or crash reports already sent to Firebase.

Depending on where you live, you may have rights to ask about, access, correct, object to, restrict, or delete personal data. MoKi does not expose Firebase app-instance or installation identifiers as a user-facing request ID, so a name, email address, device platform, or approximate date range is generally not enough to match one pseudonymous Firebase installation record. Sending a support email creates a separate correspondence record; it does not by itself identify or link that record to Firebase telemetry. Requests will still be assessed as required by applicable law, and we will explain what we can identify, delete, must retain, or cannot match.

09 · Children and families

Storefront and local-law safeguards apply

MoKi is not intended to be used in violation of a storefront age rating or local rules requiring parental permission. A child who cannot consent to app use or purchases under local law should use MoKi only with a parent or guardian’s permission. MoKi does not knowingly ask children to submit a name or email address.

10 · Security

Data minimization is the first control

MoKi limits app-owned storage and custom telemetry fields and relies on platform and Firebase safeguards for the systems they operate. No method of storage or transmission is perfectly secure, so absolute security cannot be guaranteed.

11 · Changes and contact

Questions or privacy requests

This policy may change when MoKi’s features, providers, or legal obligations change. A revised policy will be published here. To make a privacy request, email support@lavaromance.com and include your device platform and approximate dates of use. Do not send passwords, complete receipts, purchase tokens, or payment credentials. Your message creates the separate support record described above and does not by itself identify Firebase telemetry.