We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

GDPR and CCPA – how are you handling it?

Home Forums General Questions GDPR and CCPA – how are you handling it?

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #45251
    xeon
    Customer

    Hi everyone,
    I have implemented a few V3D applications and each time it seems there are new privacy laws and requirements. For some clients, I have to make things CCPA compliant, others GDPR compliant.

    As our experiences become more elaborate, data-dependent, reliant on cookies etc., I was wondering what other developers here are doing in their apps to maintain compliance.

    Currently, I use a cookie manager that is triggered on the initial load. Wondering if anyone else is using anything to stay compliant that they could recommend.

    Alternatively, if your app is being embedded into another site, and you are not implementing your own data management to comply what methods are you using with the primary site to maintain compliance?

    Xeon
    Route 66 Digital
    Interactive Solutions

    #45802
    Avier3D
    Customer

    Probably this does not help you with an answer, but ultimately WebGL and WebGPU will override a significant piece of today’s web, and this power control game from big actors will make even less sense. Good luck! ;-)

    #45816
    xeon
    Customer

    Using WebGL or WebGPU in commercial applications you have to follow all the applicable laws of and regulations regarding commercial websites and data handling. Its independent of the underlying technology. The laws are there so users of a website have the right to delete their personal data. In the vast majority of applications, we write in WebGL, there is no need to collect personally identifiable information but there is a need for storing cookies. By law, every site has to manage cookies and explain what they are used for when the website is displayed in countries that follow GDPR and CCPA. So if you use Google tracking or other tracking to monitor performance or you use cookies to store states of a settings panel. You have to allow the user to dissociate or delete that information with the IP and or name.

    Currently, we are using the parent window to handle this but as websites turn into pure WebGL solutions…the problem becomes more difficult to manage for commercial use.

    Xeon
    Route 66 Digital
    Interactive Solutions

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.