Responsible Official: VP for Development & University Relations
Administering Division/Department: ACE (Donor Records System)
Effective Date: April 01, 2004
Last Revision: March 29, 2007
To ensure that requests to update or provide information in the development database (“ACE”) on constituents are from an approved third party.
Any third party, external to the faculty and staff of Emory University, who requests to update or provide constituent information in the development database (ACE).
The Office of Development and Alumni Relations takes every measure to protect and secure constituent information in its files and in ACE in accordance with the policies of Emory University and other governing sources.
These procedures should be followed when updating information from third parties, or when requests are received from third parties to obtain information on constituents of Emory University.
- Requests for updating information in ACE may be taken over the telephone if you are able to identify the caller; but in the course of doing so, you may not release to the caller information contained in the system.
- If you are not familiar with the caller, verify degree, parent name and past address information stored in ACE. If you are unable to verify this information, and are not familiar with the caller, a better alternative for updating information is to direct the caller to the Alumni Website (http://www.alumniconnections.com/emory) so he or she can securely update the information.
- Non-alumni also can update their information online at http://www.alumni.emory.edu/bio/addressform.cfm
- If the web is not an option for the requestor, ask him/her to update the information in writing to the Office of Alumni and Development Records. They make sure the information is verified and updated accordingly.
ACE: Constituent records database, Advancement Community at Emory.
Subject Contact Phone Clarification of Policy Benjamin Tompkins 404.727.8073 email@example.com Clarification of Policy Untra Randle 404.727.9461 firstname.lastname@example.org
No previous versions of this policy were found.