-
Notifications
You must be signed in to change notification settings - Fork 0
/
resources_compliance_details_app.html
180 lines (137 loc) · 14.3 KB
/
resources_compliance_details_app.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
<!doctype html>
<!--[if lt IE 7]> <html class="no-js lt-ie9 lt-ie8 lt-ie7" lang="en"> <![endif]-->
<!--[if IE 7]> <html class="no-js lt-ie9 lt-ie8" lang="en"> <![endif]-->
<!--[if IE 8]> <html class="no-js lt-ie9" lang="en"> <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en"> <!--<![endif]-->
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>SurveillanceRights</title>
<meta name="description" content="SurveillanceRights">
<meta name="author" content="Faculty of Information, University of Toronto">
<meta name="viewport" content="width=device-width">
<link rel="stylesheet" href="css/style.css">
<link rel='shortcut icon' href='favicon.ico' type='image/x-icon'/ >
<link rel="apple-touch-icon-precomposed" sizes="114x114" href="apple-touch-icon-114x114-precomposed.png">
<link rel="apple-touch-icon-precomposed" sizes="72x72" href="apple-touch-icon-72x72-precomposed.png">
<link rel="apple-touch-icon-precomposed" href="apple-touch-icon-precomposed.png">
<script src="js/libs/jquery-1.7.2.min.js"></script>
<script src="js/libs/modernizr-2.5.3-respond-1.1.0.min.js"></script>
</head>
<body>
<header>
<h1 id="fittext1"><img src="img/veos_logo.png" alt="Camera Watch Logo">SurveillanceRights</h1>
</header>
<!--<nav role="navigation" id="access">
<a class="skip-link icon-reorder" title="Accordian" href="#menu">Menu</a>
<ul id="menu">
<li><a href="index.html">Home</a></li>
<li><a href="app.html">SurveillanceWatch App</a></li>
<li><a href="watching-about.html">Who's Watching You?</a></li>
<li><a href="events-workshops.html">Events</a></li>
<li><a href="blog.html">Blog</a></li>
<li class="active"><a href="resources.html">Resources</a></li>
<li><a href="faq-app.html">FAQ</a></li>
<li><a href="contact.html">Contact Us</a></li>
</ul>
</nav>-->
<div id="main">
<article>
<section>
<h3>Minimal Privacy Compliance Standard for Canadian video surveillance installations</h3>
<p>Draft - February 5, 2013 - Comments welcome</p>
<p>This document specifies minimum privacy compliance standards for video surveillance installations in Canada. It provides the basis for assessing the eligibility of candidates for receiving the <a href="resources_reward_app.html">$100 reward</a> offered “to the first person to bring a minimally compliant private sector installation to [the] attention” of the Surveillance Rights project.<sup>i</sup></p>
<p>This standard is designed to be uniform for all video surveillance installations whether operated by government agencies or for commercial purposes, regardless of location. It is based primarily on the <i>Guidelines for Overt Video Surveillance in the Private Sector</i> posted by the Office of the Privacy Commissioner of Canada, supplemented by provincial guidelines where these exist.<sup>ii</sup> These guidelines are synthesized from the various privacy laws in Canada.<sup>iii</sup> </p>
<p>This specification mainly addresses signage, but following the <i>Guidelines</i>, also considers other aspects of the video surveillance installation that determine minimal compliance.</p>
<h4>Signage</h4>
<p>A video surveillance installation refers to one or more surveillance cameras (and ancillary devices) in close proximity to each other managed together under a common authority. For an installation to be minimally compliant it is necessary, but not sufficient, to post signs informing passersby of the presence of video surveillance in the vicinity. </p>
<p>Signage compliance is considered along three distinct axes:</p>
<ul>
<li><i>Content</i> - what the sign says;</li>
<li><i>Form</i> - how legible the sign is; and,
<li><i>Location</i> - whether the sign is noticeable and readable <u>before</u> one enters the surveilled area.</li>
</ul>
<h5>Content</h5>
<p>A minimally compliant sign should contain the following items:</p>
<ol>
<li>The fact that video surveillance is being conducted in the vicinity.</li>
<li>Whether images are being monitored live, or recorded, or both.</li>
<li>The purpose(s) of the surveillance</li>
<li>The name of the organization(s) responsible for the video surveillance scheme.</li>
<li>The title and contact information for the person in the organization who is responsible for personal information protection. This should include a phone number for a timely response to immediate queries, as well as usual contact details for correspondence (mailing address, email contact, privacy policy URL).</li>
<li>The title of the specific privacy or personal information protection legislation that governs the handling of personal information in this situation.</li>
<li>Contact information for the office of the relevant privacy commissioner.</li>
</ol>
<h5>Form</h5>
<p><img id="infractionnotice" src="img/mincompliantsigntemplate.png" alt="minimally compliant sign template" /></p>
<p>The text of a compliant sign must be clear and visible from a reasonable distance, and the sign itself must be noticeable to the average passer-by, either through size, colour, or other means of drawing attention. In particular, the fact that there is video surveillance should be eye catching and noticeable to normally sighted people from a distance of at least 4 meters. This can be conveyed by a combination of familiar/ standard graphic icons and basic text of sufficient size. </p>
<p>The full required contents of the sign should be normally readable at a distance of 2 meters.</p>
<p>Clearly defined high contrast graphic and text elements should be used, such as are conventional in highway and other safety signage norms.</p>
<p>A sample template for signs compliant with the Content and Form requirements can be found at <a href="http://surveillancerights.ca/resources_compliance_details_web.html" target="_blank">http://surveillancerights.ca/resources_compliance_details_web.html</a></p>
<h5>Location</h5>
<p>Any signage to be compliant must be positioned so that it may be normally noticed and read by individuals prior to entering an area under surveillance, in order that they may avoid the cameras if they so wish. This means sign must be encountered initially in an area <b>not subject</b> to video surveillance, including at all usual entrances to the area under surveillance. Signs should be placed reasonably close to eye level and oriented so as to be readily noticeable by anyone about to enter the surveilled space. For extensive or indeterminately bounded spaces, additional signs should be posted throughout to remind people that they are still under surveillance.</p>
<h4>Other compliance criteria:</h4>
<p>While appropriate signage is a core criterion for compliance, there are a number of other requirements spelled out in the <b>10 things to do when considering, planning and using video surveillance</b> section of <i>Guidelines</i>. These are: </b>
<ol>
<li>Determine whether a less privacy-invasive alternative to video surveillance would meet your needs.</li>
<li>Establish the business reason for conducting video surveillance and use video surveillance only for that reason.</li>
<li>Develop a policy on the use of video surveillance.</li>
<li>Limit the use and viewing range of cameras as much as possible.</li>
<li>Inform the public that video surveillance is taking place.</li>
<li>Store any recorded images in a secure location, with limited access, and destroy them when they are no longer required for business purposes.</li>
<li>Be ready to answer questions from the public. Individuals have the right to know who is watching them and why, what information is being captured, and what is being done with recorded images.</li>
<li>Give individuals access to information about themselves. This includes video images.</li>
<li>Educate camera operators on the obligation to protect the privacy of individuals.</li>
<li>Periodically evaluate the need for video surveillance. </li>
</ol>
<p>For the purposes of the reward, a readily available policy statement (e.g. posted on the organization's website) that documents compliance with these various <i>Guideline</i> items would suffice. In particular, such a statement should at least specify and explain the following:</p>
<ul>
<li>rationale(s) for video surveillance</li>
<li>appropriate limitations of camera viewing range</li>
<li>signage and other public information</li>
<li>procedures and retention schedule for the secure storage and deletion of images</li>
<li>procedures for handling queries and individual image access requests</li>
<li>education program for camera operators and customer contact personnel</li>
<li>periodic re-evaluation of the need for surveillance and specific aspects of implementation </li>
</ul>
<h3>Notes</h3>
<p><sup>i</sup>Surveillance Rights website: <a href="http://surveillancerights.ca" target="_blank">http://surveillancerights.ca</a></p>
<p><sup>ii</sup>“Guidelines for Overt Video Surveillance in the Private Sector”, March 2008, <a href="http://www.priv.gc.ca/information/guide/2008/gl_vs_080306_e.cfm" target="_blank">http://www.priv.gc.ca/information/guide/2008/gl_vs_080306_e.cfm</a></p>
<p><sup>iii</sup>The main pieces of Canadian legislation governing video surveillance privacy for commercial activities, and the offices of the corresponding privacy commissioners are:</p>
<ul>
<li>Alberta: <i>Personal Information Protection Act</i>, S.A. 2003, c. P-65, administered by the Office of the Information and Privacy Commissioner of Alberta <a href="http://oipc.ab.ca" target="_blank">http://oipc.ab.ca</a> </li>
<li>British Columbia: <i>Personal Information Protection Act</i>, S.B.C. 2003, c. 63, , administered by the Office of the Information and Privacy Commissioner for British Columbia <a href="http://oipc.bc.ca" target="_blank">http://oipc.bc.ca</a></li>
<li>Quebec: <i>An Act Respecting the Protection of Personal Information in the Private Sector</i>, R.S.Q. , c. P-39.1, administered by the Commission d'accès à l'information <a href="http://www.cai.gouv.qc.ca" target="_blank">http://www.cai.gouv.qc.ca</a> </li>
<li>Other provinces and federally regulated industries: <i>Personal Information Protection & Electronic Documents Act</i>, S.C. 2000, c. 5, administered by the Office of the Privacy Commissioner for Canada <a href="http://www.priv.gc.ca" target="_blank">http://www.priv.gc.ca</a><br><br>
<ul>
<li>(See <a href="http://www.priv.gc.ca/leg_c/legislation/ss_index_e.asp" target="_blank">http://www.priv.gc.ca/leg_c/legislation/ss_index_e.asp</a> for details and updates)</li>
</ul>
</li>
</ul>
<p>For governmental bodies, the relevant public sector legislation at the federal, provincial/territorial and municipal levels applies. eg for the Government of Canada, it is the <i>Privacy Act</i> 1980-81-82-83, c. 111. </p>
</section>
</article>
<!-- <script> function loadContent() { $("#sidebar").load("sidebar.html"); } </script>
<div id="sidebar"> <script>loadContent()</script> </div> -->
</div> <!-- #main -->
<!-- <script> function loadContent() { $(".footer").load("footer.html"); } </script>
<div class="footer"> <script>loadContent()</script> </div>-->
<script src="js/script.js"></script>
<!-- Responsive Header -->
<script src="js/fittext.js"></script>
<script type="text/javascript">
$("#fittext1").fitText(1.1, { minFontSize: "14px", maxFontSize: '72px' });
</script>
<!-- Google Analytics -->
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-37322083-1']);
_gaq.push(['_trackPageview']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
</script>
</body>
</html>