Please note, this is a STATIC archive of website developer.mozilla.org from 03 Nov 2016, cach3.com does not collect or store any user information, there is no "phishing" involved.

Revision 539137 of Privacy policy guidelines

  • Revision slug: Mozilla/Marketplace/Publishing/Privacy_policies
  • Revision title: Privacy policy guidelines
  • Revision id: 539137
  • Created:
  • Creator: alispivak
  • Is current revision? No
  • Comment Adding tags

Revision Content

Privacy is tough to get right. It's a complicated concept involving laws, social norms and user expectations. The developer of an app, site, page, or add-on that takes privacy seriously inspires user trust. We've put together these guidelines to help you make a privacy-conscious app, and write a good privacy policy for it. Please remember that this is not a substitute for a real lawyer and doesn't provide legal advice.

Privacy policies

A privacy policy is a description of what you do with data. The critical things to describe are how you collect, use, store, and share or disclose information about people. We've put together a privacy policy template to help make this a little easier.

https://github.com/flamsmark/privacy-policy-template

Check out the README to get started. You should copy our template and fill in your data as needed. We think that using it will make writing a privacy policy easier, but we don't promise that that you'll make a good or accurate policy just because you use it. Hopefully, it'll help draw your attention to some of the main privacy issues that you should be thinking about. Feel free to fork and improve it!

It is good practice (and in some cases, legally required) to include a privacy policy to help your users understand what's happening with info about them. Different places around the world have specific requirements for how user data is collected, used, stored and disclosed. You definitely need to talk to a lawyer to help you navigate the world of privacy and make a privacy policy that tells your users what they need to know.

Mozilla Marketplace privacy requirements

If have an app or add-on that collects data about your users, you are required to have a privacy policy to list it in the Mozilla Marketplace.

Privacy tips for designing apps

  • Design your app or add-on so that what you actually do with user data is what users think you are doing with it.
  • Try to give the user as much control over their data as you can, such as giving them the choice to opt-in to or opt-out of data collection whenever possible.
  • Try to limit your data collection and use to only the data that you need.
  • Design your app and service to protect the security of your user's data in its collection, storage, and use.
  • Respond to user questions and concerns about your privacy practices.
  • Avoid 'secret' updates.
  • Make your use of social features transparent, so that users are aware of when they're sharing data socially.
  • Give people a way to turn off automatic sharing or make more granular choices about sharing data.
  • Obtain consent from users when necessary, especially for location and other sensitive information.
  • Put a link to your privacy policy and, if you have them, your "terms of use" somewhere in your app.

Revision Source

<div class="summary">
 <p>Privacy is tough to get right. It's a complicated concept involving laws, social norms and user expectations. The developer of an app, site, page, or add-on that takes privacy seriously inspires user trust. We've put together these guidelines to help you make a privacy-conscious app, and write a good privacy policy for it. Please remember that this is not a substitute for a real lawyer and doesn't provide legal advice.</p>
</div>
<h2 id="Privacy_policies">Privacy policies</h2>
<p>A privacy policy is a description of what you do with data. The critical things to describe are how you <strong>collect</strong>, <strong>use</strong>, <strong>store</strong>, and <strong>share</strong> or <strong>disclose</strong> information about people. We've put together a privacy policy template to help make this a little easier.</p>
<pre>
<a href="https://github.com/flamsmark/privacy-policy-template" title="https://github.com/flamsmark/privacy-policy-template">https://github.com/flamsmark/privacy-policy-template</a>
</pre>
<p>Check out the <a class="link-https" href="https://github.com/flamsmark/privacy-policy-template#readme" title="https://github.com/flamsmark/privacy-policy-template#readme">README</a> to get started. You should <a href="https://github.com/flamsmark/privacy-policy-template/blob/master/privacy-policy.html">copy our template</a> and fill in your data as needed. We think that using it will make writing a privacy policy easier, but we don't promise that that you'll make a good or accurate policy just because you use it. Hopefully, it'll help draw your attention to some of the main privacy issues that you should be thinking about. Feel free to fork and improve it!</p>
<p>It is good practice (and in some cases, legally required) to include a privacy policy to help your users understand what's happening with info about them. Different places around the world have specific requirements for how user data is collected, used, stored and disclosed. You definitely need to talk to a lawyer to help you navigate the world of privacy and make a privacy policy that tells your users what they need to know.</p>
<h2 id="Mozilla_Marketplace_privacy_requirements">Mozilla Marketplace privacy requirements</h2>
<p>If have an app or add-on that collects data about your users, you are required to have a privacy policy to list it in the Mozilla Marketplace.</p>
<h2 id="Privacy_tips_for_designing_apps">Privacy tips for designing apps</h2>
<ul>
 <li>Design your app or add-on so that what you actually do with user data is what users think you are doing with it.</li>
 <li>Try to give the user as much control over their data as you can, such as giving them the choice to opt-in to or opt-out of data collection whenever possible.</li>
 <li>Try to limit your data collection and use to only the data that you need.</li>
 <li>Design your app and service to protect the security of your user's data in its collection, storage, and use.</li>
 <li>Respond to user questions and concerns about your privacy practices.</li>
 <li>Avoid 'secret' updates.</li>
 <li>Make your use of social features transparent, so that users are aware of when they're sharing data socially.</li>
 <li>Give people a way to turn off automatic sharing or make more granular choices about sharing data.</li>
 <li>Obtain consent from users when necessary, especially for location and other sensitive information.</li>
 <li>Put a link to your privacy policy and, if you have them, your "terms of use" somewhere in your app.</li>
</ul>
Revert to this revision