decentralauren
commented
9 months ago @patpedrosa A few comments / feedback:
- Business Description: "AND agreeing to our linked privacy policy" - this isn't accurate. They agree to our privacy policy at the point of updating their GoodID. This screen is just resharing the link to our privacy policy for their reference.
- Acceptance Criteria: This should also include the resulting action from the user choosing Yes or No (which is the point of having these permissions). Specifically that choosing "I accept" will then result in GoodLabs being able to read their ID and make them offers based on the GoodID values (Uniqueness, Age, Gender, Location).
vldkhh
Business Description
What the feature is and why we're doing it (business & user benefit) The disclosure screen is where we ask the user's permission to read their GoodID so to show them offers tailored to their identity. By clicking on accept, the user is agreeing to allow GoodLabs to read their ID up to its expiration date. In this screen, we also reshare the link to our privacy policy for their reference. When the user taps accept, we should have a record of the timestamp when the permission was given. If the user taps no, we should record that the user did not give us permission to read their ID. In both cases, the user should be taken to the confirmation screen next.
Detailed Description of Functionality
Includes link to Figma, screenshots if applicable to describe step by step how the feature works, edge cases, and considerations. States etc should also be described here.
Design preview:
Full design: https://www.figma.com/file/ihw1PxBvLxacTHnN2aj4lC/3.-Product?type=design&node-id=13532-19584&mode=design&t=nrTfOzoTxXG9tFKt-0
Technical Implementation
How we are going to build it.
Acceptance Criteria
How we know if the feature is working as expected / how we test it.
[ ] Scenario: User accepts consent
[ ] Scenario: User declines disclosure consent