AA Website Privacy & Anonymity Checklist

Checks

• No public full member names or member rosters.
• Review photos/faces for anonymity and consent.
• No attendee tracking.
• Review analytics, third-party fonts, embeds, scripts, pixels, maps, video players, and chat widgets for privacy impact.
• Clarify who owns/monitors public email and phone contacts.
• Keep secrets outside web root and source code.
• Use HTTPS and basic security headers.
• Backups exist and restoration has been tested.
• Public wording does not imply AAWS endorsement.
• Trademark/logo usage has been checked against current guidance.
• Meeting information has an owner and review schedule.
• Handoff documents contain paths/processes, not passwords.

Website handoff

Never put secrets here. Do not enter: plaintext passwords, API keys, SSH private keys, registrar recovery codes, database passwords. Say where a secret is kept, not the secret.

Domain/registrar location

Hosting provider/location

Repository or server path

Backup process

Renewal dates

Public contact ownership

Meeting-list update process

Known open issues

Next review date