Privacy Policy

Basic Principles
1. Absolutely NO PID (Personally Identifiable Data) is to EVER be made publicly available on this Web Site. All PID MUST be protected from direct view by either being password-protected or posted in “private” postings (only visible to logged-in site visitors).
  To be specific, we will consider PID to include, but not be limited to:
  1. Personal names
    This will include all personal names, even nicknames and/or first names only. ALL trusted servants MUST be identified ONLY by their title.
  2. Gender
  3. Race
  4. Religion
  5. Political Affiliation
  6. Nationality
  7. Ethnicity
  8. Physical Characteristics (Including disabilities)
  9. Personal Postal or Street Addresses
    Please note:
    
    This means that subcommittee meetings, events or NA meetings that gather in personal homes cannot be referenced by this site. Business/Church/School, etc. addresses should only be listed in conjunction with a sanctioned NA event.
  10. Personal or Business Email Addresses
    We will use the Web Mail forms for all email, as this prevents the visitor from seeing the email address to which the message is being sent. No email address is to be directly displayed on the Web site, even in hidden or obscured code.
  11. Personal or Business Telephone/Fax Numbers
  12. Individual IP Numbers or DNS names of Visitors’ Hosts
  13. Personal Web Sites
    This will be covered in greater detail in the general site policy. We should not link to any personal Web site. As a matter of basic principle, the Web sites to which we do link will be very heavily restricted.
2. The person to whom the information applies is always considered the owner of that information.
  Even if the information is in our possession, it is considered the property of the person to whom it applies, and should always be considered held in trust; only to be used to help the person to whom it belongs.
3. We should post a privacy policy on our Web site and we should make absolutely sure that we abide by that policy.
  The privacy policy need not be displayed in full; but a link to the policy should be displayed prominently on every page.
4. The SAS Web site will maintain a consistent visual appearance “theme” throughout the entire site. Any page with this “theme” should abide by this privacy policy. Absence of this “theme” can be construed as a page that does not abide by this policy.
Privacy of SAS Members
1. The anonymity and privacy of all SAS members should be stringently guarded.
  All SAS members should be referenced by title only, and any contact should be provided by the “generic” Email addresses controlled by the SASOS. Under no circumstances should contact information for any addict ever be provided unless by their explicit written permission. Even in such a case, we should never post that information on a Web page. We should provide it privately on a case-by-case basis. All members that give permission to have their information released should be made aware that once the information has left our control, it may be made available to anyone the recipient chooses.
2. Domain Registration
  We should not place any SAS member information on the registrar database, as it is a completely public database.
Privacy of Our Visitors
1. Technical Issues
  1. Cookies
    1. What is a Cookie?
      Cookies are files that are given to Web Browsers by Web sites to track user preferences and to “shortcut” future visits to Web pages. When a user views a Web page, the server has the option of receiving a “Cookie” that was previously placed on the user’s Browser. The server may also “give the Browser a Cookie”, to be returned by that Browser the next time that the user visits the Web site.
    2. Site Cookies
      We use several cookies to help enhance the usability and power of the site. The site does not require them, but the map-based meeting search will not operate unless you have cookies enabled. No third-party cookies are given by this site (commonly delivered by applications and shared tools).
      We use Google Maps. Embedded Google Maps do not currently give cookies on the maps we display. However, they will read cookies placed from the regular maps.google.com site.
      1. AJAX_Aware
        This is a session cookie that is used to tell the server a bit about the capabilities of your browser, so we can deliver the content best suited to it.
      2. dbx-linkmeta
        This is an internal blog engine cookie.
      3. dbx-pagemeta
        This is an internal blog engine cookie.
      4. dbx-postmeta
        This is an internal blog engine cookie.
      5. nacc_cleantime
        This stores your Cleantime Calculator preferences.
      6. nameetings
        This stores your permanent NA Meeting Search preferences.
      7. nameetings_temp
        This is a session cookie that stores your temporary NA Meeting Search preferences.
      8. wordpresspass_XXXXXXX
        This is an internal blog engine cookie. It stores your login password (only relevant to authorized trusted servants). It may be persistent or a session cookie (if “Remember Me” is checked, this cookie will be persistent).
      9. wordpressuser_XXXXXXX
        This is an internal blog engine cookie. It stores your login ID (only relevant to authorized trusted servants). It may be persistent or a session cookie (if “Remember Me” is checked, this cookie will be persistent).
      10. wp-postpass_XXXXXXX
        This is an internal blog engine cookie. It stores passwords for password-protected posts.
  2. Scripting
    The site uses advanced techniques that leverage the latest JavaScript technologies. It will work without scripting, but the Cleantime Calculator and map-based meeting search will not operate without scripting enabled.