Effective August 19, 2026
Outreach CRM Privacy Policy
This policy explains how Savannah Chapter of Democratic Socialists of America Inc. handles information in the Savannah DSA Outreach CRM.
Savannah DSA
The Outreach CRM is operated by Savannah Chapter of Democratic Socialists of America Inc. for chapter organizing, outreach, member engagement, administration, security, and continuity of organizing work.
Questions or requests concerning CRM data may be sent to info@savgadsa.org.
What we receive from Google
For authorized CRM users, the application uses the signed-in user’s primary Google Account email address to identify the user, match that account against Savannah DSA’s authorized-user list, and enforce the user’s assigned application role.
The CRM does not request access to a user’s Gmail, Google Drive files, Google Contacts, Google Calendar, personal Google Sheets, or broader Google profile information.
The application also uses Google Apps Script’s external-request capability so a Savannah DSA-controlled service account can access the CRM’s dedicated Google Sheets datastore. Human CRM users do not grant the application access to their personal Google Sheets data.
Use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Information the chapter may store
Depending on the organizing relationship, CRM records may include names, pronouns, phone numbers, email addresses, Discord names, workplace or school information, preferred contact method, membership and engagement status, assigned organizer, follow-up and interview dates, organizing interests, skills, availability, access or support needs, outreach history, and organizing notes.
Authorized-user records may include Google Account email, display name, chapter role, application role, active status, administrative notes, and login timestamps.
How information is used
CRM information is used for Savannah DSA organizing and administration, including responding to interest in the chapter, assigning outreach, conducting follow-up, coordinating interviews and onboarding, connecting people with chapter work, maintaining application security, and preserving an administrative audit trail.
Savannah DSA does not sell CRM information or provide it to advertisers. Access is limited to authorized chapter users according to application role and organizing responsibilities. Information may be disclosed when required by law or when reasonably necessary to protect the security of the application, its users, or the chapter.
How long information is kept
CRM records are retained only while reasonably necessary for chapter organizing, administrative continuity, security, accountability, or applicable legal obligations. Records that are no longer active may be archived rather than displayed in active outreach workflows.
A person may request correction or deletion of personal information associated with them by contacting info@savgadsa.org. Savannah DSA will review the request and remove or correct information when reasonably possible, subject to security, audit, legal, or recordkeeping needs.
Authorized CRM users may also request removal of their application access. Deactivation prevents further application access while preserving records needed to identify historical administrative actions.
Safeguards
The CRM uses Google account authentication, a Savannah DSA-controlled authorized-user list, server-side role permissions, record-level access controls for organizers, restricted datastore access, and application audit logging. Sensitive values are not intentionally duplicated into the audit log when a field changes.
No system can guarantee absolute security. Savannah DSA limits access and maintains the application to reduce unnecessary exposure of organizing data.
Google services
The CRM is hosted using Google Apps Script and stores its dedicated application datastore in Google Sheets accessed by a Savannah DSA-controlled service account. Google processes information according to the terms and policies applicable to those services.
Source code is maintained in a private GitHub repository. CRM contact records and service-account credentials are not intended to be stored in that repository.
Updates to this policy
This policy may be updated when the CRM, applicable requirements, or chapter practices change. The effective date at the top of this page will be revised when material changes are published.