Closed Bug 820212 Opened 13 years ago Closed 12 years ago

Implement FFOS Privacy Policy

Categories

(www.mozilla.org :: Pages & Content, defect)

Product:
www.mozilla.org
Component:
Pages & Content
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED
Milestone:
Future

People

(Reporter: jishnu, Assigned: espressive)

References

Details

(Whiteboard: u=user c=content p=2 [mentor=booboobenny+bugzilla@gmail.com])

Attachments

(4 files)

FFOS mock
96.02 KB, image/gif
Details
FFOS Privacy Policy text
11.89 KB, text/rtf
Details
DEsign by Lee showing the addition of the date
183.32 KB, image/png
Details
Updated design for FF OS Privacy Policy
1.02 MB, image/jpeg
Details
Attached image FFOS mock —
Implement the Firefox OS privacy policy - mock attached. Current text: Firefox OS Privacy [DATE] Firefox OS is an operating system for your mobile device, made by Mozilla. Mozilla is an open organization dedicated to internet freedom. We've built Firefox OS with your privacy in mind. + When Firefox OS sends information to Mozilla, our [privacy policy] says how we handle that information. [anchor link to “Mozilla Privacy Policy” below] + Firefox OS connects to others in order to provide Firefox OS updates and location services. ++ Firefox OS automatically connects to your device's manufacturer to stay up to date. +++ Mozilla will make available OS updates to the manufacturer of your device who will deliver updates to you. You can disable update checking in Settings on your device. ++ When you ask Firefox OS to tell an app or site your location, Firefox OS uses various services to determine where you are. +++ Firefox OS uses multiple data points to estimate your location, including GPS satellites and other GPS service providers when you turn location services on. You can edit your location based services preferences in Settings on your device. + The device you are using, like most mobile devices, is created by multiple parties. This document only covers how Mozilla handles your information for Firefox OS. ++ If you use third party Apps, their privacy policies will apply. ++ When you swipe left on the home screen, you are using the Everything.me service and its privacy policy applies, which you can find at [URL TBD]. [Contact] [link to contact form] | FAQs
Mozilla Privacy Policy text (linked at the top, text on same page at the bottom): Mozilla Privacy Policy Your privacy is an important factor that Mozilla considers in the development of each of our products and services. We are committed to being transparent and open. We want you to know how we receive information about you, and what we do with that information once we have it. We have also created product-specific notices that describe the practices we use to implement this policy and you can find those [here]. [link to privacy practices sub page on privacy center] What do we mean by “personal information?” For us, "personal information" means: • information which identifies you, like your name or email address; or • a combination of several pieces of information which couldn't identify you on their own, but which we believe could become identifiable to you when combined. Any information that falls outside of this is “non-personal information.” If we store your personal information with information that is non-personal, we will consider the combination as personal information. If we remove all personal information from a set of data then the remaining is non-personal information. How do we learn information about you? We learn information about you when: • you give it to us directly (e.g., when you choose to send us crash reports from Firefox); • we collect it automatically through our products and services (e.g., when we check whether your version of Firefox is up to date) ; • someone else tells us information about you (e.g., Thunderbird works with your email providers to set up your account); or • when we try and understand more about you based on information you've given to us (e.g., when we use your IP address to customize language for some of our services). What do we do with your information once we have it? When you give us personal information, we will use it for the reasons we told you we would when you gave it to us. Generally, we use your information to help us provide and improve our products and services for you. When do we share your information with others? • When we tell you we will, and you consent to the sharing. • For processing or providing products and services to you, but only if those entities receiving your information are contractually obligated to handle the data in ways that are approved by Mozilla. • When we are fulfilling our mission of being open.[link to manifesto] We sometimes release information to make our products better and foster an open web, but we will try to remove your personal information and disclose it in a way that minimizes the risk of you being re-identified. • When the law requires it. We follow the law whenever we receive requests about you from a government or related to a lawsuit, and we'll notify you when we’re asked to hand over your personal information unless we're legally prohibited from doing so. When we receive requests like this, we'll only release your information if we have a good faith belief that the law requires us to do so. Nothing in this policy is intended to limit any legal defenses or objections that you may have to a third party’s request to disclose your information. • When we believe it is necessary to prevent harm to you or someone else, provided that we will do so only if we have a good faith belief that it is reasonably necessary to protect the rights, property or safety of you, our other users, Mozilla or the public. • If our organizational structure or status changes (if we undergo a restructuring, are acquired, or go bankrupt) we may pass your information to a successor or affiliate. How do we store and protect your personal information? We are committed to protecting your personal information once we have it. We implement physical, business and technical security measures. Despite our efforts, if we learn of a security breach, we'll notify you so that you can take appropriate protective steps. We also don’t want your personal information for any longer than we need it, so we only keep it long enough to do what we collected it for. Once we don't need it, we take steps to destroy it unless we are required by law to keep it longer. What else do we want you know? We're a global organization and our computers are in several different places around the world. We also use service providers whose computers may also be in various countries. This means that your information might end up on one of those computers in another country, and that country may have a different level of data protection regulation than yours. By giving us information, you consent to this kind of transfer of your information. No matter what country your information is in, we comply with applicable law and will also abide by the commitments we make in this privacy policy. If you are under 13, we don’t want your personal information, and you must not provide it to us. If you are a parent and believe that your child who is under 13 has provided us with personal information, please [contact us](#contact) to have your child’s information removed. What if we change this policy? We may need to change this policy. When we do, we'll notify you. Where can you contact us? If you want to make a correction to your information, or you have any questions about our privacy policies, please get in touch with: Mozilla Corporation Attn: Legal Notices -- Privacy 650 Castro Street, Suite 300 Mountain View, CA 94041-2072 Phone: +1-650-903-0800 Filling out the form at https://www.mozilla.org/[$lang]/privacy
Component: Other → Pages & Content
Product: Websites → www.mozilla.org
Whiteboard: u=user c=content p=
Depends on: 812956
Blocks: 812956
No longer depends on: 812956
This should probably live at the URL of www.mozilla.org/privacy/firefoxos/
Whiteboard: u=user c=content p= → u=user c=content p=2
Target Milestone: --- → Future
Jishnu: Does this privacy policy have to be legally up by a certain date?
Hi Chris Beginning of Q1 would be great. Thanks Jishnu
we don't commonly localize privacy policies, but reading the previous bugs, there have been some assumptions on exposing the policy to l10n. do we have a affirmative verdict on whether we need to get this localized, or should not. And if yes, are there legal constraints on who's doing the localization?
Blocks: 820000
Jishnu, can you add the text of this as a txt file attachment, copying out of bugzilla is error-prone.
Flags: needinfo?(jmenon)
Whiteboard: u=user c=content p=2 → u=user c=content p=2 mentor=booboobenny+bugzilla@gmail.com
Whiteboard: u=user c=content p=2 mentor=booboobenny+bugzilla@gmail.com → u=user c=content p=2 [mentor=booboobenny+bugzilla@gmail.com]
(In reply to Axel Hecht [:Pike] from comment #5) > we don't commonly localize privacy policies, but reading the previous bugs, > there have been some assumptions on exposing the policy to l10n. > > do we have a affirmative verdict on whether we need to get this localized, > or should not. And if yes, are there legal constraints on who's doing the > localization? Hi Axel - The plan was to get legal counsel to localize and run the results through the l10n team for readability.
Flags: needinfo?(jmenon)
Update: Lee and I are meeting about this next week - hope to have final text within a few weeks after that
shall i assign to me and start doing this.
Jishnu can you provide an update on the copy for this?
Flags: needinfo?(jmenon)
Blocks: 831252
Trying to bring this back to life, as it's blocking a release now. Any news from Jishnu or Lee ??
Just got a review back from a few folks. Preparing final text. AGPS is a moving feature in the phone, which is causing delays.
Flags: needinfo?(jmenon)
Hi All Adding final policy text. Thanks Jishnu
Assigning to Schalk - will set up meeting with him, myself and Lee next week.
Assignee: nobody → sneethling
Is there anything blocking here? this bugs blocks one of our tef+ blockers so if there is anything we can do to help please let us know.
Blocks: 837219
(In reply to Vivien Nicolas (:vingtetun) (:21) from comment #17) > Is there anything blocking here? this bugs blocks one of our tef+ blockers > so if there is anything we can do to help please let us know. Nope, nothing blocking at the moment except other projects ;) Will be getting back on this by Friday and over the weekend. Not a lot of work, just need to make time for it and do it. Thanks for checking in.
(In reply to Vivien Nicolas (:vingtetun) (:21) from comment #17) > Is there anything blocking here? this bugs blocks one of our tef+ blockers > so if there is anything we can do to help please let us know. talking about blockers, what is the deadline for this?
(In reply to Schalk Neethling [:espressive] from comment #19) > (In reply to Vivien Nicolas (:vingtetun) (:21) from comment #17) > > Is there anything blocking here? this bugs blocks one of our tef+ blockers > > so if there is anything we can do to help please let us know. > > talking about blockers, what is the deadline for this? Next week :)
(In reply to Vivien Nicolas (:vingtetun) (:21) from comment #20) > (In reply to Schalk Neethling [:espressive] from comment #19) > > (In reply to Vivien Nicolas (:vingtetun) (:21) from comment #17) > > > Is there anything blocking here? this bugs blocks one of our tef+ blockers > > > so if there is anything we can do to help please let us know. > > > > talking about blockers, what is the deadline for this? > > Next week :) Vivien, so I just dropped a mail to Jishnu but, thought it would better to ask the question here. How would I go about testing this? I can use the dev tools to scale things down to the device width etc. and perhaps even use the simulator but, until it is on the device, you do not really know that all is good. The thing with this is, it will be part of bedrock, (the projects that drives mozilla.org) and will thus live on the web servers serving mozilla.org. When one taps on the privacy link on the device, I assume it needs to launch the browser inline (using the browser api or perhaps it is simpler) to display this. This means there is some device level interaction and, as I believe this is part of the FTU app, that needs to be defined and there needs to be a way to test not only opening the browser and going to the policy but also, a way for a user to get back. I do not believe there is a requirement for the user to accept the policy so, would a simple back do the trick. So, my biggest concern is that there is more to this them simply having an HTML page with the content but also, that their is some interaction on device level that needs to be integrated. How do you see this all coming together. Thanks!
I was just thinking abuot something else,if the privacy policy lives inside bedrock, one needs an internet connection to view it, what if the user does not have an internet connection at this point?
(In reply to Schalk Neethling [:espressive] from comment #22) > I was just thinking abuot something else,if the privacy policy lives inside > bedrock, one needs an internet connection to view it, what if the user does > not have an internet connection at this point? Known bug fixing in v2 - all after the policy goes up
(In reply to Schalk Neethling [:espressive] from comment #21) > (In reply to Vivien Nicolas (:vingtetun) (:21) from comment #20) > > (In reply to Schalk Neethling [:espressive] from comment #19) > > > (In reply to Vivien Nicolas (:vingtetun) (:21) from comment #17) > > > > Is there anything blocking here? this bugs blocks one of our tef+ blockers > > > > so if there is anything we can do to help please let us know. > > > > > > talking about blockers, what is the deadline for this? > > > > Next week :) > > Vivien, so I just dropped a mail to Jishnu but, thought it would better to > ask the question here. How would I go about testing this? I can use the dev > tools to scale things down to the device width etc. and perhaps even use the > simulator but, until it is on the device, you do not really know that all is > good. > > The thing with this is, it will be part of bedrock, (the projects that > drives mozilla.org) and will thus live on the web servers serving > mozilla.org. When one taps on the privacy link on the device, I assume it > needs to launch the browser inline (using the browser api or perhaps it is > simpler) to display this. > > This means there is some device level interaction and, as I believe this is > part of the FTU app, that needs to be defined and there needs to be a way to > test not only opening the browser and going to the policy but also, a way > for a user to get back. > > I do not believe there is a requirement for the user to accept the policy > so, would a simple back do the trick. > > So, my biggest concern is that there is more to this them simply having an > HTML page with the content but also, that their is some interaction on > device level that needs to be integrated. How do you see this all coming > together. Thanks! Let's get the site up with a back button implemented asap - this is why I've been asking for it so we can test and iterate
(In reply to Schalk Neethling [:espressive] from comment #21) > (In reply to Vivien Nicolas (:vingtetun) (:21) from comment #20) > > (In reply to Schalk Neethling [:espressive] from comment #19) > > > (In reply to Vivien Nicolas (:vingtetun) (:21) from comment #17) > > > > Is there anything blocking here? this bugs blocks one of our tef+ blockers > > > > so if there is anything we can do to help please let us know. > > > > > > talking about blockers, what is the deadline for this? > > > > Next week :) > > Vivien, so I just dropped a mail to Jishnu but, thought it would better to > ask the question here. How would I go about testing this? I can use the dev > tools to scale things down to the device width etc. and perhaps even use the > simulator but, until it is on the device, you do not really know that all is > good. > > The thing with this is, it will be part of bedrock, (the projects that > drives mozilla.org) and will thus live on the web servers serving > mozilla.org. When one taps on the privacy link on the device, I assume it > needs to launch the browser inline (using the browser api or perhaps it is > simpler) to display this. > > This means there is some device level interaction and, as I believe this is > part of the FTU app, that needs to be defined and there needs to be a way to > test not only opening the browser and going to the policy but also, a way > for a user to get back. > > I do not believe there is a requirement for the user to accept the policy > so, would a simple back do the trick. > > So, my biggest concern is that there is more to this them simply having an > HTML page with the content but also, that their is some interaction on > device level that needs to be integrated. How do you see this all coming > together. Thanks! That was already done in some other bugs, eg Bug 812956/Bug 834036/Bug 820000 for the First Time Interaction implementation. IIRC the Back button is implemented in the interaction implemented in FTU and Settings, so there is no need of a back button in the html page.
The Settings implementation just open the URL in the Browser app, so a back button in the page won't help either anyway. As for offline, we have a message in FTU that is displayed if we're offline, saying to the user that he can access this later from the Settings app. So let's just put a page in the website and let's close this.
works for me.
Jishnu, So in the design concept there are links to Choices and FAQ and then Contact. So, for the contact bit I am fine but, there does not seem to be any content for the Choices and FAQ, is this just a link to the privacy policy or does this need to link somewhere else?
Flags: needinfo?(jmenon)
If you have internal subpages, then we don't handle this right now in FTU, is that what comment 21 was about ? If yes then I'm deeply sorry I didn't understand that. Actually, I took care that the back button we have in FTU really go back to the previous page in FTU and not the previous page in the iframe. So either you don't have any subpages and navigation inside the policy page, and this is very simple, either you have subpages and we need a navigation system, either in the policy page, either in FTU.
Commit pushed to master at https://github.com/mozilla/bedrock https://github.com/mozilla/bedrock/commit/226c34b9ef5bf14fcd4a48a52e50576b9d5ad424 Bug 820212: Implement Firefox OS privacy policy for display on device.
I see the code has been merged, thanks a lot pmac however, I tried to access the page on dev, stage and the two demo servers (did not really expect to find it here) but it seems to not have been pushed yet. I tries both: https://www-dev.allizom.org/en-US/privacy/firefox-os/ and https://www-dev.allizom.org/en-US/privacy/policies/firefox-os/
Flags: needinfo?(jmenon)
Hi Schalk, Thank you for doing this in such short time and being able to balance it. I have a couple things: 1. The text is a bit off but likely because my diagram sucks. Here's what the top box should look like (note the we care sentence is in the second para). Firefox OS is an operating system for your mobile device made by Mozilla. We care about your privacy. When Firefox OS sends information to Mozilla, our [privacy policy] describes how we handle that information. [anchor link to “Mozilla Privacy Policy” below] 2. I LOVE how the privacy policy flies in from the side. Instead of the home icon, could we use something more like a back arrow? The text is a bit off on the bullets: 3. The top level bullets should be: Bullet 1: Firefox OS connects to services run by entities other than Mozilla in order to provide Firefox OS updates and location services. Bullet 2: The device you are using, like most mobile devices, is created by several parties. This notice only covers how Mozilla handles your information for official versions of Firefox OS authorized by Mozilla. 4. Under bullet 1 Bullet 1.1: Firefox OS automatically connects to your device's manufacturer to stay up to date. Bullet 1.2: When you ask Firefox OS to tell an app or site your location, Firefox OS uses various services to determine where you are. 5. Under bullet 1.1 Bullet 1.1.1: Mozilla will make available updates to the manufacturer of your device who may deliver those updates to you. You can disable automatic update checking in Settings on your device. 6. Under bullet 1.2 Bullet 1.2.1: When you turn location services on, Firefox OS may use multiple data points and entities to estimate your location, including GPS, AGPS and other geolocation service providers. You can disable location based services in the Firefox OS “Settings” app on your device. 5. Under bullet 2 Bullet 2.1: If you use apps made by someone other than Mozilla, their privacy policies will apply. Bullet 2.2: The dynamic app search feature of Firefox OS is powered by Everything.me and its privacy policy applies, which you can find at [http://corp.everything.me/ffos-privacy/]. [link] Also, could we visually separate the sub-bullets a bit more? maybe set them in a different cell with some visual separation? Someone from John's team should be contacting me about this project and I will loop them into this. Thanks Jishnu
One more thing - the title should be "Firefox OS Privacy"
(In reply to Schalk Neethling [:espressive] from comment #28) > Jishnu, > > So in the design concept there are links to Choices and FAQ and then > Contact. So, for the contact bit I am fine but, there does not seem to be > any content for the Choices and FAQ, is this just a link to the privacy > policy or does this need to link somewhere else? Sorry i didn't see this earlier - lets omit the FAQ link for this version per your design.
In production.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
(In reply to Jishnu Menon from comment #34) > Hi Schalk, > .... > 4. Under bullet 1 > > Bullet 1.1: Firefox OS automatically connects to your device's manufacturer > to stay up to date. > > Bullet 1.2: When you ask Firefox OS to tell an app or site your location, > Firefox OS uses various services to determine where you are. > > 5. Under bullet 1.1 > > Bullet 1.1.1: Mozilla will make available updates to the manufacturer of > your device who may deliver those updates to you. You can disable automatic ...... Hey Jishnu, I would not do sub bullets here as suggested above. We simply do not have enough space on the device especially in portrait view. I would suggest we have the in the right order but simply as for first level bullets. I will implement it as such in my PR and you can review and advice after.
(In reply to Jishnu Menon from comment #35) > One more thing - the title should be "Firefox OS Privacy" Sent pull request for request changes: https://github.com/mozilla/bedrock/pull/808 :pmac r?
I don't know if this is something that can be done easily now, but I think we could have less margin on small screens. The part 'things you should know' would love to have more width-space on my unagi. I can see the margin around the box + the padding inside the box, both could be either removed or made smaller.
(In reply to Julien Wajsberg [:julienw] from comment #40) > I don't know if this is something that can be done easily now, but I think > we could have less margin on small screens. The part 'things you should > know' would love to have more width-space on my unagi. I can see the margin > around the box + the padding inside the box, both could be either removed or > made smaller. Hey Julien, I have adjusted that a bit in my last PR, which has not been merged and pushed yet but, will play around with it a little more. Perhaps we can display the second and third boxes the same as the first highlighted section? That combined with less padding left and right will make a big difference.
Flags: needinfo?(jmenon)
Hi Schalk and Julien, Point taken - instead of indenting - can we try using a break between the lighter colored parts to indicate a subsection? Or perhaps a different color or font? I'm trying to get John Slater's team to help with design. Thanks Jishnu
Flags: needinfo?(jmenon)
Commit pushed to master at https://github.com/mozilla/bedrock https://github.com/mozilla/bedrock/commit/5b943d9c53d3dfe70044219718b87feaae054861 Bug 820212 implement copy changes and icon change based on feedback
Commits pushed to master at https://github.com/mozilla/bedrock https://github.com/mozilla/bedrock/commit/604e328a726a0beaada05743cefeeb3babf76260 Bug 820212 implement subtle styling to differentiate better between sub sections https://github.com/mozilla/bedrock/commit/c606dcba75a2d668af8e24616d7ba365050b02be Merge pull request #813 from ossreleasefeed/bug820212-additional-changes-to-policy-layout
Jishnu and Julien, Two new pull requests has been merged and will be pushed to DEV in the next 15 min or so, please have a look at the styling changes made and let me know your thoughts: https://www-dev.allizom.org/en-US/privacy/policies/firefox-os/
Schalk the layout looks bad see http://cl.ly/image/3T3T060M002R
(In reply to raymond [:retornam] from comment #46) > Schalk the layout looks bad see http://cl.ly/image/3T3T060M002R I mentioned that to him before and he is aware. Given the time crunch he was focusing on mobile first and then resolving the other sizes.
looks good enough to me in the mobile view (but I am not a designer ;) ) thanks !
(In reply to raymond [:retornam] from comment #46) > Schalk the layout looks bad see http://cl.ly/image/3T3T060M002R Hey Raymond, As Chris stated, this is aimed solely at on device display at the moment, I will iterate on it do get the desktop display looking good after we have sign of on mobile. In the end, the idea that this will never be viewed by someone on anything else but a Firefox OS device.
Hi Schalk, Thanks - looking good. A couple things: 1. Why are there two font sizes for the top content and bottom content? Could we harmonize? 2. Instead of seeing two back arrows for the "Mozilla Privacy Policy", I'm seeing two error boxes with "E75D" written in them - could this be just my browser? 3. I talked with John Slater today - I'm going to ask him for help on: a. designing a 3 level version of the "Things you should know" section -- trying to indicate each sub level in more ways than just through bullets b. thinking about ways to present the text from the "privacy policy" link in a more readable form c. I'd like to try and get the "Things you should know" to show up as soon as a user loads the page on a device so would like a couple ideas on how to do that from him as well. Is there anything else you think we could use design help with - I can't think of anyting? Thanks Jishnu
(In reply to Schalk Neethling [:espressive] from comment #49) > (In reply to raymond [:retornam] from comment #46) > > Schalk the layout looks bad see http://cl.ly/image/3T3T060M002R > > Hey Raymond, > > As Chris stated, this is aimed solely at on device display at the moment, I > will iterate on it do get the desktop display looking good after we have > sign of on mobile. In the end, the idea that this will never be viewed by > someone on anything else but a Firefox OS device. +1 we have a longer term goal of working on the responsive design - likely by end of June. We're also working on porting this design to all our privacy policies.
Jishnu, is the latest content for the FFOS policy ready or did you open a new bug for it?
Status: VERIFIED → RESOLVED
Closed: 12 years ago → 12 years ago
Flags: needinfo?(jmenon)
Hi Schalk - Thanks for bringing this up - this is not the final content or design - schalk has one more push (sorry Raymond). Here's the content for the top level page: Official Firefox OS Privacy [DATE] We care about your privacy. When Firefox OS sends information to Mozilla (that’s us), our [privacy policy] describes how we handle that information. Things you should know + Firefox OS connects to us and others in order to provide updates and location services. Learn more. ++ Updates: To keep itself up to date, Firefox OS automatically connects to a service operated by or on behalf of the manufacturer of your device. Firefox OS also automatically checks for updates to installed apps by sending a request to the Firefox Marketplace or, if you installed an app from another location, that app’s developer’s services. ++ Location: When you turn location services on, Firefox OS may use multiple data points and entities to estimate your location, including GPS, AGPS and other geolocation service providers. You can disable location services in the Firefox OS “Settings” app on your device. + The device you are using, like most mobile devices, is created by several parties. This notice only covers how Mozilla handles your information for official versions of Firefox OS authorized by Mozilla. Learn more. ++ If you use apps made by someone other than Mozilla, their privacy policies will apply. ++ The dynamic app search feature of Firefox OS is powered by Everything.me and its privacy policy applies, which you can find at [http://corp.everything.me/ffos-privacy/]. [link] [Privacy ask: doing a bunch of network communication with e.me] ++ Firefox OS allows you to use several integrated third party services, such as your email or social provider. The privacy policy of those services will apply to your use of them. [Contact] [link to contact form] | printable version
Status: RESOLVED → REOPENED
Flags: needinfo?(jmenon)
Resolution: FIXED → ---
Hi Schalk - Thanks for bringing this up - this is not the final content or design - schalk has one more push (sorry Raymond). Here's the content for the top level page: Official Firefox OS Privacy [DATE] We care about your privacy. When Firefox OS sends information to Mozilla (that’s us), our [privacy policy] describes how we handle that information. Things you should know + Firefox OS connects to us and others in order to provide updates and location services. Learn more. ++ Updates: To keep itself up to date, Firefox OS automatically connects to a service operated by or on behalf of the manufacturer of your device. Firefox OS also automatically checks for updates to installed apps by sending a request to the Firefox Marketplace or, if you installed an app from another location, that app’s developer’s services. ++ Location: When you turn location services on, Firefox OS may use multiple data points and entities to estimate your location, including GPS, AGPS and other geolocation service providers. You can disable location services in the Firefox OS “Settings” app on your device. + The device you are using, like most mobile devices, is created by several parties. This notice only covers how Mozilla handles your information for official versions of Firefox OS authorized by Mozilla. Learn more. ++ If you use apps made by someone other than Mozilla, their privacy policies will apply. ++ The dynamic app search feature of Firefox OS is powered by Everything.me and its privacy policy applies, which you can find at [http://corp.everything.me/ffos-privacy/]. [link] ++ Firefox OS allows you to use several integrated third party services, such as your email or social provider. The privacy policy of those services will apply to your use of them. [Contact] [link to contact form] | printable version
Please ignore comment 56
(In reply to Jishnu Menon from comment #57) > Hi Schalk - > > Thanks for bringing this up - this is not the final content or design - > schalk has one more push (sorry Raymond). > > Here's the content for the top level page: > > Official Firefox OS Privacy [DATE] > Jishnu, Changing the title from Firefox OS Policy to Official Firefox OS Policy is going to cause the 'Things you should know' to be pushed further down and reduce the chances of this being visible on first load as I know you want it to be. Does it *need* to contain the 'Official' string? IF it does, we should probably look at making the font of the header smaller.
Flags: needinfo?(jmenon)
Sent pull request: https://github.com/mozilla/bedrock/pull/845 Not this is only for the updated design and content changes. I will be opening a separate request to implement the printable version.
Commits pushed to master at https://github.com/mozilla/bedrock https://github.com/mozilla/bedrock/commit/3f5428351c93fb2438bd4105bf4369f0e62853dc Fix Bug 820212. Update design and content to latest https://github.com/mozilla/bedrock/commit/67c8cea8ec8de0fc89670a19fa5c3580f96ba953 Merge pull request #845 from ossreleasefeed/bug820212-update-design-and-content Fix Bug 820212. Update design and content to latest
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Flags: needinfo?(jmenon)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: