What is the meaning of mail in the CCPA (California Consumer Privacy Act of 2018)? The CCPA states that under section 1798.130(2) customers can request their data BY_MAIL OR BY ELECTRONIC MEANS as the customer chooses. However NOWHERE on any website can I find a button or form to demand information via physical mail and on top of that this is economically infeasible for businesses that are small g frm. Is everyone non-compliant mr or am I getting something wrong? I am talking about ip logs mainly here.
You're misreading the law. You need to keep reading the section you referenced (emphasis added): The disclosure...shall be made in writing and delivered through the consumer’s account with the business, if the consumer maintains an account with the business, or by mail or electronically at the consumer’s option if the consumer does not maintain an account with the business Thus, the option to have the disclosure sent by mail only applies to consumers who do not have an account with the business. Since presumably a large number of sites only maintain personal information for users with accounts, such sites need not provide a mail option. Further, it doesn't say there needs to be a button: you just need the ability to say you'd like it mailed to you in the request somehow, and then they need to comply when you do.
Residents agree that the receipt of mail by any individual not listed as a Resident or Occupant in this Agreement at the Leased Premises shall be proof of occupancy of that individual and a violation of this Agreement. I assume that the lease states that only the listed individuals can reside in the unit. Maybe they think that this says that receipt of mail by an unlisted person is a further violation of the lease, I don't think that is clearly enough stated that the courts would agree that receiving mail is itself a violation of the lease. Instead, it seems to be intended to say something about an existing clause – you can't have other people living there. The courts would look at the requirements of the lease, and ask "did you comply"? The question of whether you did a certain thing is a question of fact that has to be resolved in court. However, the revised lease language does not state that all mail must be addressed to Johnny Johnson – it only addresses receipt by a person not on the lease. You are (apparently) on the lease, so you may receive mail there. Nothing in the lease controls how such mail can be addressed. If you receive mail addressed to Tommy Thompson, your defense is that you received the mail, and you are on the lease, so you will not have violated the new clause.
So I can block children under 13, but I can't tell them that? You can tell them after they fail, you cannot tell them on the asking screen. Then what is the correct way to block children under 13 to access my website and still comply with COPPA? I agree with you that it is odd that they recommend using a cookie but they do!* So you have a entry page with a simple question, "Please indicate your age" and then block based on the response. That's it. Note that the rule is neutral. This means that you do not need to disguise your purpose or try to trick people into entering their correct age. *I think that what is happening here is that any parent who wants to complain to their legislator can be met with the response, "If your kid is so sneaky that they are using different computers to lie about their age what do you want us to do about it?" The fact is, this scheme keeps innocent kids from seeing stuff they shouldn't; the sneaky ones are going to find a way.
If person A deletes their account would that mean that person B no longer can view the email sent by person A? No. Person B's inbox implies overriding legitimate grounds that limit person A's &quot;right to be forgotten&quot;. See article 17.1.(c) of the GDPR. Furthermore, item 2 of article 17 is not applicable because the email service did not make A's personal data public. The email service merely sent to B the record with which A unequivocally addressed B. This means that the email service does not even need to notify B regarding A's request for erasure. All the email service needs to do is remove A's account pursuant to A's request.
Maybe not. The ICO says that The right of access enables individuals to obtain their personal data rather than giving them a right to see copies of documents containing their personal data. It might be valid to interpret the DPA / UKGDPR in a way that the relevant personal data undergoing processing in their system is the existence of the letters, but that you are not entitled to a copy of the letters. This is in line with the purpose of the right to access, that you can check what data they are processing about you and whether it is correct. If that argument holds and the data subject insists on receiving a copy of the letters, it might be legitimate to charge them a fee for these copies. But in practice: The data controller might not make this argument and just hand over the copies. It is worth a try. A right to access founded in data protection might not be the only way to receive a copy of these materials. If the letters are relevant for legal proceedings, they could perhaps be requested during the disclosure process.
The basic requirements for the effectiveness of valid legal consent are defined in Article 7 of the GDPR and specified further in Recital 32. There is no form requirement for the consent, so using a button is not a problem. However, I do not think the MailChimp-button you reproduce as an example is good enough. It asks for a blanket consent to stuff that is buried in MailChimp's “Anti-spam Policy &amp; Terms of Use”. But according to the GDPR, what the data subject consent to can’t be buried in the ToU – it must spelled out in clear, plain language. Requests must be granular, asking for separate consent for separate types of processing. “When the processing has multiple purposes, consent should be given for all of them” (Recital 32). Blanket consent, as used by MailChimp, is not allowed. The other clear requirement from the GDPR is that opt-in is mandatory. Pre-ticked and opt-out buttons are explicitly banned: “Silence, pre-ticked boxes or inactivity should not therefore constitute consent” (Recital 32). ‘No’ must become your data default, but if the user chooses to opt-in by clicking a button, this is valid consent. The MailChimp-button complies witrh this. The GDPR also requires you to keep a records of the consents given (so make that part of the user profile), and to withdraw consent at any time &ndash; so you make make provisions for that as well in your implementation of consent.
Your basic regulatory umbrella for anything that stores, transmits or interacts with any private health information or health IT systems is Health Information Privacy | HHS.gov, as well as state authorities. There are severe penalties at the federal and state level for non-compliance and privacy breaches, and many other agencies - such as the DEA, state health departments, insurance companies - would have to be involved in testing and certification of such a App. You will simply not be able to distribute the App on Google or iTunes without their approval, and those distributors will not approve a App that has not been strictly vetted for privacy and HIPAA compliance. In order to distribute such as App - with a TOS that assures personal privacy and shields you from liability (if possible) - you will need to spend hundreds of thousands of dollars on legal representation for compliance. As an example, see ohwilleke's answer to What kind of lawyer should I seek to understand compliance requirements for processing credit cards?
Are my assumptions correct? Yes, this is precisely the sort of thing that would fall under the purview of "the purposes of the legitimate interests pursued by the controller or by a third party", as it fundamentally enables you to deliver the service to the data subject, and its also difficult to argue that "such interests are overridden by the interests or fundamental rights and freedoms of the data subject" given its a fundamental part of delivering the service before any consent can be given. Its not the intention of the GDPR to solely require a direct relationship between the data controller and data subject, its intention is to allow the data subject to control more of the relationship than they did previously - in some cases, that control remains with the data controller, which is why not all of the lawful basis for processing rest on consent. So long as you ensure that the CDN provider has a relevant privacy policy and is identified as a data processor in your privacy and data policy then you are good to go. In my mind, this is similar to the issue of how the data subjects packets get to you from their computer - we aren't including all of the network providers who carry the packets between the data subject and the processor (despite the fact that those providers will have access to much of the same information as the CDN, such as IP address, source, destination etc), even though in many cases we don't know that information (for example which route it will take over the internet). The only difference here is that as the data controller, you know about the CDN and can include it in your policies, so you should.