Folks,
I need to drill and tap a new hole. I've now got a suitable tap - M12x1.75 and an HSS drill bit of 10mm. According to all the online charts I can find, I should be using a 10.2mm drill bit. Will the 0.2mm difference mean certain failure and death?
Or should I just crack on with the 10mm?
As you can tell, this is the first time I've ever tapped a thread :)
Thanks!
<quote? I have now posted up – several times – various links (and the GDPR text itself) stating how their Personal Data definitions clearly include both LOCATIONAL and ADDRESS information;</quote>
You're looking at it backwards. To qualify as personal data, whatever data you're processing has to relate to an identifiable individual living Human. Once the Human has been identified THEN the location, address, inside leg measurement etc becomes personal data.
Locational Data of a Hot Spot, a Range Rover, a House or a Whale is irrelevant to GDPR. None of those things are humans and therefore their Locational Data is not personal data.
LPGC's first example clearly did not include the identity of any individual therefore: Not Personal Data.
My opinion on what is PD is based on training given to me by solicitors and barristers who specialise in Data Protection law.
Also, online threats just make you look a bit foolish.
But you still haven't answered your homework :)
HINT: GDPR applies equally to BT FON and Google Maps. The fact that one service is free is irrelevant when considering Data Protection
davew wrote:
One of the advantages of having revealled BT's WiFi disadvantages is (enraged) folks sending me numerous other examples, like Virgin proudly stating how in their " Free Hotel WiFi service " they 'Data Harvest' us too (albeit with our permission/consent); Moral ? Don't consent.....
" Customer analytics
Users register before they can access your WiFi – it’s a potential gold mine of data for your marketing.
Get their consent and you’ll get their dwell time, location analytics and user demographics too "
Now this is the sort of shit that GDPR was designed to counter. Yes, the correct answer is to withhold consent.
GDPR brought in some very powerful tools for the consumer. You are allowed to withdraw your consent at any point*. You are allowed to demand that your data be deleted. Most importantly, it's no longer legal to make consent to marketing analytics a requirement for provision of a service (don't quote that, I'd need to check the exact wording) which is why you get these massive cookie consent lists with different levels of consent for different types of cookie.
The cookies that make the site run can be compulsory (under Legitimate Interest) but those that track your purchasing preferences and/or are used for big data analytics and ad preferences have to be optional. If you read the Fair Processing Notice of those sites they HAVE to explain what each level of data is being used for. This is all GDPR and it has real teeth.
I'd be interested to know how Virgin are getting hold of User Demographics. IME that's either a rough guess based on device type (are you using a brand new iPhone or el-cheapo Android tablet) or it's a really deep dive into tracking cookies and/or social media. Smelly.
*which is a real pain in the arse for the processor who has to create a mechanism that allows the removal of the data subject from whatever systems they originally consented to be part of.
Dave, sorry but you can't keep misleading people like this.
In LPGC's examples.
Not necessarily a contravention of GDPR. A Ferrari dealer could very easily process the personal data of its customers in a lawful manner, as long as they abide by the terms of GDPR. A lawful basis could be "legal obligation". Should there be a recall on a model of Ferrari the dealership would need the contact details of their customers to inform them of that recall. No consent would be required for this lawful processing.
If the dealership were to publish or share the list they'd be in breach. If they were to use the list for direct marketing they'd very likely be in breach (depending on their Fair Processing Notice) and also of PECR, just for fun.
To address an earlier post
<quote> Please do read the information in the links I provided as LOCATION is part of the Personal Data definition of course: It is not just about the name of a person: It is getting a little irritating having to repeat these things as patently folks are not actually reading the links, just repeating their (possibly misguided) interpretations of the GDPR </quote><br>
This is a clear misunderstanding of the law. The location being provided is that of a Hot Spot and not an individual identifiable person. I can see no way in which the location of a hotspot identifies an individual and therefore this information is not Personal Data. GDPR is only relevant when personal data is being processed.
Dave, BT Fon Maps show the locations of one specific service - BT Hotspots. If you think that is a breach of GDPR, what do you think of Google Maps?
They show the location of nearly all addresses in the world, the location of many services (restaurants, shops, schools, hospitals etc) and they even let the public add photographs and reviews of these locations and services.
Surely this is an even more outrageous breach of GDPR?
Your starter for ten: "How are Google not in breach of GDPR due to their provision of the Google Maps service?"
I've got enough hassle with the vehicles I've got. If they were fine I'd be tempted myself - but I never seem to get to the point where I've got everything working, especially when it's dark in the evenings and I'm call two weekends a month.
Right now I need to change U Joints on the The Duchess and investigate why she drops her backside down overnight. Then there's there's the radius arm bushes because she still steers like a whale.
The Jeep needs a new clock spring, which would have been super simple if I could only get the damn steering wheel off. I've just bought a tap and die set so I can re-thread the holes in the wheel to an M9 to give me something better to grip with the puller. The original M7 thread pulled straight out on one side and drilling through so I could use nuts behind the wheel just left the tool flopping sideways under tension because the nuts weren't stable enough for me to use a bar.
Type 2 fun! :)
Tonight I'll have a romantic Valentine's day trying to get the wheel out of my Jeep and then hopefully the rough running/voltage issues it displayed at the weekend will just be a one-off. Otherwise I'll be hunting bad ground connections for a couple of weeks :(
I've been threatening to cycle to work (it's 7 miles) and now the weather seems to be improving I'm tempted!
A blue 01 on coils with dodgy HG, broken radio and satnav and no mileage listed.
Still, looks quite nice in the photos!
I just put this up because it's about 5 minutes from me if anyone wants me to go have a look.
I've got a copy of OB's disk - but very soon after I started using it my satnav lost the ability to remember where it is. I'm not sure if it's the disk or the antenna - I suspect the almanac data isn't right but maybe it's just me.
I should be able to dig out the iso if you like.
Dave,
I don't work for BT, but I am qualified in Data Protection law.
From your Fitzpatrick link I see nothing that supports your theory and nothing that contradicts mine, indeed - from your link:
You need to look at your posts and strip them back to only the points that can be argued from the GDPR/DPA 2018.
I'm sorry, this was fun but now I'm bowing out. If you want to take BT to court it's your choice. My final piece of free legal advice is that you should think very carefully before entering into a short but expensive campaign against a company with limitless resources. Especially when you're wrong.
All true, but a property address is not personal data.
Hi Pete and welcome :)
I'm about an hour south of you down the A19 - and jealous of your Holland and Holland!
Best of luck!
I'm hoping to get all four wheels in the air, undo the worst propshaft and take it way to smack the UJs out with a socket and hammer once I've removed the circlips.
I've only bought two UJs so far but I've begged 10 minutes on the 4 post lift at work this lunchtime so I can have a look see. I need to do more than two I'll order some UJs this afternoon. Sadly LRDirect have been very slow shipping my stuff but I should be able to next day another set from somewhere if required.
So far I have assembled
JAckstands x4 (2x2ton 2x6 ton)
Metric/Imperial socket set with extensions etc
Set of Circlip Pliers
Grease
Paint Marker
Blue Locktite
Hammer :)
I need to borrow my neighbours Jack.
The UJs nuts and bolts are still on the way - due for delivery today.
Lets hope it stops pissing down!
That's a funky looking thing but is it much better than a 3/8th socket and an extension? £11 is a lot of brass in Yorkshire 😀
I've just been informed that her Ladyship is away 23/24th so I'm out for both the last two weeks in March. Bogus. Any chance of April 6th/7th?
BrianH wrote:
Its not particularly difficult to get the propshaft off providing you have tools to fit the bolts ok, and once its off you can work on replacing the joints without being under the car, so it shouldn't take you too long with any luck.
Brian is there anything special required for the propshaft bolts beyond a socket and breaker bar?
I'm going with just UJs, and I've bought one of those paint marker pens so I can mark up the prop to keep it in the original alignment. I'm hoping that I'll get them sorted and the thing back on its wheels in one weekend :)
23/24 works for me, 30/31 doesn't
Glad you're busy - are you in a reachable timezone?
Just had a thought. If BT wanted to automate the mapping procedure AND make it GDPR tight they'd just use a BT FON app on the mobile device to connect to BT Fon networks. If this reported hotspot locations back to the BT HQ using all the great data you can get from a phone (GPS, WiFi signal strenght, Connection Speed) then their process would not only be easy and automated but it would be trivial to demonstrate that speedhub locations were nothing to do with Personal Data.
I've never used BT FON but that's how I'd design it if I was King of the World.
I think the crucial word in your understanding of the situation is "our" in "our locations"
As far as I can see they're not revealing YOUR location but the location of "A" speedhub. There's no visible link between the ID of the speedhub and the name of the customer which means that personal data is not being revealed.
Is it being processed? Well that's very hard to determine without knowledge of BT's internal systems, but for PD to be processed in the provision of BT FON there would need to be a link between the ID of the speedhub and the customer. Even then BT could pseudonymise or fully anonymise the data without any great effort. In fact, it's probably far harder to maintain an accurate list of who has what router than it is to simply ship the next box in the pile and be done with it.
How is the location of the speedhubs calculated for the maps I hear you ask? Well it could be simply a list of addresses of customers with speedhubs. There's no need to the customers names to be included in that list. A list of addresses isn't PD unless it's linked to names. (Even a name isn't necessarily PD, especially if it's a common one). It could be phone numbers for which BT are likely to know the locations, but even then a landline isn't going to be personal data.
Of course, even if PD is being used to provide the BT FON service (and this is only suspected and not proven) there are still mechanisms that allow BT to lawfully process that PD without consent. Consent is only one lawful basis for processing PD and BT only need demonstrate that one basis applies for their processing to be legal.
Clearly Vital Interest and Public Interest aren't going to be relevant but Performance of a Contract could easily be (especially if BT undertake to provide the BT FON service in their contract with you) and Legitimate Interest looks likely to me. For Legitimate Interest they just have to say that what they are doing is legal and doesn't infringe on the data protection rights of the subject (and for infringement to apply PD would have to be processed unlawfully during that operation).
So, I'm pretty sure that you won't be able to get BT to change their TnC on any legal basis. Of course if you raise enough public awareness you might get them to concede something - maybe a more public set of controls over BT FON on speedhubs - on a Public Relations basis.
Dave, I've just looked at the BT FON coverage map and it does not contain personal data. As I said, an address is not personal data. The location of a hotspot is not personal data. The data on that map does not identify any living person so it is not personal data and therefore GDPR does not apply.
You may object to BT FON being enabled by default, but nothing in the GDPR will help you mount a legal challenge as it does not apply.
<quote> OK, look at BT's local coverage map (as I suggested) and you can most certainly identify individual house/s (as those kids did to my neighbour, who is ill and needed his sleep etc; Thus BT seriously impinged on his health by their FON OPT IN 'default': That on its own is enough to fall foul of those principles). </quote>Sorry, that's just wrong. The map identified the location of a hotspot, it didn't reveal the identify of your neighbour therefore GDPR is not relevant. Was it a shitty situation for your neighbour? For sure. Should BT make it clear/easy for customers to disable BT FON if they wish? I would say so. But that doesn't mean you can use GDPR rules on consent to change the situation. GDPR is only relevant in cases of processing personal data and this is not such a case.
davew wrote:
Is your address and the fact that you are a BT Broadband Customer 'personal' information: I would say so !
Your address on its own is not personal data - it does not identify a person, it identifies a house.
The fact that a BT router is in the vicinity is not personal data (even if you can work out which property it is in)
Taken together, your name, your address and the fact that you are a BT Broadband customer would be personal data, but I'm struggling to see how you would link the three together from a BT FON hotspot. That's my main issue with your line of argument.