As a user, I want my PII shielded, so that I can be reasonably certain I'd have to try really hard to submit something that identifies myself.
As part of this story we want to:
[ ] Identify the following PII sources and warn the user before submitting, then if submitting anyways, replace the detected values with dummy data:
[ ] Phone Numbers
[ ] Emails
[ ] SSN
Acceptance Criteria
- [ ] Identify the following PII sources and warn the user before submitting, then if submitting anyways, replace the detected values with dummy data:
> - [ ] Phone Numbers
> - [ ] Emails
> - [ ] SSN
## Notes & Open Questions
- Dependencies/Roadblocks:
- Any internal/external dependencies?
- Test accounts needed?
- Does this require QA?
- Dev Notes:
## Ticket Checklist
- [ ] Acceptance criteria defined
- [ ] Labels added (front-end, back-end, feature)
- [ ] Linked to an Epic
Description
As a user, I want my PII shielded, so that I can be reasonably certain I'd have to try really hard to submit something that identifies myself.
As part of this story we want to:
Acceptance Criteria
- [ ] Identify the following PII sources and warn the user before submitting, then if submitting anyways, replace the detected values with dummy data: > - [ ] Phone Numbers > - [ ] Emails > - [ ] SSN ## Notes & Open Questions - Dependencies/Roadblocks: - Any internal/external dependencies? - Test accounts needed? - Does this require QA? - Dev Notes: ## Ticket Checklist - [ ] Acceptance criteria defined - [ ] Labels added (front-end, back-end, feature) - [ ] Linked to an Epic