282 Matching Annotations
  1. Mar 2020
    1. Most Google users will have a preferences cookie called ‘NID’ in their browsers. A browser sends this cookie with requests to Google’s sites. The NID cookie contains a unique ID Google uses to remember your preferences and other information, such as your preferred language (e.g. English), how many search results you wish to have shown per page (e.g. 10 or 20), and whether or not you wish to have Google’s SafeSearch filter turned on.

      They seem to claim (or hope that their description will make you think) that ‘NID’ is only used for storing preferences, but if you read further down, you see that it's also used for targeting.

      These should be separate cookies since they have separate purposes, and since under GPDR we have to get separate consent for each purpose of cookie.

    1. The problem is that even if the visitor is not watching the video or interacting with it, in any capacity, YouTube still collects and stores data on them. Not cool.This is done using cookies that are placed on the user’s browser the moment they load a webpage with a YouTube video embedded in it. These cookies are used to track users, serve targeted ads (Google’s bread and butter), and add info to user’s profile. Yes, they have profiles on everyone.
    1. A majority also try to nudge users towards consenting (57%) — such as by using ‘dark pattern’ techniques like using a color to highlight the ‘agree’ button (which if clicked accepts privacy-unfriendly defaults) vs displaying a much less visible link to ‘more options’ so that pro-privacy choices are buried off screen.
    1. While we recognise that analytics can provide you with useful information, they are not part of the functionality that the user requests when they use your online service – for example, if you didn’t have analytics running, the user could still be able to access your service. This is why analytics cookies aren’t strictly necessary and so require consent.
    1. By default, your users will be asked for their consent on each of your domains and sub domains since Cookiebot treats domains and sub domains separately. By enabling the Bulk Consent feature, however, your users will only be prompted for a consent the first time they visit any one of your websites (and again after 12 months when the consent needs to be renewed).
    1. Very few solutions include all of the GDPR required features like: 1) Enabled prior consent. 2) Clear and specific information about data types and purpose of the cookies. 3) Full documentation of all given consents. 4) The possibility for users to reject superfluous cookies and still use the website. 5) The possibility that users can withdraw their consent whenever they want. Cookie solutions that don’t have those features are not GDPR compliant.
    1. Some people prefer not to allow cookies, which is why most browsers give you the ability to manage cookies to suit you.Some browsers limit or delete cookies, so you may want to review your cookie settings and ads settings. In some browsers you can set up rules to manage cookies on a site-by-site basis, giving you more fine-grained control over your privacy. What this means is that you can disallow cookies from all sites except those that you trust.In the Google Chrome browser, the Tools menu contains an option to Clear Browsing Data. You can use this option to delete cookies and other site and plug-in data, including data stored on your device by the Adobe Flash Player (commonly known as Flash cookies). See our instructions for managing cookies in Chrome.
    1. haven’t consent tools been around for a while? Sort of! Ever since May 2011, when the EU Cookie Directive went into effect, most EU sites have added cookie notification bars to the top or bottom of their pages. This prompted many third-party solutions to pop-up, including WordPress plug-ins and the leading tool from Silktide. These tools are still around, and many sites continue to use them under the GDPR. However, these solutions were built for the older law, and the GDPR is much more specific about requiring explicit opt-in consent. Most of those older tools don't provide this, nor do they integrate with downstream ad partners, paving the way for the more sophisticated CMPs.
    1. Note that the scope of personal data is truly broad, which makes processing complex and tricky. So, even though, for instance, you employ anonymization in Google Analytics to get rid of all information that falls under this category, you’re still in a catch-22 situation. This is because GA stores a visitor online identifier in a cookie, and under the GDPR that file constitutes a piece of personal data. That means you still need to obtain consent from visitors to process their data.
    1. we make it easy to implement using our Consent by Geolocation feature that auto-identifies the location of the website visitor and applies the correct consent notice and behavior based on the visitor’s current location. For example, simply add PreferenceChoice Cookie Consent and Website Scanning to your website, and the functionality of your consent notice will automatically update to display a CCPA-compliant consent notice to a visitor in Los Angeles, and a consent notice in compliance with ePrivacy and GDPR to a visitor in London.
    1. Do I need a CMP? Short answer: Probably yes. Long answer: If your company is based in the EEA (European Economic Area) or if you are dealing with customers/visitors from this area and show them advertising, it is very likely that you will collect and/or process personal data such as IP-addresses. Therefore, according to GDPR, you need to make sure that the visitor is informed and you need to ask the user for consent. In order to do this you will need a CMP.
    1. This cookie consent notification is just a tool for getting consent, it’s not capable of managing your tracking tags because every website and every GTM container is unique, therefore there is no universal solution. As a result, you will have to manually update all your tracking tags with additional firing rules.
    2. Configuring OneTrust’s cookie consent solution is just half of the task. Your tracking scripts (like Google Analytics, Google Adwords, etc.) will still continue working as they always did unless you import my GTM recipe and then reconfigure all of your tracking tags. Yup, there’s a lot of manual work waiting ahead.
    1. CookiePro’s Cookie Consent module provides the ability to decide whether to respond to a DNT browser request by automatically blocking any category of cookies where it is configured to do so. To use this function, go to the relevant cookie group(s), and set the status to Do Not Track. The result is that cookies will be Active, unless the user has turned on Do Not Track, in which case they will be set to Inactive, with the ability for the user to override this in the cookie settings.
    1. If you wish to disable cookies, you may do so through your individual browser options. More detailed information about cookie management with specific web browsers can be found at the browsers’ respective websites.
    1. You need to provide the ability for users to look at cookies individually, so they need to be listed (and that can be quite a lot of work in major systems). You’re allowed to define some cookies as “necessary for the correct functioning of this product”, usually cookies that store session related data. After all, if a user opts out of those, they can’t meaningfully use the web site, or that part of the site.But you have to be honest about it. You can’t, for example, define marketing or analytic cookies as necessary, and you have to allow users to opt out from them. Those don’t stop the site from functioning, it just reduces the data you can collect about site use.
    1. There’s not even a consensus on whether or not cookie alerts are compliant with European law. In May, the Dutch data protection agency said these disclosures do not actually comply with GDPR because they’re basically a price of entry to a website.
    2. Most companies are throwing cookie alerts at you because they figure it’s better to be safe than sorry When the GDPR came into effect, companies all over the globe — not just in Europe — scrambled to comply and started to enact privacy changes for all of their users everywhere. That included the cookie pop-ups. “Everybody just decided to be better safe than sorry and throw up a banner — with everybody acknowledging it doesn’t accomplish a whole lot,” said Joseph Jerome, former policy counsel for the Privacy & Data Project at the Center for Democracy & Technology, a privacy-focused nonprofit.
    1. that permission must be freely obtained. Ergo, a free choice must be offered.So, in other words, a “data for access” cookie wall isn’t going to cut it. (Or, as the DPA puts it: “Permission is not ‘free’ if someone has no real or free choice. Or if the person cannot refuse giving permission without adverse consequences.”)
    1. Is that enough to be GDPR compliant? No. My understanding is that to be compliant you would wait to initialize the analytics until after you had received the user's explicit consent. Even then you would need to be able to turn off analytics again if the user later revoked their consent.
    1. To further illustrate this point, imagine that the ability to run cookies is a room, the cookie management solution is the door and the consent is the act of rotating the door handle; you can only enter through the door into the room if the door handle is rotated (the act of giving consent). In this example, if you’ve entered the room it can only be because the door handle was rotated and, therefore, your presence in the room is sufficient proof of this fact.
    1. if the cookie is installed by your own site, then the consumer can decide ON THEIR OWN BROWSER, if they want to send it. Cookies are a data signal YOU ARE SENDING FROM YOUR OWN COMPUTER. If you don’t want to voluntarily submit a cookie, just turn it off.
  2. Feb 2020
    1. Social media research ethics faces a contradiction between big data positivism and research ethics fundamentalism. Big data positivists tend to say, ‘Most social media data is public data. It is like data in a newspaper. I can therefore gather big data without limits. Those talking about privacy want to limit the progress of social science’. This position disregards any engagement with ethics and has a bias towards quantification. The ethical framework Social Media Research: A Guide to Ethics (Townsend and Wallace, 2016) that emerged from an ESRC-funded project tries to avoid both extremes and to take a critical-realist position: It recommends that social scientists neither ignore nor fetishize research ethics when studying digital media.Research ethics fundamentalists in contrast tend to say,You have to get informed consent for every piece of social media data you gather because we cannot assume automatic consent, users tend not to read platform’s privacy policies, they may assume some of their data is private and they may not agree to their data being used in research. Even if you anonymize the users you quote, many can still be identified in the networked online environment.
  3. Nov 2019
  4. Aug 2018
  5. Jul 2018
    1. Where the data principal withdraws consentfor the processing of any personal data necessary for the performance of a contract to which the data principal is a party, all legal consequences for the effects of such withdrawal shall be borne by the data principal.

      How does it serve public interest and individual rights to hold people liable for the withdrawal of consent to the processing of their personal data?

  6. Sep 2017
  7. Mar 2017
    1. Communicate with students, staff, and others whose data are collected about their rights, including the methods used to obtain consent to use the data for predictive analytics and how long the information will be stored.

      Seems to completely skim over the issue of obtaining consent for predictive analytics...."Oh yeah, make sure that you have consent"

  8. Feb 2017