...
- Roll
- IPR
- Minutes Approval
- Agenda Approval
- Intros
- Agenda Items Discussion
- Actions pending
- Actions new
- Updates from the consent community
- AOB
Roll call
Quorate:
--
IRP Policy Announcement
Approve Minutes
Minutes
Review of spreadsheets to determine working sheet for fields
...
Framework has to go through BOLTS...
| Layer | I Agree | Privacy as Expected |
|---|---|---|
Business | Data Protection | Decentralized Governance |
Operational | Compliance, Breach Resolution, Data Sharing Risk | Person Driven, Lower Operational Burden |
| Legal | Cyber Insurance | Interoperable Global Governance, Shared Liability and Risk |
| Technical |
| Lacking | Standards based receipts and records | |
| Surveillance | Lack of transparency, | Provides a trust anchor for security and identity services that include privacy |
ANCR receipt
- Place of notice digital and physical location (of the person)
- Method in 1.2
- how do I do this
- Method of collection of consent vs. collection of notice
- Method of deliver of notice
- Related to quality of consent and better definition of risk
- Location is where the subject is exposed to the policy.
- Tell me that you agree
- (Consent Methods....)
- And whether the notice is legally compliant
- Tell me that you agree
- Can you consent if you don't know who you are dealing with...
- In the US implicit consent is the norm...
- Make it something that Bob could figure out...
- 1.1. was call your lawyer to fill out the field..
- You want to be able to create your own receipt, that captures the level of transparency at that interaction
- Quality of Notice
- Use of Rights
Actions
- Create Flow to Match Protocol Contribution
- Define Initial Notice Receipt Fields
- Review framework
(Previous)
- Review receipt fields (uploaded) -> test against:
- transborder requirements
- delegation
- outsourced receipts ("store")
- legally covering GDPR and other potential laws/acts/regulations
- can we pair receipts for active state
- Updating language on our part is an important next step