# Data We Collect
“We collect information about your game to tailor advertisements to your players.”
This page outlines the data we collect to ensure our policy of transparency for players and developers. Data will never be used to personally identify players.
# Frameplay Platform
During the sign up process on our platform (opens new window) we request details about your game configuration. This allows us to serve advertisements that match your audience.
- ESRB Rating (Entertainment Software Rating Board)
- White Listed Advertisement References
# User Device Data
Frameplay collects non-personal data about your game and users to tailor advertisements and provide the best experience.
- Public IP Address
- System Language
- Device ID
- Device Model
# Advertising ID
Advertising ID. Also known as Mobile Advertising Identifier (MAID), and Identifier for Advertisers (IDFA)
Frameplay utilizes the device advertising ID serve more relevant advertisements to the player.
Users must opt-in to personalized advertising via a privacy framework.
# Android
To request access the advertising ID on Android devices, you must declare the AD_ID permission in the AndroidManifest file:
<uses-permission android:name="com.google.android.gms.permission.AD_ID"/>
Read more about Google's Advertising ID (opens new window) policy.
# iOS
To request access to the advertising ID on iOS devices (ios 14+), you must implement the AppTrackingTransparency (ATT) framework.
The FrameplaySDK/Engine/Editor/XcodePostProcess.cs script contains an example build hook that creates a NSUserTrackingUsageDescription and adds it to the info.plist file when exporting your project.
Read Unity's full ATT guide here (opens new window), and more information on Apple's User Privacy and Data Use (opens new window).
# Apple Privacy Manifest File
Apple is introducing a privacy policy for including privacy manifest files (opens new window) in new and updated applications targeted for iOS, iPadOS, macOS, tvOS, and visionOS platforms on the App Store.
The privacy manifest file (PrivacyInfo.xcprivacy) lists the types of data (opens new window) your applications, or any third-party SDKs, packages, and plug-ins collect, and the reasons for using certain Required Reason API (opens new window) categories.
Frameplay's privacy manifest only defines data categories that Frameplay collects by default
# Default Frameplay collected data categories:
| Data type | Purpose | Tracking | Linked |
|---|---|---|---|
| Device ID | - Third-Party Advertising | YES | YES |
| Advertising Data | - Third-Party Advertising | YES | NO |
| Other Diagnostic Data | - App Functionality - Analytics | NO | NO |
| Other Data Types | - Third-Party Advertising | NO | NO |
# The Frameplay SDK uses two APIs that must be declared in the manifest:
| API type | Reason | Notes |
|---|---|---|
| Disk Space | E174.1 | Write or delete file on-device, per documentation |
| User Defaults | CA92.1 | Access info from same app, per documentation |
# User Consent
Some regions may require user consent before Frameplay can serve personalized advertisements. For example, a user within the EEA requires consent under General Data Protection Regulation (GDPR). Games monetizing with Frameplay advertisements in this region must integrate a compliant Consent Management Platform (CMP) to collect consent from the user.
Typically when a user does not consent to, or opts out of data collection and processing under a privacy regulation (for example GDPR, CCPA, or PIPL), this will limit the data available about your users and will likely impact your revenue.
For more more information see IAB Europe TCF (opens new window) and the iAB's approved list of CMPs (opens new window).