Module 12 Activity

Scenario

Before this goes anywhere near real users, work out what it collects and what you promise about it.

What you build

A logging and retention design with redaction on write, per-field retention, a privacy notice checkable against the code, and a completed deployment checklist.

Steps

1. Print a realistic log line and mark every field carrying personal data.
2. Redact structured identifiers on the way in, and state plainly what redaction does not catch.
3. Set retention per field: metrics and versions indefinitely, content on a short limit.
4. Write the privacy notice from the code and your provider's terms, including whether content is used for training.
5. Confirm the stated deletion path corresponds to a mechanism that exists.
6. Work through the deployment checklist and list what is outstanding.

Evidence to hand in

• The annotated log line.
• A redacted example and a statement of what is missed.
• The per-field retention table.
• The privacy notice with its source for each claim.
• The deletion mechanism.
• The checklist with outstanding items.

Review checklist

• Redaction happens before writing, not after.
• Retention differs by field.
• The training claim comes from the provider's terms, not intentions.
• The deletion path is implemented, not just stated.
• The rollback path restores the prompt version too.

Mark complete