Skip to main content
This guide explains how the Flashduty RUM SDK (the “SDK”) processes personal information in your app. It helps you meet China’s Personal Information Protection Law (PIPL), the related app regulations on collecting personal information, and app store privacy requirements. It focuses on the SDK’s own processing rules; Flashduty’s service terms and data security commitments as the entrusted processor are covered separately in the Data protection agreement and the RUM Data security doc.

Two key requirements for compliant use

After integrating the SDK, you (the app operator) must complete the following two compliance actions — both are mandatory:

① Privacy policy disclosure

Disclose in your app’s privacy policy that the SDK is integrated and what personal information it collects. See Privacy policy disclosure.

② Deferred initialization

Do not initialize the SDK or report any data before the user accepts your privacy policy. See Deferred initialization.
Going live without completing these actions may cause your app to be flagged for “illegal collection and use of personal information” during app-store review or regulatory privacy-compliance scans. The rest of this guide explains the factual basis behind these two requirements and the concrete steps to implement them.

Division of compliance responsibilities

The SDK runs as a third-party component embedded in your app. The responsibility boundary is as follows: Under Article 21 of China’s Personal Information Protection Law, you and Flashduty form an entrusted-processing relationship. You determine the purpose, means, and categories of personal information processed. Flashduty processes data only as agreed, takes the necessary measures to safeguard it, doesn’t use it beyond the agreed scope, and doesn’t sub-entrust the processing. The rights and obligations of both parties are governed by the Data protection agreement.

How the SDK processes personal information

The following is the factual basis for completing your privacy policy disclosure.

Personal information collected

Following the principle of data minimization, the SDK collects only information directly needed for crash analysis, performance diagnostics, and user experience monitoring. It doesn’t collect personal information unrelated to these functions. The table below itemizes the information types, fields, purposes, and collection methods. Apart from “app runtime information”, all collection items can be disabled or masked through configuration (see Data handling rules and commitments).

Information explicitly not collected

To minimize privacy impact, the SDK does not collect the following, and does not request the related sensitive permissions:
  • Unique device identifiers: IMEI, IDFA, IDFV, Android ID, MAC address, OAID, and so on.
  • Precise geolocation (GPS / latitude-longitude).
  • Contacts, SMS, call logs, photo albums, microphone, or camera content.
  • The list of installed apps.
  • Telephony identifiers such as IMSI or SIM serial number. The Android and HarmonyOS SDKs also do not collect the SIM carrier name or carrier ID (the iOS SDK reports the carrier name on cellular networks, see “Network information” above).
  • Directly identifiable information such as phone numbers or ID numbers (unless you actively pass it in through the API — see the note below).
The SDK commits not to collect the above information through covert, misleading, or deceptive means, and does not read or transmit device data unrelated to monitoring.
If you actively pass personally identifiable information to the SDK through setUserInfo (user ID, name, email) or custom attributes, this information is reported along with events. Make sure such collection is disclosed in your privacy policy and consented to, and avoid passing in sensitive personal information.

Device permissions requested

Following the principle of least privilege, the SDK only requests the network permissions necessary for monitoring. It does not request sensitive permissions such as location, camera, microphone, contacts, phone, or storage, and does not present runtime sensitive-permission prompts to the user.

Data handling rules and commitments

Beyond collecting data on a minimal, as-needed basis, the SDK provides the following data-handling mechanisms and commitments to help you further control the collection scope and reduce privacy risk:
The SDK collects only the information necessary for monitoring. Sessions are identified by a random session.id and user identity is not tracked by default, anonymizing the data while preserving trend analysis.
You can finely control collection behavior:
  • Disable auto tracking: turn off automatic collection of user actions and view visits, keeping only explicit reporting.
  • Sampling: reduce collection and reporting through the session sample rate.
  • Attribute masking: use EventMapper to modify or drop fields before events are reported, removing any PII that may have leaked in (such as action names or personal information in URLs).
  • Action name masking: enable enablePrivacyForActionName to replace unnamed action names with a placeholder.
See the RUM Data security doc for details.
You can disable collection of IP address and geolocation (country/city) data on the Privacy tab of the application details; the change takes effect immediately server-side.
All RUM events can be forwarded through your own proxy server so end-user devices never communicate with Flashduty directly, letting you centrally control egress traffic.

