Search Unity

  1. Improved Prefab workflow (includes Nested Prefabs!), 2D isometric Tilemap and more! Get the 2018.3 Beta now.
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice
  4. Want to see the most recent patch releases? Take a peek at the patch release page.
    Dismiss Notice

Is Everyplay COPPA compliant?

Discussion in 'Unity Everyplay' started by ludei, Sep 21, 2017.

  1. ludei

    ludei

    Joined:
    Mar 6, 2016
    Posts:
    5
    We have customers that are sensible to the COPPA (Children's Online Privacy Protection Rule) compliance so we want to know if the Everyplay SDK is COPPA compliant as we have seen several requests sending device's information right after initializing the SDK.

    Thanks!
     
  2. ludei

    ludei

    Joined:
    Mar 6, 2016
    Posts:
    5
    @ullatussimo do you have any idea about the Everyplay COPPA compliance? We have some clients doing apps for kids that need to make sure this is the case to include Everyplay in their builds.

    Thanks!
     
  3. Nkon

    Nkon

    Unity Technologies

    Joined:
    Jun 12, 2017
    Posts:
    29
    Hi there!

    Just initializing the SDK will not send any personal information. The information sent includes technical capabilities of the device, which allows our service to determine whether the device is capable of recording replays.

    Whether the application is COPPA compliant depends on the actual implementation. If the users are known to be under 13, no personal information of them should be saved. This means FaceCam for example shouldn't be used.

    Cheers,
    Niko
     
  4. ludei

    ludei

    Joined:
    Mar 6, 2016
    Posts:
    5
    Thanks @Nkon! That's ok for us, we are not using FaceCam so I guess we are safe. Our concern was mainly for the initial requests when initializing the SDK as we were seeing lots of information being sent (ie. deviceId). But for your words I think we are safe.

    Thanks!