In T396945#10916431, @Niharika wrote:

In T396945#10915676, @kostajh wrote:

@KColeman-WMF @Niharika I filed this task based on T395212#10915463. What do you think?

I think it sounds fine. @MMoss_WMF any thoughts on this idea?

+1 to updating the preference text being the simplest solution and also still restricting who can use the API

In T395661#10905818, @JJMC89 wrote:

With limited exceptions (e.g., grammatical gender), user preferences are non-public information. Disclosing them publicly is a Vuln-Infoleak.

I took a look at this from Privacy-Legal and recommend blanking the field. Thank you!

We discussed this task in the TSP-Legal office hours and I said it was ok to proceed for privileged users (admins, CUs, etc.). Noting here for documentation.

Hi @gonyeahialam, apologies again for missing this. Since the responses will be aggregated, the responses should no longer be personally identifiable, so I still think it is best to avoid mentioning PII in the copy.

@ifried: apologies for my mistake! I think I intended something closer to "24 or under" but used the previous age buckets without altering enough. Changing to "under 25" would work!

@Htriedman and I were discussing the "What is your age?" answer ranges and were curious if it would be possible to combine the bottom two options to instead be "under 24"? Change illustrated below.

Per my earlier comment, I still recommend against saying "to view participant personal identifiable information" (reasons copied and pasted below)

A lot of good feedback has already been voiced, so I'll try and keep mine to what has not already been said.

@Nikerabbit It all looks great, thank you so much!

@Nikerabbit I just checked the target pages and the files here should still be good to go. Please let me know if there are issues when importing that I can help with, thank you for tackling this!

@Nikerabbit this is definitely not urgent and can wait until the fix goes out! The time aspect is if community translators start working fresh on these languages in the meantime, but I've been keeping an eye on that and can update these csv files as needed so we do not invalidate them