Pubeasy SDK Data Collection Notice
Last updated: July 20, 2026
This Data Collection Notice explains what information the Pubeasy SDK may collect, how it is used, and key requirements for developers integrating the SDK. This notice is a supplement to the Pubeasy Privacy Policy and should be read together with it. This Notice applies only to the Pubeasy SDK. Developers remain responsible for their own privacy notices and legal compliance with respect to their applications.
1.Types of Data Collected
The Pubeasy SDK may collect the following categories of information from end users’ devices and applications:
(1)Device Information
Purpose: Advertising delivery, anti-fraud detection
Required:
- IP address (Android / iOS / HarmonyOS)
Optional:
- Device manufacturer, brand, and model
- Operating system type and version (including kernel version)
- Screen resolution, orientation, DPI
- Time zone, network type, carrier information
- Memory size, CPU model
- Android only:GAID, OAID, Amazon ID
- iOS only: IDFV
(2)Application Information
Purpose: Anti-fraud detection, traffic segmentation
Optional (Android only):
- Application package name, running process information
- App version, installation time, installation channel and sub-channel
- App foreground/background status
- Crash data
(3)In-App User Activity Information
Purpose: Traffic segmentation and performance analytics
Optional (Android / iOS / HarmonyOS):
- User ID (as provided by the app)
- Age, gender
- In-app purchase amount, currency, and purchase count
(4)Advertising Interaction Information
Purpose: Ad attribution, performance analytics, and anti-fraud
Required (Android / iOS / HarmonyOS):
- Data on ad impressions, clicks, and related interactions
(5)Network Information
Purpose: Ad delivery, anti-fraud, attribution, and network stability
Required (Android / iOS / HarmonyOS):
- Carrier information, Wi-Fi status, IP address
(6)Location Information
Purpose: Broad geographic targeting, advertising delivery, and fraud prevention
Optional (Android / iOS / HarmonyOS):
Coarse geolocation information. The SDK may receive coarse geolocation information (approximately equivalent to latitude and longitude truncated to two decimal places. The SDK does not collect or process precise geolocation for hyper-local targeting.
Disclaimer
The exact categories of information collected by the Pubeasy SDK may vary depending on the SDK configuration, the developer's implementation, the device, the operating system, and the permissions granted by the end user.
2.System Permissions
To support advertising services and ensure stable functionality, the Pubeasy SDK may request or rely on certain system permissions:
iOS (Optional):
- NSUserTrackingUsageDescription: Used for advertising delivery and anti‑fraud purposes.
Android (Optional):
- ACCESS_WIFI_STATE: Retrieves Wi‑Fi status to update online advertising service strategies.
- WRITE_EXTERNAL_STORAGE & READ_EXTERNAL_STORAGE: Store and access ad assets for app install campaigns
- REQUEST_INSTALL_PACKAGES: Support ad-related app installations
- INTERNET: Network communication for online ad services
HarmonyOS (Required):
- ohos.permission.INTERNET: Required for internet access
- ohos.permission.GET_NETWORK_INFO: Required for network information access
These permissions are requested only after the user has agreed to the Privacy Policy and the developer triggers the relevant SDK features.
3.Developer Responsibilities
Developers integrating the Pubeasy SDK must:
- Clearly disclose SDK data collection in your app’s privacy policy
- Obtain all legally required end-user consents before initializing the SDK
- Integrate and operate the SDK in accordance with the latest version of the Pubeasy Privacy Policy and SDK Data Collection Notice
- Ensure compliance with applicable data protection and privacy laws
Learn More
For full details of our data processing practices and user rights, please refer to the Pubeasy Privacy Policy.