taler-merchant-demos

Python-based Frontends for the Demonstration Web site
Log | Files | Refs | Submodules | README | LICENSE

privacyaction.html (6256B)


      1 <!--#include virtual="/server/header.html" -->
      2 <!-- Parent-Version: 1.96 -->
      3 <!-- This page is derived from /server/standards/boilerplate.html -->
      4 <!--#set var="TAGS" value="essays cultural evils" -->
      5 <!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
      6 <title>Protect Postal Privacy
      7 - GNU Project - Free Software Foundation</title>
      8 <!--#include virtual="/philosophy/po/privacyaction.translist" -->
      9 <!--#include virtual="/server/banner.html" -->
     10 <!--#include virtual="/philosophy/ph-breadcrumb.html" -->
     11 <!--GNUN: OUT-OF-DATE NOTICE-->
     12 <!--#include virtual="/server/top-addendum.html" -->
     13 <div class="article reduced-width">
     14 <h2>Protect Postal Privacy</h2>
     15 
     16 <address class="byline">by Kathleen Ellis</address>
     17 
     18 <div class="comment">
     19 <p>The Free
     20 Software Foundation does not lead this campaign, but we support it by
     21 spreading the word and hope that you do too.</p>
     22 </div>
     23 
     24 <h3>Background</h3>
     25 <p>
     26 The United States Postal Service has submitted a rule to Congress
     27 proposing that all Commercial Mail Receiving Agencies (CMRAs) must,
     28 as of June 24, 1999, collect significant personal information from
     29 all clients using their services. This would certainly affect
     30 anonymous mail transactions, and could put millions of CMRA
     31 customers in danger.  Any CMRA or CMRA customer who refuses to
     32 comply with this regulation would effectively lose their right to
     33 receive mail.</p>
     34 <p>
     35 The proposed regulation (published in the Federal Register on March
     36 25, 1999) requires that CMRAs collect names, home addresses,
     37 telephone numbers, and photo ID information about each customer.  If
     38 the CMRA customer classifies themselves as a business, they must
     39 surrender the information on that box holder to anyone who asks for
     40 it.  CMRAs are widely used by survivors of domestic violence,
     41 undercover law enforcement officials, and stalking victims in order
     42 to conceal their locations and identities from people who could
     43 cause them harm.</p>
     44 <p>
     45 The USPS proposal was intended to help cut down on mail fraud, a
     46 practice that costs consumers millions of dollars every year.
     47 However, experts state that the Postal Service's proposal will not
     48 serve as a deterrent to criminals.  &ldquo;It will be a simple process
     49 for those with financial means to rent homes, apartments, office
     50 space, or the executive suites available in most major metropolitan
     51 area,&rdquo; says Postal Watch's website.</p>
     52 <p>
     53 Congressman Ron Paul has introduced House Joint Resolution 55, which
     54 would effectively revoke the Postal Service's new regulations
     55 regarding CMRAs, but the resolution needs your support in order to
     56 ensure that this insidious assault on consumer privacy is defeated.</p>
     57 
     58 <h3>What you can do</h3>
     59 
     60 <ol>
     61   <li>Contact your Representative and urge them to co-sponsor HJR 55.</li>
     62   <li>Write or call members of the House Appropriations Committee and
     63        inform them about this issue, and urge them to pass the
     64        resolution.</li>
     65   <li>Send written comments about this issue to the US Postal Service
     66        before July 9, 1999 to:
     67        <address>
     68        Manager, Administration and FOIA United States Postal Service
     69        <br />
     70        475 L'Enfant Plaza SW, Room 8141 Washington, DC  20260-5202
     71        </address></li>
     72 </ol>
     73 
     74 <h3>More information</h3>
     75 For further information, see the following web pages:
     76 
     77 <ul>
     78   <li>Privacy.org [in 2021: <a href="https://www.epic.org/">epic.org</a>]</li>
     79   <li><a href="https://www.congress.gov/bill/106th-congress/house-joint-resolution/55">
     80        H.J.Res.55&mdash;106th Congress</a></li>
     81 </ul>
     82 </div>
     83 
     84 </div><!-- for id="content", starts in the include above -->
     85 <!--#include virtual="/server/footer.html" -->
     86 <div id="footer" role="contentinfo">
     87 <div class="unprintable">
     88 
     89 <p>Please send general FSF &amp; GNU inquiries to
     90 <a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>.
     91 There are also <a href="/contact/">other ways to contact</a>
     92 the FSF.  Broken links and other corrections or suggestions can be sent
     93 to <a href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>.</p>
     94 
     95 <p><!-- TRANSLATORS: Ignore the original text in this paragraph,
     96         replace it with the translation of these two:
     97 
     98         We work hard and do our best to provide accurate, good quality
     99         translations.  However, we are not exempt from imperfection.
    100         Please send your comments and general suggestions in this regard
    101         to <a href="mailto:web-translators@gnu.org">
    102         &lt;web-translators@gnu.org&gt;</a>.</p>
    103 
    104         <p>For information on coordinating and contributing translations of
    105         our web pages, see <a
    106         href="/server/standards/README.translations.html">Translations
    107         README</a>. -->
    108 Please see the <a
    109 href="/server/standards/README.translations.html">Translations
    110 README</a> for information on coordinating and contributing translations
    111 of this article.</p>
    112 </div>
    113 
    114 <!-- Regarding copyright, in general, standalone pages (as opposed to
    115      files generated as part of manuals) on the GNU web server should
    116      be under CC BY-ND 4.0.  Please do NOT change or remove this
    117      without talking with the webmasters or licensing team first.
    118      Please make sure the copyright date is consistent with the
    119      document.  For web pages, it is ok to list just the latest year the
    120      document was modified, or published.
    121      
    122      If you wish to list earlier years, that is ok too.
    123      Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
    124      years, as long as each year in the range is in fact a copyrightable
    125      year, i.e., a year in which the document was published (including
    126      being publicly visible on the web or in a revision control system).
    127      
    128      There is more detail about copyright years in the GNU Maintainers
    129      Information document, www.gnu.org/prep/maintain. -->
    130 
    131 <p>Copyright &copy; 1996, 2021 Free Software Foundation, Inc.</p>
    132 
    133 <p>This page is licensed under a <a rel="license"
    134 href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
    135 Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
    136 
    137 <!--#include virtual="/server/bottom-notes.html" -->
    138 
    139 <p class="unprintable">Updated:
    140 <!-- timestamp start -->
    141 $Date: 2021/09/05 09:34:35 $
    142 <!-- timestamp end -->
    143 </p>
    144 </div>
    145 </div><!-- for class="inner", starts in the banner include -->
    146 </body>
    147 </html>