-----BEGIN PGP SIGNED MESSAGE-----

PrivacyNet Policy, 15 March 1994                   Release Number 003

Welcome to PrivacyNet, a network with special emphasis on the privacy
of the network's users.

This is the official policy document for PrivacyNet, as of 15 March
1994.  Contents are copyright 1993 and 1994 by PrivacyNet
International Association (P.I.A.).  All rights reserved.

GENERAL:

PrivacyNet is an amateur computer communications network, founded on
the principles of privacy.  It is arguably a common carrier in as
much as users of PrivacyNet have a reasonable expectation of privacy
in their communications, and will not be summarily denied access to
the network without just cause or due process.

The official domain name of Privacy Net is privynet.ftn; PrivacyNet
operates in Zone 30.  The official nodelist will be hatched from
30:30/0.0@privynet.ftn with the filename "PRIVLIST.nnn" weekly, or as
changes occur, whichever is less frequent.

PGP-encrypted messages may be sent in any echo (other than network
admin echoes, where they would be mere clutter).

The PRIVATE flag _must_ be permitted in all echoes (same restriction
as above).

It is recommended that individual, public-keys be made available via
Netmail or by file-request with the magic filename: PGPKEY and that
the public-key provided for that request by given a distinctive
filename using part or all of each provider's name and address. For
example, on my system, a file-request of PGPKEY will give BLADEKEY.ASC
to the requesting system. This will avoid duplicate overwriting and
make it easier to track the keys. Using standard magic filenames will
make it easier to find keys and keyrings on different systems.

The PGP and Privacy and encryption related files on each system
should be maintained with a magic filename for file request. PGPFILES
should be set on all participating systems to allow your current
list of Privacy-related files to be picked up at any time. It is
suggested that the actual filename indicate the origin of the list to
avoid confusion and overwriting; for example, a PGP-related files list
for 1:3807/110.0 is named 3807_110.TXT, based on the FidoNet address.

DEFINITIONS:

Network definitions are identical to FidoNet, with the exception that
PrivacyNet is contained entirely in Zone 30.  Such definitions are set
forth in FidoNet Policy 4; they will not be reiterated here.

RESTRICTIONS:

PrivacyNet includes adult-oriented echoes.  No one under the legal age
for access to adult publications, as defined by the local authorities
in the State/Province/Region of the user's BBS, may be given access to
adult echoes.  PrivacyNet assumes no responsibility for any
violations of local ordinances arising from failure of the System
Operator to ensure his users are legally entitled to access.

RESPONSIBILITIES:

1.  It is the responsibility of every user and system operator in
PrivacyNet to respect the privacy of all other users and sysops to the
greatest possible extent.  Users who find that they are able to read
any message which should be flagged as Private should be encouraged to
notify the sender of such message, and the SysOp of the BBS on which
the message is found.  SysOps are encouraged to refrain from reading
private messages, not addressed to them.

2.  Coordinators must make every effort to assist their downlinks to
ensure privacy, and to keep their portion of the PrivList up-to-date.
Each level of Coordinators will arbitrate any disputes which may
arise among their downlinks, with an eye to maintaining the
tranquility of the Net and the privacy of the users.

3.  The ZC will ensure timely dissemination of the PrivList,
arbitrate any disputes which are appealed to him, and designate
persons to fill any positions which are deemed necessary to the
smooth operation of the net, or which become vacant during the tenure
of the persons filling such positions.  At all times, the maximum
possible participation of the members of the network will be sought,
consonant with smooth operation of the network, and approriate
behavior of all involved.

4.  All sysops are responsible for ensuring, to the best of their
abilities, that users meet the legal requirements for adult access in
their local area before granitng access to the adult echoes.  

NET/NODE NUMBERS AND FEEDS:

Any member of PrivacyNet may arrange to get mail feeds from any
Coordinator; it is the Sysop's responsibility to ensure that he has
only one feed, and his Net/Node number will reflect that feed.  In
the event he wishes to change to another source for his mail, a new
Net/Node number will be issued and the old number invalidated.  This
is to ensure that routed netmail will be easily implemented at all
levels of the Net.

It is recommended, but not required, that a new applicant submit his
application to the Net Coordinator from whom he wishes to get his
echoes; this will speed the application process, and simplify adding
the new node to the nodelist.

Net Coordinators should contact their Regional Coordinator to
determine the schedule by which they must submit changes to the
nodelist.

OFFICIAL    1 January 1994      PrivacyNet HQ I, Lake Charles, LA
Latest modication:  15 March 1994

PGP Signature Certificate by Richard C. Tietjens (Captain Blade):


-----BEGIN PGP SIGNATURE-----
Version: 2.3a

iQBVAgUBLYFoPhQluB/A6mujAQEs2QH9GLgcwKDOVNldUXarbefW7Qtgh7xXfdTU
KSq6Q/2DEJomL5B3Mf9Y6CgBqnPvmFwOsGqAecIrwX8V6Dd7Bt2MrQ==
=lXPf
-----END PGP SIGNATURE-----