Related: T321822

Followup to T331351, T334633

• Read
  1. PII MVP Decision-making document
  2. Security Team's Privacy review - Campaign Registration System
  3. Notes - Engineering > Design weekly sync-up doc
  4. when to delete PII
  5. Privacy Engineering notes

• T340271
• shared with the team the benefits of working with the Country protection data on hive
• handling PII data by age - discussed with Hal T. and shared his insights with the team

• T335808
• review and provide feedback on T321822
• T340271
• T329006 Aggregate PII data before 90 days
• T329006 After at most 90 days, it will be deleted, aggregated, or de-identified
• T335526 [IMPLEMENTATION] - DB: create the tables: ce_question_answers, ce_question_aggregation and ce_event_questions
• T340271

See also:

• T334761

T328032 follow-on tasks:
T339977: Inform participants about the data retention policy for participant questions.
T339978: Inform organizers about the data retention policy for participant questions.
T339979: Implement restriction of not being able to change the end date of events that have already ended.
T339980: Acknowledge aggregated data potentially containing answers of participants who unregistered.
T339981: Prevent participants from answering again any questions whose answers were already aggregated.
T339982: Update the DB schema with the fields required for the "participant questions" feature.
T336858: [IMPLEMENTATION] Back end: Create a job to aggregate and delete participant questions.
T339986: Write logic to write the new columns related to participant questions.
T339987: Delete participant answers and date of first answer when they unregister.