Search Unity

  1. Get all the Unite Berlin 2018 news on the blog.
    Dismiss Notice
  2. Unity 2018.2 has arrived! Read about it here.
    Dismiss Notice
  3. We're looking for your feedback on the platforms you use and how you use them. Let us know!
    Dismiss Notice
  4. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  5. Improve your Unity skills with a certified instructor in a private, interactive classroom. Learn more.
    Dismiss Notice
  6. ARCore is out of developer preview! Read about it here.
    Dismiss Notice
  7. Magic Leap’s Lumin SDK Technical Preview for Unity lets you get started creating content for Magic Leap One™. Find more information on our blog!
    Dismiss Notice
  8. Want to see the most recent patch releases? Take a peek at the patch release page.
    Dismiss Notice

Official Raw Data Export - GDPR Changes

Discussion in 'Unity Analytics' started by ap-unity, May 23, 2018.

Thread Status:
Not open for further replies.
  1. ap-unity

    ap-unity

    Unity Technologies

    Joined:
    Aug 3, 2016
    Posts:
    1,002
    We are making some changes to our Raw Data Export (RDE) process to comply with the General Data Protection Regulation (GDPR) going into effect this month.

    We will be removing Personally Identifiable Information (PII) from Raw Data Export. This will affect both the export process from the Analytics dashboard and requests made through the RDE API. (We will get the Manual updated as soon as possible.)

    PII Removed

    The following fields will be removed. If you have any processes that rely on these fields, they will need to be updated to accommodate the new schema.

    remote_ip
    The IP address that the session was played from
    Dataset: All

    adsid
    Advertising Id. On iOS, collected when Unity Ads is enabled. On Android, all the time
    Dataset: DeviceInfo

    deviceid
    A unique device identifier. (This varies by platform and Unity version.)
    Dataset: All Datasets, DeviceInfo

    Timeframe

    These changes are planned to be released on June 4, 2018.

    Custom Events

    We have always discouraged sending PII in Custom Events. This policy has not changed. We cannot offer any legal advice as to what would qualify as PII for your application. We can provide some examples of data that is clearly PII and should not be sent to our Analytics system:
    • Email Addresses
    • Phone Numbers
    • Social Security Numbers
    This is not an exhaustive list. We recommend reaching out to your legal counsel with any questions about your application’s data collection.

    If you believe you have sent any PII in a Custom Event, please reach out to us and we will discuss how to handle this situation: dpo@unity3d.com
     
Thread Status:
Not open for further replies.