Is this privacy statement from a solicitors in line with GDPR? I'm in the process of buying a house and have paid for a survey to be done on the property. I have received a contract from the solicitor who will be conducting the survey for me and will provide me with a report of the findings. I found something interesting in regards to how they will use my personal information. The contract states: We will use the personal information you provided to us: - To supply the report to you - to process any payment for the report; and - If you agree to this during the order process, to give you information about similar products that we provide, but you may stop receiving this at any time by contacting us. My question is focusing on the third bullet point. It's hard to decipher because I don't think the sentence makes sense anyway (copied exactly how the letter says), and it's possible there is a typo in there, but it sounds like they are saying I will have to opt out of their marketing, rather than opting in like the new GDPR law states. At the back there is also a check list of things you agree to, such as I have read and understood the guide, understood that I cannot cancel my contract after the 'cooling period', and "I agree to the privacy terms stated above". There is no mention of marketing. Would that mean that I am agreeing to marketing, as per the third bullet point? There is no tick box for "I do not wish to be added to your marketing". Should I contact the company and request a new contract? I am in the UK.
The line they'll rely on for GDPR compliance is the first part of that sentence - "If you agree to this during the order process", which suggests that there will be a separate request to opt in to marketing communications at some other time in the process. Check any order documents. There's likely to be a tick box or similar on at least one. If that implies opting out rather than opting in there may be grounds to argue with that under GDPR, but there's nothing in the quoted text that suggests a problem.
I think this shows a misunderstanding of the meaning of the GDPR. A data subject has the right to demand information, correction, deletion etc. about some of their data held by some institutions, depending on the legal basis for the data processing. One John Smith does not have the right to see the data of any other data subject named John Smith, and he cannot even demand to know if there are other John Smiths in the database. The data controller has to make reasonable steps to ensure that an individual who seeks account information is in fact the individual who is the data subject. In the case of an email, that's usually easy -- if John Smith can access the mail account jsmith@sample.org, one can assume that he is the John Smith who opened the account. If not, then not. If the data controller has the birthplace and birthdate in their records, they can possibly match that against some government-issue identity document, too, but why would they have that data?
No, a company cannot suspend your GDPR rights – contracts can't override the law. Your rights as a data subject apply as long as your personal data is being processed. However, there is no requirement in the GDPR that they fulfill your data subject rights through a self-service mechanism like a “download my data” button. They can require you to use another support channel. (But Google offers infamously bad support.) In some cases, the service may legitimately decide that they cannot give you access to the data, for example if they believe that you are not the actual data subject (e.g. if they think that you hacked the account). The right to access must not adversely affect other people (Art 15(4)). If they have doubts about your identity, they can require further information to verify you (Art 12(6)). If your requests are excessive or unfounded (if you are spamming them), they can also turn down the requests (Art 12(5)).
To do so I used some images and Gifs which may be under copyright but since I don't earn money for myself and there is no company backing me I was hoping that there is some protection for private persons like me who just want to showcase the project. Sorry. If your website is public facing (i.e. not password protected and available only to family and close friends), you need to follow copyright law. There is no exception to copyright just because a project is run by an individual for non-commercial purposes. I am also insecure about the GDPR regulations since I give users the ability to create an account and try it out. Your profile says you're in the EU. Then you need to comply with the GDPR. Is there any way to protect me against greedy lawyers and companies? Could I write something like: "This website is a peace of art" and save myself with arguments like "artistic freedom" or "free speech"? Nope. A controversial website run by Peter Sunde had at one point a "free speech" disclaimer (similar to the one you propose) posted. However, Sunde did never use this defense in court: Finnish court slaps Peter Sunde with €350k fine. If he had shown up in court, I am pretty sure the court would have told him that such a disclaimer has no legal merit. The only protection that will make you completely safe is to adhere to the law.
The GDPR only require explicit (hard) consent if you use the cookie to store personal data. Given the conditions you cite, the data you store is not personal data, so this cookie does not require consent. In theory, someone having access to both session cookie and "analytics cookie" could relate the two, but that is highly non-trivial. You may have to do DPIA to demonstrate that this is non-trivial, or that you have mitigation in place to mitigate staff abusing such access. But provided things are as you say, the "analytics" cookie does not require consent.
Overview As described, only the last of these seems to be compliant ways of obtaining consent, and indeed even that is not fully compliant, although features not described might make it so. However, if there is a lawful basis for processing PI other than consent, under GDPR article 6, then there is no need to obtain consent at all, and doing so in an improper way is irrelevant. However storage of or access to local information (such as cookies) requires consent unless such storage or access is &quot;strictly necessary&quot; for providing a service which the user has requested. Relevant GDPR Provisions GDPR article 6 lists six possible lawful bases for processing personal data. These are, in summery: (a) consent; (b) processing is necessary for the performance of a contract or to takwe steps requested by the Data Subject; (c) necessary for compliance with a legal obligation; (d) to protect the vital interests of the data subject or another person (e) or the performance of a task carried out in the public interest (f) legitimate interests of the Controller The other provisions cited here apply only to PI for which the lawful basis is consent. GDPR article 7 reads: (2) If the data subject’s consent is given in the context of a written declaration which also concerns other matters, the request for consent shall be presented in a manner which is clearly distinguishable from the other matters, in an intelligible and easily accessible form, using clear and plain language. Any part of such a declaration which constitutes an infringement of this Regulation shall not be binding. (3) The data subject shall have the right to withdraw his or her consent at any time. The withdrawal of consent shall not affect the lawfulness of processing based on consent before its withdrawal. Prior to giving consent, the data subject shall be informed thereof. It shall be as easy to withdraw as to give consent. When assessing whether consent is freely given, utmost account shall be taken of whether, inter alia, the performance of a contract, including the provision of a service, is conditional on consent to the processing of personal data that is not necessary for the performance of that contract. GDPR Recital 32 reads: Consent should be given by a clear affirmative act establishing a freely given, specific, informed and unambiguous indication of the data subject’s agreement to the processing of personal data relating to him or her, such as by a written statement, including by electronic means, or an oral statement. This could include ticking a box when visiting an internet website, choosing technical settings for information society services or another statement or conduct which clearly indicates in this context the data subject’s acceptance of the proposed processing of his or her personal data. Silence, pre-ticked boxes or inactivity should not therefore constitute consent. Consent should cover all processing activities carried out for the same purpose or purposes. When the processing has multiple purposes, consent should be given for all of them. If the data subject’s consent is to be given following a request by electronic means, the request must be clear, concise and not unnecessarily disruptive to the use of the service for which it is provided. GDPR Recital 42 reads: ... in particular in the context of a written declaration on another matter, safeguards should ensure that the data subject is aware of the fact that and the extent to which consent is given. In accordance with Council Directive 93/13/EEC a declaration of consent pre-formulated by the controller should be provided in an intelligible and easily accessible form, using clear and plain language and it should not contain unfair terms. For consent to be informed, the data subject should be aware at least of the identity of the controller and the purposes of the processing for which the personal data are intended. Consent should not be regarded as freely given if the data subject has no genuine or free choice or is unable to refuse or withdraw consent without detriment. GDPR Recital 43 reads: ... Consent is presumed not to be freely given if it does not allow separate consent to be given to different personal data processing operations despite it being appropriate in the individual case, or if the performance of a contract, including the provision of a service, is dependent on the consent despite such consent not being necessary for such performance. Analysis I will review each of the scenarios in the question in turn. Scenario 1: not allowing [a user] to use the site until the user clicks Accept. No options, just an &quot;Accept&quot; button. This does not constitute freely given consent, because: The giving of consent is not &quot;clearly distinguishable from the other matters, in an intelligible and easily accessible form, using clear and plain language&quot; (Art 7(2)). There appears to be no way to withdraw consent (Art 7(3)). It appears that the provision of a service (use of the site) is conditional on consent not needed for that service (Art 7(3)). Consent is not informed and unambiguous (Recital 32). The use has not been informed of the extent to which consent is given (Recital 42). The subject has not been made aware of purposes of the processing (Recital 42). the data subject has no genuine or free choice (Recital 42). There is no provision for separate consent to be given to different personal data processing operations. (Recital 43). Scenario 2: A banner stating that &quot;By browsing the site you accept the conditions&quot;. Just an &quot;x&quot; to close the banner. Using the site is allowed while the banner is displayed. This does not constitute freely given consent, because: Consent was not &quot;given by a clear affirmative act establishing a freely given, specific, informed and unambiguous indication of the data subject’s agreement to the processing of personal data&quot; (Art 7(2)). The giving of consent is not &quot;clearly distinguishable from the other matters, in an intelligible and easily accessible form, using clear and plain language&quot; (Art 7(2)). There appears to be no way to withdraw consent (Art 7(3)). Consent is not informed and unambiguous (Recital 32). The use has not been informed of the extent to which consent is given (Recital 42). The subject has not been made aware of purposes of the processing (Recital 42). the data subject has no genuine or free choice (Recital 42). There is no provision for separate consent to be given to different personal data processing operations. (Recital 43). Scenario 3: A banner with an &quot;Accept&quot; (and possibly &quot;Reject&quot;) button. No other options. Site navigation is allowed while the banner is displaying. This does not constitute freely given consent, because: The giving of consent is not &quot;clearly distinguishable from the other matters, in an intelligible and easily accessible form, using clear and plain language&quot; (Art 7(2)). There appears to be no way to withdraw consent (Art 7(3)). Consent is not informed and unambiguous (Recital 32). The use has not been informed of the extent to which consent is given (Recital 42). The subject has not been made aware of purposes of the processing (Recital 42). There is no provision for separate consent to be given to different personal data processing operations. (Recital 43). Scenario 4: A banner with an &quot;Accept&quot;, &quot;Reject&quot; and also a &quot;Settings&quot; options where the user can fine tune the way his data is being used by the site. This might constitute freely given consent, provided that: a document is displayed or linked to that describes the kinds of PI that will be processed, and the purposes of the processing; There is some easy and obvious manner to withdraw consent, and to change the individual choices on what to consent to, after the banner has closed, or on any subsequent visit to the site; The consent section of the settings dialog must be clearly distinguished from other sections that do not deal with consent; Just where the lines must be drawn between &quot;different personal data processing operations&quot; which each requires the possibility of separate consent is not yet fully clear. And again, if the site or service does not store or otherwise process PI, or has a lawful basis for doing so other than consent, and does not store or access local information, it need not obtain consent at all, and the question of what constitutes freely given consent becomes irrelevant. Of course many sites do depend on consent as the lawful basis for much of their activity.
There are a few different grounds under which PII can be handled. Perhaps the most discussed at the moment of GDRP introduction is consent, because of the wave of consent-seeking. But there are a number of other grounds. "Necessary for contract execution" is a trivial one, to deliver a pizza you'll need an address. The relevant ground for sanctions lists is also pretty obvious in hindsight, you may process PII in order to comply with legal obligations. Note that this is still an integral part of the GDPR, not an exception to the GDPR. That means you need to apply all the basic GDPR rules. You need to explicitly store where you got the PII from, for which purpose, and you need to document how you're using it. Note that this might be hard - why do you need to store this data? Why can't you just check the list as the moment it's relevant? The GDPR for a large part depends on you justifying your actions, not just in hindsight but already up front.
Doing this is OK according to the GDPR and other European laws. The relevant bit is GDPRs rules for Lawfulness of processing, and in particular Article 6 (1)b, which says that it is legal to do this if processing is necessary for the performance of a contract to which the data subject is party or in order to take steps at the request of the data subject prior to entering into a contract; In your particular case, signing up for using your app is "entering into a contract" and it is the data subject who has requested to use your app that is subject to this processing.