Skip to content

Commit

Permalink
privacy: Add reference to Privacy by Design and clarify source of quo…
Browse files Browse the repository at this point in the history
…te, #403
  • Loading branch information
rhiaro authored and msporny committed Nov 4, 2020
1 parent 12873fd commit a06028e
Show file tree
Hide file tree
Showing 2 changed files with 19 additions and 9 deletions.
9 changes: 9 additions & 0 deletions common.js
Original file line number Diff line number Diff line change
Expand Up @@ -159,6 +159,15 @@ var ccg = {
],
status: "Draft Community Group Report",
publisher: "Credentials Community Group"
},
"PRIVACY-BY-DESIGN": {
title: "Privacy by Design",
href: "https://iapp.org/media/pdf/resource_center/pbd_implement_7found_principles.pdf",
authors: [
"Ann Cavoukian"
],
date: "2011",
publisher: "Information and Privacy Commissioner"
}
}
};
Expand Down
19 changes: 10 additions & 9 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -4182,15 +4182,16 @@ <h1>

<p>
It is critically important to apply the principles of Privacy by Design
to all aspects of the <a>decentralized identifier</a> architecture, because
<a>DIDs</a> and <a>DID documents</a> are, by design, administered directly by
the <a>DID controller(s)</a>. There is no registrar, hosting company, or other
intermediate service provider to recommend or apply additional privacy
safeguards. The authors of this specification have applied all seven Privacy by
Design principles throughout its development. For example, privacy in this
specification is preventative not remedial, and privacy is an embedded default.
Furthermore, the <a>decentralized identifier</a> architecture by itself embodies
principle #7, "Respect for user privacy &mdash; keep it user-centric."
[[PRIVACY-BY-DESIGN]] to all aspects of the <a>decentralized identifier</a>
architecture, because <a>DIDs</a> and <a>DID documents</a> are, by design,
administered directly by the <a>DID controller(s)</a>. There is no registrar,
hosting company, or other intermediate service provider to recommend or apply
additional privacy safeguards. The authors of this specification have applied
all seven Privacy by Design principles throughout its development. For example,
privacy in this specification is preventative not remedial, and privacy is an
embedded default. Furthermore, the <a>decentralized identifier</a>
architecture by itself embodies Privacy by Design principle #7: "Respect for
user privacy &mdash; keep it user-centric."
</p>

<p>
Expand Down

0 comments on commit a06028e

Please sign in to comment.