Striking the Right Balance between Privacy and Public Protect ion

[Dave Bird]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In article <200210251401.PAA00253@clw.cs.man.ac.uk>, Charles Lindsey
<chl@clw.cs.man.ac.uk> writes
>       On Fri, 25 Oct 2002 09:02:43 +0100
>       "Quentin Campbell" <Q.G.Campbell@newcastle.ac.uk> said...
>
>> It has been suggested that comms data requests under 22(4)(a) and
>> 22(4)(b) can be just as intrusive as interception of content. Thus
>> controls on the subsequent dissemination of this information are vitally
>> important.
>
>No, the information received regarding traffic data is nowhere as
>sensitive as the actual content of intercepted messages, and therefore
>there is no need for such high levels of vetting. Indeed, it should need
>no more than the general principle of confidentiality that all public
>servants are expected to observe.

 Really.  So details of your
 (a) health details including sexual health, mental health, and
 material which you choose not to disclose to your employer
 (b) involvement in controversial political causes
 (c) sexual contacts and preferences
 (d) activities such as seeking other jobs or whistle-blowing
 which you have a right to keep from your employer, 
 (e) impending time away from your property so that it
 can be robbed, 
 (f) informing on criminal activity or activities
 preparing to testify,
 (g) other material with opportunities for blackmail, 
 harassment, thieving, etc....

 Can ONLY EVER be detected from content of communications,
 and RARELY OR NEVER just from the numbers called.  For
 example, it would be impossible to check for contact with 
 air-lines and travel agents to target potential empty
 properties for robbery.


 It is astonishing that you think this is so.  


- -- 
   ^-^-^-@@-^-;-^   http://www.xemu.demon.co.uk/
        (..)__u     news:alt.smoking.mooses

       happy as a clam at high tide -. <_" .-._.-.


-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1

iQA/AwUBPbn7E3pGxv7MBb4WEQIX+gCg+YcVJM7Z+nwKWCAehplLKsRJLasAoP0F
dTWZCvKq9WwoHDiloE1P5tcp
=WqI7
-----END PGP SIGNATURE-----