Confirmed users
888
edits
Privacy/HowTo/WebReg: Difference between revisions
Jump to navigation
Jump to search
→Newsletter Sign Ups
| Line 20: | Line 20: | ||
Simply entering an email address is not an opt-in. Checkboxes are required. You will need permission to send an email newsletter, plus an acknowledgement of the Mozilla privacy policy. This can be accomplished in a couple different ways: | Simply entering an email address is not an opt-in. Checkboxes are required. You will need permission to send an email newsletter, plus an acknowledgement of the Mozilla privacy policy. This can be accomplished in a couple different ways: | ||
1) If it is clear to the user that the sole purpose of the activity is to receive communication(ex: newsletter sign up), you will need to add a single checkbox for the privacy policy acknowledgement. | 1) If it is clear to the user that the sole purpose of the activity is to receive a communication (ex: newsletter sign up), you will need to add a single checkbox for the privacy policy acknowledgement. | ||
*___ I’m okay with you handling this info as you explain in your privacy policy. | *___ I’m okay with you handling this info as you explain in your privacy policy. | ||
| Line 26: | Line 26: | ||
2) If it may not be clear to the user that the sole purpose of the activity is to receive communication, you may combine an email opt-in and the privacy policy acknowledgement into a single checkbox. | 2) If it may not be clear to the user that the sole purpose of the activity is to receive communication, you may combine an email opt-in and the privacy policy acknowledgement into a single checkbox. | ||
*___ I want to receive email updates | *___ I want to receive email updates about [insert name of project] and Mozilla's other projects and campaigns, and I’m okay with you handling this info as you explain in your privacy policy. | ||
3) If the user can participate in some form without opting in to communication, you will need two checkboxes. | 3) If the user can participate in some form without opting-in to communication (ex: contribute form or community site such as QMO), you will need two checkboxes. | ||
*___ I want to receive email updates | *___ I want to receive email updates about [insert your project here]. | ||
*___ I’m okay with you handling this info as you explain in your privacy policy. | *___ I’m okay with you handling this info as you explain in your privacy policy. | ||
Note: If you think there is a possibility you'll want to send broader Mozilla communications in the future, add the words "and Mozilla's other projects and campaigns" to the first checkbox above. | |||
4) If you would like to obtain permission for two distinct types of communications, but do not have the ability to offer separate unsubcribes/opt-outs, you may combine them into a single checkbox. However, an unsubscribe/opt-out must cancel both. You may also combine them with the privacy policy acknowledgement if as described in #2 above. | 4) If you would like to obtain permission for two distinct types of communications, but do not have the ability to offer separate unsubcribes/opt-outs, you may combine them into a single checkbox. However, an unsubscribe/opt-out must cancel both. You may also combine them with the privacy policy acknowledgement if as described in #2 above. | ||
*___ I want to receive email updates about Ignite and Mozilla, and I'm okay with you handling this information as you explain in your privacy policy. | *___ I want to receive email updates about Ignite and Mozilla's other projects and campaigns, and I'm okay with you handling this information as you explain in your privacy policy. | ||
5) You may combine acknowledgement of the privacy policy and terms of service. | 5) You may combine acknowledgement of the privacy policy and terms of service. | ||
| Line 45: | Line 47: | ||
The goal of the wording is to provide enough information so users know what they're opting in to, but make it broad enough so that it's practical. (For example, if you decide you want to send them a survey in the future, is your opt-in broad enough to cover that?). Below is some sample wording. | The goal of the wording is to provide enough information so users know what they're opting in to, but make it broad enough so that it's practical. (For example, if you decide you want to send them a survey in the future, is your opt-in broad enough to cover that?). Below is some sample wording. | ||
*___ I want to receive email updates | *___ I want to receive email updates about Mozilla's projects and campaigns. | ||
*___ I wish to receive information about Firefox and Mozilla via email. | *___ I wish to receive information about Firefox and Mozilla's other projects and campaigns via email. | ||
==Additional Wording== | ==Additional Wording== | ||