Everyone leaves knowing how to keep keys, data and users safe, and the team agrees the checks every tool passes before it goes live.
Read Days 65, 68 and 70 (about five minutes each), or Module 7 on the cheat sheet.
Quick round: from one to five, how sure are you that nothing secret sits in your projects?
Pick one tool the team relies on. Go through the ten checks from Day 70 together and mark each one pass, fail or don't know. Every fail and don't know gets an owner.
Each owner fixes or answers their fail or don't know this week, and uses a fresh-session review to check the result.
Agree the team rule: “Fake data for building. Real data only with a reason.”
Deleting a leaked key from the code and calling it fixed (Day 61). Revoke it first, then clean up.
A whiteboard or shared doc with the ten checks listed, and a timer.
Next session: Module 8 · Shipping. Bring the ten-check results, with what's been fixed since.