Closed Bug 844267 Opened 9 years ago Closed 9 years ago

Data Safety Review: Mozillians Profile Privacy Controls

Categories

(Data Compliance :: General, task)

task
Not set
normal

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: hoosteeno, Unassigned)

References

Details

We used the new project kickoff form to build bug 843870, but it wasn't able to create the blocking bugs. So I'm creating them manually.

Can you look at bug 843870 and advise whether data security review of this feature is necessary?
Summary: Mozillians Profile Privacy Controls → Data Safety Review: Mozillians Profile Privacy Controls
Hi, this project is chugging right along, and I wonder if anyone wants to chat with me or :williamr about its data safety implications prior to our anticipated launch at the end of the month?
Flags: needinfo?(sstamm)
The interface for privacy controls has landed on the dev server. This is just the interface: The backend code is not complete. In other words, you can't actually submit changes and have them be saved in the database or have them apply to viewers. However, I think the backend functionality is explained fairly well by the interface.

1) Here is the interface where users will edit their privacy settings. There are settings on several tabs:

https://mozillians-dev.allizom.org/en-US/user/edit

2) You'll also want to see the profile view interface; we added a dropdown there that lets users see their profile as if they were members of a particular group. To get there, click on your username at the top right and choose "View Profile".

Your feedback is welcome!
Flags: needinfo?(sstamm)
The new Mozillians privacy controls are in staging and tagged for a 3/28 release. 

https://mozillians.allizom.org/en-US/user/edit/
Stacy, can I close this bug? I believe our questions about personal data were addressed by bug 844269.
Flags: needinfo?(smartin)
Yes, you can close this one.  Data Safety is a category we are removing.
Flags: needinfo?(smartin)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Verified invalid per comment 5.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.