Skip to content

Latest commit

 

History

History
50 lines (45 loc) · 10.1 KB

File metadata and controls

50 lines (45 loc) · 10.1 KB

Privacy and trust

40 buildable project leads for small organisations and service teams. The research signal for this category is NIST Privacy Framework. Each lead needs independent source checking and an existing-solution review before it becomes a full entry.

Ideas

  1. data retention review calendar: Build a review calendar for small organisations and service teams working on data retention. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  2. data retention purpose map: Build a purpose map for small organisations and service teams working on data retention. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  3. data retention approval ledger: Build a approval ledger for small organisations and service teams working on data retention. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  4. data retention plain-language notice: Build a plain-language notice for small organisations and service teams working on data retention. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  5. data retention access register: Build a access register for small organisations and service teams working on data retention. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  6. data retention deletion checklist: Build a deletion checklist for small organisations and service teams working on data retention. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  7. data retention risk questionnaire: Build a risk questionnaire for small organisations and service teams working on data retention. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  8. data retention audit trail: Build a audit trail for small organisations and service teams working on data retention. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  9. consent record review calendar: Build a review calendar for small organisations and service teams working on consent record. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  10. consent record purpose map: Build a purpose map for small organisations and service teams working on consent record. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  11. consent record approval ledger: Build a approval ledger for small organisations and service teams working on consent record. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  12. consent record plain-language notice: Build a plain-language notice for small organisations and service teams working on consent record. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  13. consent record access register: Build a access register for small organisations and service teams working on consent record. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  14. consent record deletion checklist: Build a deletion checklist for small organisations and service teams working on consent record. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  15. consent record risk questionnaire: Build a risk questionnaire for small organisations and service teams working on consent record. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  16. consent record audit trail: Build a audit trail for small organisations and service teams working on consent record. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  17. customer export review calendar: Build a review calendar for small organisations and service teams working on customer export. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  18. customer export purpose map: Build a purpose map for small organisations and service teams working on customer export. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  19. customer export approval ledger: Build a approval ledger for small organisations and service teams working on customer export. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  20. customer export plain-language notice: Build a plain-language notice for small organisations and service teams working on customer export. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  21. customer export access register: Build a access register for small organisations and service teams working on customer export. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  22. customer export deletion checklist: Build a deletion checklist for small organisations and service teams working on customer export. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  23. customer export risk questionnaire: Build a risk questionnaire for small organisations and service teams working on customer export. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  24. customer export audit trail: Build a audit trail for small organisations and service teams working on customer export. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  25. third-party access review calendar: Build a review calendar for small organisations and service teams working on third-party access. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  26. third-party access purpose map: Build a purpose map for small organisations and service teams working on third-party access. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  27. third-party access approval ledger: Build a approval ledger for small organisations and service teams working on third-party access. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  28. third-party access plain-language notice: Build a plain-language notice for small organisations and service teams working on third-party access. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  29. third-party access access register: Build a access register for small organisations and service teams working on third-party access. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  30. third-party access deletion checklist: Build a deletion checklist for small organisations and service teams working on third-party access. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  31. third-party access risk questionnaire: Build a risk questionnaire for small organisations and service teams working on third-party access. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  32. third-party access audit trail: Build a audit trail for small organisations and service teams working on third-party access. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  33. privacy request review calendar: Build a review calendar for small organisations and service teams working on privacy request. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  34. privacy request purpose map: Build a purpose map for small organisations and service teams working on privacy request. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  35. privacy request approval ledger: Build a approval ledger for small organisations and service teams working on privacy request. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  36. privacy request plain-language notice: Build a plain-language notice for small organisations and service teams working on privacy request. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  37. privacy request access register: Build a access register for small organisations and service teams working on privacy request. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  38. privacy request deletion checklist: Build a deletion checklist for small organisations and service teams working on privacy request. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  39. privacy request risk questionnaire: Build a risk questionnaire for small organisations and service teams working on privacy request. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.
  40. privacy request audit trail: Build a audit trail for small organisations and service teams working on privacy request. Start by recording the current state, making the next action clear, and keeping a reviewable evidence trail.

Turn a lead into a project

Use the repository project template. Document the problem, users, existing approaches, material gap, first version, and sources before submitting a pull request.