Docs / Safety
The tool limits access, verifies important backups, reports incomplete work, and gives you recovery controls.
Your FTP or SFTP password is encrypted with AES-256-GCM. The encrypted vault can exist in the server-side session, while the key needed to unlock it stays in a Secure, HttpOnly browser cookie. The password is not stored in readable form or written to application logs. Disconnecting or session expiry destroys the vault and key.
Choose SFTP or encrypted FTPS when your host supports it. If encrypted FTPS cannot be established, the tool now stops instead of silently falling back to plain FTP. Plain FTP is used only when you explicitly turn encryption off, and the interface warns that the password will be sent unencrypted.
The service does not retain a copy of your website. Selected files pass through memory when required for diagnosis, verification, repair, plugin replacement, or an on-site snapshot. Snapshot copies and repair backups are written to your own server.
Before supported file replacements, the tool writes an on-site backup and verifies its contents. Recovery records are also verified. If an undo step fails, its record remains so you can retry instead of losing the recovery path.
FTP permissions, connection interruptions, file-size limits, and server time limits can prevent work from completing. The tool reports partial snapshots and stops automatic repair when the safety copy is incomplete. A staged plugin replacement is not activated until its complete upload succeeds.
Some actions are inherently different from file restoration. The optional emergency-admin action creates or promotes the account you request through WordPress, which changes the WordPress database. Its temporary helper file is tracked for removal, but removing the helper does not remove the user account.