lesson
30 min

Privacy, Personal Data, and Minors

Protect the people whose information flows through your automation, with extra care for anyone under 18.

Objective

By the end of this lesson, you can identify personal data in a workflow, limit what flows into each tool, and apply extra protections for minors.

Personal data

Personal data is any information that can identify a person. Names, phone numbers, emails, home addresses, and photos are personal data. Some personal data is sensitive, which means harm is more likely if it leaks:

  • Health or disability information
  • Immigration status
  • Income, benefits, or housing situation
  • Criminal records
  • Anything about a minor (a person under 18)

Every tool in your automation is another place this data lives. Every AI step sends text to another company's servers. So you ask: does this step need this data at all?

Send the least you need

The rule is data minimization: only send each step the data it needs.

  • The classifier needs the message text. It does not need the phone number.
  • The reminder text needs a first name and a time. It does not need a home address.
  • If a step only needs to know a family has kids, send "has children: yes," not the kids' names and ages.

Before an AI step, remove names, phone numbers, and addresses if the task does not need them. Most tools can drop or replace fields before the AI step runs.

Extra care with minors

Youth programs are some of the best places to save staff time. They also carry the most risk. Use these rules for any workflow that touches people under 18:

  1. Contact goes to the parent or guardian. Automated messages go to the adult on file, not the child, unless your partner's written policy says otherwise.
  2. No youth data in AI steps. Do not send a minor's name, school, photo, location, or personal story to an AI tool.
  3. No photos or faces without written permission from a parent or guardian.
  4. Limit access. Only staff who need it can open the youth sheet. No personal phone copies.
  5. Follow the partner's rules and the law. Schools and youth programs often have their own policies, plus laws about student records. Ask your partner. When unsure, ask your coach before you build.

Practice data and consent

Remember Module 3. You build and test with fake data. You connect to real data only when:

  • Your partner gives clear permission, in writing (an email is fine)
  • They know what data flows where
  • They can turn it off without you

Privacy check for my automation

0 of 7 done