Integrator obligations

This section details how to implement the two key requirements.

1. Privacy policy disclosure

Make sure the app you develop or operate has a privacy policy that meets regulatory requirements, and be sure to clearly inform end users that your app integrates third-party SDK services. In your privacy policy, state the purpose, methods, and scope of the SDK’s collection and use of personal information. Also give the SDK’s developer and operator (Beijing Flashcat Cloud Technology Co.,Ltd.) and a link to its privacy policy. On the login or registration page and on first launch, present the privacy policy in clear, plain language through a prominent, accessible means such as a pop-up, a text link, or an attachment. The user can then give voluntary and explicit consent on a fully informed basis. Where personal information is provided to a third party, you should also list it separately in the “third-party SDK information sharing list”. We provide the following disclosure text as a reference; you may inform users in text or table form (for the table form, refer directly to Personal information collected above). The features and required fields can differ across SDK versions, depending on your choices and configuration. Inform users and obtain their consent based on this guide and on how the SDK actually behaves in your integration. The reference text can be used directly — adjust it to match your actual integration:

2. Deferred initialization

To meet legal and regulatory requirements, make sure you initialize the SDK only after the user has consented. To keep the SDK from collecting personal information before consent, the SDK provides a deferred-initialization API and a compliant initialization approach. For details, see Android SDK integration and iOS SDK integration. The specific requirements are:
  1. Authorize first, then initialize: call the initialization API only after the user has read your privacy policy and granted authorization. If the user declines the privacy policy, you must not call the initialization API. If you initialize with the PENDING / .pending state, the SDK only buffers data locally and sends no personal information to the server. Reporting starts after the state switches to granted.
  2. No permissions, collection, or reporting before consent: don’t request sensitive device permissions involving personal information before the user accepts the privacy policy. Don’t collect or report personal information before consent. Pay special attention to Android ID, OAID, IMEI, MAC address, hardware serial number, and the installed-app list. The SDK does not collect these identifiers by default — see Information explicitly not collected.
The following shows the “deferred initialization + consent change” code for each platform:
The snippets above show only the minimal code needed for deferred initialization. For the full initialization parameters, integration steps, and consent APIs per platform, see the corresponding docs:

Data storage and security

Data collected by the SDK is reported only to the Flashduty server you configure and is used solely to provide monitoring services to you. It is not shared with any other third party and is not used for advertising, user profiling, or cross-app tracking. Throughout the data lifecycle, Flashduty applies the following safeguards:
  • Transport security: all reported data is transmitted over HTTPS/TLS.
  • Storage security: data is stored on compliant servers within mainland China, with encryption, access control, and security auditing.
  • Retention and deletion: data is stored for the agreed retention period and deleted or anonymized after expiry.
  • Cross-border transfer: no cross-border transfer occurs without your explicit consent or unless otherwise required by laws and regulations.
For the full security measures, retention periods, and cross-border transfer terms, see the Data protection agreement and the RUM Data security doc.

Compliant integration checklist

1

Update your privacy policy

Add the SDK’s name, provider, collected information, and purpose to your app’s privacy policy.
2

Defer initialization

Ensure the SDK is not initialized and no data is reported before the user consents (or use the PENDING state).
3

Register the third-party SDK list

Register the personal information fields and purposes from this guide in your app’s third-party sharing list / filing materials.
4

Provide a withdrawal entry

Provide an entry to withdraw consent in your app settings, and call setTrackingConsent(NOT_GRANTED) upon withdrawal.
5

Avoid passing in sensitive information

Review setUserInfo and custom attributes to ensure no sensitive personal information is passed to the SDK.

Contact us

This SDK is provided by Beijing Flashcat Cloud Technology Co.,Ltd. For questions, feedback, or complaints about how the SDK processes personal information, or to exercise your data-subject rights, contact us through:

Technical Support

Scan to add our WeCom for one-on-one technical supportTechnical Support WeCom

Business Inquiries

Scan to add our business manager on WeComBusiness Manager WeCom

Console Feedback

Sign in to the console and submit feedback in the bottom left corner