GDimitrov

MegaManager Connector allows you to connect your WordPress site to the <a href="https://wpmegamanager.com" rel="nofollow ugc">MegaManager</a> platform for:
<ul>
<li>Real-time Monitoring – Keep track of your site’s health and uptime status</li>
<li>Automated Backups – Schedule and manage full-site cloud backups</li>
<li>Remote Updates – Update plugins, themes, and WordPress core remotely</li>
<li>Cache Management – Clear page, object, and OPcache directly from admin bar or dashboard</li>
<li>Plugin Management – Activate and deactivate plugins from the dashboard</li>
<li>Security – Secure communication with HMAC signatures</li>
<li>Database Optimization – Analyze and optimize database tables remotely</li>
<li>Maintenance Mode – Enable/disable maintenance mode without writing files</li>
</ul>
<h3>External Services</h3>
This plugin connects to the MegaManager platform API to provide remote site management features. The service is hosted at <code>https://wpmegamanager.com/api/fn</code>.
What data is sent and when:
<ul>
<li>Site Registration (on connect): Your site URL, WordPress version, PHP version, and a generated site secret are sent once when you connect the plugin to MegaManager.</li>
<li>Heartbeat (every 5 minutes while connected): Site ID, WordPress version, PHP version, and site URL are sent to confirm your site is online and reachable. The heartbeat is essential for the connection status feature and runs automatically while the plugin is connected. It does NOT send any content, user data, or analytics — only basic environment identifiers.</li>
<li>Metrics (hourly, opt-in only): When you enable telemetry in the plugin settings, performance data (TTFB, page size, plugin list, theme, PHP/WP versions, disk/database size, activity logs) is sent hourly. This is disabled by default and requires explicit opt-in via the Settings > MegaManager page. You can disable it at any time; the setting takes effect immediately.</li>
<li>Backup operations: During cloud backups, your database and wp-content files are uploaded to MegaManager cloud storage via signed URLs.</li>
</ul>
No data is sent until you explicitly connect the plugin by entering a Connect Token from the MegaManager dashboard.
<ul>
<li>Terms of Service: <a href="https://wpmegamanager.com/terms" rel="nofollow ugc">https://wpmegamanager.com/terms</a></li>
<li>Privacy Policy: <a href="https://wpmegamanager.com/privacy" rel="nofollow ugc">https://wpmegamanager.com/privacy</a></li>
</ul>

MegaManager Connector

Connects your WordPress site to MegaManager for monitoring, backups, cache management, and remote administration.

Rocketa

PatchOn is a solution for safely updating the plugins, themes, and core of your WordPress site. Before applying an update to production, it reproduces your site’s configuration in a staging environment, applies the update there, and runs a screenshot comparison (Visual Regression Test) to check for any problems. This plugin acts as the connector between your WordPress site and PatchOn.
This plugin requires the PatchOn service (<a href="https://patchon.jp/" rel="nofollow ugc">patchon.jp</a>) and does not function on its own. No account is required to get started. Immediately after activation it performs no external communication, and a consent screen is shown in the admin area. Outbound communication with PatchOn begins only after the user explicitly clicks the “Agree and Start” button on that consent screen, which registers the site anonymously. A PatchOn account is needed only to view detailed inspection results in the dashboard or to upgrade to a paid plan.
<h4>Main Features</h4>
<ul>
<li>Pre-inspection that simulates updates in a staging environment, with results displayed in your dashboard</li>
<li>Backup of site files and database before applying updates</li>
<li>Production rollout of updates that have passed inspection</li>
</ul>
This plugin (the free distribution on WordPress.org) does not write to your site files (<code>wp-content</code>, <code>mu-plugins</code>, theme directories, etc.), even when it detects a problem. AI auto-repair, which writes patched code to <code>mu-plugins</code> or the active child theme, is provided by the separately distributed PatchOn Agent Pro extension plugin (available to PatchOn Standard / Business plan subscribers).
<h4>Data Sent</h4>
After the user has consented on the consent screen, when they run a “Pre-inspection” or “Apply update” operation, the plugin sends the following data to PatchOn and related external services. See the <a href="https://patchon.jp/privacy-policy" rel="nofollow ugc">Privacy Policy</a> for details.
<ul>
<li>Site URL / WordPress version / PHP version / DB version</li>
<li>List and versions of installed plugins, themes, and MU plugins</li>
<li>Site files prior to update application (child theme / mu-plugins / wp-config.php, used for backup)</li>
<li>Contents of WordPress debug.log (used to detect issues)</li>
<li>Lightweight database dump (only at pre-inspection time; tables and columns containing personal information are excluded)</li>
</ul>
<h3>External services</h3>
This plugin depends on the following external services. No external communication is performed merely by activating the plugin. Communication starts only after the user explicitly clicks the “Agree and Start” button on the consent screen shown on first use.
<h4>PatchOn API (https://patchon.jp and its subdomains)</h4>
The backend for all inspection, repair, update, and database-dump operations. Two host names are used, both operated by Rocketa Inc. and routed to PatchOn’s infrastructure:
<ul>
<li><code>https://patchon.jp/api/*</code> — site registration, pre-inspection control, apply-update control, billing</li>
<li><code>https://dump.patchon.jp/*</code> — database-dump control endpoints and signed-URL chunk uploads used during pre-inspection (the database dump is excluded from the data sent over <code>patchon.jp/api/*</code>)</li>
</ul>
Provider: Rocketa Inc. (rocketa.co.jp)
When data is sent:
<ul>
<li>On click of the “Agree and Start” consent button (one-time): anonymous site registration and UUID issuance</li>
<li>When the user runs a “Pre-inspection”: list of plugins / themes, debug.log, lightweight database dump</li>
<li>When the user runs an “Apply update”: backup files, application result</li>
</ul>
What is sent: see the “Data Sent” section above
<ul>
<li>Terms of Service: https://patchon.jp/terms</li>
<li>Privacy Policy: https://patchon.jp/privacy-policy</li>
<li>Subprocessors: https://patchon.jp/subprocessors</li>
</ul>
<h4>AWS S3 (Tokyo region, accessed via PatchOn)</h4>
Storage destination for the pre-update full-site backup (tar.gz). File uploads are performed only against pre-signed URLs issued by <code>https://patchon.jp/api/*</code> on a per-request basis. The customer site does not hold any S3 credentials.
<ul>
<li>Provider: Amazon Web Services, Inc.</li>
<li>Endpoint: https://*.s3.ap-northeast-1.amazonaws.com (pre-signed URLs only)</li>
<li>When data is sent: when the user runs an “Apply update”</li>
<li>What is sent: pre-update site files (tar.gz)</li>
<li>AWS Privacy: https://aws.amazon.com/privacy/</li>
</ul>

PatchOn Agent

Connector plugin that securely links your site to the PatchOn AI automated update verification service.

MegaManager Connector vs PatchOn Agent