[26022] in resnet
Network registration data retention policies
daemon@ATHENA.MIT.EDU (Jose Valdez)
Tue Mar 8 13:57:14 2011
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------000107050507030607040705"
Message-ID: <4D767B66.7000309@stanford.edu>
Date: Tue, 8 Mar 2011 10:54:30 -0800
Reply-To: Resnet Forum <RESNET-L@listserv.nd.edu>
From: Jose Valdez <jvaldez@stanford.edu>
To: RESNET-L@listserv.nd.edu
This is a multi-part message in MIME format.
--------------000107050507030607040705
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Hi,
I am curious to know what, if any, data retention policies that some of
you may use with regard to network registration information. This is of
course heavily influenced by the degree of granularity of information
that you may keep on network registrations, such as residence, room
number and contact information. If you require users to register each
academic year, do you keep year-to-year data, or is each new year's
registration completely separate from previous year's registrations.
This of course assumes that registrations are done on a per-device basis
and not a larger per-user basis that includes multiple devices, if that
assumption is wrong, I would love to hear how you manage user data. If
you have data retention policies, what motivated those policy
decisions? Were they internal decisions based on how long you thought
the information might be useful, etc.? As a related question, do you
publish a defined privacy policy specific to network registration where
you detail your data retention policies? If not, do you rely on a
higher level university policy, or is there no formal policy? Thank you.
Best,
Jose Valdez
--
Jose Valdez
Network Administrator
Academic Computing Services, Stanford University
Phone: (650)384-9065 | Fax: (650)725-4685
___________________________________________________
You are subscribed to the ResNet-L mailing list.
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
--------------000107050507030607040705
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff">
Hi,<br>
<br>
I am curious to know what, if any, data retention policies that some
of you may use with regard to network registration information.
This is of course heavily influenced by the degree of granularity of
information that you may keep on network registrations, such as
residence, room number and contact information. If you require
users to register each academic year, do you keep year-to-year data,
or is each new year's registration completely separate from previous
year's registrations. This of course assumes that registrations are
done on a per-device basis and not a larger per-user basis that
includes multiple devices, if that assumption is wrong, I would love
to hear how you manage user data. If you have data retention
policies, what motivated those policy decisions? Were they internal
decisions based on how long you thought the information might be
useful, etc.? As a related question, do you publish a defined
privacy policy specific to network registration where you detail
your data retention policies? If not, do you rely on a higher level
university policy, or is there no formal policy? Thank you.<br>
<br>
<br>
Best,<br>
Jose Valdez<br>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<title></title>
Jose Valdez<br>
Network Administrator<br>
Academic Computing Services, Stanford University<br>
Phone: (650)384-9065 | Fax: (650)725-4685<br>
<br>
</div>
</body>
</html>
___________________________________________________
You are subscribed to the ResNet-L mailing list.
<p>
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
--------------000107050507030607040705--
