• Mos, if not all, of the better features of this plugin should simply be rolled into WordPress itself. They bait you with certain features that require them to have access to your site’s complete traffic details. Whatever happened to the good ole days before my data was someone else’s big business and when open source software was designed for the end user, and not as an enticement to open up my data to someone else.

Viewing 1 replies (of 1 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    Thanks for the feedback!

    Most of the Jetpack features make use of the WordPress.com infrastructure. Things like Stats, Related Posts, Spellchecking, or Subscriptions are things that you could obviously run on your own server, but that wouldn’t be without consequences for your server’s performance, and for the performance of these features. Jetpack aims to take the burden off your server, and have WordPress.com do the heavy work for you. That’s why some of your site’s data is stored on WordPress.com. No worries though, it is safe! You an find out more about our privacy policy here:
    https://automattic.com/privacy/

    Some of the features, on the other hand, do not require a connection to WordPress.com. When appropriate, we propose that these features be included in WordPress Core. One of the most recent examples is the Site Icon module, that is now part of Core!

    All that said, if you’d like to use Jetpack and don’t have the need for any of the features that require a connection to WordPress.com, you can use Jetpack’s Development Mode, and none of your data will be shared with WordPress.com.

    I hope this clarified things a bit.

Viewing 1 replies (of 1 total)
  • The topic ‘Hello heavy plugin, goodbye privacy’ is closed to new replies.