Inside EverOn
Make permission part of the process
Keep explicit consent and guardian decisions alongside the tools that use personal memories.
The everyday friction.
A recording can carry a great deal of meaning, and permission to keep it is not permission for every use. Voice and memory tools need a place for those choices, including decisions that involve a guardian.
A different way through.
EverOn includes authenticated consent routes, a consent history, and workflows for requesting, approving, or rejecting guardian permission. The project’s stated principles pair consent with user control, giving the work around personal data a place in the product rather than leaving it as an assumption.
See the idea take shape.
Three moments in the experience. Explore the intended flow below.
- Review the requested use
- Record consent or request guardian approval
- Revisit the consent history when needed
Record the choice
Make consent an explicit record associated with the uses being requested.
Keep the history
Retain a consent history so changes can be understood as decisions over time.
Include a guardian
Use a request and response workflow when a guardian needs to take part in approving a use.
The difference it can make.
Record the choice
Make consent an explicit record associated with the uses being requested.
Keep the history
Retain a consent history so changes can be understood as decisions over time.
Include a guardian
Use a request and response workflow when a guardian needs to take part in approving a use.
Where it stands.
Good ideas deserve an honest description of where they are today.
Consent and guardian workflows are in development, with further verification still planned.