Open yaelberger-commits opened 3 months ago
Working with Jeana on including something in our Privacy Statement about using generative AI to analyze support tickets. We will need to sync with Jeana and Nisa to further scope
My understanding is that we haven't landed on what generative AI tool and how we plan to use it, so will have to wait to update the Privacy Statement until we know more
Hey team! Please add your planning poker estimate with Zenhub @mtoutloff @YedidaZalik
Description
As a GC Notify user, I need to understand how my data is being used by AI software so that I can consent to use GC Notify and its components as a fully informed user.
WHY are we building? We may wish to use generate AI for analysis of support tickets in the near future and would need to notify users of this use. WHAT are we building? Changes to our privacy statement VALUE created by our solution Fully informed users are able to consent knowingly to how their data is used.
Documentation and Artifacts
Good docs, figma mockups, ADRs, screenshots etc.
Acceptance Criteria
Given some context, when (X) action occurs, then (Y) outcome is achieved
[ ] Cypress UI tests if needed.
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
[ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
[ ] Does the feature change our Information Architecture? If so, update the Sitemap in En/Fr
A11y
Bilingualism
Privacy considerations
Security controls in place
Measuring success and metrics
Related Research Airtable records
QA Steps