Data Safety/Data Safety Consultation Meeting Notes/2012-03-15/Lovebomb Data Safety Questionnaire

From MozillaWiki
Jump to: navigation, search

Data Safety Consultation Questionnaire
Project: Lovebomb
Contact: Ben Simon
Date Questionnaire received by Data Safety Team: 09 March 2012
Data Safety Review Date: Thursday, 15 March 2012

About Your Project

  1. Please Brief description of your project.
    • This is essentially a webby ecard maker. The idea is to run a campaign using Mother's Day as the hook, where people can make their own webby ecards for their Mom, and then share out and see what others did. It provides an easy way to get your hands a little dirty with code, learn something, and then have an awesome (better than a) card at the end that you can be proud of and share widely. There are three principal goals:
      1. Provide an approachable, fun on-ramp into our learning offerings
      2. Teach a little bit (and possibly more) of code, without being too scary for a non-code
      3. Grow our base of supporters
    • Additional info about Lovebomb.me: https://etherpad.mozilla.org/lovebomb
  2. Please provide the links to your project documentation (both internal and external).
  3. What is the current state of your project?
    • There is a working prototype of a related app at Lovebomb.me; this prototype is not hosted on Mozilla hardware, and not branded Mozilla; the prototype shows the power of the design, but we're not planning on reusing its code approach or data policies.
  4. Please provide your key release / launch dates.
    • We need to be fully launched by May 6th, to be able to promote it the week before Mother's Day.
  5. What are the core technical components and features?
    • There will be a web form and a web service.
    • The web service will provide a REST api saying "here is a template ID and some template parameters, please create a short URL that will serve the customized template for 30 days".

The web service will likely use a key-value store to map URLs to blob IDs, and a blob storage system (maybe just the filesystem) to keep the customized templates.

  1. Who are the stakeholders involved with your project (internal and external)?
    • internal:
      • MoFo staff
      • Ben Simon
      • Jess Klein
      • Ryan Merkley
      • labs staff (davida)
      • SpecOps staff (philippe chiasson)
    • external:
      •  ?

Security

  1. Does your project deploy new or modify web application code that runs on Mozilla infrastructure? Does your project deploy or modify client-run software (such as Firefox or Android applications)? If YES to either of the above, please file a Security Review bug (see https://wiki.mozilla.org/WebAppSec/Security_Review_Request for more information)

Privacy Engineering

  1. Does your project change how we generate, store, share or collect information from users? If YES, please file a Privacy Review bug
    • It looks like the security review meta-bug should cover the privacy review. Let us know if not. Yep, it does.

Policy and Legal

  1. Do you have a privacy policy for your project / site? If YES, Please provide a link to it:
    • Not yet, but we will need one. We may need a DMCA notice as well (email to Jishnu asking about that).
  2. Will user data be collected from global locations (outside the U.S.) and stored in those locations? If YES, please provide the names of the countries where data is collected and stored.
    • The site is first going to be used for a Mother's Day campaign, which we expect will drive traffic mostly from North America, but we don't intend to restrict it to US residents, and expect global usage.
  3. If you're collecting data only from the US, will all user data be stored in the US?
    • N/A - See above

Data

  1. Does your project collect data from users? If YES, then someone from Data Safety will look at this bug, find out how many users' data to be involved, determine priority level (L / M / H).
    • The project asks users to customize a Mother's Day card or equivalent template. We expect it to include things like their mother's names, their own names. It is an outreach campaign, so we will drive people to the site, hoping to get XX thousands of users. We hope it is a fun campaign that will drive "viral" growth.
  2. Please provide list of data elements (e.g., email, name, location, log data, URLs, browser history, etc.).
    • We will store for each use:
      • which template is chosen (out of a small set)
      • which template customizations are done (image choices, font/color choices, etc.,)
      • text customiziations (freeform, but will likely involve names)
    • For each use, we'll generate a custom short URL which will be given to the user in the browser. We'll keep a mapping between the short URL and the customized template, but no way to associate that with any specific user.
    • We're not planning on storing HTTP logs, IP addresses, etc.
    • We will also have an email signup in the footer of the site that will link back to Blue State Digital (the foundation's email provider), and may try to provide other places where the user could sign up (after publishing, for instance), but it would be separate from the flow of card creation.
  3. Why do you need to collect user data?
    • The customization of the template is the experience goal, we can't do this without.
  4. How is this data being collected? (e.g., forms on web site, provided directly by user, observed data collection, etc.) (Consider that you may be collecting data unintentionally such as automatic logging by web servers)
    • An interactive form on a website.
    • Our current plan is to keep server logs only for one day, to allow debugging but not build any long term data.
  5. Will your project / team members need to retain user data? If YES, for how long?
    • The customized templates should be kept long enough to be read by their recipients. Our current plan is to keep the templates for 30 days. XXXX check?
  6. Will any user data be shared or accessed by third party partners, customers or providers? (If YES, see additional questions below.)
    • The customized templates will be published on the web with no access control.
    1. What is the data being shared or accessed?
      • See above.
    2. How would the data be communicated / transferred to the third parties?
      • See above.
    3. Who are the third party vendors and in what countries are they based?
      • No specific third parties.

User Benefit

  1. In particular, it's useful to list the user benefits that result from this data. A possible way of describing the benefits that flow from the data is:

User Benefits: (sample!)
A - users find applications that have their photos are more friendly/fun
B - users want to be able to access this project from computers where they just have web access
C - users want to be informed of updates from specific other users of the site
D - users want notices when important changes happen

Data collected (sample!)
A - profile picture; user submitted image (doesn't have to be their face); meets benefit A; optional
B - pseudonym: users get to pick a screen name (mostly anything goes - see name policy [..] - meets benefit C.
C - browserid-based authentication means we store email identifiers - meets benefit D, B. ...etc...

  • User benefit: We believe that people will love finding a page on the web which has clearly been customized for them by someone they know.
  • To do so we need to let people customize these pages with personal twists, and we expect people will use names to make the personalization obvious (as in, signing a mother's day card).

Community Visibility and Input

  1. Has your proposal been shared publicly, including requirements for Mozilla to collect and host user data?
    • (See below)
    1. If YES, what communication channels are you using and what kind of input have you received thus far?
      • It has been publicly blogged (in planet-syndicated feeds) on numerous occasions, and discussed on the weekly webmaker calls. A few of the blogs that have been published are:

http://engagingopenly.wordpress.com/2012/02/17/the-lovebomb-a-digital-learning-onramp/
http://jessicaklein.blogspot.com/2012/03/yo-momma-is-da-bomb.html
http://jessicaklein.blogspot.com/2012/01/e-cards-and-love-letters.html
http://jessicaklein.blogspot.com/2012/01/on-inspiration-and-lovebombs.html
http://openmatt.org/2012/02/09/lovebomb/

  • User data has not specifically been addressed, though response to the project in general has been very positive.
Retrieved from "https://wiki.mozilla.org/index.php?title=Data_Safety/Data_Safety_Consultation_Meeting_Notes/2012-03-15/Lovebomb_Data_Safety_Questionnaire&oldid=417482"