Child pages
  • User Submitted Terms -- UX and Interface V.1
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »


ICONs and INTERFACE – strawman draft

Recommendations to entities using UST standard (TBD – some initial ideas below – need to be fleshed out):
* Interface issues: how a company presents the interface on their own product or service is something we can advise on, and give examples for but obviously companies are going to do what works for them;  versions of this may include:  
** a company could show the icons and make definitions one click away, asking users to choose the icons they want
** companies might make it possible for a user to point to another user's selections and just use those
** a company might offer a simpler way to choose a lot of privacy control with little data sharing, a medium amount of each, or little privacy with lots of data sharing. NOTE: We should probably advise on this, once our project has an MVP.. based upon our experiences and ideas

USER TERMS: Human language and {{ legal language }} below.

PREAMBLE: {{ Information is defined as personal information provided by the individual about themselves. Data + Meaning = Information. The observer creates meaning (or observer is "informed by" the data), and then can be assigned duties. Information not collected from a person does not by definition constitute personal data. }}

SHARE:  {{ Information can only be shared with those parties who first agree to abide by these terms.  Any sharing of information with a party that has not first agreed to these terms is a violation of these terms. }}

Choice: 2nd

1st-2nd Party:   Information about an individual (the “1st party”) and their activities are not permitted to be shared by the 2nd party with any other parties.

Choice: 3rd

3rd Party: 

Information about an individual and their activities can be shared by the 2nd party with mutually approved 3rd parties, including the public, subject to 1st Party's purpose choices (including but not limited to advertising and data brokering).



Choice: Session

Information about an individual must be destroyed by the 2nd party immediately after the completion of the transaction for which it was collected or otherwise generated, unless otherwise required by law or contract obligation. [NOTE: What about records for audit?  What about hashed storage, e.g., in blockchain or other ledger system?]

Choice: 3 (months)

Information about an individual must be destroyed on or before the date that is 90 days after its collection or other generation by the 2nd party.

Choice: Infinity 

Information about an individual can be retained indefinitely by the 2nd party, unless and until the 1st party notifies the 2nd party they have made an alternate selection for duration. 



Choice: Transaction

Information about an individual may be used only for the purpose of the transaction for which it was collected or generated.

Choice: Site / App Use

Information about an individual may be used beyond the transaction for which it was collected or generated, but only with respect to the operation [or further development?] of the  site or app over which such original transaction occurred and not for any other secondary uses by the 2nd party or other parties.

Choice:  Partner - 3rd use

Partners: Subject to the limitations of the 1st party’s “sharing” preferences, information about an individual  can be used for 3rd party  purposes.



Choice: Tracking

Tracking of individual and their activities by any 3rd parties is authorized.  


Choice: Do Not Track

Tracking by 3rd parties is not authorized by individual. 2nd parties will not track activities by 1st party that occur on another service or site. 

NEED to add: definition of tracking that will describe exceeding authority by an unauthorized party. 



Implementation Idea:

Reverse cookie: could an entity be asked to consent to my terms before they place a cookie? Can the service, and TOU and privacy policy be customized based upon the USTs.

  • No labels