Talk:Privacy Policy

From Meta
Jump to: navigation, search

Email between users[edit source]

@Labster: What do you think of this? This should be placed after the current "email communications" text, in the same section.


In addition to the above automated messages sent by the Services, users with verified email addresses may wish to communicate with each other. By default, if you have a verified email address other users may use the EmailUser Special page (hereafter "EmailUser functionality") to send messages to other users. When you do this, the message you send will include a header and footer created by the Services, the text you choose to send, and a from address of your verified email address. You will not know the target users email unless they reply, in which case communications may continue by email. If you reply to anyone's sent emails, they will see your email. Under your user preferences there is an option called "Enable email from other users," unchecking this will disable the EmailUser functionality, but you will still receive emails generated by the Services.


-- Cheers, NDKilla ( TalkContribs ) 16:28, 26 September 2016 (UTC)

@Labster: I updated the page because I didn't realize functionality was changed to make EmailUser messages appear as 'from' noreply at miraheze.org but it can still reveal your email address. -- Cheers, NDKilla ( TalkContribs ) 00:38, 27 September 2016 (UTC)
@NDKilla: Cool thanks bro, but the point of this is not to describe specific functionality, but explain the ways in which private data can become not-private data. Implementation details should not be in the language spec. ...Uh wait this is not Perl 6. I mean, legal code should not describe the process, but the results. Labster (talk) 08:14, 27 September 2016 (UTC)
@Labster: Alright, I'm good with it as is. I dunno if I was tired or what but I just realized that (unlike my text above) you didn't say it was 'from' your email address, but that it includes your email address :p I just wanted to be clear that the message isn't coming directly from a user to you (or vice/versa) and I guess that is :) -- Cheers, NDKilla ( TalkContribs ) 13:58, 27 September 2016 (UTC)

Compare with other policies[edit source]

How does this policy compare with other policies out there? RobertSter (talk) 17:07, 26 September 2016 (UTC)

  • @RobertSter: Compared to ShoutWiki? "User information is stored on servers in the state of Chicago, USA." I'd say pretty well. Actually their policy is pretty terrible, as it has sections like this: "ShoutWiki wikis are provided "as is". ShoutWiki has no responsibility for lack of availability of any wiki or of any particular content. You should be aware that the wikis are editable by the public, and, as such, may contain inappropriate content at any time." That's ToS territory and has zero to do with privacy.
And then there's Wikia's privacy policy: "We utilize the Krux platform and cookies to store Non-PII regarding our users. Krux uses a number of technologies, in addition to cookies, to collect Non-PII data based on its analysis of your interaction with our sites and to select advertisements or content to provide to you." It's in some ways shorter, a little less specific and uh, this:
Wikia only shares your information with others in the following circumstances:
2. With our subsidiaries and affiliated companies, contractors, and vendors. We require these parties to process your information in compliance with this policy.
I'm pretty sure that this clause is recursive. Labster (talk) 19:55, 27 September 2016 (UTC)

How are the volunteers vetted[edit source]

You mention:

"Miraheze personnel and a small number of vetted volunteers have access to content on private wikis as part of their role in assisting to provide our Services."

MacFan4000 (talk) 17:41, 9 December 2016 (UTC)

Everyone in the global Steward group or the global sysadmin group can access private wikis. Although this should probably be at Meta talk:Privacy policy/Draft. -- Cheers, NDKilla ( TalkContribs ) 17:59, 9 December 2016 (UTC)

  • Well, not anymore, this is now the correct talk page. Anyway, we don't have a lot of process for vetting here -- the current process is more or less "we all knew each other from other wikis/wiki farms, and we seemed like good chaps with some technical knowledge." There's no explicit NDAs with regards to private data, but this could change. On the other hand anyone leaking private data will end up out of Miraheze pretty quickly, as we take privacy seriously.
Right now Stewards are an even more exclusive group than sysadmins. I expect that they'll have to be approved by the community, as well as by existing Stewards. We'll be looking for people who had a long history in a sysop or bureaucrat role, who are generally known to have served with distinction.
Personnel at this point means sysadmins (and me, a programmer and pretend sysadmin). In the future it could expand to include other technical support, but also community support. This could be community help, outreach, legal support, etc. These people will be approved by the Miraheze board -- which again, right now, are the syadmins. We're a very technical-heavy group right now. Future personnel may or may not get access to personal information, depending on our needs.
Right now there are no plans to expand either of these groups, but we'll keep you informed. Labster (talk) 08:33, 12 December 2016 (UTC)

Policy template[edit source]

Can we add the policy template to the top? MacFan4000 (talk) 20:20, 10 December 2016 (UTC)

Ping @ admins. MacFan4000 (talk) 13:39, 11 December 2016 (UTC)

A well-drafted policy[edit source]

Just read through the privacy policy. It gets to the point a lot quicker than other privacy policies so great work to all those involved in drafting this policy. Borderman  talk | contribs | email 13:44, 11 December 2016 (UTC)

@Borderman: You really need to thank Philip Neustrom of localwiki.org for letting us use the privacy policy from his wiki. He had some lawyers help to draft it, but he graciously licensed it CC-0 so we could reuse it. Obviously I've made some alterations for our use and our software, but it is mostly the same. The core values of our wiki farms are very much the same, it's just they're much more focused on geographic communities. Labster (talk) 08:15, 12 December 2016 (UTC)

translations[edit source]

I have prepared a translatable version of this policy here. Could it be implemented? MacFan4000 (talk) 13:53, 29 August 2017 (UTC)

Since these policies are sensitive, we need to have a clear message that the translation does not represent the official policy and if there are any discrepancies between languages English is always the correct version, like here. Reception123 (talk) (contribs) 17:14, 29 August 2017 (UTC)
Yes check.svg Added a note MacFan4000 (talk) 17:53, 29 August 2017 (UTC)
That's good, but personally I don't like the fact that it's also mentioned on the English version, and it feels pointless to me. I'm not sure if it can only be done for translate pages, but I'd prefer it that way. Reception123 (talk) (contribs) 17:56, 29 August 2017 (UTC)
I altered it a bit. MacFan4000 (talk) 21:20, 9 September 2017 (UTC)