Data Privacy and Auditability

End-to-end developer runbook

1. Step 1 - Confirm the API area: Identify the product area, route module, endpoint path, and consumer before writing or calling code.
2. Step 2 - Read the endpoint contract: Check method, auth, parameters, response, errors, side effects, and related docs.
3. Step 3 - Prepare authentication and input: Use the right session, bearer token, webhook secret, or internal header. Validate body and query data before sending it.
4. Step 4 - Make the request: Call the endpoint from the correct origin and environment. Keep credentials and secrets out of logs.
5. Step 5 - Verify response, side effects, and records: Confirm status code, response shape, database records, external side effects, and audit evidence.
6. Step 6 - Add tests, docs, and handoff notes: Update route inventory, consumer notes, and certification checks before depending on the change.

Data classes

1. Action 1 - Identify sensitive records: Attendee identity, registration, payment, staff, volunteer, report, ban, social-link, media, and event operation records.
2. Action 2 - Limit fields: Return only what the caller needs for the workflow.
3. Action 3 - Preserve actor evidence: Mutations should retain who changed the record and why when the domain requires accountability.
4. Action 4 - Keep side effects traceable: Email, Discord, Telegram, Google Wallet, and deployment side effects need enough evidence for support and incident review.