Confirmed users
134
edits
Identity/Profile/Proposal: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Stomlinson (talk | contribs) No edit summary |
Stomlinson (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
= Profile = | |||
Adding Profile Data to Persona | Adding Profile Data to Persona | ||
== Background & Motivation == | |||
Two of Persona's primary goals are to make signing up and signing into sites as easy as possible. Persona succeeds in making signin easy, but misses the mark for sign up. To create an account, many sites that use Persona must still ask users for additional personal information. How many times do users have to fill out their real names whenever they visit a new site? | Two of Persona's primary goals are to make signing up and signing into sites as easy as possible. Persona succeeds in making signin easy, but misses the mark for sign up. To create an account, many sites that use Persona must still ask users for additional personal information. How many times do users have to fill out their real names whenever they visit a new site? | ||
| Line 8: | Line 8: | ||
There should be a better way. | There should be a better way. | ||
== Proposal == | |||
Add basic profile information to Persona. To make use of profile facilities, sites must request a set of profile information from a well defined list of possible attributes. Users would then have the opportunity to approve or deny the request, as well as modify any information that is released. Sites can request the data they need, users retain control over what is released. | Add basic profile information to Persona. To make use of profile facilities, sites must request a set of profile information from a well defined list of possible attributes. Users would then have the opportunity to approve or deny the request, as well as modify any information that is released. Sites can request the data they need, users retain control over what is released. | ||
| Line 18: | Line 18: | ||
Once key-wrapping support is ready, a profile server will be set up to save data and provide a sync mechanism across multiple devices. All data stored on the profile server will be client side encrypted much in the same way as Firefox Sync operates today. Keys to unencrypt the stored data will not leave the user's devices, making the data unaccessible to third parties who have access to Persona's servers. | Once key-wrapping support is ready, a profile server will be set up to save data and provide a sync mechanism across multiple devices. All data stored on the profile server will be client side encrypted much in the same way as Firefox Sync operates today. Keys to unencrypt the stored data will not leave the user's devices, making the data unaccessible to third parties who have access to Persona's servers. | ||
== Data collected == | |||
Initially, only a minimal set of data will be requested from the user. The attributes collected are name and photo. In the future, additional attributes will be stored in multiple "contact cards". Additional data likely includes address, phone number, D.O.B., a web site, twitter handle, facebook handle, and possibly a short bio. The exact list of extended attributes which are collected have yet to be determined. | Initially, only a minimal set of data will be requested from the user. The attributes collected are name and photo. In the future, additional attributes will be stored in multiple "contact cards". Additional data likely includes address, phone number, D.O.B., a web site, twitter handle, facebook handle, and possibly a short bio. The exact list of extended attributes which are collected have yet to be determined. | ||
== Data retention == | |||
Until key wrapping support is ready, profile data will be retained only on the user's device. When a user manually signs out of Persona or a new user signs in on the device, the original user's profile data will be cleared. | Until key wrapping support is ready, profile data will be retained only on the user's device. When a user manually signs out of Persona or a new user signs in on the device, the original user's profile data will be cleared. | ||
When key wrapping support is complete and client side encryption is possible, a profile server will be set up which acts as a sync mechanism. This data will be retained on Mozilla's servers but will be unaccessible by ourselves or by third parties as the keys to unencrypt the data will not leave the user's devices. | When key wrapping support is complete and client side encryption is possible, a profile server will be set up which acts as a sync mechanism. This data will be retained on Mozilla's servers but will be unaccessible by ourselves or by third parties as the keys to unencrypt the data will not leave the user's devices. | ||
== Comparisons == | |||
Facebook Connect and OAuth? | Facebook Connect and OAuth? | ||
== User Data == | |||
Concrete user data that will initially be collected: | Concrete user data that will initially be collected: | ||
| Line 36: | Line 36: | ||
} | } | ||
== Users affected == | |||
All Persona users will be affected by this proposal. Approximately 100,000 sign-ins/month. | All Persona users will be affected by this proposal. Approximately 100,000 sign-ins/month. | ||
== Opt-in/Opt-out == | |||
All features will be opt-in. Users will not have to supply profile information. When sites request information, users can decline the request or modify any data before it is sent. | All features will be opt-in. Users will not have to supply profile information. When sites request information, users can decline the request or modify any data before it is sent. | ||
== Privacy Policy == | |||
Profile data collection and release may require a privacy policy update. Changes to our privacy policy will be made and published before this service is released. | Profile data collection and release may require a privacy policy update. Changes to our privacy policy will be made and published before this service is released. | ||
Profile information that a user releases to a site will be governed by that site's privacy policy and TOS. | Profile information that a user releases to a site will be governed by that site's privacy policy and TOS. | ||
== Publication of Collected Data == | |||
An individual user's profile data will never be published by Mozilla. We may publish aggregate information relating the number of users using the service or KPI indicators. | An individual user's profile data will never be published by Mozilla. We may publish aggregate information relating the number of users using the service or KPI indicators. | ||
Profile information that a user releases to a site will be published at that site's discression. | Profile information that a user releases to a site will be published at that site's discression. | ||
== Background Bugs & Wiki Pages == | |||
* https://github.com/mozilla/browserid/issues/880 | * https://github.com/mozilla/browserid/issues/880 | ||
* https://github.com/mozilla/browserid/issues/1588 | * https://github.com/mozilla/browserid/issues/1588 | ||
* https://github.com/mozilla/browserid/issues/1589 | * https://github.com/mozilla/browserid/issues/1589 | ||