Vibe Coder · Unit 13: Testing and Security · Lesson 10 of 11

Privacy

Know what personal data you collect, why, where it goes, and how someone can have it removed. The basics every product needs.

Read the short notes and pictures.Do everything inside a blue frame.

Looking after people’s data

Privacy is partly law and mostly respect. If you know what you hold, keep only what you need and can delete it on request, you are most of the way there. The legal details depend on where you and your users are.

A 3D scene of coloured blocks and cards. For each thing: what you collect, why you need it.
What you collect and why.

A data map

  1. List every personal field

    Email, name, anything they type or upload.

  2. Give each a reason

    No reason, do not collect it.

  3. List who receives it

    Every service it passes through.

  4. Decide how long you keep it

    And how deletion works.

A 3D scene of coloured blocks and cards. Where it goes: your database, email service, model provider.
Your database, email service and model provider.

What your product needs

A privacy policy

In plain words, matching your data map.

A delete-account option

That really deletes.

Care with AI

Tell users when their content is sent to a model, and check your provider’s data terms.

ActivityBuild stepA tested, locked-down app

Write your data map

List the personal data your product collects with a reason and destination for each. Remove anything without a reason, add a delete-account option, and draft a plain-words privacy policy from the map.

Done when

Have the policy reviewed before you launch publicly.

Keep these

  • Know what you collect and why.
  • Know where it goes.
  • Let people delete it.