Mozzy Assistance

Skildring

Mozzy Assistance is a WordPress monitoring and maintenance assistant for people who want a safer way to look after a website. It connects WordPress to Mozzy, reports website health and software inventory, monitors supported application errors, and tracks backup and maintenance activity.

Mozzy can create a verified WordPress backup before selected plugin, theme, or core updates, apply those updates one at a time, and check the database, required files, installed versions, and inventory afterward. If a Mozzy-authorized protected update needs recovery, the verified pre-update archive can be used for automatic rollback. Normal WordPress automatic updates are not intercepted.

Backups are built on your website and kept in protected local storage. Optional off-site destinations include Google Drive backup, Backblaze B2, Amazon S3, Cloudflare R2, Wasabi, DigitalOcean Spaces, and other S3-compatible storage. Archives and destination credentials go directly between WordPress and your provider; they do not pass through Mozzy. Optional encrypted backups use a recovery key held by the WordPress site.

A Mozzy account is required for connected WordPress health monitoring and remote maintenance. Local backup, protected-update, and guided website recovery controls remain in WordPress.

Mozzy follows a practical workflow: Monitor -> Backup -> Update -> Verify -> Rollback.

Monitor Your WordPress Website

After connection, the plugin sends a health heartbeat every five minutes and software inventory twice daily. It provides a public endpoint that checks the connector and database, and reports versions, available updates, fatal PHP and database errors, failed email, and supported Action Scheduler failures. This focused WordPress health monitoring supports practical website monitoring and maintenance decisions.

Back Up Before Changes

Create manual or scheduled database and file backups using full, essential, or custom scopes. Every verified archive starts in protected local storage and can upload directly to Google Drive, Backblaze B2, or S3-compatible storage. Local schedules are daily or weekly; Mozzy-managed policies can also run monthly or quarterly and provide WordPress backup monitoring in Mozzy.

Optional encryption creates authenticated XChaCha20-Poly1305 MZB archives when PHP sodium is available. Recovery keys stay in WordPress and can be exported for offline storage.

Protected WordPress Updates

For safe WordPress updates, select pending plugin, theme, or core versions. Mozzy Assistance first verifies a new full safety backup and every connected remote upload, then applies approved versions one at a time. Maintenance Autopilot lets an authorized Mozzy user approve exact versions; it does not provide a remote shell or arbitrary file editor.

Verify After Updating

Mozzy Assistance confirms installed versions, checks database access and required WordPress files, and refreshes inventory. These are focused workflow checks, not a general security, SEO, performance, or visual regression scan.

Automatic Rollback and Recovery

If verification fails during Mozzy-managed maintenance, Mozzy can request WordPress rollback using the exact verified pre-update archive. WordPress validates it and creates a failed-state safety backup first. Administrators can also confirm a guided restore of a verified same-site local or recovered remote archive. Restores run in background batches and finish with database and filesystem checks.

WordPress Maintenance From Mozzy

WordPress performs the backup, update, verification, and recovery work. Mozzy receives health, inventory, and supported maintenance status so an authorized user can monitor the site and approve limited commands. Nothing is sent until an administrator connects the site or saves a connector token. The connection can be paused or disconnected.

External services

Mozzy

After administrator connection, the plugin contacts https://mozzy.au to provide monitoring, inventory, managed backup status, and maintenance progress. Authenticated responses can include backup policies/requests, inventory requests, exact-version maintenance, or rollback commands. Mozzy does not receive archives, destination credentials, or recovery keys.

Privacy: https://mozzy.au/privacy
Terms: https://mozzy.au/terms

Google Drive

After an administrator saves OAuth credentials and connects Drive, the plugin uses accounts.google.com, oauth2.googleapis.com, and www.googleapis.com. OAuth data, tokens, archives, filenames, sizes, checksums, and folder metadata go directly to Google as needed to store, list, download, and delete plugin-created backups.

Privacy: https://policies.google.com/privacy
Terms: https://policies.google.com/terms

Backblaze B2 and S3-compatible storage

After an administrator saves an HTTPS endpoint and credentials, the plugin sends signed S3 requests, the access-key identifier, archives, filenames, sizes, checksums, and storage metadata directly to that provider. The secret is stored encrypted in WordPress and used locally to sign requests. No provider is contacted merely by activating the plugin or viewing settings.

Provider policies: Backblaze privacy and terms; AWS privacy and terms; Cloudflare privacy and terms; Wasabi privacy and terms; DigitalOcean privacy and terms.

Privacy

When connected, data sent to Mozzy can include health heartbeats; WordPress/PHP versions; theme and plugin names, slugs, versions, active state, and available versions; fatal error messages, file locations, line numbers, and affected URL; database errors; managed backup state, progress, filename, size, purpose, destinations, and errors; maintenance identifiers, progress, results, and backup filenames; failed email; and supported scheduled-task failures.

Mozzy does not intentionally receive passwords, cookies, form contents, database records, WordPress users, visitor IPs, backup archives, storage credentials, or recovery keys. Review https://mozzy.au/privacy and https://mozzy.au/terms before connecting.