Unified control of privacy-impacting devices
Systems and techniques, including a privacy service, facilitate selecting, defining, controlling, verifying, and auditing privacy-impacting behaviors of devices in alignment with the privacy behavior expectations of individuals and other entities. Techniques and systems are presented to facilitate controlling and verifying the privacy behaviors of privacy-impacting devices. Techniques and systems for defining and sharing individualized privacy behavior preferences are described. Techniques and systems are disclosed for privacy preference resolution protocols that allow for the automated or interactive resolution of conflicts that arise between individuals in multi-actor environments or ambiguous contexts. Accountability and audit mechanisms assist in verifying the control state of devices with respect to their privacy behavior preference inputs. A trust-enhancing and technically transparent system architecture includes a distributed application network, distributed ledger technology, smart contracts, and/or blockchain technology.
1. A method of facilitating the control and verification of privacy behaviors of a privacy-controlled device (PCD), comprising:
receiving a privacy ruleset request, generated by a PCD, wherein the privacy ruleset request includes operating context data of the PCD and privacy identity data of at least one entity;
determining a privacy context from the privacy ruleset request;
retrieving, from a rule data store, privacy-control rules associated with the privacy identity data and the privacy context;
determining a privacy-control ruleset for the PCD from the privacy-control rules and privacy ruleset request data;
creating a privacy rule access token that includes at least a unique privacy rule access token identifier, at least part of the privacy ruleset request data and rule identifiers of members of the privacy-control ruleset;
generating and submitting a privacy rule access token-storing transaction to store the privacy rule access token in a data structure on a distributed ledger of a distributed application network;
returning at least the unique privacy rule access token identifier and the privacy-control ruleset to the PCD; and
receiving and storing control state verification data on the distributed ledger, the control state verification data comprising the unique privacy rule access token identifier, and wherein the control state verification data pertains to the PCD.
2. The method of claim 1 , further comprising:
receiving control state verification data pertaining to the PCD, wherein the control state verification data includes at least the unique privacy rule access token identifier and one or more privacy-impacting (PI) module control states of the PCD determined from the privacy ruleset request; and
generating and submitting a control state verification transaction to store the control state verification data on the distributed ledger.
3. The method of claim 2 , further comprising:
receiving a guarantee for a quantity of cryptographic token as a stake of accuracy of the control state verification data.
4. The method of claim 1 , further comprising validating the privacy ruleset request by determining whether confirmatory data received with the privacy ruleset request aligns with the operating context data.
5. The method of claim 1 , wherein determining the privacy-control ruleset comprises:
detecting a conflict between a plurality of privacy-control rules; and
performing an autonomous merger protocol to remove or modify one or more conflicting privacy-control rules from the privacy-control ruleset.
6. The method of claim 5 , wherein performing the autonomous merger protocol comprises purpose alignment.
7. The method of claim 5 , wherein performing the autonomous merger protocol comprises normative priority analysis.
8. The method of claim 5 , wherein performing the autonomous merger protocol comprises:
comparing weighting factors assigned to conflicting privacy-control rules; and
removing the one or more conflicting privacy-control rules having lower weighting factors from the privacy-control ruleset.
9. The method of claim 5 , wherein performing the autonomous merger protocol comprises transmitting a quantity of cryptographic token from a payor repository to a receiver repository, wherein the receiver repository is associated with a privacy identity having a suppressed privacy-control rule.
10. The method of claim 1 , wherein determining the privacy-control ruleset comprises:
detecting an ambiguity in the privacy ruleset request;
formulating a clarification question directed at a designated entity;
sending, to the PCD, the clarification question directed at the designated entity;
receiving, from the PCD, clarification data including an answer to the clarification question;
modifying members of the privacy-control ruleset in accordance with the answer to the clarification question; and
recording the clarification question and clarification data in the privacy rule access token associated with the privacy ruleset request.
11. The method of claim 1 , wherein determining the privacy-control ruleset comprises:
detecting a conflict between a plurality of privacy-control rules;
formulating a consensus communication, directed at one or more designated entities, from a mediation pattern;
sending, to the PCD, the consensus communication directed at the one or more designated entities;
receiving, from the PCD, resolution data including a yielding option;
modifying members of the privacy-control ruleset in accordance with the yielding option; and
recording the yielding option in the privacy rule access token associated with the privacy ruleset request.