Moderator
t-p
(@t-p)
Please Contact:
– Plugin Review Team can be reached by email at plugins@wordpress.org, or via the #pluginreview channel on Slack. You’ll need to join that channel.
– Theme Review Team can be reached at #themereview channel on Slack. You’ll need to join that channel. Ask slackbot “How do I join a channel.” – themes@wordpress.org
-
This reply was modified 7 years, 11 months ago by
t-p.
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
the 7 point of developer’s guidelines, it’s about the prohibition of make call towards external server.
Without asking for user opt-in: YES.
Please contact the emails t-p listed with the details.
@t-p, thanks, i’ve already tried to contact WP, but not with these addresses. Many thanks for answer.
@jdembowski, yes i mean without the user’s consent. Many thanks for answer.
Some times i’ve adviced about this the authors, but seems they dosen’t understand the rule (my english could be the problem), they are convinced about this:
If they dosen’t collect data
directly, it’s ok instal third part
profiling cookie or cdn without know which data are collect and for wich purpose.
Probably they ignore that do it, these third part profiling cookie or cdn, are setted by tutorial video, social widget ecc… in the backend.
—
I really appreciate the developer’s work, i’m developer too, i know how much work there are behind themes and plugins. But ignore this rule expose the site owner (that trust in the guidelines rules) to important fine for privacy issue. Especially in Europe.
-
This reply was modified 7 years, 11 months ago by
Paride15.
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
It’s tricky and complicated.
For example: if I write a plugin and it
- Collects data
- Sends it to my server or some other server used by me
- Does this by default and doesn’t let the user (the WordPress site owner) know or opt-in
Then I’m really doing something wrong. The plugin guidelines is very clear about that.
If my plugin
- turns all of that off by default
- informs the site owner clearly what data is being collected
- why it’s being collected
- how long it’s retained
- Permits collection to stop at any time
Then that could be fine for a plugin. The WordPress site owner can turn that on and off as desired and is educated before they do enable that data collection.
Social media plugins are where it gets complicated. If the plugin is an interface to Facebook, Twitter, etc. then that becomes messy. The plugin author doesn’t necessarily know what those services are gathering.
*Drinks coffee*
Like I wrote, it’s complicated. 😛
I’m starting to understand the 7 point. The social media question is really hard, probally i would ban the social media embeed in plugin, if that won’t ask consent. But it’s just my opinion.
Thanks for answer and your informations Jan