Opened 6 years ago

Closed 3 years ago

#3660 closed enhancement (fixed) and Rosetta privacy pages mentions WordCamp Central’s DPO instead of

Reported by: audrasjb's profile audrasjb Owned by: tellyworth's profile tellyworth
Milestone: Priority: normal
Component: General Keywords: has-patch


URL: and on all Rosetta websites.

At the bottom of the page:

Please contact us if you have any questions about our privacy policy or information we hold about you by emailing dpo@….

I guess the email address should be a generic dpo@… or privacy@… for better understanding since DPO is an english and not universally understandable term.


Attachments (1)

3660.diff (1.4 KB) - added by audrasjb 6 years ago.
Replace dpo@… email with privacy@… email

Download all attachments as: .zip

Change History (13)

#1 @obenland
6 years ago

  • Owner set to tellyworth
  • Status changed from new to assigned

6 years ago

Replace dpo@… email with privacy@… email

#2 @audrasjb
6 years ago

  • Keywords has-patch added; needs-patch removed

#3 @Otto42
6 years ago

At present, this is intentionally set to dpo@… because that is a current and valid email address. Since shares logins with (as well as,, etc), then it's basically the same system.

Making an additional email address and forwarder is possible, but it would simply forward to the same people.

#4 follow-up: @SergeyBiryukov
6 years ago

Creating a alias makes sense to me.

This ticket was mentioned in Slack in #meta by obenland. View the logs.

6 years ago

#6 @ocean90
5 years ago

#4215 was marked as a duplicate.

#7 @ocean90
5 years ago

  • Component changed from International Sites (Rosetta) to General
  • Type changed from defect to enhancement

#8 in reply to: ↑ 4 @garrett-eclipse
5 years ago

Replying to SergeyBiryukov:

Creating a alias makes sense to me.

I agree setting up an alias makes the most sense to me and would remove any confusion or concerns an end-user would have seeing a privacy email that's not under the same domain as the one they're raising a concern with.
Note: I've seen this question, as to why an email is being used, raised a few times now in #core-privacy.

Also looking at @audrasjb's patch 3660.diff I wonder if we protect the email address by removing it from the translation string with a printf.

This ticket was mentioned in Slack in #core-privacy by webdevlaw. View the logs.

5 years ago

This ticket was mentioned in Slack in #meta by garrett-eclipse. View the logs.

4 years ago

#11 @dd32
3 years ago

@tellyworth is the new dpo@… email setup in HelpScout yet?

Also noting for this patch / when the texts are updated, we should use a %s placeholder to ensure that it doesn't get translated/altered.

#12 @dd32
3 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

In 10676:

Privacy Policy: Update the DPO email to dpo@….

Props audrasjb, garrett-eclipse, dd32.
Fixes #3660.

Note: See TracTickets for help on using tickets.