#For Unity Analytics they provide
1 messages · Page 1 of 1 (latest)
Hey @bitter rock
PIPL consent is slightly different from GDPR / CPPA, it is Opt In, all other legislations except PIPL are assumed to be opt-in-by-default, explicit-opt-out.
The Analytics.Instance.CheckForRequiredConsents method essentially performs a Geo-IP lookup to identify if the player is playing from China and thererfore needs to go through an explitic opt-in workflow and provide their consent for PIPL compliance. Note, if the SDK cannot make the CheckForRequiredConsents check or if it returns a PIPL value, then the SDK will not send any Analytics events until consent is provided.
The UGS Analytics - Data Privacy & Consent documentation contains more detail and some code examples for various scenarios
https://docs.unity.com/analytics/en/manual/ManagingDataPrivacy
Please note that it is your responsibility as the developer to provide the correct consent flows for the regions and stores where your game is available.
@limber perch thank you for providing that, I did read that page and got it set up. Is there anyway to do the geoIP call ourselves?
The geo-IP call is something that is done on the server, based on the IP address the client device contacts the server from. So, you would need to setup your own server based Geo-IP checking and I'm not sure what additional benefit that would bring.
There will be native, platform specific SDK methods that can be used to get location, but they may have other permission and reliability issues.
Can I ask why you would want to do the check yourself?
I was just curious in case in the future these different policies per region change, right now in it's current state it seems that it's either pipl or it's anything else, but in case any other policy changes how they should work then it would be important to call their location, is what I was thinking