Report on Data Subject Requests
Published: July 1, 2025
Updated: July 1, 2025
This report is being provided in accordance with our obligations under the California Consumer Privacy Act (CCPA). In some circumstances other jurisdictions may be included depending on how the measurements were taken. As such, this report is inclusive of requests made by consumers, including those in California.
Note: These metrics reflect requests from June 1, 2024 to May 31, 2025.
Unity Account Information
Note:
- Outstanding requests are requests that have not been processed at the time these metrics were pulled in early June. We. The most typical reason fulfillment has not been completed is that the request requires further authentication.
- Unfulfillable requests are due to the requestor providing insufficient or inaccurate data to fulfill the requests or no responsive data was identified.
Vivox
Note:
- Outstanding requests are requests that have not been processed at the time these metrics were pulled in early June. We. The most typical reason fulfillment has not been completed is that the request requires further authentication.
- Unfulfillable requests are due to the requestor providing insufficient or inaccurate data to fulfill the requests or no responsive data was identified.
Parsec
Note:
- Outstanding requests are requests that have not been processed at the time these metrics were pulled in early June. We. The most typical reason fulfillment has not been completed is that the request requires further authentication.
- Unfulfillable requests are due to the requestor providing insufficient or inaccurate data to fulfill the requests or no responsive data was identified.
Speedtree
Note:
- Outstanding requests are requests that have not been processed at the time these metrics were pulled in early June. We. The most typical reason fulfillment has not been completed is that the request requires further authentication.
- Unfulfillable requests are due to the requestor providing insufficient or inaccurate data to fulfill the requests or no responsive data was identified.
Passport
Note:
- Outstanding requests are requests that have not been processed at the time these metrics were pulled in early June. We. The most typical reason fulfillment has not been completed is that the request requires further authentication.
- Unfulfillable requests are due to the requestor providing insufficient or inaccurate data to fulfill the requests or no responsive data was identified.
Grow (including Unity Ads & Analytics, Tapjoy Offerwall, ironSource Ads)
* Deletion requests were part of opt-out count until the end of 2024. This year’s access requests include deletion requests from June-December 2024, while deletion requests include only those requests received January-May 2025.
Note:
- Outstanding requests are requests that have not been processed at the time these metrics were pulled in early June. We. The most typical reason fulfillment has not been completed is that the request requires further authentication.
- Unfulfillable requests are due to the requestor providing insufficient or inaccurate data to fulfill the requests or no responsive data was identified.
Supersonic
Note:
- Outstanding requests are requests that have not been processed at the time these metrics were pulled in early June. We. The most typical reason fulfillment has not been completed is that the request requires further authentication.
- Unfulfillable requests are due to the requestor providing insufficient or inaccurate data to fulfill the requests or no responsive data was identified.
Websites
** Number of Requests Received derived from per-day opt-in rate.
Note:
- Outstanding requests are requests that have not been processed at the time these metrics were pulled in early June. We. The most typical reason fulfillment has not been completed is that the request requires further authentication.
- Unfulfillable requests are due to the requestor providing insufficient or inaccurate data to fulfill the requests or no responsive data was identified.
Struckd
Note:
- Outstanding requests are requests that have not been processed at the time these metrics were pulled in early June. We. The most typical reason fulfillment has not been completed is that the request requires further authentication.
- Unfulfillable requests are due to the requestor providing insufficient or inaccurate data to fulfill the requests or no responsive data was identified.