powstik
Prove
LiveProof-of-Work · Oct–Nov: every verified proof counts. 35 days leftAll outcomes
Skills

Protect People's Data in Your Software

5 weeks · 2 milestones

Data Privacy Fundamentals (NIST Privacy Framework), then one project of your own. Part of the Varsity Curriculum: Computer Science.

Milestone map

Milestone map

2 milestones

Do the course work in public

2–3 weeks (3 hrs/week)

Take Data Privacy Fundamentals for free and do a data map of one app: what personal data, why, where it goes, how long it stays. Keep everything in one public repo or notebook as you go. OSSU lists a Coursera course. We use the free NIST Privacy Framework.

Proof required

Link your public repo or notebook with a data map of one app: what personal data, why, where it goes, how long it stays, and a screenshot or log showing the self-check passed.

What gets checked

  • Every personal field is listed.
  • Each has a reason.
  • Retention is stated.

Common mistakes

  • Copying posted answers: verifiers read the history.
  • Skipping the self-check, then asking for review too early.

Powstik Guide

A public repo or notebook with a data map of one app: what personal data, why, where it goes, how long it stays.

Steps

  1. Make a public repo or notebook first.
  2. Do one unit at a time and commit after each.
  3. Run the self-check: Map your app's data to the framework's functions and see what is missing.
  4. Write a short README: what is here and how to run it.
  5. Ask three people who know the topic to check it.

Template

README
Course: Data Privacy Fundamentals (NIST Privacy Framework)
What is here:
How to run it:
Self-check result:
What was hardest:

What gets sent back

  • No history, just one big upload.
  • Self-check not shown.
  • Code that does not run from the README.

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

  • Every personal field is listed.
  • Each has a reason.
  • Retention is stated.
  • Ask one question about a choice in the code; the answer should be clear.

You'll sign in first, then come straight back here.

Cut the personal data your app keeps

1–3 weeks (5–8 hrs/week)

Use what you learned. Make a change that collects or keeps less personal data, with a plain privacy note. Keep it small enough to finish in about two weeks.

Proof required

Link a change that collects or keeps less personal data, with a plain privacy note, with a README that says how to run or read it.

What gets checked

  • Less data is kept (before and after).
  • The note is plain and true.
  • Nothing breaks (tests pass).

Common mistakes

  • A project too big to finish.
  • A demo that only works on your machine.

Powstik Guide

A change that collects or keeps less personal data, with a plain privacy note.

Steps

  1. Write one line: what it does and for whom.
  2. Build the smallest version that works.
  3. Test it on someone else's machine or with someone else reading it.
  4. Write the README.
  5. Ask three people to check it.

Template

README
What it does:
Who it is for:
How to run it:
What I would do next:

What gets sent back

  • Does not run from the README.
  • Not clearly the person's own work.
  • Claims more than it does.

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

  • Less data is kept (before and after).
  • The note is plain and true.
  • Nothing breaks (tests pass).
  • Check that the work is the person's own.

You'll sign in first, then come straight back here.

Part of